Filters and Processes

Goal:  User can apply filters to all or some Process definitions. 

• Allow adding filters to all or some processes 
• Allow adding additional process in a selected filter.  
• Allow removal of individual or multiple process definitions from applied filters without removing entire filter.
• Display process name/set display name in filter snippet  

 

Adding Processes to Filters

• Filters are added / removed via a multi select dropdown 
• Processes which differ in structure due to version are considered separate processes and not available for multi selection in combination in Flow Node or variable filters
• Simple filters such as the process instance state - must now display a modal to allow for process selection 
• Variable filters are applied first by selecting the process definition

 

Removing Processes from Filter modals
• Processes can be removed from the input via the pill remove icon or the input field remove icon
Any configuration is removed along with the process. 

 

Removing Process definitions 
• When a process is removed, it is also removed from any filters it is a part of 
Filter snippet information is updated: The no of processes reflects the current state and the tooltip updates the process name.
• If a filter is the only one for that process, this filter is also automatically removed. 

 

Adding new process definition
• If filters are already applied, modal displays to ask user if they want to apply possible current filters to the new process 

 

Filter snippet

• In single process reports no process name seen in filter snippet
• Multi process reports display the name of the process / No. of processes (Discuss in kickoff)
• When a Process definition is added or removed - the filters react accordingly- as specified above.
• DESIGN: replace close icon with close-small icon (already done?) 
• Error displays - see design

 

Multiple process definitions with structural differences in version

When selecting process definitions to add Flow Node filters on, multiples of the same process with differing versions could have different diagrams. 
Check if process models are the same by checking if names of flow Nodes match. 
Match = Filters requiring Flow Node selection can be applied to both at once. 
Not a Match = 
a) allow applying Filter - but if the specific selected Node is missing, show error in the resulting filter snippet (Similar to what we do when version is changed now. ** Prefer A, most likely changes will be small. 
b) If there is a structural difference - consider these as completely different processes. 

If it is not possible to ascertain if the process diagrams match - consider allowing the addition of the filter anyway, and throw an error after. 

**:Discuss with team.

 

Multiple process definitions with differences in variables

All variables are pulled in for all versions. 
If a variable appears only in version 10 of a process, it will still be available for selection in the filter modal for a V1 process selection - this filter will simply contain no data for the result. 

• Differences between process versions are not reflected in the variables/identities. All variables and identities are available at all times, and new ones may appear at any time. 

 

Multiples of the same variable name

Often the same variable names appear across processes, though they are not necessarily the same variable.  
In such cases we treat them as the same and only have one option per name. 
If we find there are many requests for differentiation, we can allow custom setting of variable names, or some other solution. 

 

 

Filtering bulk processes 

It is possible to create a Bulk Process report - where all processes definitions available in home or in a Collection are used in the Report - Limited filters are allowed for these bulk process groups

View more -> https://jira.camunda.com/browse/OPT-5018 

 

 

View Prototype movie :Prototype
 
Notes: WIP Meeting notes to facilitate discussions