Process Reporting in Boomi Vs Log reporting in Celigo
- Technical Guide

- Dec 8, 2022
- 3 min read
Process Reporting in Boomi :
Process reporting Use the Process Reporting page to search for information about process executions and their related documents and logs.
Process Reporting page shows all the Boomi deployed Processes that ran in the account within the Past hour. Navigation of Process Reporting page (Manage > Process Reporting).
The process Reporting page has filters :
Find process executions, documents, or trading partner documents.
Find test mode executions.
We can find processing results that occurred for a specific time frame.
Find processing results based on specific criteria.
Successful, Pending, View all, failed, or process executions or documents.
View document logs and process for deployed processes
View the actual data for deployed processes and process execution documents.
View information about documents that encountered errors
In Boomi for troubleshooting errors, we use Boomi Resolve.
Rerun documents for a deployed process
Export processing results to a CSV file
The process Reporting page shows information about process executions and their related documents and logs.
On the top right side of the Process Reporting page there are controls for:
Selecting and executing a process manually.
Turning Auto Refresh Table on or off. When Auto Refresh Table is on, the search results table is updated every minute. If you start to page through the list of results, Auto Refresh Table has turned off automatically.
Filtering the search results table by all process executions or documents, executions or documents with errors, pending executions, or successful executions or documents.
The columns in the table vary, based on whether you are searching by process execution, document, or trading partner document.
Process executions and documents have a green or red icon indicating success or failure.
Process executions can have a blue icon indicating that it is pending.
Use the logs to troubleshoot errors and to determine why a document failed.
The Atom column appears in the process execution, document, and trading partner document results tables. In this column, the Atom name links to the Atom Information panel on the Atom Management page (Manage > Atom Management), in which Atom status information is available.
Search results are displayed after the platform receives them from Atom. The search results table can be sorted by any of the fields by clicking a column header. Click the header column again to switch between descending and ascending and order. By default, results are displayed by date and time in descending order.
The bottom of the Process Reporting page contains controls for navigating to the first, previous, next, or last page of search results.
Clicking the date and time link in a row displays more detailed information about the process execution or document.
Note: The process execution detail view is not available for test mode executions.
Log Reporting in Celigo:
Audit logs This page shows the changes like Some fields that are changed, the type of change and who is responsible for that change, etc. The audit log page shows these changes in your flows.
All the activities related to export and imports respectively you can see the changes in the Audit logs page.
Uses of Audit Logs
Download audit logs integrator.io show the last one year. You can download your logs in the form of a CSV file and download 1000 records simultaneously.
Practical uses for audit logs In Audit logs, you can also determine who changed account permissions. For example, you can use audit logs to review the changes, and if someone changed an import field and caused an error.
Time You can configure your account profile to display timestamps in any date/time format in Celigo.
User, The user is responsible for the changes. Where an account is shared by multiple people with the same password, the only username is something similar to “Account Owner” or your company name.
Source Determines how the change was made. This could be:
API – Changes were made in the API.
Stack – Changes were made from the stack.
Resource Type:There are nine resources monitored for changes:
Action The action that was taken. Actions include:
Create
Update
Delete
Sign in
Sign out
View
Old and new values In the Old and New value fields, you have options including Clicking to view edits, dates and times a token was updated, and secure connection details. You should never know that won’t display your secure connection details, like keys, tokens, or passwords, in audit logs under any circumstances, as those details are encoded.





Comments