Feature Enhancements

Global

Feature

Description

Design : Business Requirements

You are now asked to confirm edits you save to Business Requirements, Apollo Events, Attributes, Data Sources, and Variables.

Design : Business Requirements

If you are an Agency/Organization Admin or Architect, you can delete Business Requirements that are still in a "Design Incomplete" status at the Agency/Organization scope. You may also delete Apollo Events, Attributes, Data Sources, and Variables that have an "Inactive" status at the Agency/Organization scope.

Design : Business Requirements

When you go to mark a Business Requirement as "Design Complete", validation now runs to ensure that only complete Tracking Items are associated with your new Business Requirement. This means that each Tracking Item as an associated Apollo Event, Attribute, Data Source, and Variable.

Adobe: You have an ecosystem config (variable) that is a Product Syntax eVar but the associated tracking item doesn’t have a collection path (containing array in the UI) for the Data Source Config (because the value should be in an array) - error expected

Adobe: You have an ecosystem config (variable) success event that is a product syntax event, but the associated tracking item doesn’t have a collection path (containing array in the UI) for the Data Source Config (because it must be in an array) - error expected

Adobe: If the variable (event or evar) is NOT product syntax and it is associated with a data source config that has a collection path (containing array in the UI)

Design : Business Requirement Templates

When you filter the list of Business Requirements based on those that are "Selected", if no Business Requirements are returned, all Business Requirements are displayed instead of none.

Adobe

Feature

Description

Design : Business Requirements

When you go to mark a Business Requirement as "Design Complete", extra validation now runs to ensure that the design of your Business Requirement meets Adobe Analytics tracking requirements. The following scenarios will trigger errors:

1) You have Variable that is a Product Syntax eVar or Product Syntax Success Event, but the associated Data Source doesn’t have a Containing Array.

2) You have a Variable that is a non-Product Syntax eVar or non-Product Syntax Success Event, but the associated Data Source has a Containing Array.

Bug Fixes

Global

Feature

Description

Design : Business Requirements

Reactivity updates have been made to expanded Business Requirements.

Adobe

Feature

Description

Deploy : Builds [Data Layer Docs]

Fixed a bug related to event sequencing messaging not being updated during data layer documentation deployments for certain Events.

Did this answer your question?