Work Tracking
The information on this page covers work tracking for workspaces and the integration builder.
Work Tracking is a feature used to postpone the processing of work until a later date. Work items are used to represent a piece of queued work and are usually grouped by date. You can also use it to batch the processing, meaning waiting until there is a specified time or number of data objects to package that will send the event to trigger the flow run.
To open the Work Tracking page and see work items for a given workspace, select Work Tracking in the workspace menu.
You can see work items and add work request to both the workspace or the integration. Work requests at the integration level must have automatic batching. Work request types without automatic batching are generated by the flow runs, when the workflow adds the work item to the definition.
Any changes made to an integration work request will affect only that workspace.
Select Work Tracking in the Workspace menu.
Select the integration name in the integration builder and choose Work Tracking.
Modify a Work Request
Create or change a work request type to specify what you want to track or batch. When you add a work request type, you can designate a name and key. The key value will be automatically generated if you don’t enter one in the Key field.
To add a work request type, select Add Work Request Type.
To edit a work request type for the workspace, select the work request type and then the pencil Edit icon. For the integration builder, select the pencil Edit icon.
Enter or change the display name. The name should make it easy to identify the type of work being tracked or batched in the flow.
For the workspace, if you plan to wait until there are many data objects to process, select the Enable Batching checkbox.
Enter or change the time in minutes in the Timeout field. This is how long App Xchange will wait before running the flow containing the batch work request.
You can also enter or change the batch limit in the Items per Batch Limit field. This is how many data objects need to accumulate before the flow is run.
Select OK.
You must sync the workspace in order to see the work tracking integration.
If the work request was added through the Integration Builder, you’ll see a managed tag on the request. Changes to the work request for the integration builder are unique to that workspace.
Remove or Reset a Work Request
Removing a work request sends it to the archive. It will be removed from your work tracking page and from any work space.
You can reset a modified integration work request to the original values in the workspace.
If this is for the workspace, select the work request type.
To remove the work request, select the trash Delete icon. Choose OK in the confirmation window.
To reset the work request, select the arrow Reset icon. Choose Reset in the confirmation window, then perform a sync.
The work request is removed or reset.
View Work Tracking Details
Several flow steps facilitate this process, including Create Work Item, Get Work Items, and Resolve Work Items.
To open the Work Tracking page and see work items for a given workspace, select Work Tracking in the workspace menu.
Select one of the Work Request Types to view all the groups that exist for that type.
Select one of the Work Request Keys to view the work items for that key.
Work items are grouped by data object. The group name comes from the Connector and Data Object fields in the Create Work Item flow step configuration.
You can see each work item’s current status, as well as a progress bar summary for each group.
Select a work request key to see the details of the work or batch. Use the down arrow icon at the end of each row to see the related flows.
Example Scenario
Let’s say for your organization, purchase order files are created several times per hour. Instead of processing each file immediately, you can use work items to keep track of each created purchase order. Then schedule a flow to run every hour to fetch all unresolved work items (the unprocessed POs in this case) and process them all at once, resolving the work items when complete. You can also set up a batch job to run the flow once the limit for the batch has been reached.