View Categories

Event Subscription Screen

Table of Contents

Last verified with: 10.8.6.0

Event Subscriptions are configured in Setup / Extensibility / Event Subscriptions

Overview #

The Event Subscriptions screen is used to configure subscriptions that react to business events in LogiSense Billing. An event subscription allows the system to listen for a specific event, optionally narrow that event with filters, and then perform one or more configured actions when the event occurs.

This screen is commonly used when administrators want the platform to send a notification or trigger an external integration automatically. For example, you can configure a subscription to send an email when an invoice is delivered, or to send a webhook when a payment status changes.

Each subscription combines four main parts:

  • the Entity that the event applies to
  • the Binding Action that defines the event being monitored
  • optional Filters that narrow when the subscription should apply
  • one or more Actions that determine what happens when the event is triggered

Event Subscriptions Panel #

The Event Subscriptions panel on the left displays the list of configured subscriptions. Selecting a subscription loads its details on the panel to the right so that you can review or update the configuration.

Actions #

IconDescription
Adds a new subscription
Deletes the selected record when deletion is allowed

Edit Event Subscription Panel #

The information in this section reflects the currently selected event subscription.

Fields #

  • Name: The name used to identify the event subscription.
  • Active: Enables or disables the subscription.
  • Internal Use Only: Marks the subscription for internal-use scenarios where applicable.
  • Description: Stores additional information about the purpose of the subscription.
  • Entity: Identifies the business object or process area the subscription applies to.
  • Binding Action: Identifies the event that will trigger the subscription.

Filters Tab #

The Filters tab is used to define the conditions that must be met before the subscription will run.

Filters are useful when you do not want the subscription to react to every occurrence of an event. Instead, you can limit the subscription to specific statuses, dates, accounts, invoices, or other relevant values exposed by the selected entity and binding action.

If multiple filters are configured, the event must satisfy the full filter set for the subscription to apply.

How Filters Work #

Each filter is made up of:

  • a field
  • an operator
  • a value

The available fields depend on the selected Entity and Binding Action. When you choose a field, the screen updates the rest of the dialog so you can enter a value that matches that field type.

Examples:

  • a status field may allow you to compare against a specific status value
  • a date field may allow you to compare against a fixed date or a relative date
  • a yes/no field may allow you to choose a boolean value
  • an identifier field may provide a list of available records to select from

Adding A Filter #

  1. Open the Filters tab.
  2. Select Add Filter.
  3. Choose the field you want to evaluate.
  4. Choose the operator to apply.
  5. Enter or select the value to compare against.
  6. Save the filter.

After the filter is saved, it appears in the filter list on the tab. Existing filters can be edited or removed from the same list.

Choosing The Field #

The Field list is populated from the selected event context. Only fields that are valid for the current event configuration are available.

When you change the field, the dialog automatically updates the operator and value controls to match that field’s data type.

Choosing The Operator #

The available operators depend on the selected field. For example:

  • text and numeric fields use comparison operators that are appropriate for those values
  • boolean fields use true/false choices
  • date and date-time fields can use date-based comparisons

The operator determines how the event data will be checked when the event occurs.

Entering The Filter Value #

The value entry method depends on the field type:

  • free-text fields allow you to type a value directly
  • lookup fields provide a selectable list of valid records
  • boolean fields let you choose a true or false value
  • date fields allow either a fixed date or a relative date option

Using Relative Dates #

For date and date-time fields, the filter dialog can use a relative-date option instead of a fixed calendar date.

This is useful when the subscription should always evaluate against a moving date reference such as:

  • today
  • the start of the month
  • the end of the month
  • the start or end of the quarter
  • the start or end of the year

Relative dates are useful for recurring operational logic because the filter continues to evaluate correctly without needing to be updated manually.

Editing Or Removing A Filter #

  • Select the edit option on a filter row to update the field, operator, or value.
  • Select the delete option on a filter row to remove that filter from the subscription.

Actions Tab #

The Actions tab is used to define what the subscription should do when the event occurs and the filter conditions are met.

Each action row represents a delivery or callout action linked to the subscription. A subscription can have more than one action, which means the same event can trigger multiple downstream results.

For example, the same event subscription can:

  • send an email to internal users
  • send an email to selected account contact types
  • send a webhook to an external endpoint

Adding An Action #

  1. Open the Actions tab.
  2. Select Add.
  3. Choose the action type you want to configure.
  4. Complete the required fields for that action type.
  5. Save the action.

Existing actions can be edited or removed from the list on the tab.

Configuring An Email Action #

Use an Email action when the event should send an email notification.

