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

[Ray Ennis]

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:

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

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.

[Brad Tilton]

I just realized I tested in a London instance, so it could be something that was fixed in London. Do you have access to a London developer instance where you could test?

[Ray Ennis]

Yeppers... I'm sure I can change/update my personal instance to London.

Lemme check.

This will be interesting.

[Ray Ennis]

So I finally got my personal instance up to London.

Went in to duplicate my test in Flow Designer.

...and found out that for some odd reason the Flow Designer will not allow me to choose the "sc_task" table in the trigger portion.

I thought perhaps that London for some-odd reason, split up or otherwise modified the sc_task table, but I was able to confirm the table exists in Reports.

Any suggestions?

p.s. I am about to try another test using what you did, the Problem/Incident part (verses the Catalog Request/Task).

[Ray Ennis]

I just finished duplicating the process (in London) to have any updates to the Work Notes in Incidents, if there is a related Problem, to transfer the Work Notes to the Problem Ticket.

Works as intended (i.e. it works and shows in the Problem Work Notes what I originally wrote in the Incident).

No joy when attempting to do a similar process with Catalog Requests/Tasks.

[Brad Tilton · 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-...