Business events overview

Business events provide a mechanism that lets external systems receive notifications from finance and operations apps. In this way, business actions can be performed in response to the business events.

Business events occur when a business process is run. During a business process, users who participate in it perform business actions to complete the tasks that make up the business process.

A business action that a user performs can be either a workflow action or a nonworkflow action. Approval of a purchase requisition is an example of a workflow action, whereas confirmation of a purchase order is an example of a nonworkflow action. Both types of actions can generate business events that external systems can use in integration and notification scenarios.

Prerequisites

Business events can be consumed using Microsoft Power Automate and Azure messaging services. Therefore, customers must bring their subscriptions to such assets to use business events.

Business events that are implemented

Business events are implemented in some business processes out of the box. These business events include both workflow and nonworkflow business events. For more information, see Application business events, Workflow business events, and Alerts as business events.

A developer must use extensions to implement new business events. For more information, see Business events developer documentation.

Business event catalog

The business events catalog can be accessed from System administration > Set up > Business events. The business event catalog lists the business events that are available in the instance that you're using. The catalog is useful because it shows which business events are available, and you can filter it by category, business event ID, and name.

The category of a business event identifies its source. Business events that originate from the workflow system are assigned to the Workflow category. For business events that originate from other modules, the module name is used as the category name.

The business event catalog is built during database synchronization at the time of deployment. Therefore, users should see the complete list of business events in the catalog. However, if an explicit update of the catalog is required, you can select Manage > Rebuild business events catalog.

For each business event, the business event catalog shows a description. This description can help you better understand the business event and its context in the business process. The catalog also shows the list of data fields that is sent out in the event.

In scenarios where external integration systems require the schema of the payload for a business event during development, you can select Download schema to download the JavaScript Object Notation (JSON) schema.

In summary, the business event catalog helps identify the business events that are required for an implementation. It also helps identify the schema for each business event.

The next step is to manage the endpoints.

Business events parameters

General

The General tab of the Business events parameters page provides general settings that are applied to business events.

• Retry count – The number of times that the system tries again to send business events to an endpoint if an error occurs. The default value is 3.
• Wait time between retries – The interval, in milliseconds, between attempts to send a business event to its endpoint. The default value is 1000 milliseconds.
• Endpoints allowed per event – The maximum number of endpoints that can subscribe to the same business event in a legal entity. The default value is 10.
• Key vault secret cache interval – The number of minutes that the key vault secrets that are used for business events are cached in memory before they're read and cached again from the configured key vault. The default value is 5 minutes.

Performance

The business events framework has two primary settings that can affect performance: Processing threads and Bundle size. The application allocates dedicated batch threads to process business events in near-real time. Because threads are a shared resource for all batch processing, you must take care when you decide to change the thread allocation for business events.

• Processing threads – The number of threads to use to process business events.

  • With dedicated processing for business events, the thread count is the number per Batch Application Object Server (AOS) instance.
  • The maximum value is 4.

• Bundle size – The number of events to group together at a time for processing by a thread.

  • By increasing the number, you produce fewer bundles and reduce the ability to distribute the events to parallel threads.
  • By decreasing the number, you produce more bundles and increase the ability to distribute the events to parallel threads. However, if you make the number too small, you cause unnecessary parallelization on small bundles.

Event Grid settings

The Event Grid settings tab provides options that apply to business event endpoints with an endpoint type of Azure Event Grid.

The Send object in Event Grid data field toggle controls whether the type of object serialized and sent to the Azure Event Grid endpoint is a JSON string or an object. By default, the object sent to these endpoints is serialized as a JSON string. Turning on this toggle sends these objects as an object to the Azure Event Grid endpoints.

HTTPS settings

The HTTP timeout (milliseconds) toggle controls how long the default HTTPS adapter waits before timing out a request to an endpoint. The default timeout period is 10 seconds. Entering a value of 0 in the field is an indicator to use the default timeout period.

Activating business events

Business events in the business event catalog aren't active by default. From the catalog, you can activate any business events that you require. Select one or more business events, and then select Activate.

Business events can be activated either in all legal entities or in specific legal entities. If you leave the Legal entity field blank, the selected business events are activated in all legal entities. If a business event is required only for specific legal entities, it must be configured separately for each legal entity.

Endpoints must be assigned to the business events that are activated. For more information about setting up and managing endpoints, see Manage business event endpoints.

When business events occur as business processes are run, the system does outbound processing only for business events that are activated.

After business events are activated, they appear on the Active events tab.

From the Active events tab, you can inactivate business events. The system doesn't perform outbound processing for inactivated events.

After business events are inactivated, they appear on the Inactive events tab.

Business events can be inactivated when processing of business events must be paused for a period because of specific system maintenance activities in the integration landscape.

