Currently, when you create a process and initiate an instance, the user is prompted to name the instance, presumably as some way they can remember it in their own jumble of process instances (or tickets, as I like to call them).
I would like the admin to have the ability of eliminating that need on a per-process basis, and instead automatically naming the instance with the instance ID. This should give people the flexibility, if they want, to allow the user to create a memorable moniker, or allow it to traditionally take on a "ticket number" type of designation.
It really depends on the environment that the workflow is being used in. In a high-volume workplace, it may be best to use a ticketing style of identification. In a smaller-volume workplace, I can definitely see how custom names would be beneficial.
If I get time, I'll work on this.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |