Description
This article shows how to send a request through GMUS to run a Scenario Chain Set with G-Repository Client. A Scenario Chain Set can be run by itself or with a case, rule, or query. A checkUpdate parameter is also available when sending a request. The method type for requests in this article is POST.
In This Article
- checkUpdate Parameter
- Run a Scenario ChainSet with GRepository Client
- Run Scenario Chain Set with Test Data Case
- Run Scenario Chain Set with G-Rules
- Run Scenario Chain Set with G-Queries
- Run Scenario Chain Set with G-Case with G-Rules and G-Queries
checkUpdate Parameter
The checkUpdate parameter can be used to test when to update a Scenario. This parameter works with It can be set to:
- true - By default, the parameter is true and checks if the Scenario should be updated.
- false - Can be set to "false" to disable the check.
Run a Scenario ChainSet with GRepository Client
A REST request is made to the GMUS to run a Scenario Chain Set with the G-Repository Client.
JSON Payloads to execute Scenario Chain:
Example success response:
Run Scenario Chain Set with Test Data Case
JSON Payloads to execute G-Case using GMUS API.
Run Scenario Chain Set with G-Rules
JSON Payloads to execute G-Rules using GMUS API.
Run Scenario Chain Set with G-Queries
JSON Payloads to execute G-Queries using GMUS API.
Run Scenario Chain Set with G-Case with G-Rules and G-Queries
JSON Payloads to execute G-Case with G-Rules and G-Queries using GMUS API.