schedule a task without using OD

workflow modeler version 1.0.0.1

does anyone know if there is a way to schedule the execution of a task without using opendeploy?

i want to know if there is a way to specifically deploy on a schedule, but also, might need to be able to schedule the execution of a user task.

thanks.

Find more posts tagged with

Comments

Pawan

workflow modeler version 1.0.0.1

does anyone know if there is a way to schedule the execution of a task without using opendeploy?

i want to know if there is a way to specifically deploy on a schedule, but also, might need to be able to schedule the execution of a user task.

thanks.

Do you want to schedule a deployment without using the OD?
You can use a dummy task for this.

edwang

the dummy task allows for the absolute or relative delay from the time of execution. but what if i know that i want it to run at the next occurrence of a certain time of day, or day of month, etc.

for example, if i want the task to run at the next 12:00AM, no matter what day it is.

is there a way to configure, or assign the "absolute" date from within the workflow, as the workflow is being executed?

or is the only way to assign that value through the modeler?

or is there possibly another solution?

-e

moonkhanna

the dummy task allows for the absolute or relative delay from the time of execution. but what if i know that i want it to run at the next occurrence of a certain time of day, or day of month, etc.

for example, if i want the task to run at the next 12:00AM, no matter what day it is.

is there a way to configure, or assign the "absolute" date from within the workflow, as the workflow is being executed?

or is the only way to assign that value through the modeler?

or is there possibly another solution?

-e

This can be accomplished using script variables pretty much easily

Adam Stoller

the dummy task allows for the absolute or relative delay from the time of execution. but what if i know that i want it to run at the next occurrence of a certain time of day, or day of month, etc.

for example, if i want the task to run at the next 12:00AM, no matter what day it is.

is there a way to configure, or assign the "absolute" date from within the workflow, as the workflow is being executed?

or is the only way to assign that value through the modeler?

or is there possibly another solution?

-e

You mean you want the next task to run on the next 12:00 AM when this task gets activated?
You can do this - but I believe it requires an additional task.
If you put an externaltask prior to the dummytask, the externaltask can determine when the next 12:00AM is (either relative or absolute) and use that information to programmatically change the timeout value of the dummytask before transitioning to it.

Now - you may need to figure out the relative time between now and then in seconds (I don't know if it's still that way, but I believe back in 5.5.2 the value provided for SetTimeout was based in seconds)

You might be able to do the whole thing with an externaltask (and no dummytask) as you might be able to alter the timeout of the externaltask during the externaltask itself (while it's active) - but the "safe" and supported way would have the externaltask precede the dummytask and alter the timeout on the dummytask.

ISCBorisB

back in 5.5.2 the value provided for SetTimeout was based in seconds

Not any more. Allowed Formats are MMDDYYYYHHMM or +HHHHMM. (Modern TeamSite::WFtask: Smiley Frustrated

etTimeout is actually just a
wrapper for iwsettasktimeout CLT Command). I do not know if Date Format changes for locales that differ from the US ("Day First" European Style and the like)

edwang

thanks for the help everyone.

ghoti, yes, you understood the problem correctly.

what i really needed to do was to figure out a way to programatically set the "timeout duration" attribute of a timeout link.

as it turns out, as moonkhanna pointed out, i was able to use a script variable and write some javascript that output a time in one of the formats that ISCBorisB indicated.

the solution was sufficient, although, i don't know if it was the BEST way to do it.

anyway, now i have a solution. but if anyone has a better way to do it, i'd be interested in hearing about it.

thanks again.

ISCBorisB

thanks for the help everyone.

ghoti, yes, you understood the problem correctly.

what i really needed to do was to figure out a way to programatically set the "timeout duration" attribute of a timeout link.

as it turns out, as moonkhanna pointed out, i was able to use a script variable and write some javascript that output a time in one of the formats that ISCBorisB indicated.

the solution was sufficient, although, i don't know if it was the BEST way to do it.

anyway, now i have a solution. but if anyone has a better way to do it, i'd be interested in hearing about it.

thanks again.

Re-read Ghoti's post one more time. The best way by far to do this sort of things is to code an External task
right before Dummy Task and re-calculate / re-set Timeout on the fly.

Javascript is actually a wrong way to do it. Upfront you have no way of knowing when the flow will reach your dummy task.
Therefore with JS approach you can use only absolute date/time which a) may be too late on the actual execution and
b) does not cover (possible) flow looping back and such