v4.7.0 Release Notes
Feature Enhancements
Global
Feature | Description |
Property Settings: Manage Custom Components | A new feature, Manage Custom Components, has been introduced to Property Settings. This allows you to import the custom records created in different properties within your organization to your property. From this module, you will be able to sync your property or rollback the custom imports iteratively. This feature is only available to Organization Architects. |
Design: Business Requirements | You are now able to see the scope and status of each asset in the Business Requirement drawer. View business requirement, event, attribute, or data source details to see the scope and status of the associated item. |
Design: Business Requirements | Minor visual updates have been made to the event and attribute details screens within the Business Requirements drawer to create clarity. |
Bug Fixes
Global
Feature | Description |
Document: Data Layer | If you enabled 2 attributes with the same name, but different data layer paths, only one would be represented in the definition table. For example, in your implementation you may be using both the standard and merchandising attribute for “Content Title”. The merchandising attribute is located within the ‘items” array, whereas the standard attribute is not. Therefore, you should have two different definitions for Content Title in your Data Layer specification. You will now see both definitions in the table. This update is also reflected in Github. |