The menu “controls and automatisms” allows to manage and parameterize efficiently and finely the triggering events as well as all that ensues from it … automatically.
Sending mails, changes of status, status, loading of notes …
The contact defined as requestor on current item; sometimes appears as “contact” (on quotation and order, for instance) and sometimes have no meaning (for instance for milestone).
It is possible to define indicators on most elements.
You can set the indicators on:
actions
activities
customer invoices
customer invoice exchanges
customer orders
customer quotes
individual expenses
issues
meetings
milestones
supplier orders
projects
project expenses
supplier invoices
supplier offers
questions
requirements
risks
payment deadlines to suppliers
test sessions
and finally the tickets
Depending on type of elements the type of indicators that can be selected in list differs.
Some indicators are based on delay (due date), some on work, others on cost.
For each indicator, a warning value and an alert value can be defined in days or hours (working or not).
Indicator display
On the Today screen, on the item summary lists, a color code is applied to the line if the item is subject to an indicator and is concerned by the alert values entered.
Color code applied to lines whose elements are subject to indicators¶
On the screen of an element subject to the indicators and whose values enter the alert zone, an icon is displayed in front of the description of the element.
display of the indicator and the values applied to the element¶
When you hover over the icon, the raised indicator on that item is displayed along with reminder and alerts values.
Mail receivers
List of addresses of the mails.
The list is not nominative, but defined as roles on the element.
Each addressee will receive mail only once, even if a person has several “checked” roles on the element.
The definition of notification generation is based on the following:
The title that can contain the field values of the notifiable element or its sub-elements
The element of the system that determines the notification, called “Notifiable Element” (notifiable)
The type of notification (Alert, Warning, Information)
The notification rule notifying the elements related to the generation of a notification
The content may also contain the field values of the notifiable element or its sub-elements.
The date (referred to as the reference date) at which the notification must be generated. This is one of the dates of the notifiable item that is not the creation date.
The generated notification receivers. Fields of the notifiable element or its sub-elements that refer to users.
The choice to send, or not, to all the sending of emails at the same time as the notifications.
Section Description
This section briefly describes the type of notification
Its name, its type: alert, information or warning as well as the notifiable element.
Section Notification title
This section allows you to give a title to your notification.
This title will be the object of the programmed mail if you tick the box send an email in the receivers section
You can add dynamic fields with help to insert a dynamic field in the title
The title of the notification can therefore contain fields of the “notifiable” object and its linked elements via an idXXX.
where XXX is the name of the linked item.
Select an object and / or a field and click the Insert button so that the dynamic field with the correct syntax fits directly in the title, where the cursor is.
In this case, the syntax must be: #{the name of the field} …
Tip
#{billId} - Invoice not paid - Sent on #{sendDate}
If the rule (see below) of the instruction on the invoice of ‘billId’ 2019-12-30-0001 whose sending date is 30-12-2019
then the title of the notification will be:
2019-12-30-0001 - Invoice not paid - Submitted on 12-30-2019
This rule determines which instance of the item will generate a notification.
The syntax is the one we take for a WHERE clause in an SQL statement.
Tip
Scheduling a notification for all invoices where the amount has been paid = total amount AND project name ‘ACME’
#{paymentAmount} < #{fullAmount}
AND
#{idProject.name} = ‘ACME’
AND
isnull (#{paymentDate)
Note
The rule to apply is not mandatory. If the rule is empty, then only the reference date is used to determine whether or not a notification is generated.
In addition to choosing a dynamic field, you can choose to use an operator or function with the following elements:
Notification content
This section is mandatory
You can also add dynamic fields with help to insert a dynamic field in content in the same way as in the description section
to display the status list.
to create a new checklist line.
to update an existing checklist line.
to delete the corresponding checklist line.
allows you to refresh notifications without waiting for the scheduled update.
provides direct access to the notifications screen.
