Cross solution datasource access

Jigx solutions are self-contained by default, but there are scenarios where one solution needs to read data from, or trigger actions in, another installed solution. Cross-package support makes this possible without duplicating data or creating custom sync pipelines. See Cross-solution datasource access to learn more about the configuration options.

Examples and code snippets

Cross solution datasource and action access

This example demonstrates how to configure and use cross-solution datasource and action access between two solutions: Assignments and Human-Resources.

The Assignments solution contains a projects table as part of its datasource configuration, while the Human-Resources solution contains an employees table.

Within the Assignments solution, a manager datasource is configured using the package and entity properties to access employee data (name and id) from the Human-Resources solution. This datasource is used to populate a Project Manager dropdown list. A second datasource, project-details, retrieves project data from the local Assignments solution to populate a Project dropdown.

The jig (assign-project-manager.jigx) includes two dropdown fields:

• A Project dropdown populated from the projects table.

• A Project Manager dropdown populated from the HR solution’s employees table.

Once selections are made, two actions are triggered:

1. A local execute-entities action in the Assignments solution updates the selected project table with the project manager’s name.

2. A cross-solution action calls the global execute-actions action from the Human-Resources solution to update the assigned_to column in the employees table with the project name.

This example demonstrates how solutions can securely share both data and actions across packages. More complex scenarios can be configured where local and cross-package data can be combined within the same SQL query using operations such as JOIN or UNION ALL.

Assignments Solution

project-details.jigx (datasource)

type: datasource.sqlite
options:
  provider: DATA_PROVIDER_DYNAMIC
  entities:
    - entity: default/projects
  query: |
    SELECT
      P.id AS id,
      json_extract(P.data, '$.project_id') AS project_id,
      json_extract(P.data, '$.project_name') AS project_name,
      json_extract(P.data, '$.status') AS status,
      json_extract(P.data, '$.start_date') AS start_date,
      json_extract(P.data, '$.end_date') AS end_date,
      json_extract(P.data, '$.assigned_employee_id') AS assigned_employee_id
    FROM [default/projects] AS P
    WHERE json_extract(P.data, '$.status') != 'archived'
    ORDER BY json_extract(P.data, '$.project_name')

managers.jigx (datasource)

assign-project-manager.jigx

Human-Resources Solution

assign.jigx (global action)

# Global action configured to save the project name witht he associated employee.
action:
  type: action.execute-entities
  options:
    provider: DATA_PROVIDER_DYNAMIC
    entity: default/employees
    method: update
    data:
      id: =@ctx.action.parameters.employee_id
      assigned_to: =@ctx.action.parameters.project_name
parameters:
  employee_id:
    type: string
    required: true
  project_name:
    type: string
    required: true