new
October 2023
Important
- Provisioning requires the newest agent for communication
Provisioning
Changed:
- Support mapping for object type (We do not support nested objects) in the Powershell V2 target system
- Powershell V2 mapping support for an array type
- Improved Powershell source execution resilience
- Improved uniqueness script result validation and error messages
Fixed:
- Added more logging when updating or creating an Exchange Online mailbox in Azure AD target system
- Improved retrying connection for mailbox actions in Exchange Online for the Azure AD target system
- Removing all actions from a mapped field in Powershell V2 could result in not being able to create a field with the same name until you refresh the page
- Account correlate create success output is ignored in the create action of a Powershell V2 target system
- Account reference is required for the preview of an update account action (which should not be required).
- Disabling the uniqueness check on an action when the Onpremise agent is used will result in an error when that action is executed.
- Snapshot logging cannot be displayed for scheduled snapshots
- PowerShell v2 default mapping error caused on entitlement revokes when the person no longer exists
Service Automation
Changed:
- Add API support for new product actions
- Allow URL filtering on managed products overview
- Allow URL filtering on managed users overview
- Import GitHub code snippets for new product actions
- Enlarge modal for Product action CRUD UI
Fixed:
- Delegated Form $requester not correctly resolved at task retry
- Too much recursion error in console in product edit screen
- Managed Products - Product name not displayed when using multi line product description
- Groups for products and delegated forms are not shown in admin UI
- Delegated forms with automation tasks keep triggering the automation tasks (hotfix)
- Improve inbox on landscape tablet view (hotfix)
- OS 15.7 devices can't login (hotfix)
General
Fixed:
- Wildcard certificates with more than two dots in the full name were seen as faulty certificates when setting up a custom domain