Step 1- Create Watcher for a record
Watchers can be configured to watch changes that have been made to records or views. On this page, you can specify the record to be monitored, fields to which the conditions are applied, and the actions that are taken when the conditions are met.
To create a Watcher, go to, Dashboard > Watchers > Add new
To edit an existing Watchers definitions, go to, Dashboard > Watchers, and then select a Watcher from the list.
Field | Description |
---|---|
Watcher details | |
ID | Required. Enter an ID for the Watcher. This field is editable only when the Watcher is created and is displayed as a read-only field when editing the Watcher. |
Watch a view | Enable to create a watcher for a view. |
Record Type/View Type | Required. From the drop-down, select the record type or view type for which you want to create a watcher. This field is editable only when the watcher is created and is displayed as a read-only field when editing the watcher. |
Permissions | Permissions can be set to allow users in a group to:
Group name: Enter the name of the group Ensure that you set the required permissions for a record definition before you save it. If you fail to do so, users (including the creator of the record definition) are not allowed to view or edit it. |
Conditions | The condition is displayed in the Conditions section. Set conditions using the following options. A matching condition, for instance, "When the City (Field name) is equal to (predicate) London (Value)" can be set here. Field name: Select a field name from the drop-down. The list may display fields that are set to not be displayed in the table. Value: Enter a value to match the predicate settings. Click |
Actions | When the set conditions are met, you can choose to send an email, to make outgoing API calls to other systems, or use a custom plugin.
Send an email To send an email you can set the following details:
Make an API call The system can also make an outgoing API call in response to an observed event. API settings:
Successful HTTP Status codes: Enter a status code to represent how the request was processed. Status codes are expressed through 3-digit numbers.
Headers: Headers are used to give server instructions about the variables in the request. Click Add to add more headers.
Fields: In this section, you can define the parameters that are sent and processed when the API call is made. The request can be to create, update, delete or request data. Click Add to add multiple fields.
Using a custom plugin Predefined plugins (API and email) are provided with the WatcherSubscriber. You can, however, add other capabilities by writing custom plugins. For example, you can create a custom plugin which communicates with an external system when the watcher conditions are met. An example of this could be where you want to automatically trigger a purchase order to be generated on your SAP system if the watcher detects a parameter change in a record. You could write your own plugin to take to output of the watcher and pass it to your SAP system for processing. If you are setting up a custom plugin, ensure that you start the custom plugin also with the predefined plugins when starting the WatcherSubscriber.
Retry: The option is disabled by default. If enabled, watchers automatically re-tries the action that failed. |
Click Save to save your changes. Click Revert changes to undo the current changes and revert to the last saved version.