Issue with cross-domain approvals

[peterwigham]

Hi all,

I'm busy working on a requirement for cross-domain approvals; the approvals for this change process require approval to be sought from several different domains that essentially move up and down the domain hierachy chain.

We are using domain separation within our instances and currently have a hierachy of:

- BTLG (internal to our company)

- Pan-London (external domain, child domain to BTLG)

> WCC (external sub-domain, child to Pan-London)

> RBKC (external sub-domain, child to Pan-London)

> H&F (external sub-domain, child to Pan-London)

So, BTLG is the main domain, underneath this is Pan-London and this contain the three other domains.

All internal employees are in the BTLG domain whilst the Pan-London employees are spread amongst the domains of WCC, RBKC and the H&F domains.

We have a workflow in place called 'Comprehensive Change LF' that includes four approval group steps; Change Manager Approval, CAB Aproval: CAB1, Client CAB Approval: CAB2, CAB Aproval: CAB3. All of these steps require approval from BTLG users apart from Client CAB Approval: CAB2 which requires aproval from a user group consisting of users across the three Pan-London sub-domains.

When testing this I've noticed that when I log this with a user in the WCC domain if there are no WCC users within the groups from the same user domain as the user logging the record, the step is skipped and no approval is requested. I understand why this is however, we need to find a way to get approvals to be generated back up the hierachy to the BTLG level.

I've set up the relevant domain 'Contains' and 'Visibility' for the Pan-London sub-domains so that they can all see one another however it would seem that the approvals will not be generated back up to the BTLG users. Has anyone ever has to create a workaround for this using domain 'Contains' and 'Visibility' or within the workflow.

Any help or suggestions would be hugely apreciated.

Cheers,

PW

[jagmjavier]

Hi,

have you try setting the domain of the users that you need as approvals to "global'? This allows that users in below domains can see them and for sure that your approvals will be generated.

Regards

[jlkovalik]

Doesn't that defeat the purpose of domain separation?

We've been running into the same issue.   Prior to Eureka, you could manually set the workflow to "global" but with the changes made in Eureka, the only workaround we've found is to superficially put a "timer" step in the workflow [which pushes the workflow back to executing in a global context].   This is still a bit of a hack and wish there was a better alternative to this.

[williamsun]

Worked like a charm, thanks Jon Kovalik

[ponns1]

Hi William,

                                    We too have a similar requirement, so could you please elaborate a bit more on how you added the Timer activity in the workflow and modified the workflow context record to global domain.

Thanks in Advance.

Ponnusamy Subramaniam.