The Dealer Programming form contains the Event Actions Programming and Post Processing actions related to the Dealer.
Event Actions Programming
Event Actions Programming overrides the company specified Action Patterns and alarm state. Event Actions Programming should be used sparingly and only when a global item cannot manage the dealer's requirement.
Adding Event Actions Programming to a Dealer
- Click the Pencil (✏️) icon, located on the upper-right-hand corner of the Event Actions Programming card.
- Find, enter, or select the event code to override.
- Select the Alarm value.
- Default - Uses the alarm status of the event code.
- No - Forces the event to log to history as a signal.
- Yes - Forces the event to deliver as an alarm to an operator.
- Residential - Forces the event to alarm for ONLY residential accounts.
- Commercial/Other - Forces the event to alarm for all types EXCEPT Residential accounts.
- Set the Action Pattern to use when an alarm presents to the operator.
- If necessary, add any additional alarm instructions. This should be used RARELY, and contain information that the operator MUST know to process the alarm and cannot be include in the Action Pattern.
- Repeat 1-5 as required by clicking Add.
- Click Done.
- Save (💾) the record.
Post Processing
The Post Processing allows automated actions on specific event categories for automating responses or taking additional actions.
Adding Post Processing Actions to a Dealer
- Click the Pencil icon (✏️) located on the upper-right-hand corner of the Post Processing card.
- Select the Event Category to apply Post Processing.
- Select the Action ID - This must have an action pattern for successful completion.
- Repeat as required by clicking Add.
- Click Done.
- Save (💾) the Record.
