Question
3
Replies
49
Views
Posted: January 16, 2020
Last activity: January 17, 2020
Closed
Foreign Tables
We have a use case where we want users logging in/available in one platform to be easily accessible to users of another platform running pega.
Is it safe to designate pr_operators as a shared table? Do we have any customers who have implemented this successfully? Is this supported for postgres? Does this handle both read and updates seamlessly?
Thanks
Sethu
***Edited by Moderator: Lochan to update platform capability tags***
Consider using custom authentication (like SSO) to grant access to a set of users to multiple Pega applications.
As you know already, the pr_operators table just holds the operator details, but accessing another platform depends on the access group/application/portal mappings, just having a shared table won't work. There are also other dependent tables for operator preferences, skills, workgroups. In any case, I don't think it's a safe approach, but you can still look forward to hearing other opinions if anybody has tried.