Copying parent job properties to the child

Question

I am nesting a WMX job within another job using the CreateJobAdvanced custom step so that I can create the job version using the original job version as the parent.  I would also like to pass on some properties of the parent job to the child such as job name or job description.  Currently I am not too concerned with copying extend properties but rather just the basic job properties.  I have found some old questions regarding this but nothing recent.

Thanks in advance for your help.

SachinChand · Answer

This is a bit off topic but what is the difference between the "JTXDesktopSteps.CreateJobAdvanced" step and the "JTXSteps.CreateJob" step?

We had WMX running with parallel steps in our job workflows (and appropriate user queries to see their assigned steps).  We just upgraded to v10.6 (from v10.2) and see that the step assignment has been depreciated.  Now our user step queries are useless (in job workflows with parallel steps) and we see no way to continue to run parallel job workflow steps (please correct me if I'm wrong).  Therefore, we have decided to generate spin-off jobs to remove the parallel steps.  My original question is to that end, however, I'm also curious how users migrated from the step assignments to path assignments when there are parallel steps.

CharlesMcNeel · Answer

Meggie,

They are two different workflows so clone is out.

I could put the information in an extended table, we just had not used that functionality so far.  I would then, of course, need to add that to the workflow.  So far the description has been enough and has served us well.  I have already set up a test workflow that uses the Create job advanced step and saw that extended properties could be copied but first thought I would pose the question to avoid the addition of the table and setup of extended properties.  I will explore this more and may use the extended properties and take that opportunity to add other properties as well.

Thanks for your help.

Charles

XiaomengZheng · Answer

Hi, Charles,

Does your event edits job share the same workflow as the LRS job? If it's a different workflow, clone will not work. Clone can only create child job with same job type as parent. Will it be do-able if you can put the information in the extended property of parent job and that can be copied over to the child job via running Create Job Advanced step?

More details on how to configure "Create Job advanced" step can be found:

https://pro.arcgis.com/en/pro-app/help/workflow-manager/step-templates.htm

Thanks,

Meggie