The Settings > Automation > Rules page lists all your automation rules, with the following information:
- Status: Whether the automation rule is enabled or disabled.
- Trigger: What trigger activated the automation and, if scheduled, how often it runs. Several triggers or schedules show as a semicolon-separated list here and in the rule version header, with a tooltip for the full text when it’s truncated.
- Last run: When the automation rule was last activated.
- Last run status: Whether the last rule activation was successful.
Only admin users can manage automation rules.
Add a new automation rule
To add a new automation rule to Dawiso:
- Go to Settings
> Automation > Rules and click + New rule.
- Enter the automation’s key, name, and description (last one is optional for better overview). Only the key cannot be changed later.
- Save the rule.
- You are redirected to the built-in Dawiso editor, where you can configure the automation rule using a JSON file. You can also use a text editor like Visual Studio Code instead.
- Once the JSON file is configured, save and install the automation rule.
For documentation on configuring automation rules, see the automations asset article.
Edit automation rule details
To edit your automation rule and its details:
- Select your automation rule and click + New version.
- In the top-right corner, click Edit rule definition to change the automation rule name or description. The key cannot be changed for an installed rule.
Tip
You can also click the three dots next to your automation rule and select Edit rule definition.
- In the built-in text editor, you can edit the automation rule itself.
- Once you’re finished with the changes, click Save, or Save & Install the rule immediately.
You don’t have to install the new version right away, but save your progress. You can create as many drafts as you want, but a new draft isn’t saved automatically.
Export and import automation rules in bulk
To move many automation rules between environments (for example from a test instance to production), use the Export and Import buttons on the Settings > Automation > Rules page. Only admin users can use them.
Export
- Click Export. A dialog lists all automation rules by name and key.
- Select the rules to export, or use Select all. Only rules with an installed version can be exported; rules without one are shown but cannot be selected.
- Click Export. Dawiso downloads a ZIP file named
automations-<instance>-<UTC timestamp>.zip.
The ZIP contains one <enum_key>.json file per rule. Each file holds the rule name and the definition of its last installed version:
{
"name": "Notify steward on review",
"definition": {}
}
Import
- Click Import and choose a ZIP file.
- Rules are matched by
enum_key, which is the file name without.json. Rules that are not in the ZIP are not touched. For each rule in the ZIP:- A rule that does not exist yet is created.
- An existing rule is updated: renamed if the name differs, with a new version validated and installed, and any open draft discarded.
- Dawiso reports the result, for example Created: 2. Updated: 1.
The numbers show how many rules were queued. If a definition fails validation in the target environment, that rule stays as a draft version instead of being installed.
The whole ZIP is rejected, and no rule is changed, if any file in it is invalid:
- The file is not a ZIP.
- It contains a non-JSON file.
- A file name is not a valid or unique
enum_key. - The JSON is invalid.
nameordefinitionis missing or invalid.
Dawiso shows the reason. Limits: 50 MB per upload, 500 files per ZIP, and 10 MB per file.
Enable or disable an automation rule
To enable or disable your automation rule:
- Identify your automation rule.
- On the right side, click the three dots.
- Click Enable or Disable depending on the current status.
Delete an automation rule
To delete your automation rule:
- Identify your automation rule.
- On the right side, click the three dots.
- Click Delete and confirm.
Audit logs
The Settings > Automation > Audit Logs page lists the changelog for your automation rules.
Click a log ID for more details on the process.