5.1 - Process Reporting

The Process Reporting page is a search console for accessing information about deployed processes. When accessing this page, Dell Boomi AtomSphere will automatically display all process executions that occurred in the account within the past hour. You can view the historical results of all executions, documents and trading partners by adjusting the search options in the left pane. Processing results from all atoms within your account (whether hosted or deployed locally) can be monitored from this central console. You can then view process logs, see how many records were processed, view actual document data, retry documents, and more.

Process execution results are available for 30 days. If you require the inbound and/or outbound data to be kept longer for audit or other purposes use the connector operation archiving functionality or send data to another location as part of the process logic itself. Also, review the Atom Management topics to learn how the purging schedule can be adjusted for local atom history.

Process Reporting Types

Executions -- Search for process execution information and logs.
Documents -- Search for document instances and related log data.
Trading Partner -- Search for trading partner document data and executions (X12). This must be enabled in your account.

Process Reporting Search Options

The left pane of the Process Reporting page includes a number of different search options to display the desired reporting results. Make sure to click the Refresh Search button to enforce your latest selections.

Reporting Type	Option	Description
All	Time Window	Defines the range of desired processing results.
All	Atoms	List of all atoms in the account. Press Ctrl + click to select one or more, or the default All to return everything. Refer to Executing a Process to learn more about the green play button for manual executions.
All	Advanced > Search Across All Accounts	When on, displays results from various sub-accounts when searching from a parent AtomSphere account.
Executions	Advanced > Only show executions with more than 0 inbound documents	Removes results where no documents are used at the Start step.
Executions	Advanced > Process	Limits results to the select process name.
Executions	Advanced > Execution ID	ID that is displayed when Loading Execution from Documents view. This is commonly used for administrative review.
Documents	Tracked Fields > Search For	Used to search for results by custom, tracked field or connector and X12 - specific attributes. Works with Search Box selection(s).
Documents	Tracked Fields window > Search Box	Lists possible selections for Search For. Press Ctrl + click to select one or more, or the default All to return everything. User Defined Fields: List of the tracked fields from the Setup page's Document Tracking tab. Refer to the Document Tracking topic to learn how to expose tracked fields in your connector operations for searching. Connector Attributes: List of core connector properties that are captured per document. X12 Attributes: List of standard X12 properties captured for EDI processing.
Documents	Connector Type	Allows searching of documents for specific connector types.
Documents	Document Type	Allows you to limit search down to X12 type data.
Trading Partner	From Trading Partner	Component Explorer look-up that allows definition of Trading Partner component for inbound documents.
Trading Partner	To Trading Partner	Component Explorer look-up that allows definition of Trading Partner component for outbound documents.
Trading Partner	Document Standard	Allows you to define the X12 standard.
Trading Partner	Document Type	Allows definition of the X12 transmission type to narrow results.
Trading Partner	ISA Control Number	Allows definition of specific ISA Control Number.
Trading Partner	GS Control Number	Allows definition of specific GS Control Number.
Trading Partner	Errored / Unacknowledged Docs Only	When on, displays Trading Partner documents that were not acknowledged or failed.

Process Execution Results Table

The process executions view is divided into two tables, with process results on top and document results on the bottom.

Each row in the executions table represents an instance of when a process ran and displays the following information.

Column	Description
Status	Success -- Process and all documents were processed without errors. Error -- There was at least one error in processing one or more documents. Pending -- The process is still executing.
Time	Time stamp of when the process began. The time displayed uses the time settings of the PC viewing the results.
Execution Type	Scheduled -- Indicates that an execution schedule is enabled for the process and an execution was automatically triggered. Scheduled Retry -- Indicates that a retry schedule is enabled and one to many failed documents were automatically retried. Manual -- Indicates that a user triggered the process manually. Child Process -- Indicates that a process was triggered by a parent process with the Process Call step. Listen -- Indicates that a process was executed in real-time by enabling the Web Services Server Connector.
Process	Name of the process.
Details	Actions -- Select one of the available actions. View Process Logs -- View the process-level log information. (See Viewing Logs for more information.)
Atom	Name of the atom on which the process ran.
In	Number of documents read into the process. A single document can represent a batch containing many individual records.
Out	Number of documents sent out of the process. This number represents an aggregate of all the documents sent by a Send connector, so if a single document is sent to multiple outbound connectors, it will counted for each. Splitting and combining documents within the process will have a direct affect on this value.
Elapsed Time (s)	Total duration (in seconds) of the process execution.
Error Message	Main process-level error for a failed execution instance. Double-click the record's message window to expose a pop-up with a longer error message string.

