Sometimes a user will accidentally select an action that completes a workflow (such as selecting "Disapprove" instead of "Approve". When this happens and the workflow has ended, there is currently nothing that can be done to fix this. The best we can do right now is to start a new instance of the workflow and have it go back up the approval chain, which is unacceptable to our users. It would be very helpful if there were a way to to "reinstate" a workflow at the prior step.

We have much Problems to build Workflows as good as in 4.7. We used line rules and predeceding rules in nearly every workflow. For example when you had 4 check boxes and a Task for every check box which should only run when the Checkbox is clicked. We had massavie Problems to rebuild this easy.

I think it would be great, if you could add a logic per split line or descicion oder add more than one IF THEN in one logic

Currently when an activity encounters errors, workflow only offers two options ("continue on error" or "log exception"). There is no way to handle the exception gracefully within the workflow self (e.g. retry x number of times then create a human task if retry doesn't resolve the issue). it will be great if activity level exception can be caught right at that activity and allow designers to build a specific exception handling for that activity.

Currently our 4.7 legacy workflows have a line of code which increases the priority of a running workflow instance when an escalation is triggered.

Without this ability to automatically increase priority to red we will find it hard to replace our existing workflows with K2 Five.

In previous versions of K2, it was possible to load an HTML template in the Email wizard and then edit the raw HTML in the wizard. However, I didn't see this feature in K2 5.3; here is a related community post: https://community.k2.com/t5/K2-Five/HTML-in-Email/m-p/102701

Please consider adding this feature back in K2 Five. Thanks!

Workflow doesn't have capability to handling error message has been throw by SmartObject

Hello K2 Folks,

The SMART ACTIONS are extremely helpful for users and processes that doesn't required to open the form to make decisions.

I see a possibility for the same to be deployed in Workflow Reminders as well. This could help users/processes to make sure decisions are made on time which could potentially benefit the Business functions and minimize time delay.

The activity system name still has a large importance in many places: GoTo Activity, Worklist. In K2 Five, I cannot edit the activity System Name, which is really bad for such situations. It is not even displayed somewhere easily accessible,

Ideally the system name should be editable, At least the display name should be usable in the worklist.

In K2 4.7 and before, you were able to decide the action outcomes and you could select update, instead of finished. We are using this a save function in most of our workflows, as the user might still have to collect data before filling up all the data on the workflow and then sending it to the next user for approval, completion, etc.

Currently, this does not exist in K2 Five and it a major problem for us.

We need the possibility, to add roles as destination for a Mail Event in K2 Five.

In 4.7 this was possible and I was able to drag and drop a role into the field.

In K2 Five, we can choose for a Task destination if it is a user, group or role.

It would be very nice, if the same mechanic would accessable for the destination in Mail events.

By clicking on taskitems in a viewflow a new tab with detailed information for the task opens. This is a very nice feature. But it would be nice to get the most important information without open a new tab/page. To get the most important information a small Infobox could be a nice feature which appears with the mouseover event. Have a look to the attached example.

Would be great if any workflow event had another tab that could evaluate a condition as to whether it would be executed or not. Hence, I could have an activity with 10 events. And based on a condition from a smartobject or process data field all or only some of the events would executed. This would be an event condition for execution. In 4.7 we used to jumper out events by going into the code behind to achieve a similar functionality.

When you enter Management > Workflow Server > Workflows, the list is sorted ascending by date. It would be more convenient to have it initially sorted by Start Date, descending.

Additionally, acting on a workflow instance (like clicking Retry) sorts the list back to the initial sort state, and if you've done a sort, you're forced to re-sort to see your workflows in the list again. Persist the sorting after taking action on a workflow.

| Any new enhancement implemented in K2 will take effect only for requests raised after deployment of the changes. So the old requests which haven't closed yet will have the old flow and the new requests raised will pass through the updated flow. This will cause confusion for the users, if we want the changes to take effect for all the outstanding requests, how do we do this? |