A release is a frozen copy of a decision flow. You can test it, check it against your policies, and deploy it to an endpoint. Later edits to the decision flow do not change an existing release. They are included in the next release.
The release list
"Releases" in the "Publish" section of the main menu lists all releases in your account, with the newest first. Each row shows the "Release name", the "Decision flow" used to create it, and the "Release time". Hover over the help icon next to the time to see who released it. A release remains available even if its decision flow has been deleted. The flow appears as "Deleted".
To create a release, open the decision flow and release it from there. See Releasing decision flow.
The release page
The header has three buttons:
| Button | What it does |
|---|---|
| "Deploy release" | Opens the deploy dialog. See Deploying a release to an endpoint. |
| "Release details" | Shows the decision flow, the release time, the person who released it, and the release notes. |
| "Further actions" | "Compare with ...", "Download report (PDF)", "Download report (Markdown)" and "Delete". |
The tabs below the header appear in this order:
| Tab | What it is for |
|---|---|
| "Unit test" | Run one input through the release and read the output. See Releasing decision flow. |
| "Batch test" | Run many inputs at once. See Batch test. |
| "Rule mining" | Find rules in production data. Shown only when a decision archive is connected. See Rule mining. |
| "Compliance check" | Check the release against a policy document. See Compliance Check. |
| "Deployments" | Every deployment of this release, with the endpoint, the person who deployed it, and when it finished. The tab is disabled until the release is deployed. |
| "Approval process" | The progress of each approval started for this release. The tab is disabled until an approval starts. See Approval Sequence. |
Batch test
The "Batch test" tab runs a set of inputs through the release. The "Data source" select determines where the inputs come from and where the run takes place.
| Data source | Where it runs | What you give it |
|---|---|---|
| "Uploaded dataset" | In your browser, one call per row | A file with one JSON object per line, or a saved dataset |
| "Upload and run on node" | On your execution node | A file or a saved dataset, plus an optional analytics recipe |
| "From storage" | On your execution node | An s3:// or gs:// location, a credential, and an optional place to write results |
| "Decision archive (production data)" | On your execution node | An endpoint, a date range and a row limit |
"Upload and run on node" and "From storage" are included in the batch module of your subscription. "Decision archive (production data)" requires a connected decision archive and is covered in Backtesting.
Running an uploaded dataset
- Under "Upload file", choose a
.jsonl,.jsonor.txtfile containing one JSON object per line, then select "Start batch test". - Alternatively, open "Use dataset" and choose a saved dataset. "Manage datasets" lets you add a dataset from a file, give it a name and description, and reuse the same inputs across releases.
"Batch testing progress" tracks rows as they finish. When the run ends, "Batch testing results" lists each row with its status, input and output. Selecting an input or output cell displays its full contents. The eye icon in the "Compare" column shows what the release added or changed in that row, using the same "Tree", "Δ Tree", "JSON" and "Δ JSON" views as the unit test.
Results remain in your browser until you select "Clear results". "Download" saves all outputs in a single JSON Lines file.
Runs on the node appear as an analysis in the same view as Impact Analysis. The "Analysis history" lists all earlier runs.
Analysing batch results
Selecting "Analyze" above the batch results opens "Analyse results". For each measure, set a "Metric" (a JSONPath into the output), an optional "Dimension" for grouping, and an "Aggregation". Select "Add measure" to add more measures, then select "Analyze" to draw one chart for each measure.
"From recipe" loads the measures from a saved analytics recipe. The gear icon next to it, "Manage recipes", opens the recipe list in a new tab.
Reports
"Further actions" provides the release as a report for audit or review outside the portal. "Download report (PDF)" and "Download report (Markdown)" contain the same content: the decision logic of every step in the release.
Deleting a release
You can find "Delete" in "Further actions" on the release page and in the row menu of the release list. Deleting a release also deletes its compliance checks, batch test runs and analysis runs. Its deployments remain in the deployment log. An endpoint continues running the release deployed to it until you deploy another one.
Related Documentation: