> ## Documentation Index > Fetch the complete documentation index at: https://docs.ulm.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # MarketONE Connect 2021.06 - Release Notes Release Date: June 29, 2021 ## Annoucements This release includes the following announcements: * Create Custom Data Array on Demand * Onboard, Authenticate and Purchase Process (Soft Release) ## Connect Features This section describes the key updates in this release. ### Create Custom Data Array on Demand Earlier this year, Connect introduced a set of Custom Data (or CD) API for client applications to store, retrieve, and update data within the Connect data store, and to associate that data to existing User entities. This feature allows an application to capture and leverage additional data points regarding a known end user, usually with regards to the end user's activity within a given client's service (for example, viewing history, preferences, etc). Organizations leveraging this service can structure and store data in most any order they want, provided that the data properly conforms to JavaScript Object Notion (JSON). If valid, the custom data for a User is stored as a single JSON document or record in the cloud. The CD API includes a set of endpoints specifically for writing JSON arrays (that is, lists) to a CD records That set includes following [API endpoint](https://app.swaggerhub.com/apis/Amdocs_Media/CustomData/2021.03.Released#/Custom%20Data/addCustomDataArrayItem): * `POST /v1/user/{{userID}}/{{propertyArrayName}}` | Summary | Description | | - | - | | `userId` | The unique id property on the target Connect User entity. | | `propertyArrayName` | The target array on the custom data record that is associated to the target Connect User entity. | Your client application calls this endpoint, and specifies the target User, as well the desired array name. If the request body is valid, Connect adds the new array to the CD record for the target User, and adds the request body contents to the array. However, as of this release, this API can now also write additional array elements to an existing array in a CD record. In other words: * If the client calls this API and specifies a propertyArrayName that does not exist, then Connect will write the new array onto the record. * If the client call this API and specifies a propertyArrayName that does exist on the record, but the body contains an element that does not currently exist in that array, then Connect adds that element to the array as a new entry. Update Array ### Onboard, Login and Enrol Process (Soft Release) As of this release, a new Connect API Process is available that enables end users to onboard, authenticate, enrol, and prompt for a purchase in one seamless flow. Key features of this Process include: * An end user can onboard with their email or mobile number. If the end user onboards with their mobile number, then the password is optional. This option supports existing integrations for the sake of backwards compatibility. * An end user can authenticate with their email or mobile number. If the end user authenticates with mobile number and they currently do not have a set password, then Connect sends a One-Time Passcode (OTP) is sent to the end user's mobile device. The end user then needs to supply that OTP to authenticate and continue their journey. * During the initial user authentication, Connect can optionally perform additional checks to determine if the end user is already entitled to any services with your organization. To do this, Connect queries your organization's customer record system with the end user's authentication identifier (email or mobile). If a service is found, then the end user successfully authenticates. Alternatively, if a service is not found, the system can automatically prompt the end user to make a purchase before they can proceed. * Connect can also query your system to verify if the end user owns (or is entitled to) any billing accounts with your organization. If any accounts are found, the end user will have the option to associate the account directly to their Connect User profile. **Note:** Optional service and/or account checks will require a lightweight integration between Connect and your organization's external system. At a high level, this Process authenticates the end user, and confirms ownership/eligibility of their mobile number and related account. Connect will return the relevant data to your client, so that it can direct the end user to a 3rd party partner application for targeted purchases. Successful Process execution means the end user is authenticated (and possibly subscribed) to the given service. This Process is highly flexible, and offers a variety of configuration points to tailor the user journey to your organization's desired use case. Documentation and APIs will be made available in the near future. Contact the MarketONE team ([connect@vindicia.com](mailto:connect@vindicia.com)) to learn more. ## Bug Fixes The following bugs have been fixed in this release: | Summary | Description | | - | - | | Soft Profile - Improper error response when calling the `POST /group/{groupId}/removeUser` API with the userID | If the client attempts to remove a Soft Profile User (or SP User) that does not exist in the specified Group, Connect returns an error message that indicates the userId field in the request body was null, even if it the field was not null. The proper error response should simply indicate that the specified User (SP or Regular) is not in the specified Group. | | Soft Profile - user can be created with unidentifiable information | When a client attempts to create an SP User, the `POST /group/{groupId}/addUser` API request must specify a display name to identify that end user. However, the API was allowing SP Users to be created without a name, and thus created unidentifiable or "empty" User entities. The proper API response should reject, and display the appropriate error message. | | Device authorization link redirects user to profile management page | After an end user clicks a device authorization link sent to their contact channel, the end user is successfully authenticated, but they are then redirected to a profile management page. Expected behaviour is to show a success message (that the relevant smart device was authorized), and to not redirect the end user. | | Change password shows blank page when current password is entered incorrectly | From Connect's out-of-the-box IdP and User Management UI, if the end user attempts to change their password, then they must enter both their current and new passwords. However, if the end user incorrectly enters their current password, a blank page appears. The expected behaviour is to simply show an error message that informs the end user of their mistake, and to allow them to retry their input. | ## Known Issues There are no known issues in this release. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.