Notices, notes and notifications

Notices make reference to an event and its date. They may or may not have a duration (start date and end date of the event), for example, a notice that refers to a meeting.

They are created either manually, or are programmed in an “Smart Box” template or are programmed as notifications in an existing “Smart Box”. They refer to an event or its absence, for example, a period of inactivity.

Notices may be configured to fire prior alerts to the date of the event. The alerts appear to, and are administrated by, the user to whom the notice has been addressed. He may remove, discard, or postpone the alerts.

The characteristics of notices are as follows:

  • They may have attached files and/or be linked to a “Data Smart Box” which one accesses directly from the notice.
  • They may be marked so that they are displayed in the calendar (if appropriate with their duration) of either the actual user or of other users to whom the notice is addressed.
  • The notice may also generate an email to some or all of the recipients. If the notice is linked to a “Smart Box” a hyperlink will appear in the email.

Notes may be created in any “Data Smart Box” and may also be a notice. The notes allow for replies that will be indented and that may be viewed in the notes section of the corresponding “Smart Box”.

Notifications are programmed notices in the “Smart Boxes”, which may be configured in their templates, for the occurrence of an event or its absence. The event may refer to the state of one phase in a workflow.

What does it solve?

Notices facilitate the collaboration among users. The possibility of incorporating scripting code in the templates allows one to establish different types of notifications with different recipients according to the event, for example, when there is a change of state in an attribute.

(See more…)

Print page
Bookmark the permalink.

Leave a Reply