Operations

Use operations to connect an Experience Designer component to a data service and define what the component does with the returned or submitted data. Use operations when a component needs to retrieve, update, delete, submit, or display information from a data service.

Operations overview

Configure operations in each component. An operation connects a component to one or more data services and identifies the purpose of the connection. For example, a data service that uses a get or list transaction is typically connected to a Read operation, while a data service that uses an update transaction is connected to an Update operation.

This concept is generic across Experience Designer and applies to most components, but the exact operations available vary by component type.

How operations tie to data services

Operations do not contain API logic. Instead, operations refer to a data service, and the data service contains the definitions for API transactions, inputs, outputs, and sequencing.

  • Data service: defines MI, LISTMI, or API Gateway transaction(s), input values, output fields, and sequencing.
  • Operation: A usage pattern for the data service, such as Read, Update, or Delete, or a custom operation.
  • Interaction: The event that starts the operation, such as Load, Select, Click, Input, Enter, Search, Filter, or Success.
This separation is important because one component can have multiple operations, and one application can reuse different data services across several components.
Note: Use this recommended design flow: First, add and arrange components. Then, assign component IDs and save the application. Next, create the data services. Finally, return to each component and connect operations and interactions.

What operations are used for

Use operations to make components interactive and useful. Common task include:
  • Load data into an index list, form, data grid, chart, header, tree, or spotlight item.
  • Update data from a form, application header, or data grid.
  • Delete records from components that support deletion.
  • Run various actions through custom operations tied to toolbar buttons or button components.
This separation is important because one component can have multiple operations, and one application can reuse different data services across several components.
Note: Use this recommended design flow: First, add and arrange components. Then, assign component IDs and save the application. Next, create the data services. Finally, return to each component and connect operations and interactions.
Combined operations and interactions support event-driven scenarios such as:
  • Load a customer list when the application opens.
  • Load a details form when the user selects a row in an index list.
  • Run an update transaction when the user clicks a button.
  • Refresh a component after a dialog closes successfully.
  • Display a document or image when the user selects a record.