Wiki source code of 4.6 Message Management
Last modified by Admin User on 2023/06/30 10:26
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | The Message Management screen is available at all organisation levels and allows administrators to be assigned as the recipients of certain system messages: | ||
2 | |||
3 | 1. Defining one recipient for undeliverable eMail messages received as a result of failed transmissions from PECOS P2P. | ||
4 | 1. Defining recipients for all replies received to any system generated order transmission or approval message. | ||
5 | 1. Defining one recipient for error messages generated from failed workflow approval tasks and configuring an override eMail notification message. | ||
6 | |||
7 | The recipients of these eMail messages are selected from a list of available system administrators and it is recommended that an appropriate administrator be assigned to each setting in order to effectively manage potential configuration errors: both internal and external to PECOS P2P. | ||
8 | |||
9 | The level 2 (Company) provides the parent defaults and completion here is mandatory. | ||
10 | |||
11 | The same settings are provided for all L2 subordinate child organisations (i.e. levels 3 to 10) where configuration is optional. The system provides a check box as a means to identify when override settings are to be entered and invoked for an subordinate organisational level. The check box is called: "Override parent organisation message management definitions" and until selected, options are inactive and read only. | ||
12 | |||
13 | Where settings are not specifically provided for a subordinate organisation level (i.e. 3 to 10), the system will look up the organisation hierarchy until a parent setting is found, as far as level 2. | ||
14 | |||
15 | Where no valid recipient is defined at the L2, (i.e. the selection is empty or a selected administrator’s rights are retrospectively changed) all message failures and replies will be sent by default to the level 1 site administrator. In multi-organisational environments these messages will therefore be received by the Elcom Service Desk. | ||
16 | |||
17 | **Security Note.** Many organisations will employ spam filtering for eMail messaging. Problems may arise, for example, when an internal domain is present in a reply to address, for eMails that originate externally to that domain {for example, an eMail from admin@elcom.com will have a reply to as j.smith@myco.co.uk}. | ||
18 | |||
19 | Elcom strongly recommends that all failure and reply recipients are thoroughly tested prior to migrating into a live environment. If restrictions are experienced please contact the Elcom Client Services team in order for solutions to be discussed. | ||
20 | |||
21 | [[eMail Delivery Failures and Replies>>eMail Delivery Failures and Replies]] | ||
22 | [[Default Workflow Approver>>Default Workflow Approver]] |