nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WFM Unique identifier

nipper

OK, should be simple

in the command line, you invoke OD with something like -inst $$ which includes the process ID. What is the equivalent function in WFM ? Can I take a prepopulated variable like $IW_SESSION ?

Find more posts tagged with

Comments

Adam Stoller

OK, should be simple

in the command line, you invoke OD with something like -inst $$ which includes the process ID. What is the equivalent function in WFM ? Can I take a prepopulated variable like $IW_SESSION ?

You're talking about using a Deploy Task with the OOTB deployment class?
I thought it set the inst flag itself, if not, you might need to create your own custom deployment class (extending DeployURLExternalTask) ... I thought there was a thread or two that went into more detail about this, but I cannot seem to find them with the "wonderful" devnet search right now.

nipper

No, I do not need that. We have a DNR that uses $taskID in the command string (as a unique identifier).

I agree your approach is the"typical" TS approach

Adam Stoller

No, I do not need that. We have a DNR that uses $taskID in the command string (as a unique identifier).

I agree your approach is the"typical" TS approach

I'm confused - where do you need the unique id?

nipper

OK Linux 7.2.1

Use the OOTB OpenDeploy, where $taskID is passed as a -k

The deploy script runs a DNR using that variable (the deployment itself does not use the variable), so it is not using -inst, I just used that as an example.

Adam Stoller

OK Linux 7.2.1

Use the OOTB OpenDeploy, where $taskID is passed as a -k

The deploy script runs a DNR using that variable (the deployment itself does not use the variable), so it is not using -inst, I just used that as an example.

If you're just looking for a unique value - then you're DNR script should be able to do that on it's own (using either the value of $$ or some time-related value or a combination of the two).
If you're looking explicitly for the jobid or taskid - I think you're back to either writing your own deployment class or put in place your own externaltask [Perl] script to initiate the deployment - both of which would allow you to get a handle on the jobid and/or taskid to use however you want.

worries

nipper there is deploy task variablecan able help you out. you need to set it before to get unique deployment name every time
the variable name is "odDeploymentInst" set this as task variable with job id and now you are able to get unique deployment name.

Adam Stoller

nipper there is deploy task variablecan able help you out. you need to set it before to get unique deployment name every time
the variable name is "odDeploymentInst" set this as task variable with job id and now you are able to get unique deployment name.

How does one set odDeploymentInst, which is defined within the Workflow Model, with the jobid value, which doesn't exist until the model has been compiled and the job instantiated? The only way I can think of to do it is:

And you'd still have to be able to access the variable within the configuration file so that you can pass it to the DNR script (which I believe is the objective here) - or, what I indicated in my previous response.

worries

[QUOTE=ghoti]How does one set odDeploymentInst, which is defined within the Workflow Model, with the jobid value, which doesn't exist until the model has been compiled and the job instantiated? The only way I can think of to do it is:

Yes ghoti, what you had said is correct i didn't elaborated it.we need to right a code(external task) which will set the task variable after job initiation in order to get the unique name for every deployment.