Skip to main content

Service Entities

Service Entities are non-persistent entities designed to handle temporary data processing, transformations, and API interactions without being stored in a database. These entities are primarily used when data needs to be processed dynamically but does not require long-term persistence.

During application development, there may be a need to exchange multiple variables across different logic flows. A service entity allows grouping multiple related entities into a single structure, which can then be used as input/output for logic flows.

Service entities are primarily used to define the request and response structure for logic flows. They can contain one or more attributes and can also establish relationships with other entities.

For example, in an e-commerce application, a service entity like OrderDetails can be created to group both Order and OrderItems, facilitating efficient data exchange.

Key Use Cases of Service Entities​

  1. API Data Processing – Storing and transforming data fetched from external APIs.
  2. Computation & Business Logic Execution – Performing calculations or business rule validations without persisting results.
  3. Workflow & Event Data Processing – Holding data temporarily during workflow executions or UI events.

Add Folder​

For better organization and accessibility, users can group database entities into folders.

  1. Create a Folder:
    • Right-click Service Entities in the Explorer Menu.
    • Select Add Folder and provide a name for the folder.