Record data, active processes, and process reports

Question

I have a requirement to add a new field, contained in a record, to an existing process report. In an interface a gridField with filters is used for displaying the task data, but cannot find a way to get this data in a way that makes it available for both new and previously started active processes. 
 
 Process Report is tasks per process model 
 Process Report is tasks per process model 
 Process uses Records for data management () 
 Requirement to get additional data from the Process into the Process Report 
 Additional data is a value found in the Record 
 Process reports cannot index Records 
 Less than ideal solution has been to add process variables for any data point needed from the record 
 These single data point process variables can then be seen in the process report 
 Process report is displayed in an interface using a a!gridField() 
 Data for the gridField is pulled using a!queryProcessAnalytics() 
 a!queryProcessAnalytics() uses logicalExpressions in an a!query() to filter data

Query filters fields found in the task report for filtering. e.g. "field: "c8" 
 Adding another process variable to add data as a new field in the process report will work for all processes started after it's addition 
 Previously started active processes do not have access to this new process variable 
 Editing the active process to add and set the process variable makes the new value available in the active process 
 Editing the active process to add and set the process variable does not update the process report with the newly added data

Is there a way to filter data using a field in Record contained in the process report? 
 Is there a way to add and set new process variables in active processes so they will show in the process report?

srikanthreddy9369 · Answer

Let's address your questions step by step:

Filter Data Using a Field in a Record in the Process Report: 
 It seems you want to filter data in your process report using a field from a record. The a!queryProcessAnalytics() function is typically used to query process-related data, but it may not be directly able to access data in records. If you want to filter or include data from a record in your process report, you may need to consider alternative solutions. Here are a couple of options:

Custom Query: Instead of using a!queryProcessAnalytics() , you can create a custom query by directly querying the records containing the data you need. You can then build a report that combines data from both the process and the records in your interface.

Process Variable: If you must stick with a!queryProcessAnalytics() , you can use process variables to store the data you need from the record. When a task in the process starts or completes, update the process variable with data from the record. The process variable can then be included in the process report.

Adding and Setting New Process Variables in Active Processes: 
 You mentioned that adding new process variables works for new processes but not for previously started active processes. This behavior is expected because process variables are typically set at the time of process initiation and are not retroactively applied to existing processes. There are a few ways to deal with this:

Reinitialize Active Processes: If possible, you may consider reinitializing existing processes to bring them in line with the updated process definition. This can be a manual effort and should be done with caution, as it may disrupt ongoing work.

Alternative Data Storage: If you need to access the new data for historical processes, you might consider alternative data storage, such as a dedicated database or external system, that can be queried for historical information.

Hybrid Approach: You could implement a hybrid approach where you continue using process variables for new processes and consider an alternative method (e.g., custom queries) for accessing historical data from the records.

In conclusion, addressing your requirements may require a combination of solutions, including custom queries and potentially changes to process initialization. It's essential to consider the trade-offs and the impact on existing processes when making such changes. The feasibility and best approach can vary depending on the specifics of your system and requirements.