Updating Request 'Work Notes' from Task (using Flow Designer)

Ray Ennis
Tera Expert

We're now in Kingston and while I have been fairly successful with past attempts using Flow Designer; I am stumped trying to make this work the way I intend for it to work.

I am wanting the 'Work Notes' from a Requests' various Tasks to also update the Requests' Work notes.

a working example:
Technician receives a Task to install software; does the work, updates the Tasks' Work Notes with their activity and Closes the Task.
Then the 'Flow Designer' rule, sensing an update to the Catalog Task, will update the parent Catalog Request.

In the Flow Designer my 'Action' flow is as follows:

find_real_file.png

With a result (using the "Test" feature) is as follows:

find_real_file.png

So my first 'work notes' works (not want I wanted... but it works).

However my second (my goal) is not working and only shows the glideobject comment.

Any suggestions?

Past research on how to get past this shows using a business rule with a script... however it appears (at least I haven't found it) that one is unable to plug in Scripts in ones' Flow Designer rule.

 

1 ACCEPTED SOLUTION

I just tried and couldn't trigger a flow from sc_req_item or sc_task, which I'm guessing has to do with the added flow designer/service catalog functionality that came out in London.

https://docs.servicenow.com/bundle/london-release-notes/page/release-notes/servicenow-platform/flow-...

View solution in original post

14 REPLIES 14

Brad Tilton
ServiceNow Employee
ServiceNow Employee

What if you do everything in the same field setter? I tried to replicate this and found that when I tried just setting the work notes once, the work notes copied over correctly. However, when I added another field setter for work notes I ended up with some strange behavior. 

I initially used only one field.

My example showed two fields so I could include what was working and what wasn't.

Can you screen-shot what worked for you?

The goal is to include the entered text (into the Task-related Work Notes) to be automatically copied to the Request-related Work Notes.

Sure, I ran mine as Incident > Problem but the relationship should be the same. I did one real world test and then another using the test feature of the flow designer and they behaved the same.

find_real_file.png

find_real_file.png

Odd... just in case your test Problem/Incident was different from my test Request/Task I duplicated your actions in my Dev Instance with a Problem/Incident.

...and got the same response (i.e. it failed for me)

find_real_file.png

I wonder now if it is a plug-in or setting?

(Thank you for testing this for me.)