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

SUPPORT Q&A - Workflows

Rekha - Friday, May 31, 2013 4:52 AM:

Hi ,

I have an activity on workflow which has four approvers P,Q,R,S. Approval from these four is mandatory and hence given the weightage as 25 for each.

There is rework path which goes from this activity to previous activity('ActivityX') and there is a default next activity 'ActivityY'

I got to know that all the approvers have to choose rework to send it for rework.

If one of the four approvers sends for rework, will the request go to previous activity?

Also, the request has to go for approval only by those who sent for rework, on submission for approval again.Can you please let me know if this is possible in workflows and how to achieve this with configuration only?

Is customisation required by writing server methods?

Regards

Rekha



Naveen - Friday, May 31, 2013 8:27 AM:

Hi Rekha,

On the Rework path select "Override Path", this will make sure that if any one of the approvers send it for rework then the other Signatories are overridden, and it moves to the (Activity X).

I am not sure how to go about the second part of your question, hopefully some one else will be able to help you.



Rekha - Friday, May 31, 2013 11:17 AM:

Thanks Naveen. The 'override path' works for the first part of requirement. 



Brian - Monday, June 3, 2013 8:56 PM:

Hi Rekha,

If you want the workflow to work as automatically as possible, with no extra manual intervention then yes, customisation via server methods would be required to meet your second requirement.

If you are happy having someone intervene with the workflow whenever it goes back to the re-work stage then you can achieve your requirement without code.

When the workflow loops back and then moves forward again all of the assignees are once again asked to vote.

However, before an activity becomes active you can go to the workflow process and change the assignees for a future activity.

To do this you need to configure the Managed By and Role for the specific activity that is to be manually changed.

The Managed By identity can change the assignees for the Activity, provided the activity hasn't become active yet. They can assign anyone who is a part of the Role identity to be an assignee for the upcoming activity.

So when the item goes back to Rework the Manager of the next activity after Rework needs to view the Item then select Views | Workflow. Select the next activity and then they can change the Assignees.

Given that you are "reworking" something isn't is reasonable to suggest that someone who voted "OK" before might now not be "OK" with the changes and would therefore want to vote again anyway?

Have a look and see if you can get this to work.

Hope this helps,

Brian.



Rekha - Tuesday, June 11, 2013 1:24 PM:

Thank you Brian for the solution without code. I will check this out. Yes even I understand that it is good to get voted by all again after rework.

Regards

Rekha