Hello
I have a requirement where I'm having to dynamically create sc_tasks in a wf activity run script and now a new requirement came in about sequencing these tasks.
I've never worked with execution plans and I am wondering if I need to change from having the sc_req_item be workflow-based or part of an execution plan. I have heard that execution plans have been deprecated in favor of workflows.
Background:
I am doing an Integration between a 3rd party system and ServiceNow.
I have created a "scripted web service" that uses the CART api to dynamically create the sc_request and sc_req_item and does a bunch of other things like setting values in variables and creating the requested_for (user record) if it does not already exist.
There are two custom fields on their Software Asset Mgmt (SAM) table where one is type = list (e.g. watch list) and second is yes/no. On the List field (provisioning groups) it can contain an empty value or many provisioning groups (upward of 10-15) listed for each SAM record.
At first there was no task ordering/sequencing requirement and for every group in the list, just create a sc_task with the related group becoming the assignment group. I have this working now. One group, one sc_task, 13 groups, 13 sc_tasks.
The new requirement now wants to deal with sequencing and has provided the business rules/logic for what the sequencing needs to be.
I have been searching quite a bit on this and saw an old post on SN Guru where Mark had a few options on how to do this (kind of) with execution plans.
I will past the code I have where I do this without the ordering/sequencing part, but am struggling to find a way to do this. It has been suggested to try the "create task" workflow activity but I'm having a hard time to figure out how to deal with the randomness of it being one or many tasks that need to be created based on how many groups are in the provisioning groups field on the SAM record.
Any idea's or suggestions would be appreciated.
Thanks,
-Erik
// WF Run script to create stasks for IDM Access requests.
//Grab the SAM record from the variable pool of the item.
var samRecSysID = current.variable_pool.sam_record.sys_id;
var samGR = new GlideRecord('cmdb_ci_spkg'); //Base Software Table
samGR.addQuery('sys_id', samRecSysID);
samGR.query();
if (samGR.next()) {
var list = samGR.u_idm_access_support_groups.getDisplayValue();
var array = list.split(",");
// for each support group we need to create a unique task and assign the group to it.
for(var i=0; i< array.length; i++) {
var ag = array[i].replace(/^\s+|\s+$/g, ""); //remove leading space after split() for every loop after the first one.
createStask(ag);
}
}
// write some code here to set the sc_req_item.order value to help with the sequencing of sc_tasks...???
function createStask(Assignmentgroup) {
// start task creation
var taskGR = new GlideRecord('sc_task');
taskGR.initialize();
taskGR.request_item = current.sys_id;
taskGR.short_description = current.short_description;
taskGR.u_details = current.u_details;
taskGR.u_due_date = current.u_due_date;
taskGR.u_op_tier_1 = 'Allocate'; // Temp, need to verify req's
taskGR.u_op_tier_2 = 'Space'; // Temp, need to verify req's
taskGR.assignment_group.setDisplayValue(Assignmentgroup);
taskGR.insert();
}
