Wiki source code of 18.4.3 Activity

Last modified by Admin User on 2023/06/30 10:26
Show last authors
1 {{box cssClass="floatinginfobox"}}
2 {{toc/}}
3 {{/box}}
4
5 The first sub screen to be completed when creating a new task is the **Activity**. This is the activity to be undertaken by any document that agrees to the task C**riteria** that is defined in the same step.
6
7 [[image:PECOS Admin.WebHome@Fig 17.9 - Approval plan activity.png]]
8
9 = Task Name =
10
11 **Task Name **is **mandatory** and can be a maximum of 48 characters. Enter a name for the task to indicate what this task does or when the task will be invoked. For example: “Manager Approval over £100”, or “IT Notification”. Each task name must be unique within each plan.
12
13 = Action =
14
15 * **Action **is **mandatory** and must be selected from the drop down selection box. The available actions will vary slightly depending on the plan type.
16
17 * **Request Approval:** Send the document out to the task owner for approval.
18 * **Request Receipt:** Used in receipt plans to send a receipt object to the task owner for action or update.
19 * **Request Qualitative Action:** Used in receipt plans to send a receipt object to the task owner for review.
20 * **Request One Step Approval:** (Not available for invoice settlement plan types.) Send a requisition, order or change order out to the task owner for approval. Allow the approver to optionally approve or reject directly from the email message.
21 * **Require Receipt:** (Not available for invoice settlement plan types.) Invoke the 3-way match for this order and send an eMail to the task owner.
22 * **Notify User:** Send an eMail to the task owner.
23 * **Notify External Party:** Send an eMail to an external party and optionally copy it to an additional user.
24 * **Initiate External Process:** Initiate a process on an external server (e.g. budget review or real time price check).
25 * **Execute a Sub Plan:** Call and follow a sub plan of the same plan type.
26
27 = eMail Message =
28
29 Configuring an** eMail Message** for each step is** mandatory**. Click on the hyperlink to configure the eMail notification message to be sent to the owner of this activity. A sub window will open to configure the eMail. Messages are not required when the Activity Actions are either Initiate External Process or Execute Subplan.
30
31 1. When the following Activity Actions are selected a simple eMail must be configured:** Request Approval; Request Receipt; Notify User; Require Receipt and Request One Step Approval**.
32 [[image:PECOS Admin.WebHome@Fig 17.10 - Request approval eMail message.png]]
33 Complete the following mandatory fields:
34 1*. **eMail Subject Text**: This is the eMail subject.
35 1*. **eMail Body Text**: Text to appear in the main body of the eMail, describing what activity is to be undertaken and why. Keywords can be added to either the subject or body text.
36 Click ‘OK’ to save the text or ‘Cancel’ to close the window without saving changes.
37 1. When the Activity Action is **‘Notify External Party’** an alternate eMail format is available. This eMail will not be sent to the task owner (which is still a required setting and should be set to ‘requisitioner’) but to the destination address defined.
38 [[image:PECOS Admin.WebHome@Fig 17.11 - Notify external party eMail message.png]]
39 1. For __**Requisition**__, __**Purchase** **Order**__, __**Receipt**__ and __**Change Order**__ approval plan types the following must be completed:
40 1*. **External eMail – eMail Address (mandatory)**: The eMail address of the external party to whom this message is to be sent.
41 1*. **External eMail – Recipient Name (mandatory)**: The name of the person to whom the eMail is to be sent.
42 1*. **eMail cc**: Optionally, a courtesy copy of the message and attachments can be sent to another party by selecting one of following radio buttons.
43 1**. **None (default) **–**   **No copy will be sent
44 1**. **Task Owner **–** **A copy of the message will be sent to the user who is specified as the owner of the approval task, either by name or role association. There may be multiple users filling the associated role.
45 1**. **Other **–** **Enter an alternative email address and user name into the appropriate fields. Both fields are mandatory if this option is selected.
46 1**. **eMail Address **– The eMail address of the party to whom a copy is to be sent. Note that this field is also validated in the same way as the External eMail Address (see above).
47 1**. **Recipient Name** – The name of the person to whom a copy is to be sent.
48 1*. **Include Attachments**: Check the box if you want the original attachments to be sent with the external party notification. A requisition summary is also sent for requisition plans and a copy of the purchase order is sent with purchase order and change order plans. Header and line level external attachments are sent with all plan types.
49 1*. **Subject Text (mandatory)**: This is the eMail subject.
50 1*. **Body Text (mandatory)**: Enter the body of the eMail message.
51 1. For __**Invoice Settlement**__ approval plan types the following must be completed:
52 1*. **External eMail – Supplier:** the system will send an email to the supplier’ eMail address (as defined in the supplier profile). No eMail address detail is required.
53 1*. **External eMail – Other: **enter the **eMail Address** of the external party to whom this message is to be sent and the** Recipient Name **of the person to whom the eMail is to be sent. These fields are **mandatory** if this option is selected.
54 [[image:PECOS Admin.WebHome@Fig 17.12 - External email options for invoice settlement plans.png]]
55 1*. **eMail cc**: Optionally, a courtesy copy of the message and attachments can be sent to another party by selecting one of following radio buttons.
56 1*.
57 1**. **None (default) **–**   **No copy will be sent
58 1**. **Task Owner **–** **A copy of the message will be sent to the user who is specified as the owner of the approval task, either by name or role association. There may be multiple users filling the associated role.
59 1** **Other **–** **Enter an alternative email address and user name into the appropriate fields. Both fields are mandatory if this option is selected.**
60 1**. **eMail Address **– The eMail address of the party to whom a copy is to be sent. Note that this field is also validated in the same way as the External eMail Address.
61 1**. **Recipient Name** – The name of the person to whom a copy is to be sent.
62 1*. **Include Attachments**: A PDF version of the invoice will be rendered and automatically attached to the eMail if this is selected. If there are any other associated invoice attachments (e.g. thorough the Elcom eInvoicing module) these will also be attached.
63 1*. **Subject Text (mandatory)**: This is the eMail subject.
64 1*. **Body Text (mandatory)**: Enter the body of the eMail message.
65
66 == **eMail Address Validation** ==
67
68 The eMail Address field is validated to reduce the likelihood of an invalid eMail addresses being entered. The following validations are undertaken:
69
70 * There is at least one ampersand (@). (eg: jsmith.elcom.com)
71 * The ampersand is neither the first or last character (eg: jsmith@)
72 * There is at least one dot in the address (eg: jsmith@elcomcom)
73 * Two dots do not appear simultaneously (eg: jsmith@elcom..com)
74 * There are no spaces in the domain name (eg: jsmith@elcom .com)
75 * The domain name does not start or end with a dot (eg: jsmith@.elcom.com)
76 * Characters used in the domain name are valid (eg: jsmith@elcom.co£)
77 * The domain length is between 3 and 255.
78 * User name does not start with a dot (eg: .jsmith@elcom.com)
79 * User name does not end with a dot (eg: jsmith.@elcom.com)
80 * User name is checked for invalid characters which include: (“£€)(@][;:><\`¬) (eg: jsmi£h@elcom.com)
81 * Domain is checked for invalid characters which include: !#$%&'*+,/=?^_{|}~~“£€)(@][;:><\`¬ (eg: jsmith@el#om.com)
82
83 If validation fails an error message will be displayed.
84
85 == **Keyword Search** ==
86
87 Keywords are database identifiers that can be embedded into the text of eMail notification messages. Keywords therefore allow you to make eMails more meaningful for the recipients by adding, for example, document id’s or user names. These keywords are replaced with the matching variable database values when the notification is generated. For example, if a requisition number, Requisitioner’s name and requisition value is required, a message could read:
88
89 * “Requisition number %@ExternalRequisitionID% from %@BuyerName% for GBP%@DefaultCurrencyTotalOrder Amount% has been sent to you for approval.”
90
91 To access the current list of keywords available click on the **Keyword Search** button in the eMail message sub window.
92
93 == **Suppress Require Receipt eMail** ==
94
95 It is possible to suppress the eMails for the Require Receipt approval activity. A check box appears in the approval plan Activity screen for Purchase Order Approval and Requisition Approval plan types to appear when the Activity Action 'Require Receipt' is selected.
96 The check box, called "Suppress eMail message", is placed adjacent to the "Edit eMail message" link and has a default of unchecked (i.e. the eMails will not be suppressed). When the box is checked, PECOS P2P will suppress the transmission of the eMail notification message to the task owner.
97 Note that the 3-way match and audit messages will NOT be affected in any way if the eMail is suppressed.
98
99 = Audit Trail Message =
100
101 An audit trail follows orders from requisition creation to financial settlement, tracking who performs each task and when. For every task you must enter **mandatory** Start and Completion text.
102
103 [[image:PECOS Admin.WebHome@Fig 17.13 - Approval plan audit trail message.png]]
104
105
106 * **Start:** Will appear stamped in the audit trail when the task is invoked. For example when a document is sent out for approval.
107 * **Completion:** Will appear in the audit trail when the task has been completed. For example when a document has been approved.
108
109 = Deactivate Task =
110
111 Click the Deactivate Task check box only if you want to deactivate an existing task and have PECOS P2P skip over it for all future document routing. A deactivated task can later be reactivated by removing the tick in the check box.
112
113 = Escalation =
114
115 Setting an escalation for a task is **optional**. An escalation will create an expired task if the activity has not been completed within a fixed period. The document is moved forwards in the approval plan without the task owner completing their action, and an eMail sent to the requisitioner informing them of the escalation (see __[[Organisation Maintenance > Notification Messages>>PECOS Admin.Organisation Maintenance.Notification Messages.WebHome]]__). For example, important approval steps may be escalated to a subordinate or deputy approver.
116
117 If you want this task to be escalated after a fixed time period, enter the following details:
118
119 * **Timeframe: **Choose** **a timeframe from the drop down selection box.
120
121 * **Days / Hours: **Uses the Organisation calendar to calculate working time. Non working time will be ignored in the escalation calculation.
122 * **Minutes / Seconds: **Does not use the Organisation Calendar to calculate working time. Real time is used to calculate when the task is escalated.
123
124 * **Units:** Specify the timeframe units to determine when this escalation should be triggered.
125
126 An escalation task must immediately follow any task that is escalated to define the new action and owner of the escalation activity.

Navigation

© Elcom Systems Ltd 2025