Skip to main content

Provenance tags

This page lists the tags on the rows of the Server effects dialog. A provenance tag says where a row comes from: your browser, the server's dry run, or both.

Where you see them​

Open the Server effects dialog with Preview server effects or Preview on-complete effects. Each row in Notifications, Events and Server validation has a tag on the right. See Preview server effects.

How the app picks a tag​

The app compares the latest rule evaluation in your browser with the last Verify with server result for the same form. A row matches when the same rule produced the same action type in both.

  • Before you run Verify with server, every row from your browser is Simulated.
  • The dry run doesn't report notifications, so notification rows stay Simulated even after a dry run.
  • If a later Verify with server fails, the app keeps comparing against the last result that completed.

Tags​

TagHow it looksWhat it meansWhat to do
SimulatedBlue tagThe effect was evaluated in the browser and has no server report to compare with.Run Verify with server to compare. Notification rows always stay Simulated, because the dry run does not report notifications.
Server-verifiedGreen tagThe browser and the server both produced this effect.Nothing. The playground and the server agree.
Server onlyRed tagThe server reported this effect but the browser did not simulate it.Find out why the playground did not produce it: check the rule condition and the values in the form. See Why client and server results differ.
Not executed by this serverNo tag. The row is dashed and dimmed, with the note "Not executed by this server" or "Not executed by this server (requires 2.43)".The server version does not execute this action type, so it is shown for reference only.Treat the row as reference only. The server you are connected to will not run this action.
note

The server runs SCHEDULEEVENT on DHIS2 2.43 and later. On DHIS2 2.40 to 2.42, SCHEDULEEVENT and CREATEEVENT rows show "Not executed by this server (requires 2.43)". On 2.43, CREATEEVENT rows show "Not executed by this server", because the server declares the action but doesn't run it. The app reads the server version from the instance and treats an unknown version as 2.40.