Help with Flow designer code (autoassign "assigned to" field)

[cicgordy]

Hi all,

I have a few subflows and I need to add a code in flow designer, within the "assigned to" field code snippet when creating a "catalog task action" (image below)

I need to auto-assign the same person that user would assign this particular task to, to subsequent tasks that creates after in other subflows(so perhaps by using short description name of other tasks).

So I guess I will need to add a code into subsequent tasks "assigned to fields" where I will need to copy same person assigned for previous task. 

Anyone can help in writing this code? 

Many thanks

[Allen Andreas]

Hello,

If these tasks are sequential, meaning they aren't all issued at the same time, but instead one after the other and the flow waits for each one to finish/complete, then...after each create task action, you have access to those pills on the right-hand side. When creating tasks after the 1st, you can access those create task actions (so the settings/configuration for each) and drag the prior task's "assigned to" pill and set it to that new tasks assigned to field. All without code.

[cicgordy]

Hi @Allen Andreas, 

Yes thats right, I'd have done the same if I only had one flow.

Because I have different tasks in different subflows, I won't be able to drag the "assigned to" pill from a subflow to another, hence I thought I needed to code in each "assigned to" fields of the tasks needed.  

[Allen Andreas]

Hi,

My apologies that my reply wasn't helpful, I didn't see the subflow part in your script. If possible, feel free to add more information to your post in the future such as what you've tried thus far, etc. Just to help us help you.

Moving on...you'd want to use script then to query for related records and order them by their number (newest to oldest). Example of a GlideRecord query here: https://developer.servicenow.com/dev.do#!/reference/api/rome/server_legacy/c_GlideRecordAPI#r_GlideR... 

var gr = new GlideRecord('sc_task');
gr.addQuery('request_item', 'request_item_value_here');
gr.orderByDesc('number');
gr.query();
if (gr.next()) {
return gr.assigned_to;
}

The above is just an example, but that is what you could use and you'd want to replace the "request_item_value_here" with the sys_id from the RITM record. So if you have access to that, you should, you can walk to it like: fd_data. and right after pressing the . you'll see the guide pop-up to help you walk to that RITM sys_id value.

[cicgordy]

@Allen Andreas is it possible to achieve this by querying the "short description name" of the tasks I want to auto-populate the "assign to"? Because not all the tasks are creating after another, I may have to skip some.