0
5.0.0
Australia, Zurich, Yokohama
Standalone Application
A task plan template enables business users to define repeatable tasks and other items required to complete a business process. A task plan template consists of template items that define tasks, including any child tasks or related items that are created when the template is applied.
Tracking of task plan template items
Templates have several template items which can be created for multiple business organizations. The data model enables the tracking of template items so that the template owner can see the status of generated tasks and follow up with the right person.
Task Dependencies
- The Template Dependencies tab on a task plan template record displays a node map of dependencies between template items. Users can create a dependency and then view the the dependency.
- Task dependencies can be cloned and created using the multi case generator.
- Admins and template authors can now configure advanced conditions on template items using referenced fields from parent or target tables. The Template Item Condition table supports both simple and advanced modes, enabling conditions based on related tables and mapping fields. Dynamic field visibility and mandatory validation are enforced, with error messages shown for missing required fields.
- Template authors can now define and propagate three new tracking fields for generated records. Template Item and Template Item Config forms expose item, execution, and business organization tracking fields, allowing authors to configure back-reference tracking for generated records. These fields are visible and editable in the UI, with dependent visibility and updated labels.
- Multi-case task dependencies and document associations are now supported at scale. Dependency relationships and document links are created for all generated records across multiple stores, with optimized insert paths to handle large volumes efficiently. Feature hooks for dependency and document association fire exactly once per execution after all workers finish.
- Clone feature now supports affected stores and dependencies. When cloning a template, all related features—including affected stores, scheduling details, and dependencies—are cloned, ensuring complete plans without manual setup. Cloned dependent tasks are maintained and visible in relevant tables.
- Document references are maintained during task generation and template cloning. Generated tasks refer to documents attached to template items, and cloned templates preserve document associations.
- Cascade confirmation popup added for template item configuration changes. When updating configuration fields, admins are prompted to cascade changes to existing template items, ensuring consistent tracking across linked items.
- Workspace and platform UI layouts updated for advanced condition fields. New fields are added to form and list layouts, with conditional visibility and proper spacing across all views.
- White papers available for multi-case changes and Task Plan Template features. Comprehensive documentation covers design, functionality, and usage for stakeholders.
Not applicable for this application version.
This store app does not have any dependencies.