AnsweredAssumed Answered

Role Membership Rule doesn't detect tne new users

Question asked by Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016
Latest reply on Jul 7, 2016 by Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ=

Like • Show 0 Likes0
Comment • 10

Hi,

I create a new Role with this following Membership Rule

It create two rules, the first for adding the new identity in the role and the second to deleting the identity from the role

I have two identities with the attribute IS_BU_OBO set to 'y'

When i run the both rules (UINC and UOOC) it work just for the first time, it add the users to the role. But if i modify the attirbute IS_BU_OBO (i modify IS_BU_OBO using a workflow) and reexecute the rules manually (process rules), it not detect the new users and not delete the old users.

Have you any idea about that?

Regards.

Venkata Ramana Reddy Kanaparthy

Jul 7, 2016 5:30 AM

Correct Answer

It should ideally not be required to run unification after editing a managed attribute from UI. Please raise a ticket for that.

Here is the workaround to avoid running unification.

Run the below procedure after updating the user's attribute value and commit. This fills up some tables that are required for rules to run (It runs post unification apart from many other times). Rule run should detect users after that.

exec Role_Management_Pkg.Populate_Role_Metrics(0, 1, 0);

See the reply in context

No one else had this question

Outcomes

Boris Lekumovich

Jul 7, 2016 4:43 AM

Is your attribute (IS_BU_OBO) managed or collected?

Actions

Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Boris Lekumovich on Jul 7, 2016 4:46 AM

Hi Boris

I modified it using workflow, so i put it as a managed attribute

Regards

Actions

Boris Lekumovich

@ Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016 4:52 AM

Try running identity collector with unification and then re-execute the rules.

2 people found this helpful

Actions

Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Boris Lekumovich on Jul 7, 2016 4:59 AM

I try it (i need to wait 1 hour for unification), but i want know if i need to run the collection before execute the rules, cause the collection is scheduled once by month and the workflow is scheduled once by week ,so i can not run collection before each update of the role?

Actions

Venkata Ramana Reddy Kanaparthy

@ Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016 5:06 AM

It seem to work if unification is run (no need to run collection) before processing rule.

1 person found this helpful

Actions

Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Venkata Ramana Reddy Kanaparthy on Jul 7, 2016 5:11 AM

Yes it work after the unification, but i want know if i must run the unification before processing the rules

Actions

Venkata Ramana Reddy Kanaparthy

Jul 7, 2016 4:55 AM

Can you change that attribute from UI by editing the user and then running the rules.. Wondering if you missed updating something that is required when you updated the attribute using SQL from workflow..

Actions

Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Venkata Ramana Reddy Kanaparthy on Jul 7, 2016 5:06 AM

I editing it using workflow, it do not detect the change, in the workflow i modify the attribute in T_ENTERPRISE_USERS and in T_MASTER_ENTERPRISE_USERS.

Actions

Venkata Ramana Reddy Kanaparthy

@ Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016 5:30 AM

It should ideally not be required to run unification after editing a managed attribute from UI. Please raise a ticket for that.

Here is the workaround to avoid running unification.

exec Role_Management_Pkg.Populate_Role_Metrics(0, 1, 0);

2 people found this helpful

Actions

Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= Jul 7, 2016 5:34 AM

Thank you that work for me.

I used call not exec.

Actions

10 Replies

Boris Lekumovich Jul 7, 2016 4:43 AM
Mark Correct
Correct Answer
Is your attribute (IS_BU_OBO) managed or collected?
Like • Show 0 Likes0
Actions
- Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Boris Lekumovich on Jul 7, 2016 4:46 AM
  Mark Correct
  Correct Answer
  Hi Boris
  
  I modified it using workflow, so i put it as a managed attribute
  
  Regards
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016 4:52 AM
    Mark Correct
    Correct Answer
    Try running identity collector with unification and then re-execute the rules.
    2 people found this helpful
    Like • Show 1 Like1
    Actions
    - Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Boris Lekumovich on Jul 7, 2016 4:59 AM
      Mark Correct
      Correct Answer
      I try it (i need to wait 1 hour for unification), but i want know if i need to run the collection before execute the rules, cause the collection is scheduled once by month and the workflow is scheduled once by week ,so i can not run collection before each update of the role?
      Like • Show 0 Likes0
      Actions
      - Venkata Ramana Reddy Kanaparthy @ Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016 5:06 AM
        Mark Correct
        Correct Answer
        It seem to work if unification is run (no need to run collection) before processing rule.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Venkata Ramana Reddy Kanaparthy on Jul 7, 2016 5:11 AM
        Mark Correct
        Correct Answer
        Yes it work after the unification, but i want know if i must run the unification before processing the rules
        Like • Show 0 Likes0
        Actions
Venkata Ramana Reddy Kanaparthy Jul 7, 2016 4:55 AM
Mark Correct
Correct Answer
Can you change that attribute from UI by editing the user and then running the rules.. Wondering if you missed updating something that is required when you updated the attribute using SQL from workflow..
Like • Show 0 Likes0
Actions
- Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Venkata Ramana Reddy Kanaparthy on Jul 7, 2016 5:06 AM
  Mark Correct
  Correct Answer
  I editing it using workflow, it do not detect the change, in the workflow i modify the attribute in T_ENTERPRISE_USERS and in T_MASTER_ENTERPRISE_USERS.
  Like • Show 0 Likes0
  Actions
  - Venkata Ramana Reddy Kanaparthy @ Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Jul 7, 2016 5:30 AM
    Unmark Correct
    Correct Answer
    It should ideally not be required to run unification after editing a managed attribute from UI. Please raise a ticket for that.
    
    Here is the workaround to avoid running unification.
    Run the below procedure after updating the user's attribute value and commit. This fills up some tables that are required for rules to run (It runs post unification apart from many other times). Rule run should detect users after that.
    
    exec Role_Management_Pkg.Populate_Role_Metrics(0, 1, 0);
    2 people found this helpful
    Like • Show 2 Likes2
    Actions
Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= Jul 7, 2016 5:34 AM
Mark Correct
Correct Answer
Thank you that work for me.
I used call not exec.
Like • Show 0 Likes0
Actions

Role Membership Rule doesn't detect tne new users

Outcomes

Related Content

Recommended Content