RFC
From UG
(→RFC 1 Auto BCC list) |
|||
| Line 5: | Line 5: | ||
Misc specs that are in RFC stage. | Misc specs that are in RFC stage. | ||
| - | == | + | == RFC1 Auto BCC list == |
This an e-mail distribution list associated with specific ASN Portal. | This an e-mail distribution list associated with specific ASN Portal. | ||
Revision as of 23:55, 8 March 2013
Contents |
Info
Misc specs that are in RFC stage.
RFC1 Auto BCC list
This an e-mail distribution list associated with specific ASN Portal.
To be managed through Portal Admin.
Any comment posted into Com tab gets also send to this list.
RFC 2 Urgent CT Flag
Request by Arden.
In some cases ASN record becomes Urgent. There is also a Reason associated with it.
We want to add attribute to ASN/CT record that indicates that it is urgent or not (checkbox) and associated Reason (dropdown).
Each Client Company has its own List of Reasons. Should be managed through Admin.
ASN is set as urgent by special type of Planner called Urgency Planner (to be set in user profile).
If ASN is set as urgent this can not be undone (checkbox becomes read only).
In case when for some reason Planner wants to say that it is no longer urgent ASN he will have to check another check box "Urgency canceled". Thich checkbox is also editable by Jag Ops.
All this data is only visible to Urgency Planner and Jag Operator.
When any change happens to above:
- post comment into Com tab
- send e-mail to #Auto BCC list