When business requirements change, some business events might no longer be required. In this case, you can inactivate them instead of deleting them from the list of active events. This approach is useful if the history of errors for the business events must be preserved. Inactivated business events can be deleted later, when there's no longer a business need to keep them inactivated.

Errors

While the system does outbound processing of business events, errors can occur. These errors might prevent the system from successfully delivering a business event to the endpoint. If an error occurs, the system retries several times to successfully process the business event. However, if all attempts are unsuccessful, the business event is saved in an error log.

Error logs can be accessed from the Active events, Inactive events, and Errors tabs. The Errors tab shows all errors across all business events, whereas the other two tabs show errors in the context of a specific business event.

You can do on-demand outbound processing on each error by using the Resend action. This action invokes the outbound processing logic. This logic includes retries. If the outbound processing is still unsuccessful, the error is logged in the error log. In this case, the Last process time field on the Errors tab indicates when the last attempt to process the event occurred.

If an error can't be successfully processed, you can use the Download payload option to download the payload from the event for offline processing, as you require.

Business event consumption models

The integration requirements and integration solution design for implementations vary. The integration requirements play a role in identifying the consumption model for business events. In summary, you must consider the following points when you design integrations that use business events:

• Business events can be consumed using Power Automate, Service Bus, Event Grid, or other endpoint types.
• Customers must bring their own subscriptions to use Power Automate, Service Bus, Event Grid, or other endpoint types.
• A business event can be activated in all legal entities or in specific legal entities.
• A business event can be sent to a unique endpoint or multiple endpoints.
• Power Automate can directly subscribe to business events.

Idempotency

Business events enable idempotent behavior on the consuming side by having a control number in the payload. The consuming application can use the unique control number to detect duplicate delivery. The control number can't be misread as the sequence number because the control number can't be sequential. There can be gaps in the numbering space. The order in which events emitted in finance and operations apps isn't guaranteed to preserve the order in which they're delivered to the endpoints.

Filtering in Azure Event Grid and Azure Service Bus

Azure Service Bus and Azure Event Grid support subscribing to topics by specifying criteria on the incoming message. For more information, see Topic filters and actions and Understand event filtering for Event Grid subscriptions.

A business event that is sent to an Azure Service Bus or Azure Event Grid has the following fields made available for this purpose. Subscribers can use this information to subscribe to more specific topics as required.

• Category – The business event category shown in the business event catalog. It's useful as a filter when a common article is used for receiving business events from multiple categories and subscribers want to only receive business events for the category that they're interested in.

• Business event ID – Business event ID is the class name of the business event implementation shown in the business event catalog. Business event ID uniquely identifies the business event (not the instance of the business event). It helps in validation of received business events on the consumer side to ensure the expected business event is being received and processed.

• Legal entity – The legal entity in which the business event happened. Legal entity is useful information to base the consuming logic on if the processing and distribution of business events on the consumption side must be driven by a legal entity.

Role-based security for business events

Role-based security can be applied to business events to meet the following requirements using the appropriate security artifact.

These privileges can be added to the required duties to grant corresponding roles appropriate access levels.

Enabling role-based security for business events

Role-based security for business events must be enabled via Feature management.

1. Go to System administration > Feature management.

2. Select the Business events catalog security feature.

3. Enable the feature.

4. Go to the business events catalog via System administration > Set up > Business events > Business events catalog.

5. The Security tab in the catalog is where a business event must be mapped to one or more roles. You must complete the configuration as required.

6. Enable security by selecting the Enable menu button on the Security menu on the top navigation pane. An informational message confirms if security is enabled or disabled.

7. Modify the necessary security role to add the appropriate privilege or the duty based on security noted in the informational message.

Subscribe to business events from service

Users having access to the privilege Subscribe to business events from service via their roles are able to only see and subscribe to business events that are assigned to their roles, as described below. The organizational assignments that are done, if any, as part of role-based security is honored in the context of business events by letting users to only subscribe to business events in the organizations to which they have access to via their roles. This behavior is effective using any service calls like from Power Automate or Logic Apps.

Backward compatibility

To ensure backward compatibility, the following behavior must be understood.

• Role-based security for business events is disabled by default.

• Even if the feature is enabled in Feature management, role-based security doesn't take effect.

• Role-based security must be explicitly enabled in the business events catalog via the Security menu.

• After role-based security is enabled completely, security will be enforced henceforth. It means that any user with an administration role doesn't notice any change in behavior. However, any nonadmin users either see only business events that their roles were assigned to in the business events catalog security configuration or doesn't see any business events because their roles weren't assigned to any business events.

Limitations

The Business events that occur in finance and operations apps are processed asynchronously across multiple systems to deliver them to the target endpoint. Therefore, the order in which they're emitted in finance and operations apps isn't guaranteed to preserve the order in which they're delivered to the endpoints.