Configure events in Jitterbit App Builder

Introduction

The following Intrinsic events can be configured to have associated actions or validations at the Data layer and the Business Logic layer:

• Delete: Associated action(s) or validation(s) will trigger upon a record being deleted.

• Insert: Associated action(s) or validation(s) will trigger upon a record being inserted.

• Save: Associated action(s) or validation(s) will trigger upon a record being saved.

• Update: Associated action(s) or validation(s) will trigger upon a record being updated.

Event detail options

The following properties can be configured for an Event to define its behavior and user experience:

Event information

• Name: The unique name used to define the event.

• Refresh Scope: Determines what data is reloaded after the event:

  • Data Object: Affects other rows in this data object.

  • Global: Affects other data objects; reloads the entire page.

  • None: Input values are unaffected.

  • Row: Affects values in only the current row.

• Active: Indicates whether the Event is currently active.

Messages

• Confirmation: Displayed to the User to confirm if they wish to proceed.

• Success: Displayed after a successful Action.

• Failure: Displayed after an Action has failed.

Execution properties

• Skip Parent: If enabled, the event will skip parent Events and associated Actions.

• Transaction: Processes the event's Actions as a database transaction.

• Execution Type: Determines when the Event runs:

  • Foreground: Executes immediately in the UI.

  • Launch Now (Background): Executed in the background when invoked.

  • Launch Now or via Schedule (Background): Background execution via invocation or schedule.

  • Launch via Schedule (Background): Background execution via schedule only.

• Background Specific Options: Includes Max Concurrency, Blocking (waits for event completion), Run as User, and Operating Hours (Pause/Resume execution).

Locking

• Use Lock: Enables event locking to prevent concurrency issues.

Role of binding in Events

While configuring the event details above is essential, setting up the binding is a required step that ensures the Event has the correct data context. When you register notifications, migration rules, CRUD rules, or validation rules on actions and validations, you must specify the binding. This mapping connects the panel columns (UI) to the target rule columns (logic), allowing the application to pass the necessary values to the event's associated actions.

Custom events

In addition to intrinsic events, you can define custom events associated with actions or validations. These can be fired from the UI layer via controls like text, images, buttons, and lists.

Where events get configured

Events are generally configured on the Data layer, but can be moved to the Business Logic layer for specific page-level requirements.

Data layer

It is faster and simpler to maintain events on the Data layer. Configure them here unless the logic is page-specific or requires binding not available on the table.

1. Navigate to App Workbench > Tables.

2. Locate the table and click the Events icon.

3. For intrinsic events, click the pencil icon and then Create & Register on the actions or validations panel.

4. For custom events, click + Table Event, name it, and then Create & Register the associated action/validation.

Business Logic layer

Use this layer to configure intrinsic events for specific pages or when the action requires binding outside of the standard table context.

1. Navigate to App Workbench > Rules.

2. Locate the business rule and click the Events button.

3. Follow the same Create & Register process used in the Data layer.