This forum allows users to post and respond to "How Do I Do ....." questions. The information contained in this forum has not been validated by K-Rise Systems and, as such, K-Rise Systems cannot guarantee the accuracy of the information.
In EASYProcess 5.1 Classic/MVC we are unable to edit workflow status descriptions.
image.png (22.76 KiB) Viewed 2017 times
image.png (22.76 KiB) Viewed 2017 times
when statuses are multiple words, to be a valid status name in easyprocess, we take special characters out and spaces. So "Tech Dev" becomes "TechDev". That part isnt a big deal, but then when we want to display it on application pages to show history or info useful to the end users, we have to do one of the following solutions to display it:
Leave it with no spaces. It doesnt look the best, but its the easiest
Have a developer made db table to store the desired description for each status. join to that and show that field (extra work)
hard code it in the query that retrieves from the workflow table to say CASE WHEN VALUE = 'TechDev' THEN 'Tech Dev' (bad to hard code)
REQUEST 1: Can the [workflow_statuses] table description field be exposed to be edited in the workflow canvas so the description field can be the one shown to end users with special characters and spaces?
REQUEST 2: Can Workflow Status Names and Status Exits be changed to allow underscores their names?
REQUEST 3: Can Workflow status exits also have a description field where we put the readable name to show to end users?
Last edited by CathyC on May 3rd, 2023, 11:08 am, edited 1 time in total. word count: 229
discussed with internal team. underscores are not allowed in page name, so to be consistent with that, underscores are not allowed. So REQUEST 2 is no longer needed.
However, we found a bug which needs a task. We tested and underscores are allowed in services when you first try and create one. but when you edit they are no longer allowed. if you try and change it the underscore is automatically removed. So that should be fixed to be consistent
BUG: RESOLVED. I just tested the bug described and that is fixed now. When creating services, they do not allow the underscore to be in the name. When editing, it still doesnt allow underscored.
I have opened a task (#11510) for the below requests REQUEST 1: Can the [workflow_statuses] table description field be exposed to be edited in the workflow canvas so the description field can be the one shown to end users with special characters and spaces? REQUEST 3: Can Workflow status exits also have a description field where we put the readable name to show to end users?
Translation