Documentation Index

Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt

Use this file to discover all available pages before exploring further.

Public/Private WebApp Events

Prev Next

Overview

In legacy Construct, you could mark a business rule as Public, and any WebApp could directly invoke it. This provided:

  • Single definition of shared logic.

  • Implicit availability across WebApps.

  • Minimal configuration overhead.

Cloud Construct does not support the public/private access control model. Instead, Events are scoped to the page and its containers where they are defined, making them essentially private to those containers. Cloud Construct requires explicit event invocation through Orchestrate Workflows:

  • More transparent: You can see exactly which pages invoke which logic.

  • More flexible: Workflows can be customized per page.

  • Trade-off: Requires more manual configuration for cross-page scenarios. You must manually create an Orchestrate Workflow on each page that invokes the shared Orchestrate Step, configuring parameters separately per page.

You can achieve cross-WebApp logic sharing through manual workflow creation on each page.

Updated Methodology

Create an orchestrate step once and manually invoke them from multiple pages:

  1. In the Orchestrate module, create an Orchestration Step to define business logic accessible to all WebApps.

  2. For the construct page needing this logic, configure an Orchestration Workflow with the Orchestrate Step as one of its task.

  3. Configure required variables as needed to provide values from the page that invokes this Orchestrate workflow.

  4. Save this Orchestrate Workflow.

Note

  • Keep the Orchestrate Step generic with the primary key as one of the arguments in the stored procedure.

  • Different WebApps can invoke same the Step with different Orchestrate Workflows and variables (parameters).

Create WebApp Event

  1. Edit the required WebApp/construct page.

  2. In the WebApp Builder, set up a event with the same name as the Button column, or set up an event to be invoked via the Toolbar Button.

  3. In the event, ensure that the Orchestrate Workflow is added as one of its task.

  4. If you are using Toolbar Button, you can pass key field values as parameters using the Parameter Dataset to the event.