Work-Relay DocumentationCore Design and ExecutionProcessesProcess StepsProcess Step Settings: Notifications/Progress Component Settings

Process Step Settings: Notifications/Progress Component Settings

Along with customizing progress component for the whole process, user can modify it on the step level as well.

Click process step on the canvas(1). Expand "Notifications / Progress Component Settings" (2).

Chatter, Dates and Comments settings

To use chatter notifications make sure Chatter is enabled on in your organization

Each of the step level setting above have following options:

Use Process Settings - process step will behave according to the process level settings.

No - disables feature for the step even if it is enabled on the process level.

Yes - enables feature for the step even if it is disabled on the process level.

Buttons configuration

Standard Button(s) setup

Custom Label (3)- update standard button label

Color (4)- change color of  the standard button

Options (5)- (available in 4.1 release) options to be added to standard button. Options will be displayed under button, and will behave the same way standard button does. Button "Settings" opens "Option Visibility" formula popup (available in 5.0 release) to configure conditions (7).

 

Once clicked option value will be stored in Environment context object as {$Environment.ProceedOption}, which can be used when building conditions and formulas within the process.

Before Handler (6) - define behavior before proceed of the step. One is to choose from following handler types:

  • Form
  • Global Action
  • Action Group

NOTE: By default, following params are passed to standard button before handlers: cursor (process instance cursor id), workflow (process instance id), id (object id). For 'Form' handlers type both default and custom parameters can be accessed via form's $URL context object ({$URL.cursor}), for 'Action' and 'Action Group' handlers parameters can be accessed via $Variables context object ({$Variables.cursor})

Custom Parameters should use static values.

Below is example of before handler configuration. Clicking Proceed button will open '01. Files' form, 'test1' value will be passed as 'Test' parameter. Form will be opened within lightning component and 'Proceed' button will be displayed on the forn footer.

Custom Button(s) setup

Use Process Settings - step will display buttons according to the process level settings.

Do Not Use - step will not display custom buttons at all

Extend Process Settings - allows user to add custom buttons to the progress component. Buttons will only be displayed on particular step.

Type (8): Step level custom buttons can be of following types:

  • Form - opens Work Relay form (available from version 5.0 form can be for any data source object)
  • Action - executes global action
  • Action Group - executes global action group
  • Visualfoce page - redirects to Visualforce page
  • Visualforce Component - redirects to visualforce component
  • URL - redirects to specified URL

Access (9): One is to choose who will see custom button in "Access" picklist. It contains the following options where Managers" are Work-Relay process managers, "Admins" are Work-Relay process admins and "Assignee" is/are cursor assignee(s):

Parameters (10): By default, following params are passed to Form, Action and Global Action custom button handlers: cursor (process instance cursor id), workflow (process instance id}.

For "Form" handlers type both default and custom parameters can be accessed via form's $URL context object ({$URL.cursor}), for "Action" and "Action Group" handlers parameters can be accessed via $Variables context object ({$Variables.cursor})

NOTE: Custom parameters should use static values

Below is an example of step level custom button setup. Button "My Profile" will be visible for process admins and managers only, it will navigate user to the MyProfilePage Visualforce Page and will pass "TestParam" value as a parameter.

Additional Access

Here user can specify users/roles/profiles who should be able to mange process steps, whether they are step assignees or not.

Each of access type setting above have following options:

Use Process Settings - access rules will inherit the process level settings.

Use Default Settings - access to step will be the same as set to process by default.

Use Custom-Settings - access can be granted to different users/roles/profiles (11) in the popup appeared.

All Can Access.

Access types are:

  • Activate/Deactivate - grants permission to activate/deactivate a process instance and displays proper item in process instance menu (12) at Progress Component
  • Change Assignee - grants permission to change assignee on step where user is not an assignee or manager
  • Change Step - grants permission to change active step
  • Make Unique - grants permission to make process instance unique and displays proper item in process instance menu (13) at Progress Component
  • Proceed Step - grants permission to proceed/approve/reject tasks and enables proper buttons at Progress Component, Task manager, Planning Dashboard  and Progress Dashboard
  • Restart Branch - grants permission to restart branch and and displays proper item in process instance menu (14) at Progress Component
  • Restart Workflow - grants permission to restart the whole process instance and and displays proper item in process instance menu (15) at Progress Component
  • Update Pending Status - grants permission to make system try to update statuses of pending steps manually and enables proper buttons at Progress Component and Task Manager

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.