Email Action Fields #

  • Action: Displays Email.
  • Name: The name used to identify this action row.
  • Email Template: The event email template that will be used to generate the email content.
  • Recipient: Determines how recipients are selected.
  • Select User: Used when the recipient type is based on one or more Admin Portal users.
  • Select Contact Type: Used when the recipient type is based on account contact types.

How To Configure An Email Action #

  1. In the action dialog, choose Email.
  2. Enter a meaningful Name for the action.
  3. Select the Email Template to use.
  4. Choose the Recipient type.
  5. Select the users or contact types that should receive the email.
  6. Save the action.

Recipient Options #

The email recipient method is selected through the Recipient field.

Depending on the event, you can configure the email to send to:

  • specific users
  • selected contact types

When User is selected, use Select User to choose one or more Admin Portal users.

When Contact Type is selected, use Select Contact Type to choose one or more account contact types. The notification will use the matching contact information from the account involved in the event.

For some events, the system restricts the recipient method to User only.

When To Use Email Actions #

Email actions are useful when people need to be informed directly when an event occurs. Common examples include:

  • notifying staff that a bill run has started or completed
  • notifying users that a scheduled report was generated
  • sending business notifications related to invoices, payments, or account changes

Configuring A Webhook Action #

Use a Webhook action when the event should send a machine-readable payload to an external system.

Webhook Action Fields #

  • Action: Displays Webhook.
  • Name: The name used to identify this action row.
  • URL: The endpoint that will receive the webhook request.
  • HTTP Method: The request method used for the webhook. The current options are POST and PUT.
  • Format Type: The webhook body format. The current options are JSON and FORM URL.
  • Authentication Type: Determines whether and how authentication details are sent with the request.

Depending on the selected authentication type, additional fields are shown.

How To Configure A Webhook Action #

  1. In the action dialog, choose Webhook.
  2. Enter a meaningful Name for the action.
  3. Enter the target URL.
  4. Choose the HTTP Method.
  5. Choose the Format Type.
  6. Choose the Authentication Type.
  7. Complete any additional authentication fields that appear.
  8. Save the action.

Format Type #

The Format Type controls how the payload is sent to the endpoint.

  • JSON: Sends the payload as JSON.
  • FORM URL: Sends the payload using form URL encoding.

Choose the format expected by the receiving application.

Authentication Types #

The webhook configuration supports multiple authentication methods.

None #

Use None when the receiving endpoint does not require authentication.

Key Value Pair #

Use Key Value Pair when the endpoint expects a token or credential pair.

Additional fields:

  • Auth Key: The key or header name to use.
  • Auth Value: The corresponding authentication value.

OAuth 2.0 Password #

Use this option when the endpoint requires OAuth 2.0 password-based authentication.

Additional fields:

  • OAuth Username: The username that the webhook uses when requesting an OAuth access token.
  • OAuth Password: The password associated with the OAuth username.
  • OAuth Client ID: The client identifier registered with the target authorization service.
  • OAuth URL: The authorization or token endpoint URL used to obtain the OAuth access token.

OAuth 2.0 Client #

Use this option when the endpoint requires OAuth 2.0 client-credential style authentication.

Additional fields:

  • OAuth Client ID: The client identifier registered with the target authorization service.
  • OAuth Client Secret: The client secret associated with the registered client ID.
  • OAuth URL: The authorization or token endpoint URL used to obtain the OAuth access token.

When To Use Webhook Actions #

Webhook actions are useful when another system needs to respond automatically to a LogiSense Billing event. Common examples include:

  • notifying an integration platform that a payment status changed
  • sending billing or account events to an external orchestration system
  • forwarding operational events to a monitoring or downstream processing service

Managing Multiple Actions #

A subscription can have more than one action. This allows one event to trigger more than one result.

For example, one subscription can:

  • send an email to internal users
  • send a webhook to an external integration

Each action is configured independently and appears as a separate row on the Actions tab.

Guides #

Adding An Event Subscription #

  1. Select Add from the Event Subscriptions panel.
  2. Enter the subscription Name.
  3. Set Active if the subscription should be enabled immediately.
  4. Enter a Description, if needed.
  5. Select the Entity.
  6. Select the Binding Action.
  7. Add any required filters on the Filters tab.
  8. Add one or more actions on the Actions tab.
  9. Save the subscription.

Editing An Event Subscription #

  1. Select the event subscription from the list.
  2. Update the main fields as needed.
  3. Add, edit, or remove filters on the Filters tab.
  4. Add, edit, or remove actions on the Actions tab.
  5. Save the changes.

Deleting An Event Subscription #

  1. Select the event subscription from the list.
  2. Select Delete.
  3. Confirm the deletion when prompted.

lsb-screen-help