Jenzabar Campus Portal Features Help Hub

Workflow Feature Content

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

You can add, remove, rename, and reorder the FormFlow - Workflow features on the appropriate Campus Portal pages.

  1. Log in to the Campus Portal as an administrator.

  2. Select Site Manager from the profile drop-down options.

  3. Click the Tabs tab.

  4. Click Edit next to the tab name where your page is located.

  5. Under Portlets Available to Pages in this Tab, select the portlets and features that are to be made available for the addition to the page.

  6. Click Save changes.

  7. Click Exit.

  1. Log in to the Campus Portal as an administrator.

  2. Access the page where you want add the FormFlow - Workflow feature.

  3. From the Admin Toolbar, click Options.

  4. Click Add a new feature to this page.

  5. Click General Purpose features to view a list of the general purpose features.

  6. Click FormFlow - Workflow.

  7. Make any additional changes to the page name, layout or features on the page.

  8. Click the Back to... link to return to the feature page.

Note

When you choose to add the FormFlow - Workflow feature as its own page, it will appear as a link on the sidebar for the currently selected tab.

  1. Log in to the Campus Portal as an administrator.

  2. Select the tab where you want to add the FormFlow - Workflow feature.

  3. From the left-hand side, click Add a Page.

  4. Click General Purpose features to view a list of the general purpose features.

  5. Click FormFlow - Workflow.

  1. Log in to the Campus Portal as an administrator.

  2. Navigate to the page with FormFlow - Workflow.

  3. From the Admin Toolbar, click Options.

  4. Click the link for the feature you want to remove.

  5. Click the Delete... or Stop sharing... button on the confirmation pop-up. If a second pop-up window appears, click the Delete button.

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

Before users can access and manage FormFlow - Workflow, they must be granted administrative permissions. These permissions let users set up Workflow tracks.

Grant Administrative Access to Workflow
  1. Log in to the Campus Portal as an administrator.

  2. From the profile drop-down options, select Site Manager.

  3. From the side menu, click Global Portlet Operations.

  4. Click J1 FormFlow - Workflow.

  5. Click the button in the Allow Access column to toggle it to Yes for the global user groups that will have permission to administer workflow tracks.

  6. Click the button in the Allow Access column to toggle it to No for the global user groups that will not have permission to administer workflow tracks.

  7. Click Save.

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

Any user who will be approving document submissions that are sent to a Workflow track will require access to see the Workflow feature pages. Only administrative users who will be managing Workflow tracks need permissions to manage the Workflow feature pages. They only need to belong to a Campus Portal user group with permission to manage Workflow.

Grant Access to Workflow Pages and Additional Permissions
  1. Log in to the Campus Portal as an administrator and navigate to the page with FormFlow - Workflow.

  2. From the Admin Toolbar, click Access.

    Tip

    A green check mark indicates a Campus Portal role was granted permission to access the page and a red circle indicates the role was not granted permissions to access the page.

  3. Click on the Campus Portal role you are setting up permissions for.

  4. If the role has not already been granted access to the page, click the Show this page to [the role] link.

  5. To grant administrative privileges to a Campus Portal role, click Allow this role to manage this page.

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

Note

Any database connections you set up are available to all forms within any FormFlow or Workflow instance in your Campus Portal.

Database connections let you exchange information between your form and the J1 database, a custom ICS NET table, or your own custom table. Database connections use ODBC connection strings. When J1 Desktop and the Campus Portal are installed, a J1 database connection is created for you based on your Campus Portal Site Manager settings. Jenzabar recommends verifying the connection string before using the form, and deleting, updating, or creating different connections as needed.  If you import a form and no database exists, the feature will create a database but will not provide a connection string. An administrative user will have to manually update the connection string.

Caution

Using a standard ODBC connection string to SQL Server requires that TLS 1.0 be enabled on the server. Some security standards require that TLS 1.0 and TLS 1.1 be disabled on the server and force the use of TLS 1.2.

Connection strings with the driver set to “SQL Server” will not work when connecting to a server with TLS 1.0 disabled. To fix the issue and ensure compatibility moving forward, the connection string driver should be updated to reflect the current version of SQL Server Native Client that is installed on the Campus Portal web server. An example connection string is below:

DRIVER={SQL Server Native Client12.0};
SERVER=myserver;UID=te_pgmr;PWD=password;
DATABASE=TmsePrd;Application Name=FormFlow - Forms;

This currently only impacts customers that have the requirement to disable TLS 1.0. However, it is recommended that all clients follow this practice to avoid compatibility issues moving forward.

Tip

Ensure the user specified in the database connection string has permission to access the objects defined in your data sources, mapped statements, or stored procedures.

Additional Resources

SQL Server Connection Strings