Announcements
There are no announcements for this release.Connect Features
This section describes the key updates in this release.Custom Data Bulk Update Support
Custom Data is a flexible storage mechanism that is collected from an entity (for example, User), either directly (through means such as configuration) or indirectly (through means such as UI engagement), stored, and retrieved on demand. Until now, Connect offered an API to perform bulk custom data updates using a special key that permits applications, such as ETL (Extract, Transform, Load) software. At volumes of over 10,000+ custom data updates, calling an API for each update can take hours to complete and perform. As of this release, Connect offers a new, faster method to perform bulk updates of custom data documents. Organizations can upload JSON files inside a tar.gz archive that includes the thousands of custom data updates to a repository through Secure File Transfer Protocol (SFTP), and Connect will process the files daily. For each file processed, Connect provides a report that includes:- the date of processing execution
- processing duration
- items processed
- Item status (success or fail)
- error details
Dynamic Redirect URL Logic for Social Authentication
Connect Onboard & Authenticate User with Social Account process APIs enable users to onboard and authenticate using their social media account. Connect supports onboarding or logging in with Apple, Google, Facebook, LinkedIn, and Microsoft. A Redirect URL is a configuration per social media provider. Users are redirected to this URL once they complete connection via the social media provider. As of this release, Connect supports dynamic redirect URL logic. Merchants may have numerous login screens that can be tailored for various applications in their ecosystem. Dynamic redirect URL can be used to specify a new optional parameter for the different scenarios final-redirect-uri. For example, a merchant that has enabled onboard or log in with Facebook, can callPOST /process/start/socialFederation.SocialMediaAssistedOnboarding?provider=facebook&final-redirect-uri=/idp/social_end, whereby once the user has completed onboarding, they will be taken to /idp/social_end.
Required End User Verification Flow
Currently, Connect Add/Update Email, Mobile, or Alias Process enables an end user to add or update their email address, mobile number, or alias to their profile. Once an end user attempts to add or update, they will receive a verification email or SMS. When the end user completes the verification step, the added or updated email address or mobile number will be verified. The end user can verify at a later time and Connect maintains both verified and unverified email addresses or mobile numbers on the profile. As of this release, Connect also supports an additional, alternate flow whereby an end user must verify their email address or mobile number. In this alternate flow, Connect will not maintain unverified email addresses or mobile numbers. Connect will therefore require that the end user complete the verification step.New Process API: Set/Update Passcode
In Connect 2022.01 release, a new process API Onboard and Authenticate with Mobile Number and Passcode was released. This new Process API supports applications or systems that allow numerical digits input only as in the case of an IVR system. As of this release, Connect supports a new API to set or update passcode, where a passcode is a string of numeric characters used as a password, with a singlePUT /user API call. The end user must already be authenticated for the API to work. This API is intended for profile management related use cases.