Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A permanent workflow is a workflow that needs to run runs continuously on a consistent schedule based on business needs or requirements. For example, you may wish to create a workflow that runs once a day and sends an e-mail alert to a manager if any of their direct reports had not logged into the system in a certain number of days. In EmpowerID, a permanent workflow can only run on one worker role container (server) at a time, and only one instance of the permanent workflow can run at a time. EmpowerID ships with a number of permanent workflows out of the box, but you can create new ones in Workflow Studio as needed.

EmpowerID uses default settings for each workflow if no configuration is applied. Default settings are defined on each workflow View One page. To view the View One page for a permanent workflow, navigate to the Find Permanent Workflows page by expanding Infrastructure Admin > EmpowerID Servers and Settings and selecting Permanent Workflows from the navbar. Once on the Find Permanent Workflows page, click the Display Name link for the workflow whose View One page you want to view.

...

Key Points

✔ Permanent workflows are managed by the Permanent Workflow Job

Image Modified

✔ At least one server must be running this role for any permanent workflow to function.

Image Modified

✔ Each permanent workflow can be enabled/disabled and configured individually.

Image Modified

Insert excerpt
IL:External Stylesheet
IL:External Stylesheet
nopaneltrue

Info

Key Takeaways:

  1. A permanent workflow needs to run continuously on a consistent schedule.

  2. A permanent workflow can only run on one worker role container (server) at a time.

  3. New permanent workflows can be created in Workflow Studio.

Info

Related Docs Topics:

Permanent Workflows

Creating Permanent Workflows

Easy html macro
theme{"label":"solarized_dark","value":"solarized_dark"}
contentByMode{"html":"<!doctype html>\r\n<head>\r\n<link href=\"https://cdn.jsdelivr.net/npm/bootstrap@5.1.0/dist/css/bootstrap.min.css\" rel=\"stylesheet\" integrity=\"sha384-KyZXEAg3QhqLMpG8r+8fhAXLRk2vvoC2f3B09zVXn8CA5QIVfZOJ3BCsw2P0p/We\" crossorigin=\"anonymous\">\r\n</head>\r\n<nav aria-label=\"...\" class=\"overflow-hidden\">\r\n <ul class=\"pagination justify-content-center\">\r\n <li class=\"page-item\">\r\n <a class=\"page-link\" href=\"https://dotnetworkflow.jira.com/wiki/spaces/EIDIGACore/pages/2387740451/Server+Roles+and+Jobs\" target=\"_top\"> &laquo; &nbsp;&nbsp;Previous</a>\r\n </li>\r\n <li class=\"page-item active\" aria-current=\"page\">\r\n <span class=\"page-link\">Current</span>\r\n </li>\r\n <li class=\"page-item\">\r\n <a class=\"page-link\" href=\"https://dotnetworkflow.jira.com/wiki/spaces/EIDIGACore/pages/2387740584/UI+Page+Structure+and+Terminology\" target=\"_top\"> Next&nbsp;&nbsp; &raquo;</a>\r\n </li>\r\n </ul>\r\n</nav>","javascript":"","css":""}

...