Execution results are displayed once the platform receives them from the atom. Depending on the complexity of the process, volume of data and varying Internet connection speeds (if the atom is running in your local network), it may take up to several minutes for results to be posted. Use the Refresh Search button or turn on the Auto-Refresh option in the top-right corner of the executions window to see updated results each minute.

You must highlight a process execution to display the process documents. The results can be sorted by any of the table fields simply by clicking the column header. Click the column header again to toggle ascending/descending order. By default, results are displayed by time, descending. You can also filter the results by the execution status when clicking on a filter link. Pending, for example, indicates that the execution has not yet completed.

Viewing Process Execution Documents

You can access the document results from the execution results table by highlighting a single execution record. The documents window will then display in the bottom half of the results view with both an Inbound and Outbound Documents tab. You can also filter the results by the document status when clicking on a filter link.

Keep in mind that the terms "inbound" and "outbound" are from the AtomSphere process perspective, as opposed to a business process perspective.

Process Reporting Inbound Data Tab

Each row in the Inbound Data table represents a single document read into the process via the Get connector in the Start step. The following information is displayed for each document. Additional options are displayed when clicking on the gear icon drop-down ( ) per document.

Column	Description
#	Counter or ID of the document.
Status	Success -- Document was processed without errors. Error -- There was at least one error in processing this document.
Actions	View Log -- View the document-level log information. (See Viewing Logs for more information.) View Document -- View a sample of the actual data in the Document Viewer dialog. While viewing it you can save the full document data locally for further investigation. Re-run Document -- This creates a new process execution. Re-run Document in Test Mode -- This will open a pop-up that will run the document(s) selected in the latest build version of the process. View Linked Documents -- View the outbound documents produced from this inbound document.
Size (kB)	Size of document data in kilobytes.

Depending on the connector type used in the Start step, additional columns for connector-specific information may be added to this table such as File Name, Host, Port, Directory, Email Subject, etc.

Process Reporting Outbound Data Tab

Each row in the Outbound Data table represents a single document sent out of the process via the one or more Send connectors used in the process. If there is only one outbound connector in the process, you will see the Outbound Documents table.

However, if there are more than one outbound connectors in the process, you will first see the Connector Summary table displaying the total number of documents sent via each connector. Use the Show Data for Connector drop-down above the table to see the detailed results for each connector operation.

Outbound connectors also refer to connector steps that are bringing data into the process. Depending on the process configuration, you can display document data this is being used in subsequent process steps.

Column	Description
#	Counter or ID of the document.
Status	Success -- Document was sent without errors. Error -- There was at least one error in sending this document.
Actions	View Linked Documents -- View the inbound document that this outbound document came from. View a sample of the actual data in the Document Viewer dialog. While viewing it you can save the full document data locally for further investigation.
Size (kB)	Size of document data in kilobytes.

Depending on the connector type used in the Start step, additional columns for connector-specific information may be added to this table such as File Name, Host, Port, Directory, Email Subject, etc.

Re-Running Documents in Process Reporting

You can re-run documents directly from the Manage menu without having to re-execute the process. This can be useful when troubleshooting or reprocessing data that no longer exists in the source system. For example, consider a process that gets and deletes files from a trading partner's FTP site. Those files will no longer exist after the first execution. If you need to reprocess one of those files for some reason, you can do it directly from the Manage menu without having to coordinate with your trading partner to recreate the file.

To re-run a single document, find the particular document in the Inbound Data tab and click the re-run icon ( ) in the Actions column for that row. The document will be reprocessed as a new process execution.

To re-run more than one document, select multiple documents using the convenience links (All, None, and Errors) above the table or hold down either the Ctrl or Shift key while clicking rows. Click the Re-run selected documents link above the table to reprocess all selected documents as a new process execution.

If the number of inbound documents spans multiple pages, AtomSphere will only re-run the documents on the current page if you choose All for the re-run documents feature.

You can also re-run documents in Test mode. When selecting one or more inbound documents, this feature will launch a pop-up (ensure pop-ups are enabled for platform.boomi.com) that will send the document(s) down the latest process version on the Build tab. This will help you to troubleshoot the inbound document(s) from beginning to end through each step.