This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Persons marked as outstanding still have their account definitions and resources assign through dynamic rolesmark

Hi.

I have an employee that have three account definitions assigned and one resource assigned through dynamic roles. But when the person is marked as outstanding the definitions and resources are still there (they're present in PersonHasTSBDefinition and PersonHasQERResource).

But if I go and test the condition for those four dynamic roles they're not there.

The entitlements origin "report" shows that they're still assigned to the person indirectly and that they're still in effect.

The condition for the dynamic group is to exclude persons that are marked as outstanding.

Please help..

PS: We're on version 8.0.1 (or 8.0.2)

Best regards,
Henrik

Parents
  • So when you are saying that an object suddenly re-appears then you mean that the same object will be seen in one sync run but not in another one?

    Regardless, you haven't specified how you are importing the data from HR, therefore, I am unable to answer your question.

  • We're importing through a sync project connected to a SQL-database.

    When the object disappears the Person is marked for deletion, but when the object reappears the Person the marked for deletion-flag is not removed.

  • I am coming back to my original post, explaining that the Outstanding handling is working as designed and intended.

    The reason I suggested the use of the delete operation was your request for removal of inherited permissions.

    I am still wondering why an object could suddenly reappear but so be it.

    I suggest contacting support in that matter then. It's hard to solve this via the community. They can help you identify what the reason for that behavior is (Workflow configuration in the Sync Project, Product Bug, ...).

Reply
  • I am coming back to my original post, explaining that the Outstanding handling is working as designed and intended.

    The reason I suggested the use of the delete operation was your request for removal of inherited permissions.

    I am still wondering why an object could suddenly reappear but so be it.

    I suggest contacting support in that matter then. It's hard to solve this via the community. They can help you identify what the reason for that behavior is (Workflow configuration in the Sync Project, Product Bug, ...).

Children
No Data