In the review escalation workflow, when the review state is changed to 'Complete', the system also changes the review state to complete.
You can configure a group review definition to make bulk actions available for the members and entitlements tabs in a group review.
Bulk actions did not work on account entitlements in an account review.
The product now constructs a URL link to data resource reviews and data ownership reviews. Previously only null URLs were generated for those reviews.
A runtime exception prevented the ability to sign-off a group in a group review. This was caused when the account IS_Deleted data was null.
Characters such as '&', '>' '<' etc. are treated differently in XML based SOAP connectors. (sanitize) These characters are now encoded (sanitized) in input values before the SOAP payload is created.
AFX deleted accounts before deleting the associated entitlements, which caused failures. Fulfillment order is now maintained for accounts.
Change Requests and Workflows
Purging now includes the additional unused data associated with change requests that are waiting for dependencies.
Scheduled pending submission cleanup jobs fail intermittently with error ‘ORA-02292: integrity constraint (AVUSER.FK_CRDETAIL_DEPENDENCY_CRI_ID) violated - child record found’.
Email nodes now support imbedded base64 images.
The sub-select clause displays a warning message during data collector queries.
The generic REST account data collector mapped attribute values to the wrong account when the mapped attribute was null in the response.
On initialization of the generic REST collector connection, the property key for setting and getting the proxy credentials from the collector settings did not match, causing the proxy settings to be ignored in the connection.
In Workday Identity Collector, when connecting to the Workday instance, the proxy settings were overwritten by the latest CXF library. Proxy settings are now retained.
While configuring LDAP collectors using SSL, LDAP server certificate host name validation was incorrectly coded to be case sensitive.
Users’ custom attributes of User type - (Supervisor, Admin, Technical Advisor) were not being collected.
Identity and metadata collectors showed an incorrect “Last Successful Collection Date”.
The RESTful connector did not properly escape double quotes and was not handled when the header contained content-type = application/json;charset=UTF-
The ServiceNow connector failed while running capabilities due to conflicts in the Apache cxf libraries.
Null pointer exceptions are now handled while workflow watch processing of workflow job data is erased by purge schedule.
Security Context queries have been optimized for permissions related to role membership on large datasets.
When editing an email template from the workflow, the HTML head and body tags were removed.
Email approvals from an Outlook client resulted in the message, "reply could not be understood."
Database-only installation failed if install directories were not created with appropriate umask in place.
Importing rules failed if Ruleset Name and Rule Set Raw Name were different. Importing Rule now only uses the Rule Set Raw Name as the identifying unique ID.
Code failed to handle errors associated with importing deleted attribute sync mappings.
In Report > Charts when the Show percent values option was deselected, the absolute number values were displayed in both preview and actual charts without any invalid message.
While performing a request activity for a new user which triggers a defined joiner/mover rule, business roles and technical roles were not displayed in 'default provisioning form' under suggested/ optional categories even though they were suggested by entitlements suggestion modelling.
Duplicate change requests were created with Provisioning Termination rule for the ‘Revoke Entitlements’ action if the rule ran multiple times for the same user.
The roles 'business-role' and 'technical-role' were not listed in entitlement modeling of the joiner/mover rule when the role-set was added as an entitlement filter condition.
When the “Attribute Change” rule was fixed to add users, the change request also created a ‘System’ User. The system user is no longer created.
User details were missing in the attribute sync change request.
Email approvals from Outlook client result in "reply could not be understood" in IG&L.