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; } } }

Jobid in workflow

kelvin_p

Hi ,
jobid and taskid is automatically pass to externaltask but is there a way for get the jobid in main workflow?

thanks.
Best Regards,
Kelvin

Find more posts tagged with

Comments

Adam Stoller

Hi ,
jobid and taskid is automatically pass to externaltask but is there a way for get the jobid in main workflow?

thanks.
Best Regards,
Kelvin

What do you mean by "main workflow"?

If you mean in the WFT or WFM itself - no - because the jobid doesn't exist until after the WFT or WFM gets instantiated, at which point its too late for it to be incorporated into the WFT or WFM.

If you mean something else, please elaborate.

kelvin_p

Hi ghoti,
Yes, I mean in wft itself. I would like to query who is involve in the whole workflow chain and send a email notification only to those who involve before end the workflow. it can be done in externaltask, just try to figure out if it can be done in wft.

Best Regards,
Kelvin

Migrateduser

My head hurts from reading this last statement.

ISCBorisB

Hi ghoti,
Yes, I mean in wft itself. I would like to query who is involve in the whole workflow chain and send a email notification only to those who involve before end the workflow. it can be done in externaltask, just try to figure out if it can be done in wft.

Best Regards,
Kelvin

As has been already noted by Ghoti, wft generates WF specs for subsequent Job instantiation.
There is no way to reliably predict the future - even seconds ahead Smiley Sad

You simply can not
know within wft code what Jobid will be assigned to the Job Object.

That said, it is certainly possible to send some sort of bulk notifications from wft. There are few
caveats (like the fact that wft is evaluated twice) to consider but it is certainly doable. Before
getting there however - why don't you send your notifications as the very first task of your Workflow?

Sending time difference is negligible comparing to sending from WFT, you'll have your Job Id, you seem
to know how to do that through external Task, etc...

Rick Poulin

Before
getting there however - why don't you send your notifications as the very first task of your Workflow?

I read the query as "I want to notify everybody that has been involved (owners of group tasks and not the whole shared by) that my job has now successfully completed". If that's the case, you'll have to roll your own external/URL task to compile that list.

Adam Stoller

I read the query as "I want to notify everybody that has been involved (owners of group tasks and not the whole shared by) that my job has now successfully completed". If that's the case, you'll have to roll your own external/URL task to compile that list.

To expand a tad bit on the above (which was generally my thought) -

send a email notification only to those who involve before end the workflow

What you do is add an external task just prior to the end task of the workflow - the external task would be responsible for determining the complete list of users who took part in the workflow (removing duplications) and then invoking some sort of program to send all of them email - and then transition to the end task.
This is generally considered custom code (though you may be able to utilize some of the OOTB code) - and as such it is up to you (kelvin_p) to write the code.