Calculated Time Periods can be used in Policy and Product Policy. A Calculated Time Period is a date subtracted from another date, this is different to a calculated date field, as the output is a time period. For example 25d.
Users can be suspended, this will prevent them from logging in until they are reactivated.
A new option has been introduced in the Related Parties task in Journey Builder that will allow the restriction of entity group associations to only be permitted to members of the entity group. Once enabled, the search will return results from verified members of the entity group in journey.
Aligning with recent enhancements to Policy, 'Date' requirements in Deals can now be configured with a validation time zone. This can be used with three validations: No Past Dates, No Future Dates and Disallow Todays Date. When setting a 'Default Value' for a date requirements as 'Default to todays date', the default value will be set according to the date in that time zone (when applied). If there is no value selected in 'Validation Time Zone', UTC will be used to determine the date in these circumstances. Note: The 'Date Range' validation in deal requirements can reference relative values like 'Today', however this will continue to follow UTC for the time being.
Aligning with recent enhancements to Policy, Product 'Date' requirements can now be configured with a validation time zone. This can be used with three validations: No Past Dates, No Future Dates and Disallow Todays Date. When setting a 'Default Value' for a date requirements as 'Default to todays date', the default value will be set according to the date in that time zone (when triggered). If there is no value selected in 'Validation Time Zone', UTC will be used to determine the date in these circumstances. Note: The 'Date Range' validation in product requirements can reference relative values like 'Today', however this will continue to follow UTC for the time being.
The extension of Teams Limits to 80 Teams; the extension of Access Layers Limits to 900 Access Layers & the extension of Dynamic Access Layer Rule Limits to 380 Rules.
The Integration Hub highlights all FenX integration services in one location for easy access and provides screens for technical users to troubleshoot any issues related to these integrations in their tenant. Includes initial support for Event Ingress and Event Notifications (Webhooks).
Document Persistence is now available for related party document requirements in the Related Parties task. Once enabled, any documents satisfied in the task for direct associations will persist to future journeys with an 'Approval Pending' status.
User Guide Reference: Document Management->Document Management Datakeys & Document Persistence Related Party Management->Related Party Management Configuration User Guide Related Party Management->Related Party Management Functional User Guide
Ability to reuse screening results from previous resolutions.