hi @Lindsay Estabrooks please can any one assist me . how do i use below macro in change management wf. macro::upd val("cr wf", format("cr = '%s' AND sequence IN (20, 30)", cr.persistent id), // search over other tasks in the same parent request with seq 20, 30 1, 0, // delays "status", ...
Following the approach that I suggested, you would need 3 macros. First you need to identify an unused OOTB (out-of-the-box) attribute in the ticket object to use or add a custom attribute to the ticket object using the schema designer. Then you need 3 macros for the workflow object: An...
@Lindsay Estabrooks Can you tell me the Action macro according to your idea. Need your help.
@Lindsay Estabrooks Please can you tell me the action macro using your idea.
It is not so simple to reference the attributes of another object instance when there is no direct relationship. In this case the only common attribute of the two workflow task instances is that they reference the same ticket object (so the two workflow tasks are indirectly related). If you want...
thanks @Lindsay Estabrooks for the great idea. I'am thinking a macro something like this in my change workflow .Need your help as well. 1. if task "SYST" (wf.status = "APP") 2. set task "UATM" (wf.status = "PEND") 3. else 4. set task "UATM" (wf.status = "SKIP") here, "SYST" is a task code....
Obviously, to accomplish what you want, the three tasks can no longer be parallel. I would design this so that the first task had included a special " complete " status that had a behavior and action that set an attribute in the ticket to a value to indicate that the second task is needed/not...
Hello, I'am using a Classic workflow in a parallel form and i want to skip a task. In my environment there are 3 task (task 1, task 2 and task 3) in a group and everyone gets the notification at the same time.My requirement is that I want to skip task 2 . when task 1 gets the notification he...
Hello, we always use a sub-workflow for such dependencies. All jobs which should skip are in this sub-workflow and the sub-workflow check the status of the first job. Regards, Bernhard