Introduction of a configuration option to enable the Documents V2 modal functionality when uploading documents via the "Documents" component in the Overview tab and the "Documents" tab in the Entity Profile. To facilitate this there has been a change to the way Entity Profile is utilised within Configuration Exchange.
Set conditionality to filter the content that will appear on a generated document.
Enhance the Products Data Source, so that Related Parties of Products can be generated.
Control layout options such as page layout (Portrait/Landscape), Format and Scaling.
Create Custom Templates in a no-code design space, removing the need for technical HTML coding knowledge when designing templates.
Supergraph schema extended to support two new sets of data...
We released Product Risk Assessment in May of this year. The feature will assess the risk of products that were added/updated in the current journey. Some clients also want to included 'Onboarded' products in Product Risk Assessment so that migrated products can be assessed for the first time or previously assessed products to be reassessed against the latest configuration. Verified data is never directly changed, so we need to bring onboarded products into review in order for them to be assessed. We're introducing the 'Create Onboarded Product Drafts' Service task to automate the effort to include these products in the scope of a Product Risk Assessment. The task will only open drafts for Onboarded products that are Owned by the root entity and can be further configured with a Product Scoping Rule for scenarios where only a subset of onboarded products need to be re-assessed.
We have introduced new validations to set limits to number columns relative to other number columns. If an entered value meets a limit condition, the configured error message will be displayed. This capability is available for data groups in all contexts.
'Number' type Product Requirements can now be configured with 'Conditional Limit' validations which are configured relative to other number requirements in Product data ('Current Product' source) or Entity Data ('Related Entity' source) using operants. In addition, Product Requirements can also be used as a trigger for columns and conditional values in data groups linked to the same product. Further we've introduced the 'Current Product' source for Logic Engine conditions configured Trigger Conditions or Conditional Values. This source allows conditional behaviours to be driven based on product requirements in the product the datagroup is linked to.
This release includes: 1. Entity Level Access Layer logic, 2. BETA Tag to call out that full release is not yet deployed, 3. Sticky filtering when navigating away from page and back, 4. Filtering on system fields and lookup fields, 5. Search capability across all open Journeys based on search criteria, 6. Sorting for Journey Owner or Team selection.