The below workflow was created for a Creative Team. The work request for this workflow (project) allows the requester to dictate the content type which also determines which teams are engaged. More than one team will be engaged if more than one Delivery Channel is selected. Each content type (Delivery Channel) has its own project and team with independent due dates.
The workflow below works well to engage the teams through the first column of tasks. Each of those tasks identify the Delivery Channel selected and launches that team’s project as an output.
The problem with this approach is there is no way to “tie together” all the projects before closing the Activity. Once the individual assets project launches, the main workflow seen here continues to process without any regard to the subsequent projects. So all the required work is launched however the Activity will close out and send a notification to the requester right away even though all the assets (and workflows) are just beginning.
James Miller and I worked together to create this solution. It isn’t ideal but it does work. Any Delivery Channel selected will kick off its own workflow then go into an iterative loop until an EA called Project Closed changes the value to “Yes” at the end of the workflow.
The good news is this works however it’s not clean. The audit trail and task worksheet for the main workflow is riddled with these iterative loop steps making it very difficult for our users to read the task worksheet. Also, we had to put a 24 hour dwell in this loop to minimize the trail of iterative loop steps. That slows down the list however it also puts a delay of up to 23 hours and 59 minutes to properly close out an activity as well as send the requester the proper notification.
I’d like Aprimo to develop a “Dwell Timer” or some sort of “wait for a project to close” option so I don’t have to use this design. It is effective but not ideal.
Customer support service by UserEcho