From version 8.2 users have the capability to seamlessly navigate to the Work-Relay Task Manager with pre-set filter parameters through a dedicated URL. This allows more functional integration with external systems and improves cross-system navigation efficiency.

Assumptions & Dependencies:

• The user has the necessary permissions and licenses to access the Work-Relay Task Manager.
• The external system integrating with Work-Relay can construct and send URLs using the required format.

The URL for the Task manager may be constructed in the following format:  https://my_server.lightning.force.com/lightning/n/WR_BPM__Dashboards_Lightning#%filters% where %filters% is a filters parameter specified in JSON format and encoded in Base64.

The Filters parameter has the following properties:

• filters - An array of objects with "name", "operator" and "value" properties.
• fliterLogic - A text expression which must correspond to logic rules, and operate with "filters" array elements indexes.
• view - The name of View for which the filter will be applied.

The example of filters parameter in JSON format:

{
  "filters": [{  
    "name": "task_title",
    "operator": "not equal to",
    "value": "test1"
  },{
    "name": "task_title",
    "operator": "equals",
    "value": "test2" 
  }],
  "filterLogic": "1 OR 2",
  "view": "All Tasks"
}

An example Base64-encoded filters parameter:

eyJmaWx0ZXJzIjpbeyJuYW1lIjoidGFza190aXRsZSIsIm9wZXJhdG9yIjoibm90IGVxdWFsIHRvIiwidmFsdWUiOiJ0ZXN0MSJ9LHsibmFtZSI6InRhc2tfdGl0bGUiLCJvcGVyYXRvciI6ImVxdWFscyIsInZhbHVlIjoidGVzdDIifV0sImZpbHRlckxvZ2ljIjoiMSBPUiAyIiwidmlldyI6IkFsbCBUYXNrcyJ9

The resulting Filters that will be applied to the Task Manager screen opened by that URL:

Standard Filter field names are the following:

• task_title (Task Title)
• task_assignee (Assignee)
• task_processName (Process Version Name)
• task_objectId (Record Name)
• task_objectName (Instance Name)
• task_risk (Risk)
• task_startDate (Start Date)
• task_dueDate (Due Date)
• task_priority (Priority)

Object Filter field names are built as lookup_{referenceName}.{fieldName}, where referenceName is the name of relationship in the WR_BPM__Flow_Instance__c object, e.g. lookup_Account__r.Name.