Implement the display name of the workflow instance

[hyzx86]

Currently, the display name of our workflow instance directly uses the instance Id, which is very unfriendly to users

I tried to implement this in my project, but found that there was no extension field Properties in WorkflowType

Can we make WorkflowType inherit from 'Entity' and only need one change to achieve unlimited expansion? It should be great.

In the figure below, I added a last execution time with the extended information for the workflow instance.

For the process title, however, it should be a user-defined expression, like 'TitilePart', or specified directly by the script node.

[hyzx86]

related : #14275

[MikeAlhayek]

@hyzx86 adding Entity to the WorflowType sounds like a reasonable request. However, what user friendly name would you choose here? If there is a better idea that the ID, maybe it is something that we can bring into OC.

[hyzx86]

I am trying to do a user-driven workflow that contains a to-do list, for example the process instance name that the user will see will be shown as
{workflowName}-{CaseID}-{RequestorName}

[MikeAlhayek]

I see. Maybe a PR with new option on the workflow that a user can change. By default it would be something like this {{ Workflow.Id }}

[hyzx86]

I see. Maybe a PR with new option on the workflow that a user can change. By default it would be something like this {{ Workflow.Id }}

Yes, it is.
I'll also add some other fields, such as the user/role that can initiate the workflow
But these are less applicable to the current OC

[MikeAlhayek]

I would say configurable title is something we can bring to OC. Not sure other field will. If you are using Liquid, you can freely access any property from the workflow and other things like HttpContext. If you need custom data like roles or fields, maybe access the HttpContext.User via liquid.

Feel free to submit a new PR to change the title. I don't think this will be a problem

[sebastienros]

I would suggest to add the title template property to WorkflowType directly, and not use Entity for that.