This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SOLUTION - PROGRAM MANAGEMENT - Reverting project activity status / and returning activity to inbasket

ejmoska - Thursday, October 6, 2016 3:51 AM:


Lets say we have a situation where a Project Manager has assignment for one of the team members, in Project he marks the assignment as "Leader sign-off required"

After the asignee finishes the task , the leader inspects the work that has been done and decides not to approve.

what do we do in this situation? task seems to be marked complete and not visible in the assignee inbasket, only the status doesnt change to 100%

is there any way for PM to say "REWORK" and the activity would be reinstated to the asignee's inbasket?T

also another scenario is when you complete the task , and then it turns out it's not really that complete... is there any way to reset it back to active?

Thank you for the information, really appreciated

edonahue - Monday, October 10, 2016 4:25 PM:

Hi ejmoska,

I would recommend adding a workflow path called "Rework" that links the PM's decision activity back to the previous task activity. This would essentially create a loop in your workflow where the PM could decide to approve and advance the workflow to the next activity, or they could reject and sent the task back to the assignee to rework. When the workflow loops back, Aras will create a new copy of the activity and the assignee will receive a new assignment.

See the example diagram below.

ejmoska - Tuesday, October 11, 2016 2:55 AM:

Hello, Eli,

Thank you for a quick response.

Your solution is great when it comes to workflow tasks, but how about Project tasks?

I have figured out there is no workflow map neither for itemtype "Project" or "activity2" , but there is a method called "onSaveActivity2" which seems to do most of the job.


edonahue - Monday, October 24, 2016 5:56 PM:

Hi ejmoska,

Ah, sorry about the misunderstanding. For projects, there is a "leader signoff" concept that may help you with your use case. Essentially, any activity that needs to be reviewed has at least two assignments: one or more assignments for the intended activity assignee, and one assignment for the "leader" to sign off on the work. The assignments for the intended assignee should add up to a vote weight of less than 100 (ex: 99), and the leader's vote weight makes up the difference (ex: 1). This will ensure that the activity cannot be closed until the leader approves and the cumulative vote weight reaches 100.