Provisioning

Link an Unmanaged Account to an Person in the Entitlement Import Report
Enable manual linking of an unmanaged account (not currently matched via correlation or as account entitlement in system) to a person when processing an entitlement import report. This facilitates future automatic matching through updated correlation values. Manual Selection of Unmanaged Accounts Allow users to manually select an unmanaged account from the entitlement import report when: A person should have an account entitlement, but no matching account is found based on the correlation value. Also when we found mulitple macthing accounts. There exists a potential unmanaged account not currently linked or managed to another person. Search on account username & displayname as returned in import account data script. Allow to edit/clear the manual selected account up until the entitlement import is executed Add extra filtering state “manually matched” Link and Import Action Upon selection: The unmanaged account is imported and granted to the selected person. The system should perform an update acount on the imported account, setting the account correlation value (e.g., username, employee ID) to match the person’s correlation property value. When account is selected update the view with account access and permissions that will be imported When a manual selection for an account has been made then add warning uppon recreate report for the import of entitlements: Export import entitlement report Add manually selected state and other states to report Effect on Future Imports This linkage ensures that: On the next entitlement import run, the previously unmanaged account is now recognized and automatically matched to the correct person. Remove correlation reports from AD & Azure AD builtin target systems Use Case Example Person John Doe should have an account entitlement, but no matching account is found. An unmanaged account jdoe123 exists in the source system but the correlation value of the account doesn’t matched the person correlation value. Admin manually selects jdoe123 to link to John Doe. The account is imported, the correlation value (e.g., username) is updated to jdoe123, and the account is linked to John Doe. When all account entitlements are unmanaged on the next entitlement report, the system automatically matches jdoe123 to John Doe.
2
·

planned

Comments and tags on reconciliation exclusion
Goal: Improve traceability and filtering when excluding issues from reconciliation by allowing users to specify reasons and categorize exclusions with tags. Add Comment Field on Exclusion When excluding an issue, users should be able to enter a free-text comment. Purpose: To describe the reason for exclusion (e.g., link to a ticket, explanation, etc.). The comment should be visible in the issue details and available for future reference. HTML santization. Add Multi-Select Tag Field on Exclusion Allow users to assign one or more tags when excluding an issue. Tags should be user-defined, similar to tagging in Azure DevOps. System should provide autocomplete/suggestions from previously used tags. HTML santization. Bulk Mode Behavior When excluding multiple issues in bulk: A single comment and tag set should apply to all selected exclusions. Users should enter the comment and select tags once for all. Filter on comment and tag field Allow user to filter on the comment (contains) and tag (equals one of the items) in the excluded list view System should provide autocomplete/suggestions for tag in the equals condition Add support for empty filter on tags Elastic audit logging Add comment and tags to the existing audit logging to elastic Use Case Example A user excludes an account and enters the comment: Linked to ticket TICKET-1234 – account under review They select tags: ["admin account"] This enables others to: See why it was excluded Filter for all exclusions with the tag "admin account" Revisit later once the ticket is resolved Limits Max number of tags in tag field is 10 Limit max number of unique tags to 1000 Max limit of tag length (same as br category) Max lenght of comment is 1024
3
·

planned