- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2022 10:43 AM
I have a Flow with Record Updated as Trigger has actions to go in and the update State property of related Tasks but the related Tasks states are not being updated and I am not sure why
In the example below I am getting the Parent Task from the Catalog Task Trigger and attempting to set the State of the Parent Task record to the State selected in the Catalog Task when it is updated.
Solved! Go to Solution.
- Labels:
-
flow designer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2022 09:21 AM
The default behaviour, when creating a Catalog task, is to have the Flow wait for it's completion before continue the process to the next action.
It should look like this:
Did you disable the waiting of the completing of the Catalog task?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2022 01:43 PM
Hi Jeremy,
Did you try to configure all the update actions in the main flow which is used for parent task(Catalog Item)?
Thanks,
Raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2022 05:30 AM
Yes, I tried this but being so new to ServiceNow Flow Designer, I could not build it in a way to make the Flow wait for action to be taken on Catalog Task before attempting to update the Request and Request Item.
Besides that, I am not sure what is wrong with my flow.
The problem I have is that I am trying to use the Catalog Task State field value to map to the Request and Request Item State field values upon record update of the Catalog Task and even though those values have the exact same Label and option value as the Catalog Task state it is not properly assigning the values to the REQ and RITM records. If I explicitly set the value for each of the State fields of the related records it works fine, but I don't want to have to do that for every flow I use in the future.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2022 03:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2022 05:25 AM
I am not doing it this way because the Task is immediately evaluated and always returns False as the State is Open when it is created so the Request and Request Item are never closed. The Workflow does not wait for a change in the Catalog Task. Am I missing something about your example?