> ## 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 2020.12 - Release Notes Release Date: December 02, 2020 ## Announcements There are no announcements for this release. ## Connect Features This section describes the key updates in this release. ### Admin User and Admin Role Creation APIs Connect includes a robust set of Admin APIs to configure and administer various aspects of the Platform. The library includes APIs used exclusive by internal admins (that is, Connect internal system administrators) as well as tools available to external admins (that is, customer employees who manage their company's instance of the service). **Note:** Certain Admin API functionality is built into the Connect Admin web application. Other APIs, currently available only at the API level, are marked for implementation into Connect Admin UI at a future date. The Admin API library now includes new endpoints that enable an authorized admin user to easily create and manager additional admin users. These APIs provide the following capabilities: * Create, manage, deactivate admin users. * Send emails to newly provisioned admin users, so they can activate their Admin ID (that is, set their own password). * Create, manage, deactivate admin roles. These APIs are roadmapped for implementation in the Connect Admin web application at a future release. However, in the interim, Connect provides an intuitive, user-friendly command line tool to execute the endpoints without the need to run these functions directly through the API. Admin Manager ### Associate Billing Account Returns Additional Context for End User The Associate Billing Account to User ID Process queries a service provider's external Billing or Operations Support Service (B/OSS) for an end user's specified account data. If successful, the Process takes information and maps it to a Connect Account data entity (including any Connect Subscription and Feature entities, depending on the integration between Connect Cloud and the B/OSS). During the Process, the new Account must be associated to a Connect Group of which the current end user is the "Group Primary." The following conditions apply: * If the user does not have a valid Connect Group, the Process automatically creates one, set the user as Primary, and associates the Account to that Group. * If the user has one valid Connect Group, the Process automatically associates the Anew Account to that Group. * If the user has more than one valid Connect Group, the Process prompts the user to select one, and returns a list of applicable Groups. The Process response specifies each Group entity by their unique id number. As of the Connect 2020.11 release, the Process now returns a list of User-to-Group associations when the user has more than one applicable Group. Each result in the list includes: * The Connect Group, including its properties and attributes. * The specific association (including permission flags) between the current User and that particular Group: **Example** ``` "processId": "ec90ed2c-eca9-42de-9fbc-a81506c5d1e8", "displayMessage": "Please select a group", "stepName": "GroupSelectionPrompt", "parameters": { "groupId": "Long" }, "output": { "groups": [ { "association": { "flags": { "mint.permission.delete": "true", "mint.permission.read": "true", "mint.permission.write": "true", "mint.role": "mint.role.primary" } }, "status": "activated", "displayName": "Jane Smith Family Household", "id": 328494, "attributes": { "service.attribute": "A", "com.uxpsystems.mint.group.MaximumNumberOfMembers": "5", } }, { "association": { "flags": { "mint.permission.delete": "true", "mint.permission.read": "true", "mint.permission.write": "true", "mint.role": "mint.role.primary" } }, "status": "activated", "displayName": "Jane's Extended Friends and Family", "id": 330001, "attributes": { "service.attribute": "B", "com.uxpsystems.mint.group.MaximumNumberOfMembers": "5", } } [ } ``` This enhancement ensures that, within the context of this Process execution, the client has all the relevant information to provide the end user with clear, meaningful choices. ### Associate Billing Account Process Enables Creation of Separate External Billing Account Process now allows for the creation of an external billing account (through Vindicia Subscribe) for each end user account retrieved from the customer's back-end system. For customer's that adopt both Vindicia MarketONE Connect and Vindicia MarketONE Subscribe products, the result is a stronger integration between the two products. ### Streamlining Code Platform code was significantly streamlined to improve performance and overall user experience. Improvements include, but are not limited to, the following: * Technology upgrades. * Batch cleanup jobs. * Removing parameters that are not used often. ## Bug Fixes The following bugs have been fixed in this release: | Summary | Description | | - | - | | User search in care portal returns results with no delay | When searching for a user in the Care Portal, the results are displayed with no delay in loading. | | Admin Portal user can see all values of access token | In the Admin Portal, the "Access Token Expiration" field accommodates more than 3 digits so that the admin user can see all values of the access token. | | Helpful message when user creates ID using invalid password | In the IdP UI, when a user creates an ID but enters an invalid password, they will receive a helpful message that explains what needs to be adjusted so that the user is aware of the actual issue with their invalid password. | ## Known Issues This release has the following known issue: | Summary | Description | | - | - | | Sign out option not visible from Care Portal | In the Care Portal, once a user has signed in and refreshes the page, the sign out option is not visible. | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.