Basically, I haven't built out the Description script, I was more interested in having the execution do what I was looking to do.
Here is a screen capture of the part of the test that will move the change request forward...update the timer...
The script that I wrote inside of the Test "Update Change Request Scheduled Job..." to execute the timer activity on the workflow is the following, and it only needs the sys_id of the change request form as the input to query its way thru tables to get to the correct sys_trigger table. There are no outputs. The step just updates the timer for 2 minutes past the time it gets when the step runs and then the step sleeps for 2 minutes to allow the trigger job to actually run.
(function executeStep(inputs, outputs, stepResult, timeout) {
var cntxID = '';
var wfVerID = '';
var actvID = '';
var execID = '';
var nextAction = 'No';
//----Get Current Date Time
var gdt = new GlideDateTime();
var schdt = new GlideDateTime();
gdt.addSeconds(-10680); //Convert Time to Central + 2 minutes
//---------------------------------
var wfcontext = new GlideRecord('wf_context');
wfcontext.addQuery('id', inputs.u_request);
wfcontext.query();
if (wfcontext.next()) {
cntxID = wfcontext.sys_id;
wfVerID = wfcontext.workflow_version;
}
var wfactivity = new GlideRecord('wf_activity');
wfactivity.addQuery('name', 'Wait for CR Planned Start Date');
wfactivity.addQuery('workflow_version.sys_id', wfVerID);
wfactivity.query();
if (wfactivity.next()) {
actvID = wfactivity.sys_id;
}
if (cntxID != '') {
var wfexec = new GlideRecord('wf_executing');
wfexec.addQuery('context.sys_id', cntxID);
wfexec.addQuery('activity', actvID);
wfexec.query();
if (wfexec.next()) {
execID = wfexec.sys_id;
}
}
if (execID != '') {
var sched = new GlideRecord('sys_trigger');
sched.addQuery('document_key', execID);
sched.query();
if (sched.next()) {
schdt = sched.next_action;
sched.next_action = gdt;
nextAction = 'Yes';
sched.update();
}
}
gs.sleep('120000'); //2 Minutes
if (nextAction == 'Yes') {
stepResult.setSuccess();
stepResult.setOutputMessage = "Original Planned Start of " + schdt + " changed to " + gdt;
} else {
stepResult.setFailed();
}
}(inputs, outputs, stepResult, timeout));
I believe that tables that extend from Task (Incident, Problem, Change, Request etc...) can use Task as the referenced Table. Maybe sc_req_item is able to be used also, not sure as I haven't tried, but that does limit the usage of that step only to Requested Items if it does work.
This might be your issue, as I am not sure what your WF's Activities Name would be... This could also be an input variable too I would think. "Wait for CR Planned Start Date" is the Timer Activity Name for my test and I'm sure isn't the same for the Activity your are looking for.
In regards to the datetime addition of seconds...This is a tricky part and I always need to log values via gs.info to see what the values are. If I remember right 10800 is 3 hours (3600 seconds is 1 hour) and based on the date that it gave without any manipulation, the date I needed was 3 hours earlier but I needed to subtact 2 minutes which is 120 seconds...So basically I logged the datetime that "var gdt = new GlideDateTime();" was so I could determine what the raw date was getting set as.
10800-120 =10680. This calc may be off, but it worked for me, so I think I am close.
Let me know if this helps!
