> ## 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.11 - Release Notes Release Date: November 30, 2021 ## Announcements This release includes the following announcement: Connect Care is a ready-to-use web application for your organization's customer support representatives (CSRs), also referred to as **Care agents**. Care agents can search for and view your existing Connect User profiles, and take certain actions against that profile on behalf of end users. You can now view the Connect Care user guide here: [Introduction to Connect Care](https://docs.vindicia.com/bundle/b_careGuide) ## Connect Features This section describes the key updates in this release. ### Enhancements to UXDR® Connect User eXperience Data Record (UXDR®) is an exhaustive data record that collects and organizes the details of an end user's interaction with the IdP service, as well as CRUD (create, read, update, delete) actions performed against Connect entities (for example, User, Runtime, Account). Connect feeds certain UXDR data through pipelines to different areas of the platform, most notably the user **[Activity](https://docs.vindicia.com/bundle/b_careGuide/page/c_userActivity.html)** screen in Connect Care. An organization's Customer Service Representatives (CSRs) can leverage this screen to review a selected User ID history, and take appropriate steps if needed. Connect primarily populates UXDRs with event data generated by Connect Process execution. For example, if an end user goes through a "Forgot Password?" flow, then the [Recover ID and Reset Password Processes](https://docs.vindicia.com/bundle/b_processGuide/page/connectProcessAPIGuide/processes/identityManagementProcesses/c_forgotPassword.html) generate event data as the end user goes through that flow. As of this release, UXDRs now also include the following data points: * Non-Process user management API actions (for example, PUT /user) generate UXDR entries, and those entries appear in the **Activity** screen * MarketONE's purchase subscription API (for example, POST /v1/subscription/purchase) generates UXDR entries, and those entries appear in the **Activity** screen * Custom Data API (for example, PUT /v1/user/\{userid}) generates UXDR entries, and those entries appear in the **Activity** screen ### Account Validation API Synchronizes Payment Methods in Connect The [POST /v2/account/validate](https://app.swaggerhub.com/apis/Amdocs_Media/MarketONE-CSP-Adapter/Released#/account/accountValidation) API, a MarketONE CSP Adapter API, uses an identifier (for example, mobile number) to query an external system for account details. The API synchronizes accounts and payment methods (for example, credit card, e-wallet) between MarketONE Partner and the external system. As of this release, this API call synchronizes the payment methods (for example, direct carrier billing, e-wallet) from the external account to the current Connect User's associated Connect Account entity. This enhancement is helpful in scenarios where the merchant wants to ensure that upon each successful authentication, the end user's Account entity is up to date both at the account level, and payment method level. ### Connect Entities include New Provisional Status All Connect data entities include a status parameter. Possible statuses are: * **activating** — the entity (or an authN ID, registered on a User entity) has been provisioned, but it is not yet ready to be used or accessed. The most common example is when new end user has onboarded with Connect, and their corresponding User entity (and their authN ID) has been created, but not yet activated. When the end user verifies their email address or mobile number, Connect changes the status for both that authN ID and the User entity. * **activated** — the entity (or authN ID) is ready to be used or accessed. * pending - similar to activating, this status applies to an authentication identifier (authN ID) that has been registered to a Connect User entity, specifically to replace an existing authN ID. This status signifies that the replacement authN ID has yet to be verified. * **suspended** — the entity is temporarily inaccessible (for example, suspended user due to irregular activities but can be activated by CSR agent at a later time) * **deactivated** — the entity permanently inaccessible, and has been marked for deletion (for example, end user requests CSR agent to "delete" profile, canceled billing account, broken CPE device) As of this release, a new provisional status is available. This status is for use cases where a customer purchases a subscription, but a service provider wants to grant them immediate access before the entitlements update is made on the backend. This update has been added to the [Entity Status](https://docs.vindicia.com/bundle/b_restApiGuide/page/dataModel/r_connectEntityStatus.html) topic in the Connect REST API guide. **Note:** Connect is extensible to support other project or custom-specific status needs, if required. ## Bug Fixes There are no major bug fixes in this release. ## 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.