New

Campaigns now support metric bundling and unified workflow management
Users can group related metrics into campaigns, so all metrics within a campaign move through data collection, review, and approval as a single unit. Shared properties such as start date, due date, entities, attachments, and project-level comments are managed at the campaign level.
Streamlined campaign UI and bulk actions
The campaign workspace provides a scalable interface for managing up to 30 metrics across 17 entities, with dropdown filters and minimized scrolling. Users can bulk submit and approve metric data tasks, and tick marks indicate completion status for campaign setup steps.
Automated campaign cycle and task management
Campaign cycles are created and managed based on campaign state and schedule. Campaign and cycle states update automatically as underlying tasks progress, and due date changes at the campaign or cycle level propagate to all related tasks.
Configurable data owner and approval workflows
Admins can assign data owners and configure single-level or multi-level approval workflows for campaigns, with validation to prevent conflicts between data owners and approvers.
Enhanced metric data task (MDT) lifecycle and UI
Metric data tasks now support campaign-driven scheduling, custom due dates, and read-only data fields for calculated metrics. The MDT UI includes new filters for project and task, project details on the ribbon, and approval page updates for bulk actions.
Threshold variance calculation and configuration
Metric definitions now support configurable variance base values and improved variance calculation logic, including handling of missing or overridden data and immediate client-side updates.
Support for calculated metric definition (CMD) task creation and approval
Tasks are now generated for calculated metrics, enabling review and approval before data is used in disclosures or reporting. CMD recalculation occurs in real time when source data changes, and approval flows are fully supported.
Naming conventions for campaign cycles
Campaign cycles are named according to frequency (daily, weekly, monthly, quarterly, semi-annually, annually) for clarity and consistency.

Changed

Campaign and metric data task logic updated for campaign-driven scheduling
When a metric is part of an active, published campaign, its data collection schedule, due date, and lifecycle are governed by the campaign rather than the individual metric definition. Updates to campaign cycles or due dates are reflected across all associated tasks.
Bulk state updates for campaign cycles
Campaign cycles automatically transition to "Approval" or "Closed" states based on the status of underlying tasks, eliminating manual intervention.
Validation and filtering improvements for campaign setup
Entity selection now prevents duplicates, and the system shows an error message when a user attempts to add an entity already present in another campaign with matching group, frequency, and calendar. Bulk submission is disabled by default for new campaigns.
Metric data logic refined for task state and value propagation
Metric data values populate immediately when child tasks complete, but the state remains "in-progress" if tasks are enabled. CMD recalculation and approval flows are updated so task states and value propagation stay correct.
Approval configuration UI updated
The data owner and approval configuration page now supports adding multiple approval levels, error handling for empty or conflicting values, and automatic clearing of multi-level settings when switching to single-level approval.
Field-level access controls and UI policies updated
Data owner and approver fields are now managed at the campaign level, with updated ACLs and UI policies to enforce correct permissions and field behaviors.