Create a new Microsoft Excel file.

Type in the following values in the top line:

• Job ID

• Name

• Status

• Progress

• Volume Loaded

• Volume Exported

• Operation Number

• Operation Name

• Operation Progress

Select the newly added values and from the Styles section click Format as Table and select any table format.

Check the option My table has headers.

Save the file on One Drive under the name Rampiva Job Tracker.

Open Microsoft Power Apps at https://make.powerapps.com/

Select the Flows tab.

Create a New flow of the type Instant cloud flow.

Name the flow Update Rampiva Tracker.

Select the trigger When an HTTP request is received from the Request app.

Expand the step details and select Use sample payload to generate schema and paste the following content:

{
  "id":"aaa-bbb-ccc",
  "name":"Sample Job Name",
  "status":"Running",  
  "progress": 10.33,
  "volumeLoaded": 123.45,
  "volumeExported":50.01,
  "currentOperationNumber":"2/10",
  "currentOperationName":"Add Evidence",
  "currentOperationProgress": 70.01
}

Add a New step with the action Get a row, from the Excel Online (Business) app.

In the Location field, select OneDrive for Business.

In the Document Library field, select OneDrive.

In the File field, browse to the Rampiva Tracker.xlsx file create previously.

In the Table field, select Table 1.

In the Key Column field, select Job ID.

In the Key Value field, add the dynamic content id from the When a HTTP request is received step.

Add a New step with the action Update a row, from the Excel Online (Business) app.

In the Location field, select OneDrive for Business.

In the Document Library field, select OneDrive.

In the File field, browse to the Rampiva Tracker.xlsx file create previously.

In the Table field, select Table 1.

In the Key Column field, select Job ID.

In the Key Value field, add the dynamic content id from the When a HTTP request is received step.

Leave the Job ID and Name fields blank. These fields do not need to be updated.

Map all of the remaining fields with their corresponding counterparts dynamic content from the When a HTTP request is received step.

Minimize the Update a row step by clicking on the header.

Select Add a parallel branch by clicking on the plus sign in between the Get a row and Update a row steps.

Click on the … symbol on the Update a row step and select Configure run after.

Ensure that the option is successful is selected and click Done.

In the right-side branch, add a New step with the action Add a row into a table, from the Excel Online (Business) app.

In the Location field, select OneDrive for Business.

In the Document Library field, select OneDrive.

In the File field, browse to the Rampiva Tracker.xlsx file create previously.

In the Table field, select Table 1.

Map all of the fields with their corresponding counterparts dynamic content from the When a HTTP request is received step.

Click on the … symbol on the Add a row into a table step and select Configure run after.

Check only the has failed option is selected and click Done.

In the right-side branch, add a New step with the action Terminate, from the Control app.

In the Status field, select Succeeded.

Click Save in the top-right section of the screen to save the flow.

Expand the top When a HTTP request is received step, and copy the HTTP POST URL value.

Open the website https://reqbin.com

Replace the sample URL https://google.com with HTTP POST URL of the flow created in the previous step.

Set the method to POST.

In the Content tab, use the following sample data to create a new record with:

{
  "id":"aaa-bbb-ccc",
  "name":"Sample Job Name",
  "status":"Backlog",  
  "progress":0,
  "volumeLoaded": 0,
  "volumeExported":0,
  "currentOperationNumber":"",
  "currentOperationName":"",
  "currentOperationProgress": 0
}

Click Send to submit the data and run the pipeline.

Return to Power Apps, to the Flows tab and select the Update Rampiva Tracker application.

Open the Excel file Rampiva Job Tracker previously created in Excel Online.

Return to the website https://reqbin.com .

Set the contents to the following JSON data, to test updating an existing jobs record:

{
  "id":"aaa-bbb-ccc",
  "name":"Sample Job Name",
  "status":"Running",  
  "progress": 10.33,
  "volumeLoaded": 123.45,
  "volumeExported":50,
  "currentOperationNumber":"2/10",
  "currentOperationName":"Add Evidence",
  "currentOperationProgress": 70.00
}

Click Send to submit the data and run the pipeline.

Return to the Excel file Rampiva Job Tracker.

On the Engine server that will run the jobs, create the script file C:\Scripts\PowerApps-update.py.

Update line 8 from the script with the endpoint URL defined in the flow.

Sample settings used in this guide:

url='https://prod-175.westus.logic.azure.com:443/workflows/c924b5baadd94c6ba22cf9670491ae58/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=ZqLXqVhWEzcAJV6AfVaVSw_kF-gLm-YLN5GdSwI4W7c'

In Rampiva Automate, edit the Execution Profile used, and set the parameter {job_side_script_file} to C:\Scripts\PowerApps-update.py

Submit a Job with the updated Execution Profile.

Wait for the Job to start running, and then inspect the Excel spreadsheet table.

The Volume Loaded and Volume Exported fields are not automatically calculated. The job-side script expects this values to be available in the user-defined {volume_loaded} and {volume_exported} parameters. To update these values, add a Script operation in the Rampiva Workflow with the required logic to set these parameters. See https://downloads.rampiva.com/workflow-for-nuix/release/guides/en_US/user-guide.html#_script_operation for more information.

By default, the job-side script does not output logs. Update the variables debugToExecutionLog, debutToLogFile and debugLogFile as needed for troubleshooting.

Sample code to enable logging to both the Job Execution Log as well as to file in C:\Temp\logs:

debugToExecutionLog=True
debutToLogFile=True
debugLogFile="C:\\temp\\logs\\job-side-script.log"

If no log file is created when running a Job, inspect the Rampiva Engine log for python errors.

If the debug log file indicates that data is sent to Power Apps but data is not visible in Power Apps, inspect the Power Apps flow events for anomalies or errors.