[multi site changes]

With the parallel processing if only one from eighter team approves the change it hits 100%, so your correct the question would be who to handle the outcome. 

I think the best approach is to create one team for the approvers, but hat responds differently than i would think it does. 

When i create the request it's assignd to Team A (via Process Cap), the authorization kickes in after the change date has been set.
So in BP i re-assign the request to the Infra Team and the authorisation thereafter. 
looking at the tasks, thoose are assigned to Team A rather that the infra Team, i don't understand that bit.

[multi site changes]

That's a difficult one to answer, we currently have this.

Team a - 3 members 
Team b - 6 members 
Team c - 8 members 
Team d - 2 members

 

[multi site changes]

Hi @James Ainsworth

sure, we have a rule set, that when there is a multi site change at least one member of each team should review / authorise the change. 
so i want to create a task for every sites-team for authorization, so they can deside among themselfs who check's / authorises the change. 
 

[multi site changes]

Hello, 

I’m in the midst of a business process creation for a multi-site change. 
The thing I’m after is how can i get at least one member of each site(5sites) to be set as an approver for a change.

Without having to set them individually(bit convoluted for 5 sites), did look at did he variable &[global["flowcode"]["assignedTeamId"]] that works kind of.. It misses the weight as well as the authorization type. 

any idea / guidense on how to achief this?