I am really struggling with the CMDB Health Simulator Configure Remediation - Task 13. I do not understand how to create the workflow to be executed from an Orphan Task.

Bux
Tera Contributor

I am trying to complete the CMDB Fundamentals On Demand course.  The last task on the CMDB Simulator is to:

Create, configure, and publish a workflow using the following information:

*workflow name is "Remediate Orphan WF"

*workflow can be executed from an orphan task

*workflow, when executed, writes to the short description field of the orphan task the following: Workflow launched for task number [actual task number of orphan rule].

I have created a workflow and named it "Remediate Orphan WF".  I have 2 boxes on the canvas, Begin and End.  I do not understand which boxes I need to add to the canvas or how this workflow will even begin.  Do I need to create some kind of scripts?  The video lesson on the CMDB Fundamental On Demand was over my head.  It started off with the canvas already created and was for remediating Stale CIs.  I've tried reading the How to create Workflows and I keep going down rabbit holes.  It says drag the activity to the canvas.  I don't see any activity that will Execute from a task or write some task number into the Short Description field on the Orphan page.  I'm not a Dev/Ops guy, I'm a project manager who is taking this on demand class while I've been off work.  I would really like to finish this last task and be done with this.  

My email address is rbuxmann@cox.net.  I would really appreciate if someone can talk me through this please.

Regards.

Rob Buxmann

 

1 ACCEPTED SOLUTION

glenn_pinto
ServiceNow Employee
ServiceNow Employee

For the script you don't need to refer to orphan_ci_remediation as current translates to the current table from the record making the initial call to the wf. In the demo, we had to dot walk to the CI record's ip address from the incident table and thus we had a slightly different syntax. The following should suffice.

workflow.scratchpad.number = current.number; 

 

We provided AUS01-EXCH as a sample record that you can test with which should be there, but if you can't locate it, run the test from any other orphan task record and you should get the same result. 

View the demo video when it explains the set values activity on the proper syntax to write literal text plus the specific orphan number back to the orphan task record.

Hope this helps.

 

 

View solution in original post

119 REPLIES 119

JGC
Tera Contributor

Please disregard, I was able to find this and it is also set to true already but still no data for my Orphan CIs

glenn_pinto
ServiceNow Employee
ServiceNow Employee

For the script you don't need to refer to orphan_ci_remediation as current translates to the current table from the record making the initial call to the wf. In the demo, we had to dot walk to the CI record's ip address from the incident table and thus we had a slightly different syntax. The following should suffice.

workflow.scratchpad.number = current.number; 

 

We provided AUS01-EXCH as a sample record that you can test with which should be there, but if you can't locate it, run the test from any other orphan task record and you should get the same result. 

View the demo video when it explains the set values activity on the proper syntax to write literal text plus the specific orphan number back to the orphan task record.

Hope this helps.

 

 

Bux
Tera Contributor

Hello Glenn, I contacted a coworker who knows jova scripting and works with Servicenow.  He provided the same script that you have posted and it worked for me.  Thank you for your time and input.  Regards.  Rob

I had a silly issue and it took me a while to figure it out.

The default workflow condition was none, when I changed it "Run the workflow always" it did what it was supposed to.

Great help, thanks