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

Moving to next task in custom Java code

System

Anybody know what are the possible ways to move to the next task in your custom Java class? The two ways I know would be to either know what the name of the Flow (transition) where you can use the transistionTo method. The other way I know is to know the name of the next task, then you can loop through the task to find the next transition. Is there any other way?

Find more posts tagged with

Comments

vpatel

What are you trying to achieve? What is the use case?

Faizi

Anybody know what are the possible ways to move to the next task in your custom Java class? The two ways I know would be to either know what the name of the Flow (transition) where you can use the transistionTo method. The other way I know is to know the name of the next task, then you can loop through the task to find the next transition. Is there any other way?

I think you should go through the Workflow Modeler API docs. You can find this as

modelerworkflowapidoc.jar

file at

/iw-home/httpd/webapps/content_center/WEB-INF/lib

location. After unzipped this jar file you get the docs.
Hope this helps.

Migrateduser

I don't have a use case for this, more just a general idea of how Interwoven does their programming.

According to /iw-home/local/config/lib/content_center/customer_samples_src/src/com/corp/custom/MailNotificationTask.java, it looks like it picks up the target_task_name to get to the next task.

Looking through the Publish LiveSite Content workflow, From the Review Notification Email task to the Review Files task, there is no target_task_name variable like there is in the Email Task (but that looks just like another urlexternaltask with some given variables.) The Publish LiveSite Content workflow calls the workflow.task.EmailTask bean to do the work. Just curious how they get to the next task with no target task name? Did they not write in the specific transition and just wait for the timeout link to take it to the next task? Or was the "Flow" name coded into the program to move to the next task?

vpatel

Many instances in the OOTB Publish LiveSite content (PLC) Workflow uses following convention:

Let's that current external/URL task is called "Task-101" then following transitions would be available:
1. "Task-101 Success"
2. "Task-101 Failure"

NOTE: Success and Failure suffixes.

Quite a few of the tasks are handled in this manner. I am not sure if the task that you are referring to is handled this way or if it is really missing the transition. Check it out for yourself and let us know.

HTH

Faizi

I don't have a use case for this, more just a general idea of how Interwoven does their programming.

According to /iw-home/local/config/lib/content_center/customer_samples_src/src/com/corp/custom/MailNotificationTask.java, it looks like it picks up the target_task_name to get to the next task.

Looking through the Publish LiveSite Content workflow, From the Review Notification Email task to the Review Files task, there is no target_task_name variable like there is in the Email Task (but that looks just like another urlexternaltask with some given variables.) The Publish LiveSite Content workflow calls the workflow.task.EmailTask bean to do the work. Just curious how they get to the next task with no target task name? Did they not write in the specific transition and just wait for the timeout link to take it to the next task? Or was the "Flow" name coded into the program to move to the next task?

According to my understanding MailNotificationTask.java is purely based on CSSDK while EmailTask bean class is developed on Livesite extended apis that is inherited from the CSSDK apis and extended its functionality.
So the way of transition to next task is different in both. As "vpatel" has said, it is absolutely right that in OOTB workflow (PLC) the transition name of URLTask should be with postfix of " Success" and " Failure" and no need to pass the name of next task.