Hello,
We have a workflow scenario, where a data change request goes to the approver, but the approver has to also be able to make additional changes to the submitted data before the final approval.This workflow will be used in a UI5 application.
The standard behaviour in such applications (and workflows) give the approver options to accept, reject and send the form back for corrections. In our scenario however, we need to have a 'Change' button, which give us the option to change the data ourselves by directing us to another screen for example, and approve the request afterwards.
So here's the problem - if we use a decision step for this kind of approval, then the 'Change' button would essentially be the same action as 'send back for corrections', only the receiver would be the approver. In that case, the approver would get another workflow task in their inbox and again another one when the data is changed.
We'd like to handle this more elegantly and be able to somehow handle changing of data in between receiving the workflow task and approving the changed data.
Would a regular activity task be able to handle this kind of behaviour? So that the application buttons would be linked to the activity step outcomes?
Another thing we have discussed is adding the 'Change' button to the workflow task in UI5 (so in the application side) and have this functionality separate from the workflow. However, this also raises the question of how this changed data would get into our workflow, because the decision step's container cannot be changed when the step has been sent out.
I would be very happy to hear your thoughts and ideas about this issue.
Regards,
Maia-Lii