I am using SAS Compliance Solution 7.4 (Anti money laundering)
and I need to restrict routing for employee in branch (Queue) to rout for specific branch (Queue).
For Example Employee works on branch 15 he can rout to main branch only, and the employees in the main branch rout to all other branch.
Is this scenario applicable in SAS Compliance Solution 7.4?
If not applicable I need a workaround for this scenario if possible.
Please Advise.
Hi,
Preferences
1.enforceQueuesForAlerts – Specifies whether to perform queue access checks for the alert details GET method
I believe for your use case, branch 15 user should be set up with a role that does not have access to items in main branch queue and preferences 1, 2, and 4 need to be turned on so that branch 15 user can route to the main branch (or any other queue) but not see entities in any non-authorized queues. This will allow the user to route but not see entity information in the queues for which they do not have access. However, this set up does not appear to exactly meet the use case in your first post where you said you wanted branch 15 user to only be able to route to main branch. In order for branch 15 user to only be able to route to one of the queues, the user must have access rights to the queue and preference 4 would be unchecked. Hope this helps.
You can use the routeToAllQueues preference in the admin consol to determine if users are allowed to route to any queue or only queues where they have access rights. This means that the branch15 employee would need access to the main branch queue and the main branch employees would be set up with access to all queues.
Hi,
Preferences
1.enforceQueuesForAlerts – Specifies whether to perform queue access checks for the alert details GET method
I believe for your use case, branch 15 user should be set up with a role that does not have access to items in main branch queue and preferences 1, 2, and 4 need to be turned on so that branch 15 user can route to the main branch (or any other queue) but not see entities in any non-authorized queues. This will allow the user to route but not see entity information in the queues for which they do not have access. However, this set up does not appear to exactly meet the use case in your first post where you said you wanted branch 15 user to only be able to route to main branch. In order for branch 15 user to only be able to route to one of the queues, the user must have access rights to the queue and preference 4 would be unchecked. Hope this helps.
Could you tell me if there is a way to create queues by country. for example users from France see their own alerts, then users from Spain with their alerts too but those from Belgium see all countries ?
Yes you can. In his response, Matt Needles referred to the way we can permit/restrict access to alerts. You can make use of the fsk_advanced_alert table to make sure country code or name is included in the alert details, and then you can use these to route the alert on custom queues based on their country. In SAS Management Console, the user admin plug-in, you can define roles and groups that can be used by the custom queues. SAS AML consultants will be able to help you configuring the solution as per your needs. (Off topic: assuming Compliance Solution 7.4 is a typo error. The only version available in the 7 generation is SAS Compliance Solutions 7.1, which encompasses SASAML 7.1 and SAS CDD 7.1.
Chartis names SAS a leader in both Model Risk Governance and Model Validation