Configuring Business Process
  • 01 Apr 2022
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Configuring Business Process

  • Dark
    Light
  • PDF

Creating a Business Process

  • Users can create a new business process by selecting Create Business Process option from the Actions dropdown available in the Business Process section.

Users with at least a Contributor role is required to access the Actions option.

BusinessProcess page.png

  • Tracking name is a name given to a business process that is used to identify the business process while tracking data.

  • Friendly name is a name given to a business process to identify it in Serverless360 Business Activity Monitoring.

  • Use the Optional settings if necessary, and then click the Save button to finish creating a business process.

Managing a Business Process

  • Users can update the name and the description of the business process by clicking the Edit button in the context menu of the relevant business process.

  • If a business process is no longer required, the user can delete it by selecting the Delete option from the context menu of the relevant business process.

All the tracked transactions, dashboards, and other configurations cannot be accessed once the business process is deleted.

Users are advised to export the business processes before deleting them since this action is irreversible,

Import a Business Process

  • Users can import a business process by selecting Import Business Process from the Actions dropdown in the Business Process section.

  • Select the business process JSON file that is downloaded and click Open.

  • The relevant business process already has a tracking name assigned to it. Users must provide a tracking name only if the existing business process has a tracking name that is similar to the tracking name of the business process to be imported and click Next.

The tracking name should be unique, as a name that is similar to the friendly name may result in a violation when displaying the data.

  • By selecting the checkbox labeled, Import all the Business Process tracking names dynamically, an auto-generated name can also be assigned to the selected business process. Click the Import button to complete the importing process.

Import Business Process.gif

Export a Business Process

  • Users can also export a business process and import it later by selecting Export Business Process option from the Actions dropdown in the Business Process section.

  • Select the required business processes to be exported from the checkboxes and click the Export button.

  • Provide a Name to the JSON file that is to be exported. Finally, press the Export button to export the business process. The selected business processes will be compiled into a JSON file that can be downloaded.

If the user does not give a name, an auto-generated name will be assigned to the exported file using date and time data.

Export Business Process.gif

Enable/Disable tracking and monitoring

  • By default, monitoring and tracking for a business process will be enabled. The Disable monitoring button in the context menu can be used to disable query and exception monitoring if the user does not want to be notified.

  • Disable tracking will disable tracking for the selected business process and transactions in that business process will not be tracked.

  • Users can enable the disabled tracking and monitoring for a business process by clicking Enable tracking and Enable monitoring respectively.

Enable/Disable message archival

  • Message archival at a stage can be enabled by passing the SL360-ArchiveMessage header as true while instrumenting either Azure Logic Apps, Functions, or Custom Applications integrated with Business Activity Monitoring.

  • Whereas, one can enable or disable Message Archival at the business process level, using Override runtime BAM configuration settings along with message archival in business process settings.

Scenarios for message archival

Following are some of the scenarios when the message will be archived in a stage:

  • When Override Runtime BAM Configuration and Archive messages are enabled.

  • When Override Runtime BAM Configuration is disabled and SL360-ArchiveMessage header is passed as true in Logic App custom connector action or while checkpoints to stage using .Net Library.

Scenarios for non-message archival

Following are some of the scenarios when a message will not be archived in a stage:

  • When Override Runtime BAM Configuration and Archive messages are disabled.

  • When Override Runtime BAM Configuration is disabled and SL360-ArchiveMessage header is not passed or passed as false in Logic App custom connector action or while checkpoints a stage using .Net Library.


Was this article helpful?