Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Provisioning access based on dynamic value not working

supriya_singh
New Contributor II
New Contributor II

Hi,

We have about 400+ technical rule and they have difference of only one attribute i.e costcenter in condition. Also in entitlement name only costcenter is different other things are common. We are trying to create one technical rule to provision access by using costcenter as dynamic attribute. Its not working

We are using Saviynt v5.5SP3 . Can someone help.
 
Thanks
6 REPLIES 6

rushikeshvartak
All-Star
All-Star

Can you explain use case.

dynamic attribute won’t be accessible in technical rule it must be request rule


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Manu269
All-Star
All-Star

Hi Supriya,

As I understand your query does dynamic attribute is being utilized while raising the request?

Also, dynamic attribute cannot be accesed in technical rule.

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

Hi,

Our req is like we have around 400 rules but we don't want to create 400 rules we want to group these in one technical rule or analytics as they have difference of one attribute i.e costcenter.

Below are example of two technical rules :

If  Users. Job Code IN (50059105, 50118548) AND COMPANYCODE IN (1000, 2000, 4000) AND Users. Cost Center like '000000%1001'
Then
Assign Groups::CN=sec_Shared_Mbx_Store1001,OU=abc,OU=Groups,DC=xyz,DC=local
If  Users. Job Code IN (50059105, 50118548) AND COMPANYCODE IN (1000, 2000, 4000) AND Users. Cost Center like '000000%1002'
Then
Assign Groups::CN=sec_Shared_Mbx_Store1002,OU=abc,OU=Groups,DC=xyz,DC=local

Want to create single technical rule for above 2 or single analytics.

Regards,

Supriya

 

You should use request rule if you are using ARS Module

make dynamic attribute but costcenter 

rushikeshvartak_0-1666362256945.png

 


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Vamsi
New Contributor III
New Contributor III

Hi Supriya,

you can use a Analytics report to provision access  below is a sample query you have to make changes according to your requirement . Its tested with accounts table for your requirement you have to join user table and check on create date if its for new users

Query:

select distinct ac1.ACCOUNTKEY as 'acctKey',case

when Users.JobCode IN (50059105, 50118548) AND COMPANYCODE IN (1000, 2000, 4000) AND Users. Cost Center like '000000%1001' then '1234' 

when Users. Job Code IN (50059105, 50118548) AND COMPANYCODE IN (1000, 2000, 4000) AND Users. Cost Center like '000000%1002' then '5678'

END as 'entvaluekey',

ac1.name as 'accName',

Users.userkey as 'userkey',

'Provision Access' AS Default_Action_For_Analytics  from accounts ac1  where ac1.created_on > DATE_SUB(now(), INTERVAL 2 DAY) AND ac1.endpointkey =1

Regards,

Vamsi

supriya_singh
New Contributor II
New Contributor II

Hi All,

Issue is resolved and it is working fine now. Used the same technical rule having costcenter as dynamic attribute. It was not working before because we selected wrong group.

Regards,

Supriya