Hi,This is the Scenario which i am trying using BPT :
There are two users in the system.
The first user can either:
Move the request directly to Approved, which assigns it to User 2.
Move the request first to On-Hold and later to Approved.
The table should reflect both statuses: On-Hold first and then Approved when the same user updates it later.
But while doing i am facing issue like when User 1 initially updates the request to On-Hold, the status is correctly saved in the table. However, when the same user later updates the request to Approved, the process is stuck at a Human Activity Wait for Approval instead of proceeding further.and also there is an Activity Wait ID in the table, and i am not sure whether it is affecting the update process and preventing it to update second time the same record to other status. Please anyone do suggest me for this ? Note:This is for o11 not ODC .
Hi,
You can refer below forum discussion.
https://www.outsystems.com/forums/discussion/66933/bpt-is-there-another-way-to-terminate-or-skip-an-activity-inside-of-it/
If it is not helping, kindly share your OML file. I can give you the solution after analysing the code.
Thanks,
Sriyamini J
@Rakhi Bhadauria : Can you please share the screen shot of your Process ? It would help us better understand the workflow and how the implementation is done.
Hi Siya, Implantation screenshot i can' t share but I will let you know about the scenario which i am trying to do but its failing with error that this ACTIVITY ALREADY BEING CLOSED. So its like, we are calling human activity manually from a button click of approver and sending its approval action as rejected, approved or onhold. Now same user has to make the request on hold for 1st time and 2nd time same user again work on this and changed it to approved it but when 2nd time when same user trying to take action on that its throwing error mentioned above. Please let me help out if any solution for this.
Hi @Rakhi Bhadauria
In your scenario, you seem to be having this workflow:
But since BPT does not allow a Human Activity instance to be “reused”, once a Human Activity is completed, that instance is closed permanently. So,
This could be the reason why the process gets stuck on Activity Wait since you are trying to close something that is already closed instead of creating the next activity.