6 Replies Latest reply on Jan 28, 2020 9:44 PM by Vaishali Ahlawat

Enabling Notification and not approval steps in ActiveVos Workflow

Vaishali Ahlawat Jan 27, 2020 1:47 AM

Hi Team,

I am new to ActiveVos and we would be starting a new project for which we have a requirement in which one record would be created by the contribution of some 8-9 different teams like first initiator would initiate a request with basic details followed by another team who will add plant details to it then followed by other team which will add packaging details to it and so on.

Now this we need to implement using MDM and Avos Integration .

And my question is if we create an Avos Workflow for it and add a Human task for every step and get it approved at every step to move it to next step it will become a very cumbersome process .

Hence, I want to know can we create a workflow in which every step is just a notification task so that respective team knows that a request has been initiated and they have to take it further and then just one step approval at the end ?

Could someone please suggest the feasibility for the above scenario ?

Thanks,

Vaishali

1. Re: Enabling Notification and not approval steps in ActiveVos Workflow

kunal pandit Jan 27, 2020 10:08 PM (in response to Vaishali Ahlawat)

Vaishali,

This seems to be feasible in ActiveVOS workflows but your exact requirements and how you design is something that you will need to consider, for e.g. notification Human task will still need human intervention for the process to move forward. unlike an email which after being send by the workflow, will cause the workflow to proceed forward.
Like Show 0 Likes(0)

Actions
2. Re: Enabling Notification and not approval steps in ActiveVos Workflow

Vaishali Ahlawat Jan 28, 2020 2:15 AM (in response to kunal pandit)

Thanks Kunal .

Yeah, I also have that kind of understanding only but I wanted to understand if we have a possibility in which intermediary parties are just notified via email and when the last party or all of the parties are done with their contribution of data then it can move to the approval step .

Just want to know if that kind of structure we can achieve in Avos which I think no as per your statement above "unlike an email which after being send by the workflow, will cause the workflow to proceed forward
Like Show 0 Likes(0)

Actions
3. Re: Enabling Notification and not approval steps in ActiveVos Workflow

Dhananjay Singh Jan 28, 2020 7:19 AM (in response to Vaishali Ahlawat)

Can you please elaborate on "all of the parties are done with their contribution of data"?
Like Show 0 Likes(0)

Actions
4. Re: Enabling Notification and not approval steps in ActiveVos Workflow

kunal pandit Jan 28, 2020 2:41 PM (in response to Vaishali Ahlawat)

Vaishali - please note that you will need a human task to be created if you want parties to contribute data from e360 or IDD applications. If the sources are outside of MDM, then you will need to wait for the external sources to contribute the data. How you are going to implement this is upto you - whether these sources will be contributing in real time or if they also need human intervention.
Like Show 0 Likes(0)

Actions
5. Re: Enabling Notification and not approval steps in ActiveVos Workflow

Vaishali Ahlawat Jan 28, 2020 9:41 PM (in response to kunal pandit)

ok Clear, I will see it through once environment gets ready .

Thanks for the suggestion .
Like Show 0 Likes(0)

Actions
6. Re: Enabling Notification and not approval steps in ActiveVos Workflow

Vaishali Ahlawat Jan 28, 2020 9:44 PM (in response to Dhananjay Singh)

I mean that every role or party is responsible to fill data for one particular entity or subject area like one role will fill material data only then next role will fill plant data then next sales and so on.

But I think I will need Human Task only and whether that task would be review type or notification task that is something I will have to explore further .
Like Show 0 Likes(0)

Actions