Resolution Rule Internal Error Detection and Remediation to Trim Task Count

Resolution rules are a single pass thing where the single mode of error detection is “not there”. Using an OA as an example, a request is sent for a USER_ID maps person.user_id to it.  If nothing maps, then something phony is returned to trigger a loop in the workflow.  Then a conditional task, possibly a delay task, maybe some other task or two, then the OA is retried.  So there is, at a minimum 3 to 5 tasks associated with each OA (including the OA).  Using the min of 3 tasks, multiply that by 10 OA’s in a workflow, and the workflow getting hit 100 times a day.  That’s 2000 extra tasks a day added to the system!  Multiply by a year, or 5 years, well you see the point.  This fills up IN_IS_WORDS, makes the task row count unnecessarily huge, and slows down stencil deletion.  So why not put error detection/retry actually within resolution rules where applicable.

  • Guest
  • Jul 27 2017
  • Reviewed by Alemba Product Manager
  • Attach files