Response to "Workflow Approval Tasks, Roles and Coupling - Part 1"

[JSchrader]

All,

As I promised last week, here are the steps and instructions we did to perform a variation at least of Antonio's problem with dynamic roles and a dynamic workflow. Please let me know if I am missing anything. I've attached a Word document detailing what was setup (I've left some of the things out and tried to focus on the role issue only) plus some of the files used. Please note that the source files attached are setup to go into the specific directories called out in the Word document and contain a lot more methods than what are actually used in the workflow.

Let me know if I missed anything or if it's still confusing and I'll try and rectify the information.

Jason Schrader
Kalypso

Tel (336) 303.8482

jason.schrader@kalypso.com

_____________________________________

Delivering on the promise of innovation

www.kalypso.com

See what makes us different

[avillanueva]

Jason, when you update the AssignedActivity roles
(updateRolesOnActivity(...)), you are actually modifying the template,
right? When you go to the workflow admin, does then template now show
the last edit due the most recent execution of this workflow? For
example, I edit the workflow template and for that task, I leave no
roles listed as participants. When I execute the workflow, it adds 5
roles. What will I see when I look at the template again in the workflow
admin? Does this affect the iteration history of the workflow template?

[JSchrader]

Antonio,



No it does not iterate the workflow. The modification that's being done
on the fly is a modification to the task template that's instantiated
when the workflow is executed. So I basically modifying the newly
created and running workflow process to modify the task object that it
created.



When you click on the running workflow process (from the document that
the workflow is running against), it will show the roles added after the
task has been reached and executed. But in the Workflow Administrator,
you won't see these running modifications.



Thanks,

Jason Schrader

[avillanueva]

Update from Tech Support:

R&D commited the resolved datecode as windchill 9.1M070.