Triggers/DE

From Sit
Jump to: navigation, search
Broom icon32.png This article (or section) needs work.
Please help us and our readers by clicking the edit link above and expanding/improving this text.
Broom icon32.png Diese Seite nimmt Bezug auf eine deutsche Übersetzung, die sich noch in der Entwicklung befindet.
Sie ist aber schon im Subversion Repository zu finden. Einen Überblick über alle deutschsprachigen Seiten des Wikis bietet folgender Index
A User Trigger action

Ein Trigger wird durch das Eintreten eines Ereignisses im SiT! ausgelöst. Es gibt viele solche, z.B. ein Trigger, der feuert sobald ein neues Ticket hinzugefügt wird. Sie können bestimmte Aktionen an diese Trigger binden, z.B. dass eine Mitteilung oben in den SiT! Webseiten eingeblendet wird, sobald Ihnen ein Ticket zugewiesen wurde.

Trigger sorgen dafür, dass Ihnen die Benachrichtigungen oder den AdministratorInnen die Systemaktionen im SiT! angezeigt werden.

Contents

Bearbeiter/innen

Info.png Info: Trigger-Aktionen für sich selbst zu erstellen bedeutet schlicht, dass Sie wunschgemäß bei Ereignissen Meldungen erhalten.

Zur Konfiguration ihrer Trigger-Aktionen wählen Sie im Menü SiT! -> Meine Einstellungen -> Benachrichtigungen

Administrator/innen

Info.png Info: Die Systemaktionen beziehen sich nicht auf die Bildschirmmitteilungen sondern auf andere Arten von Aktivitäten und den Versand von E-Mail (z.B. an Kunden)

Bei Trigger-Aktionen des Systems spielen die SiT! User üblicherweise keine Rolle. Es geht da z.B. um automatisch versandte E-Mails an die Kontaktpersonen oder darum, Ereignisse im System-Journal festzuhalten.

SiT!-Administrator/innen können die Systemaktionen unter folgendem Menüpunkt konfigurieren SiT! -> Systemeinstellungen -> Systemaktionen

335triggerssettings.png

Example Triggers

User triggers

Create a notice based on NOTICE_INCIDENT_ASSIGNED. Rules: {userid} == 1

This creates a notice for the current user based on the template NOTICE_INCIDENT_ASSIGNED when the incident has been (re)assigned to the current user (ID of 1)

Create a notice based on NOTICE_INCIDENT_NEARING_SLA. Rules: {ownerid} == 1 OR {townerid} == 1

This creates a notice for the current user based on the template NOTICE_INCIDENT_NEARING_SLA when the current user (ID of 1) either owns or temp owns the incident

System triggers

Incident Created: Send an email based on a EMAIL_INCIDENT_LOGGED_CONTACT template. Rules: {sendemail} == 1

This send an email based on the EMAIL_INCIDENT_LOGGED_CONTACT template when the checkbox 'Send opening email to incident contact?' is checked. As this is a system trigger, this occurs for any user.

Service Limit: Send an email based on a EMAIL_SERVICE_LEVEL template. Rules: {serviceremaining} <= 0.2

This sends an email to the salesperson associated with the site (as specified in the EMAIL_SERVICE_LEVEL template) when their balance of services falls below 20%

Rules and Parameters

Trigger rules specify in which conditions the trigger will fire. If you create an action to create a notice on incident assign, you we receive one for every incident (re)assign. If you create a rule of '{owner} == {currentuser} OR {towner} == {currentuser}', upon saving it will convert {currentuser} into your user ID and you will only receive assign notices when you are either the owner or the temporary owner.

Rule Syntax

It is very important that your rule syntax is valid. SiT does not currently check trigger rules for validity before saving and using them, which could mean that SiT will break badly when it attempts to run the trigger and process your badly formed rule.

Parameters are variables you can pre-fill yourself to pass to the trigger. An example is the {numupdates} variable used for {updatetext}, if you set a parameter of 'numupdates = 4', {updatetext} will have 4 updates in. Another example would be providing an email address if you wanted to email a support manager every time an incident was created for example. For this you would have a parameter of 'useremail = manager@company.com'.

Trigger Types

The following triggers which are available for use and the variables that can be used in their repective rules

  • Contact reset password

Occurs when a contact wants their password resetting


  • Holiday Requested

Occurs when a user requests a holiday

{approvaluseremail}
  • Incident Assigned

Occurs when a new incident is assigned, or reassigned to a user

{contactid} {contractid} {contractproduct} {incidentid} {ownerid} {townerid} {siteid} {sitesalespersonid} {userid}
  • Incident closed

Occurs when an incident is closed

{awaitingclosure} {contractid} {contractproduct} {feedbackurl} {incidentid} {notifycontact} {notifyexternal} {ownerid} {townerid} {siteid} {sitesalespersonid} {userid}
  • Incident Created

Occurs when a new incident has been created

{contactid} {contractid} {contractproduct} {ownerid} {townerid} {sendemail} {siteid} {sitesalespersonid} {userid}
  • Incident Nearing SLA

Occurs when an incidents nears an SLA

{contactid} {contractid} {contractproduct} {incidentid} {ownerid} {townerid} {siteid} {sitesalespersonid} {userid}
  • Incident Review Due

Occurs when an incident is due a review

{contactid} {contractid} {contractproduct} {incidentid} {ownerid} {townerid} {siteid} {sitesalespersonid} {userid}
  • Incident updated externally

Occurs when an incident is updated by someone external

{contactid} {contractid} {contractproduct} {incidentid} {ownerid} {townerid} {siteid} {sitesalespersonid} {userid}
  • Incident updated internally

Occurs when an incident is updated by an engineer

{contactid} {contractid} {contractproduct} {incidentid} {ownerid} {townerid} {siteid} {sitesalespersonid} {userid}
  • Knowledgebase Article Created

Occurs when a new Knowledgebase article is created

 {userid}
  • Current Language Differs

Occurs when your current language setting is different to your profile setting

{currentlang} {profilelang}
  • New contact added

Occurs when a new contact is added

{contactid} {siteid} {sitesalespersonid} {userid}
  • New contract added

Occurs when a new contract is added

{contractid} {contractproduct} {siteid} {sitesalespersonid} {userid}
  • New Held Email

Occurs when there is a new email in the holding queue

{contactid}
  • New site added

Occurs when a new site is added

{sitesalespersonid} {userid}
  • New user added

Occurs when a new user is added


  • Scheduler action failed

Occurs when a scheduled action fails


  • SiT! Upgraded

Occurs when the system is upgraded


  • Task Due

Occurs when a task reaches its due date

{taskid} {userid}
  • User Changes Status

Occurs when one of your watched engineers changes status

{userid}
  • User reset password

Occurs when a user wants their password resetting

{userid}
  • Waiting Held Email

Occurs when there is a new email in the holding queue for X minutes

{holdingmins}
  • Service Limit

Occurs when an billable incident is approved

{serviceremaining}
Personal tools
project