Flow designer overwrites field with an old value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2023 07:18 PM
I created a catalog item that uses Workflow and flow designer at the same time. My process is upon submitting a form the workflow will call the flow designer to create multiple tasks along with approvers with “Approval Required” as the task’s short description. Once approval record is approved the task short description will be updated to Approved.
My issue: the flow is updating the short description to “Approved”. Then 5-10 seconds later is gets overwritten with the old value “Approval Required”. I could mains why this is happening!!
I would appreciate any help the community will give. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2023 05:57 AM - edited 09-10-2023 05:58 AM
Hi veeco,
So is this the process? Catalog item submitted > Workflow begins > Workflow calls Flow > Flow creates Tasks initially with "Approval Required" in the short description > Once (RITM approval) approved > Tasks' short description updated to "Approved"
If the above steps are correct:
How many approvals are there?
How many tasks are we talking about?
Is there a reason why you are creating the tasks before an approval is actually approved? You might avoid this issue completely if you wait to create the tasks only if the request if approved.
When the short description changes back to "Approval Required", is that happening on all the tasks or just one? Since it is happening about 5-10 seconds after update, I'd suspect a business rule might be causing it (or another flow).
Have you queried other BRs or Flows?
You might try using Script Tracer to see if that helps, especially if you can reproduce the issue yourself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2023 08:20 AM
Approvals and tasks number depends on how many values the end-user selects of the form. Also, it’s happening to all created tasks under that request.
I created approvals after tasks because each task will have an approval record associated with it that has “Approval Required” before moving forward. So that everything will be under one RITM.
i tried using a script tracer but couldn’t find a solution! FYI. The unwanted update get recorded on audit table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2023 01:38 PM
The tasks would still be under one RITM if created after the approvals but nonetheless since this is all customized functionality, try performing a filter on the sys_update_xml table for Payload contains "Approval Required". This should return anything customized referencing "Approval Required" and investigate any business rules or flows included in the results.