--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined Service Catalog release notes for upgrades from Australia to Brazil # Combined Service Catalog release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Service Catalog Release Notes for Upgrades from Australia to Brazil This consolidated release notes document provides ServiceNow customers with essential information about Service Catalog updates from the Australia release through to the Brazil release. It includes new features, changes, deprecations, and important upgrade considerations to help you prepare and manage your upgrade process effectively. Show full answer Show less ## Key Features * **Multi-user Editing of Catalog Items (Australia):** Assign multiple users via the Secondary owner field to edit catalog items collaboratively, enhancing catalog management flexibility. * **Request Fulfillment Stages (Australia):** Define distinct stages and states within fulfillment steps in Catalog Builder, allowing requesters to track progress clearly. * **Advanced UI Policy Configuration (Australia):** Use scripting and multiple actions in UI policies within Catalog Builder to create more complex and dynamic catalog items. * **Variable Visibility on Multi-Row Variable Sets (Australia):** Control visibility of variables on grid layouts with a "Hide on grid" option for better form customization. * **Custom Update Set Prefix (Australia):** Standardize update set names using the glide.sc.cb.item.updatesetprefix property to improve update set identification and tracking. * **Configurable Subscription Access Enforcement (Brazil):** Enforce user criteria on catalog item access even with parent service subscriptions, configurable via glide.sc.catalogitem.subscriptionenforcement property for tighter access control. * **Migration to Angular Portal (Brazil):** Transition from Core UI to Angular portal for catalog experience on upgraded instances by installing the com.glideapp.servicecatalog.ui16portal plugin, providing a modernized interface for requesters. ## Changes * **UI Policy Management (Australia):** UI policies must now be created and managed via the dedicated UI Policy tab in Catalog Builder; the previous UI policies icon option has been removed. * **Brazil Release:** No changes reported in this release. ## Deprecations * **Removal of Catalog Roles from Request Management ACLs (Brazil):** ACL records for request management tables no longer use catalog or catalog admin roles for access control. Access is now governed solely by request management roles, impacting users with only catalog-related roles. ## Activation and Requirements * Service Catalog is a ServiceNow AI Platform feature and is active by default in both Australia and Brazil releases. * No additional or changed browser requirements, localization considerations, or accessibility updates were noted for these releases. ## Practical Impact for ServiceNow Customers By upgrading to Brazil, customers gain enhanced control over catalog item editing, fulfillment tracking, and UI policy complexity, improving catalog management and user experience. The migration to the Angular portal modernizes the request interface. The introduction of configurable subscription enforcement strengthens security and access governance. Changes to ACL roles require review of user permissions to ensure appropriate access post-upgrade. Consolidated page of all release notes for Service Catalog from Australia to Brazil. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Service Catalog release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Australia to Brazil. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Service Catalog to Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-servicecatalog-summary__entry__2} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for Service Catalog. {#dfrn3-servicecatalog-summary__entry__8} | Release | Release notes | |-|-| | Australia | [Enable editing of catalog items by multiple users](https://www.servicenow.com/docs/access?context=set-up-cat-builder&family=australia&ft:locale=en-US) : Enable other users, who are added to the Secondary owner field, to edit catalog items. To enable these users, add people to the Secondary owner user-criteria field in the sc_cat_item and sc_cat_item_producer tables, enabling others to make changes to catalog items owned by another person. [Define and add stages in fulfilment step](https://www.servicenow.com/docs/access?context=configure-flow-sf-flow&family=australia&ft:locale=en-US) : Define and add distinct stages and states in the fulfillment step when building a catalog item in Catalog Builder, enabling requesters to view the request-related current stages and their states together. [Use advanced UI policy capabilities in Catalog Builder](https://www.servicenow.com/docs/access?context=set-up-cat-builder&family=australia&ft:locale=en-US) : Configure catalog UI policies with scripts and multiple catalog UI policy actions in the Catalog Builder to facilitate the creation of complex catalog items. With these enhancements, catalog item creators can confidently take advantage of advanced options, simplifying and speeding up the entire catalog development process. [Configure variable visibility on multi-row variable set grids](https://www.servicenow.com/docs/access?context=service-catalog&family=australia&ft:locale=en-US) : Configure the visibility of a variable on the grid layout within a multi-row variable set (MRVS) for a catalog item by using the Hide on grid check box. By default, the check box is not selected. [Configure update set prefix](https://www.servicenow.com/docs/access?context=service-catalog&family=australia&ft:locale=en-US) : Configure the update set prefix to set a custom name for the update set that gets generated automatically in Catalog Builder, making update sets easy to identify and track for consistency. Use the glide.sc.cb.item.update_set_prefix property to standardize update set names. By default, the property uses the value CB_${template_name}_${item_name}_${timestamp}. | | Brazil | [Configurable subscription access enforcement for catalog items](https://www.servicenow.com/docs/access?context=r_ServiceCatalogProperties&family=brazil&ft:locale=en-US) : Control whether service subscriptions can bypass "Available for" user criteria on catalog items using the `glide.sc.catalog_item.subscription_enforcement` property. This setting verifies that only users meeting specific criteria can access items, even with a parent service subscription. The property controls this behavior with the following two modes: * require_criteria: Prevents access to users who don't meet the item's criteria, even if they are subscribed to the parent service offering. * allow_bypass: Preserves existing behavior that means users gain access through the "Available for" user criteria. "allow_bypass" is a default value. [Migration from Core UI to Angular portal](https://www.servicenow.com/docs/access?context=migrate-core-ui-to-angular-catalog-exp&family=brazil&ft:locale=en-US) : Migrate from the Core UI catalog experience to the Angular portal using the `com.glideapp.servicecatalog.ui16_portal` plugin, but only for upgraded instances. Administrators on upgraded instances must install the` com.glideapp.servicecatalog.ui16_portal` plugin to move from the Core UI catalog experience to the Angular portal. On new instances, the plugin is active by default. Requesters view the Angular portal instead of Core UI while requesting a catalog item. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing Service Catalog features. {#dfrn3-servicecatalog-summary__entry__14} | Release | Release notes | |-|-| | Australia | [Use UI Policy tab to add and manage the UI policies](https://www.servicenow.com/docs/access?context=create-ui-policies-in-catalog-builder&family=australia&ft:locale=en-US) : Previously, when creating or editing a question in Catalog Builder, users could define UI policies or dynamic behavior by selecting the UI policies icon (). This option has been removed. Now, users must directly use the UI Policy tab to add and manage the UI policies (actions, conditions, scripts, and other required details) to the catalog item. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some Service Catalog features or functionality were removed. {#dfrn3-servicecatalog-summary__entry__20} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some Service Catalog features or functionality were deprecated. {#dfrn3-servicecatalog-summary__entry__26} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | Removal of Catalog Roles from request management ACLs : ACL records on request management tables and fields no longer grant access based on the catalog role or the catalog admin role. ACL records for tables owned by request management, such as Request \[sc_request\] and Requested Item \[sc_req_item\], no longer include catalog-related roles in the list of required roles. Each ACL record retains at least one request management role, so the list is never empty. Users who have only a catalog-related role and no request management role can no longer use these ACL records to access request management tables or features. Another ACL record on the same table might still grant access through a different role. This change affects only the ACL records that the catalog team owns. | [ ] ## Activation information Review information on how to activate Service Catalog. {#dfrn3-servicecatalog-summary__entry__32} | Release | Release notes | |-|-| | Australia | Activation information : Service Catalog is a ServiceNow AI Platform feature that is active by default. | | Brazil | Activation information : Service Catalog is a ServiceNow AI Platform feature that is active by default. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Service Catalog we have noted them here. {#dfrn3-servicecatalog-summary__entry__38} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Service Catalog we have noted them here. {#dfrn3-servicecatalog-summary__entry__44} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Service Catalog, such as specific requirements or compliance levels. {#dfrn3-servicecatalog-summary__entry__50} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Service Catalog we have noted them here. {#dfrn3-servicecatalog-summary__entry__56} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Service Catalog we have noted them here. {#dfrn3-servicecatalog-summary__entry__62} | Release | Release notes | |-|-| | Australia | * Enable other users, who are added to the Secondary owner field, to edit catalog items. * Let your requesters view the stage and the state of their requests while using the service fulfillment step. * Configure catalog UI policies with scripts and multiple catalog UI policy actions in the Catalog Builder to facilitate the creation of complex catalog items. * Hide or show variables on a grid layout of the multi-row variable set (MRVS) for a catalog item. * Configure the update set prefix to set a custom name for the update set that gets generated automatically in the Catalog Builder. See [Service Catalog](https://www.servicenow.com/docs/access?context=service-catalog&family=australia&ft:locale=en-US) for more information. | | Brazil | * Develop comprehensive service catalogs to empower users with self-service capabilities. * Tailor portals to let users request a range of catalog items, including services and product offerings. * Standardize request fulfillment processes to verify the accuracy and availability of items within the catalogs. See [Service Catalog](https://www.servicenow.com/docs/access?context=service-catalog&family=brazil&ft:locale=en-US) for more information. | [ ]