๐ปDry Run Mode using UI
Last updated
Last updated
In this mode of operation all artifacts (files, documents and transactions) that are produced in the course of execution of the policy are stored in the local database but not sent out to Hedera or IPFS. The artifacts are stored in the database in a separate table specific for the โdry runโ mode. This also allows the trial for executing the workflow without real accounts.
There are different ways to start the Dry Run Mode after importing Policy.
When the Policy is imported, its in Draft status by default. This status can be seen in the Status/Actions column. To change the Draft status to Dry Run status, click on the drop down arrow and select Dry Run option.
When imported Policy is opened for editing, there's an option of changing the Policy status from Draft to Dry Run. The Dry Run option can be selected by clicking on drop down arrow and selecting Dry Run option as shown below:
Dry Run mode can be started by calling the following API:
To get complete information on the above API, please check : Dry Run policy
There are different ways to exit from Dry Run to Draft mode.
Policy, which are in the Dry Run status, can be changed to Draft/Publish state by selecting respective option from the drop down arrow. To change the Policy status to Draft, please select Stop option and to change the Policy status to Publish, please select Publish option.
Policy status can be changed from Dry Run to Draft/Publish by selecting from the drop down option in Policy Configurator Page.
Dry Run mode can be exited to Draft status by calling following API:
To get complete information on the above API, please check : Return policy to editing
There are two ways to open the Policy in Dry Run mode:
To open the Policy in Dry Run mode, click on a Go button in the Operation column.
There's a Go option in Policy Configurator page to view the Policy in Dry Run mode.