Hi Experts,
I've created a leave workflow which is copy of std leave request workflow and have included the same that is the custom workflow id in the configuration.
In our case, once the leave request is applied, in the custom workflow in the approval task we've passed LV_USER_ID in the Agent assignment. This container is a multiline element, and may contain more that one portal user id's.
Hence once the leave is applied, it'll be visible in the UWL of one or more approvers according to the custom functionality that has been designed.
Now, after the leave has been applied, we try to change the leave request, which is still in SENT status only.
We are able to change say the dates, and the revised dates are even reflected in the overview of the initiator on portal.
But in the backend, when we see the workflow log, no new workflow instance has been triggered.
In addition to this, the previous workflow instance itself reflects the revised dates in the REQ.ITEMS_TAB.ATTS table (fields BEGDA ENDDA).
But the issue is, the request is no longer visible in the other approver's queue. It vanishes from there.
Though it stays in the queue of only one approver, and after investigation it's observed that this approver is nothing but the one in the REQ.N_PROCESSOR.USER container.
How is the workflow container altered when the SENT leave request is changed from the portal?
And why does it disappear from the other approver's queue?
Pls help.
Regards,
Pranita