Workflow Base Versus Workflow Licensed
Workflow Base features are available to all J1 Web users. Base permissions for the core product let users build workflows, associate workflows with individuals in the system, and view workflow progress. Licensed features enable users to automate updates and processes and associate them not only with individuals but also objects in the system (e.g., a building).
The following table describes the features available with the different versions.
Feature | Workflow Base | Workflow Plus | ||
|---|---|---|---|---|
Create, view, associate and remove, and delete workflows associated with individuals. This includes any workflow stakeholder, which could be internal individuals (have a system ID) and prospective students or event attendees (external individuals without a system ID). |
|
| ||
Include the following requirements in your workflows:
|
|
| ||
Make workflows sequential or concurrent, and allow for multiple workflows to be active and running simultaneously. | ![]() | ![]() | ||
Leverage rules to develop complex scenarios to meet various conditions. | ![]() | ![]() | ||
Use the Workflow Status feature allows Campus Portal-only users such as students, faculty, and staff associated with workflows to complete tasks and monitor workflow progress. | ![]() | ![]() | ||
Manage Jenzabar-provided and custom blocks on the module home page. | ![]() | ![]() | ||
Access audit histories to monitor and track changes and usage. | ![]() | ![]() | ||
Use a FormFlow form to initiate a workflow. | ![]() | ![]() | ||
Group and sequence interactions in automation plans to create a communication workflow. Automation can also include workflows. | ![]() | ![]() | ||
View, associate and remove, and delete workflows associated with objects such as budgets, courses, events, student conduct, FormFlow forms, etc.. | ![]() | |||
Collect digital signatures in workflows using DocuSign integration. | ![]() | |||
Include the following requirements in your workflows:
|
| |||
Use specialized workflow items to apply requirements such as data changes, form submissions, and document uploads. | ![]() | |||
Automatically associate a workflow with a group of people/objects imported into the system via the import processing queue. | ![]() | |||
Require a video as a part of a workflow. | ![]() | |||
Utilize internal commenting on workflows to facilitate collaboration and communication | ![]() |
