| Install | Install the Jigx Builder extension in Microsoft Visual Studio and create your Jigx's solutions. | |
| Build | Start creating your mobile apps, use intellisense prompts and code completion to speed up development. | |
| Data | Integrate with with your business's datasources, REST, Salesforce and more, or use Jigx's built in real-time datastore. | |
| UI | Choose from a range of available components, add actions and integrate these with your data to create powerful apps. | |
| Logic | Structure and manipulate data before binding the data to the UI using JSONata expressions, or use states to manage inputs at runtime. | |
| Manage | Manage your organization details, users, and solutions, send push notifications, and configure authorization and authentication. |
Registration screen
Registration Pin code
Create an organization
Jigx invitation email
Welcome and sign in
Jigx app verification email
2-Step verification screen
New Password screen
Jigx Builder installed
Publish Jigx project
Hello Jigx Solution
Jigx project in VS code
Publish Jigx project
Map jig on Home Hub
Form and list widgets
New customer form
View customer jig
Edit customer jig
Hello Jigx Solution
Solution with Calendar -3 icon
Solution with calendar badge
Hello Jigx solution with location icon
Widget location & image
Signature component template
Component template
Template gallery
Insert template
Inserted YAML
Pre-built Solutions
Download solution files
Solution in Jigx builder
| Example | |
|---|---|
| Hello REST | In this section, a REST API is used to create a customers Jigx app, allowing you to add new customers and update and view customer details, location, and images. |
| MS Graph | The MS Graph examples use the User, Calendar, Mail, Insights, and To-do tasks to create a powerful Jigx apps with everything you need in one app. |
| Microsoft OneDrive | Use the Microsoft OneDrive data provider to create, update, list, delete, and download files. |
| Salesforce | The Jigx Salesforce provider brings data directly into the app from Salesforce, giving you access to real-time data and visual insights no matter where you are. |
| OpenAI | Jigx supports any AI service that is exposed to a REST service. By leveraging the power of advanced AI models, you can create smarter, more responsive, and engaging apps that meet users' evolving needs. |
Plan the home hub
Data visualization
Build plan
App skeleton
Jigx Overview
| Component | Description |
|---|---|
| Jigx Builder | The Jigx Builder is an extension in Microsoft VS Code, a development environment that can be installed on many platforms, including Windows and Mac. Use YAML, SQL, JSON, and JSONata to build, test, debug, and publish Jigx mobile apps. |
| Jigx Cloud | JigxCloud authenticates users, stores organizations and solutions, and sends notifications. |
| Jigx Management | Jigx Management exposes the Jigx Cloud functionality in a browser-based portal, allowing you to manage users and solutions, set up send and push notifications, and view usage metrics of your organization. |
| Jigx App | The Jigx App is an iOS and Android app that works on mobile devices such as phones and tablets. The app is available in the iOS and Google Play stores. Jigx solutions built-in Jigx Builder, published to Jigx Cloud and permissions granted in Jigx Management are accessible in the Jigx App. The Jigx App is only supported in portrait mode on iOS and Android phones. |
| Data | Understanding how data is used and how it flows between the Jigx components is important. Jigx data concepts, including data lifecycles, syncing and loading data, and how to work with REST, Azure SQL, and Dynamic Data are covered in the Data topic. |
List icons in a list
Preview of icons
Icon asset list
Jigx Builder installed
Sourcecode details
Jigx extension settings
| Folder | Default File | Description |
|---|---|---|
| .vscode | settings.json | Relates to your Jigx solution and contains internal parameter settings required by Jigx Builder runtime. This file's scope is local (workspace) and applies to the current solution. For more information, see . |
| actions | Actions refer to specific controls or operations responding to an event or input. Create under the actions folder to define actions once and reuse them multiple times in different jigs. | |
| assets | The solution's images and icons defined under the folder will preload and cache when the solution downloads or updates in the app. Allows images and icons to display when the app is offline and improves the app's performance. | |
| databases | default.jigx | You can use the default.jigx file to define the tables in the Provider. |
| datasources | Create global data files with .jigx extension- these are available for use in your whole solution to any of the jigs. | |
| functions | myfirstfunction.jigx | You can build logic into your solution by adding functions to get or update data from a remote service, such as or SQL Functions. |
| jigs | myfirstjig.jigx | The jigs folder is where you create all the files used to configure the screens for the app on your mobile device. You can create sub-folders inside the jigs folder for categorization. All files in the jigs folder must have the .jigx extension, e.g., leave-form.jigx |
| translations | Create files for various languages using localization, then reference the file in your jig using the Text Locale property with id: file name. For more information, see . | |
| index.jigx | The index.jigx file is the app's home screen. It uses bottom tabs to determine the layout. See and Index settings for more information. | |
scripts/ expressions | Create .js files to define your that can be used in expressions. |
Indentation levels in color
IntelliSense & code snippets
Validation
Diagnostics icon
Diagnostics commands
Solution Diagnostics notifications
Jigx output
| Shortcuts | Mac | Windows |
|---|---|---|
| Publish all files in Jigx solution | ⌘R⌘R | Alt+R Alt+R |
| Publish an individual file | ⌘R⌘F | Alt+R Alt+F |
Jigx Dev Tools
Enabling Jigx Dev Tools
Problems pane
Debugging data in Jigx Console
Debugging functions in Jigx Console
Jigx logs
Jigx watcher
| Shortcuts | Mac | Windows |
|---|---|---|
| Publish all files in Jigx solution | ⌘R⌘R | Alt+R Alt+R |
| Publishing an individual file is useful if multiple developers work on the same solution. You only want to publish your changes. Note index.jigx, is a shared file that people all work on, so the last one updated on the server gets published. | ⌘R⌘F | Alt+R Alt+F |
| Invoke IntelliSense | Ctrl+space | Ctrl+space |
| Quick Fix | ⌘+. | Ctrl+. |
| F12 or ⌘+click | F12 or Ctrl+click | |
| shift+F12 F12 | shift+F12 F12 | |
| The swagger parser function | ⌘ + shift + p Generate Jigx Functions | Ctrl + shift + p Generate Jigx Functions |
| Color | Description |
|---|---|
| white | The file is issue-free. If connected to a Git repository, the file is committed. |
| red | The file has validation issues/errors/deprecated properties that must be fixed. The number of issues is shown by a red number on the right of the file name in the sidebar. |
| yellow | This means the file is connected to a Git repository and is modified; the letter M displays on the right of the file name in the sidebar. YAML is squiggled in yellow to show deprecated properties, hover over the YAML to see the expected property. |
| green | Indicates a new file has been created but not committed to the Git repository yet. |
| blue | Indicates the active screen on the mobile device that you are debugging in the builder using Jigx Dev Tools. |
Update local and REST providers
Only update REST Service
Local data provider
Solution data sync
Sync data just in time
| Property | description |
|---|---|
replace | All queued commands for the specified record and method type are replaced with the current action. For example, a record is created and then updated a few times. Using replace for the update method results in only two commands in the queue for the record: create and update. If replace is not used, there will be a command for every action: create, update, update, update. Replace is recommended for backend systems with rate limits. The
|
add | All commands are added to the queue. When the queueOperation property is omitted, the default is add. |
| Data | Conversion configuration | Result |
|---|---|---|
| REST Provider calls with files | Add the conversion to the REST function | GET - incoming SAVE - outgoing CREATE - outgoing UPDATE - outgoing |
| SQL Provider calls with files | Add the conversion to the REST function | GET - incoming SAVE - outgoing CREATE - outgoing UPDATE - outgoing |
| Datasource queries with files | Add the conversion to the datasource when using Dynamic Data. | Incoming |
| Actions with files | Add the conversion to the action when saving images and files. | outgoing |
| Core structure | |
|---|---|
conversions: | This holds an array of properties that should be converted. The following properties control the conversion:
Conversions can be set up as a static array of definitions or dynamically as an array returned by an expression. To set up dynamic conversions, use the expression |
Dynamic Data Overview
Tables in Dynamic Data
Form creates column and data record
Creating columns
Add data with JSON file
Deleting tables
Dynamic Files
| Provider | DATA_PROVIDER_SQL for making calls to Microsoft Azure SQL. |
| Connection | Provide the name of the connection configured in for the Azure SQL database. |
| Methods | Jigx supports the following methods in the provider:
|
Update local and REST providers
Only update REST Service
Local data provider
Connections in Jigx Management
Add a new connection
Azure SQL connection
Jigx IP address
Azure administrative portal
Adding IP addresses
Testing SQL connection
| Example | |
|---|---|
| Hello REST | In this section, a REST API is used to create a customers Jigx app, allowing you to add new customers and update and view customer details, location, and images. |
| MS Graph | The MS Graph examples use the User, Calendar, Mail, Insights, and To-do tasks to create a powerful Jigx apps with everything you need in one app. |
Update local and REST providers
Only update REST Service
Local data provider
Crendentials configuration
Credentials configuration
Credentials configuration
Credentials configuration
| Structure | Description |
|---|---|
| Continuation | Use when REST services limit the number of items to be returned. Jigx function calls can automatically repeat calls by specifying a continuation block. This overwrites the parameters in the original function call. |
| Conversions | Handles file format conversions between local-uris and base64, data-uri, or buffer when sending to or receiving from a REST datasource. |
disableTokenRefresh | Disables the auto-handling of 401 errors that refresh tokens twice. |
| error | Customize REST endpoint error messages to suppress or customize default error messages, log error details for more effective debugging, configure retries, and track errors through error logging. |
format | Specifies the format of the data returned from the REST server. Supported formats include json, text, pdf, and xml. This setting determines how the response is processed by the function. |
| forRowsInRange | This function's results are for a specific range in the data - all rows matching the specified column name and parameter value ranges (inclusive) will be removed and replaced with the results from the function. If not specified, the whole table is replaced with the function results, unless either for RowsWithValues is specified. |
| forRowsWithMatchingIds | This function's results are for specific rows with matching IDs, and other rows are not changed or removed. If not specified, the whole table is replaced with the function results, unless either forRowsWithValues and/or forRowsInRange is specified. |
| forRowsWithValues | This function's results are for specific rows in the data - all rows matching the specified column name and parameter value pairs will be removed and replaced with the results from the function. If not specified, the whole table is replaced with the function results, unless forRowsInRange is specified. |
functionId | Used to override the name of the function. Expected value is a string that respects the following rules: The first character has to start with a letter. The name can contain alphanumeric or symbols '-' and '_'. The name cannot contain spaces. The name cannot end with special characters. The length must be between 2-50 characters. |
| guard | Guard functions allow you to control what happens after a query runs by conditionally executing additional logic. These functions are called after a query completes and can invoke any other function. |
| inputTransform | When the function format is JSON, the request body is generated using the inputTransform, a JSONata expression that can reference parameters defined in the function. |
keepTempIds | If set to true, temporary Ids in local data will not be deleted on sync. This does not apply when forRowsWithMatchingIds is set to true. |
method | Jigx supports the following methods when making REST calls: DELETE GET HEAD PUT PATCH POST |
| operations | A function can specify zero or multiple table operations to perform on the solution's local SQLite database. |
output | The function’s output is returned to calling actions or functions. If an outputTransform is defined, its result is returned; otherwise, the full response from the REST provider is used by default. |
| outputTransform | The outputTransform is a JSONata expression that converts the REST response into JSON for local SQLite insertion. |
| parameters | Function parameters are used to pass data into the function definition from the jig that uses the function. It can be used in body, query, path, and also as input parameters for procedures and views. |
provider | DATA_PROVIDER_REST for making REST service calls. |
| queries | Queries in functions provide Just-In-Time (JIT) access to the latest local data, evaluated during function execution. The results can be used in function expressions. |
url | The URL of the service that must be called. Jigx supports path and query parameters in the URL. Path parameters are tagged with curly brackets {}. Jigx will replace the path parameters with the values of the parameters defined in the parameter section of the function definition. Query parameters specified in the URL will be removed by Jigx and replaced by parameters defined in the parameters section of the function definition with a location property of type |
| when | Specify a condition for when to execute a function (default) and when to skip and not execute a function based on the local state of the database. The when expression is evaluated after the parameters and queries are evaluated. The when expression is evaluated before token credentials are checked and inputTransforms are evaluated. The when expression is re-evaluated on each continuation. |
Jigx functions
Functions code completion options
| Example | |
|---|---|
| Hello REST | In this section, a REST API is used to create a customers Jigx app, allowing you to add new customers and update and view customer details, location, and images. |
| MS Graph | The MS Graph examples use the User, Calendar, Mail, Insights, and To-do tasks to create a powerful Jigx apps with everything you need in one app. |
Generate Jigx functions
File options
| Options | Description |
|---|---|
location | The location determines where the parameter will be applied in the REST call as follows:
|
type | Type is specific to the REST call being made. Most types are defined as strings when they are used in path, query, or body locations. The available types are When types are declared in authentication header parameters, they are specific to the authentication type being configured. |
required | The required value can be either true or false, indicating whether the parameter must be provided when the function is used in a jig’s datasource. Parameters used in URL paths must be set to required: true; otherwise, the function will generate an error. Set this property to true if the REST call requires the parameter, or false if the parameter is optional. |
value | Provide a value for the parameter based on its defined location (e.g., query, header, path, or body) and type (e.g., string, number, boolean). |
| Options | Description |
|---|---|
when | This condition determines when pagination continuation should occur. The continuation will execute only when the value exists in the API response. |
url | This specifies the complete URL for the next page of results. Certain APIs, such as Microsoft Graph, provide the full continuation URL in the @odata.nextLink response field, which includes the base endpoint plus any necessary query parameters (like skip tokens or cursors) to retrieve the subsequent batch of data. This eliminates the need to manually construct pagination URLs. Other APIs require the full url to be specified. |
parameters | These are the parameters required for continuation requests. Unlike the initial request, which included the optional $top query parameter, continuation requests only need the authentication token. |
| Property | Purpose |
|---|---|
onInitial | Runs guard before the initial REST call. |
onContinuation | Re-evaluates guard on function continuation. |
onRetry | Runs guard before retrying a failed function. |
| Properties | Description |
|---|---|
function | The name or functionId of the function to execute as the guard, before the main function, to determine whether the main function should be executed. |
Parameters | parameters passed to the guard function from the specified function. |
onContinuation | Determine if the guard function should be executed on a continuation call. Defaults to true. |
onInitial | Determines whether the guard function executes before the first call to the REST function. Default is true. If set to false, the guard function will execute in the defined execution order. |
onRetry | Determines whether the function should execute a retry call. Defaults to true. |
operations | Operations to run if the guard function fails. Used to update local data, show messages, or log state. |
result | The result of the guard function is evaluated to determine whether the main function should be executed. If the guard function fails or the result of the expression is falsy, the main function is not executed. The output of the guard function is available to expressions and scripts using =@ctx.guard.output |
when | Condition to determine if the guard function itself should execute. |
| Expression | Description | |
|---|---|---|
| output | =@ctx.guard.output | Output of the guard function is returned to the function as actions. If specified, the output of the function is the result of the expression; otherwise, the output is defined as the default output of the REST provider. |
forRowsInRange
Combined properties
| Scenario | Combinations | Results |
|---|---|---|
| Scenario 1 (Default) | No forRowsWithMatchingIds + no operations | Wipe and sync |
| Scenario 2 (Automatic) | forRowsWithMatchingIds: true + no operations | Automatic upsert-merge |
| Scenario 3 (Manual) | forRowsWithMatchingIds + explicit operations | You control the behavior |
forRowsWithMatchingIds, no operations (Default behavior)forRowsWithMatchingIds specified, no operationsforRowsWithMatchingIds with explicit operationsforRowsWithValues
| Property | Description |
|---|---|
conversions | Converting files runs per operation. This holds an array of properties that should be converted. The following properties control the conversion:
Conversions can be set up as a static array of definitions or dynamically as an array returned by an expression. To set up dynamic conversions, use the expression: |
forRowsWithValues | Only applies to operation.delete-insert |
forRowsInRange | Only applies to operation.delete-insert |
parameters | Only applies to operation.execute_sql. The parameters used in the above statement. |
primaryKey | Specify the remote data column that must be used as the primary key in the local data, such as Customer ID. This allows you to specify an expression (=@ctx.record.CustomerID) to define the primary key, including the ability to reference the whole record. This enables the building of dynamic keys, for example, by concatenating multiple fields from the record to construct an ID, timestamp, or GUID. |
records | What records to use for the table operation, can manipulate data. Evaluates the expression against the function inputs and result to construct the records for the specified table. The constructed data will be stored in the table. |
statements | Only applies to operation.execute_sql. List of statements to execute in sequence. Multiple statements can be configured to execute in sequence.statement - the SQL statement to execute against the solution database. |
tables | Only applies to operation.execute_sql. The tables affected by the statements. Before executing the statements, a check ensures that the tables exist. After execution any datasources that use these entities will be notified that the database was changed. |
timeStamp | Use a timestamp such as last modified from the remote data that must be used as the timestamp in the local table. |
type | See the table operations types in the table below. |
when | Specify the condition under which the function should execute (default) and when it should be skipped. |
| Type | Property | Description |
|---|---|---|
| DELETE_INSERT (used to sync data) | operation.delete_insert | Deletes old records that match a specified range and rows with matching values and inserts new records. Deletion runs at the beginning of the function. The table is only cleared on non-continuation operations on the first call. Uses this to overwrite the local data with the remote data. |
| UPSERT_REPLACE | operation.upsert_replace | Appends new records and replaces matching existing records. (Continuous update). The data of any existing record is replaced with the data from the matched new record. Records are matched by id (primary key). Use this type to append records to the local data and replace any existing records with the same id, leaving unmatched records unchanged and undeleted. |
| FIND-REPLACE | operation.find-replace | Executes an operation to find and replace values in local tables. You can also decide whether to find and replace records in the CommandQueue. |
| UPSERT_MERGE (used on CRUD methods and output transform) | operation.upsert_merge | Appends new records and merges matching existing records. The data of any existing record is merged with the data from the matched new record. Only top-level properties are copied, overwriting any existing top-level properties. Records are matched by id (primary key). Use this to append records to the local data and merge any existing records with the same id, leaving unmatched records unchanged and undeleted. |
| EXECUTE_SQL | operation.execute_sql | Executes a custom SQL operation specified with the SQL statement and parameters. This is the same functionality as the execute-sql action, which runs when a button is tapped; here, it runs when the function finishes or on continuation. |
| records | =@ctx.record.{primaryKey} | Defines the primary key, including the ability to reference the full record. |
operations:
# Only when there's NO X-opsPrimaryKey parameter (bulk processing mode) then,
# Deletes all existing records from folders-split-queries table
# Inserts new records by transforming each folder from $.folders array.
# Maps folder data to a flattened structure with space information included.
- type: operation.delete-insert
table: folders-split-queries
when: =$not($boolean(@ctx.parameters.X-opsPrimaryKey))
records: |
=$.folders.{
"id": id,
"name": name,
"orderIndex": orderindex,
"overrideStatuses": override_statuses,
"hidden": hidden,
"archived": archived,
"task_count": task_count,
"spaceId": space.id,
"spaceName": space.name
}
# Store Specific Folder (Primary Key Mode)
# Only when X-opsPrimaryKey parameter exists (single record mode), then
# Uses either the provided primary key OR the output name as the primary key.
# Targets a specific record for update rather than bulk processing.
# Same data transformation as above but for targeted updates.
- primaryKey: >
=$boolean(@ctx.parameters.X-opsPrimaryKey) ?
@ctx.parameters.X-opsPrimaryKey:@ctx.output.name
type: operation.delete-insert
table: folders-split-queries-primary
when: =$boolean(@ctx.parameters.X-opsPrimaryKey)
records: |
=$.folders.{
"id": id,
"name": name,
"orderIndex": orderindex,
"overrideStatuses": override_statuses,
"hidden": hidden,
"archived": archived,
"task_count": task_count,
"spaceId": space.id,
"spaceName": space.name
}
# Iterate through each folder,
# for each list within a folder, creates a record linking the list to its
# parent folder. Processes lists that don't belong to any folder.
# Sets folderId and folderName to null
# Uses $append() to merge folder-based lists and folderless lists into a single array.
- type: operation.delete-insert
table: lists-split-queries
# Convert list thumbnails from buffer to local-uri for efficient storage
# Operations are not aware of conversions configured at the function level.
# Each operation must define its own conversions property to handle file
# format transformations.
# Function-level conversions do not cascade to individual operations.
conversions:
- property: listThumbnail
from: buffer
to: local-uri
convertHeicToJpg: true
records: |
=$append(
$reduce(folders, [], function($acc, $folder) {
$append($acc,
$map($folder.lists, function($list) {
{
"listId": $list.id,
"listName": $list.name,
"listThumbnail": $list.thumbnail,
"folderId": $folder.id,
"folderName": $folder.name
}
})
)
}),
$map(@ctx.queries.folderless-lists, function($list) {
{
"listId": $list.listId,
"listName": $list.listName,
"listThumbnail": $list.thumbnail,
"folderId": null,
"folderName": null
}
})
)
| Type | Description | Returned value |
|---|---|---|
records (default) | Returns all matching records | Array of objects |
record | Returns the first matching record | Single object |
scalar | Returns a single value from the first column of the first record | Single value (string, number, etc.) |
| Properties | Description |
|---|---|
dependencies | The queries that this query depends on. They will be executed before this query. Dependencies allow you to stop recursive queries, because queries can be inputs to each other. |
jsonColumns | The columns that are automatically parsed as JSON string. Defaults to no JSON columns to parse. |
onContinuation | Set to false re-runs the query on each continuation of the function. Defaults to true, so the query only runs initially by default and not again on each continuation. |
parameters | Named parameters used in the query statement. They are referenced using the @ prefix (e.g., @id). If not prefixed manually, the @ is automatically added. Defaults to no parameters. |
resultType | Defines the expected result format. Can be one of: records (default), record, or scalar. |
statement | The SQL query statement to execute. |
tables | The tables to use in the query. Defaults to none. These tables are validated to exist before the query is executed. |
| Where | When |
|---|---|
Main function | Determines whether the function should be executed. The when expression is evaluated after the parameters and queries are evaluated. The when expression is evaluated before token credentials are checked and inputTransforms are evaluated. The when expression is re-evaluated on each continuation. |
Operations | Determines whether the operation should execute. Useful for selectively inserting, updating, or transforming data. |
Error handler | Determines the conditions under which the error should be executed. Specify one or more error handling definitions. The first rule that matches the when condition will be used. A rule without a when condition will become the default error handler. If no rules are specified, default error handling will be used, i.e., checking for actual errors or using HTTP status codes and messages for REST providers. |
Guard function | Evaluates whether the guard function should run, allowing conditional validation or control. |
Standard error handling
Customized error handling with alert
Error function alert properties
| Property | Description |
|---|---|
alert | See Configuring error alerts. |
description | Description of the error for logging purposes. Provide a detailed message of the error to write to the logs. Defaults to the provider's description if absent. For example, the REST provider uses the HTTP status code and message. The description property supports localization. |
details | Add additional error details for logging purposes. Defaults to the provider's details if absent. |
notification | Determines whether the error alert message notification should be shown on the device. (true/false) |
operations | Additional table operations for the error table. See /pages/htfriCQTAbMWrvlrjmxO for more details.
|
retry | Provides the ability to configure an automatic retry, set a delay time before the retry is executed, and specify the maximum number of retries allowed. By default, Jigx automatically handles 429 (Too Many Requests) error responses for CRUD and sync methods by retrying the request up to three times, with a five-second delay between each attempt. If the request still fails after the third retry, the error is raised in the app. You can customize this behavior by configuring the handling of the 429 status in the error property. |
title | Title of the error for logging purposes. Defaults to the provider's title if not provided. The title property supports localization. |
when | Checks if the result of the function is an error, the first one that resolves to true is used.
|
| Properties | Description |
|---|---|
actions | Interactive buttons or controls displayed within the alert let users respond or take specific actions. Use IntelliSense to see the list of available actions. |
title | The main heading text is displayed at the top of the alert. |
description | The detailed message content that explains the alert’s purpose, provides instructions, or delivers additional information to the user. |
dismiss | Configures how users can dismiss the alert. You can enable a gesture dismissal and set an automatic dismissal time.
|
icon | The icon displayed alongside the alert content provides visual context and helps users recognize the alert’s type or purpose. The alert’s style property determines the icon color. If no style is set, the default isWarning style is applied. |
group | Grouping allows you to manage multiple alerts under a shared identifier. This ensures that only one alert from a group is visible at a time, preventing alert overload and improving the user experience. |
group |
Use |
group |
|
style | Visual styling options let you set the tone of the alert:
|
subtitle | Secondary text that appears below the title, providing additional context or supplementary information. |
| Variables | Value |
|---|---|
| commandId | Unique id logged for the item on the commandQueue. The id matches the id in the entity table. |
| correlationId | The unique identifier that appears in the app. It is used in troubleshooting to help identify specific entries in the logs and to follow the user's journey while using the solution in the app. By filtering logs using this ID, you can troubleshoot issues more effectively. |
| entity | The specified table where the error context is logged |
| error |
|
| parameters | Specify any of the parameters in the function to be logged to the error table. |
| request |
|
| response |
|
| solution |
|
| user |
|