Breaking changes
Breaking changes are changes that will cause existing integrations and functionality to break unless you take remedial action.
- Alert templates: The New Alert Template was renamed to ~*** New Alert Template - Configuration Use ***~. The New Template was renamed to ~*** New Template - Configuration Use *** ~. These changes were made to prevent operators from accidentally overwriting the system alert templates when creating a new alert template.
- API Get Alert Template, Get Event Template, and Alert Details APIs: The following APIs return AttachmentIds instead of Base64Attachment:
- GET /orgs/{orgCode}/alerts/{auId}
- GET /orgs/{orgCode}/alerttemplates/{templateCommonName}
- GET /orgs/{orgCode}/AccountEvents/templates/{commonName}
To download an attachment, use the AttachmentId with the Attachment GET API:- GET /orgs/{orgCode}/attachments/{guid}
- Organization ID and provider ID disallowed in externally-facing URLs: The organization ID must be replaced with the organization code in any bookmarked Self Service and Single Sign-On URLs. The Provider ID must be replaced with the organization code in the identity mapping file in the SSO configuration.
- SSO URL: If a secondary authentication method is selected for Self Service,/ssois appended to the SSO URL.
- User base operator import: When importing user base restrictions, each operator (such as "less than" or "equal to") must be enclosed in double quotation marks ("").