Table of Contents

Search

  1. Preface
  2. Informatica MDM - Product 360 10.5
  3. User Experience
  4. Platform Enhancements
  5. Changes in Packaging and Supported Platforms

Escalation Process for Workflow Tasks

Escalation Process for Workflow Tasks

As the idea of workflow tasks is to have them permanently active and objects simply flowing through them with their own independent lifecycle, the escalation of a whole workflow task is not a common practice or use case. Still, we have found some customer cases where the project design demanded to set the deadline or escalation date on workflow tasks. Hence, we've implemented a simplified escalation process for workflow tasks on the task level. If the deadline or escalation date is met, all objects currently included in it will be directly assigned to the substitute/responsible person and the deadline/escalation date will be reset to keep the workflow task clean for the next incoming objects.
There is no email notification about escalations and the escalated workflow task assigned to the responsible person will get its date reset only after the background job for escalated tasks is being executed.
Further note: If you follow the best practice implementation with the STEP workflow accelerator we ship with the software, you will now have another method for escalations by using classic tasks in the workflow. See chapter "Step workflow accelerator enhancements" in this document.

0 COMMENTS

We’d like to hear from you!