Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

or in Workflow you would enter parameters in the Additional parameters box e.g.

Switch / Parameter

Effect

-? Or -help

To print out the help for the switches. Will not attempt to run.

<userlist>

Optional comma separated list of user ids. The console will only attempt to run on these users. Note that the list cannot contain any spaces.

E.g. Astun.MyAlerts.Console.exe 1,3,4

-debug

To run the console in debug mode. In this mode checks are still carried out and a new snapshot written to the cache database, but no email will be generated.

Note
titleSwitch order

If you use -debug then this must be the first parameter in the list as per the above screenshot otherwise the following parameters, which are reliant on debug being enabled, will not work.


Note
titleLast run time
When the console is running in debug mode it will not update the last run time in the database, even if the cache database is updated. For examples of how to  set the last run time, see the SQL code in Flush out major changes below.


-nowrite

Only applicable in debug mode. This will stop the writing of any cache entries.

-email

Only applicable in debug mode. This will generate and send the email.

-address=<new-email>

Only applicable in debug mode with –email set. This will cause all emails generated to be sent to the specified address.

-workspace=<workspace_name>This will just run My Alerts for the specified Workspace. ( Only required if Workspaces are enabled). Users tied to workspaces will not be included in runs unless this parameter is specified.

Flush out major changes

When a large number of administrative changes have been made, such as to the structure of the data or an import of new data, for example, adding a new layer, it's usually best not to send a flood of emails out to My Alerts subscribers.

...