Approval manual - Revision history

Nele.scherrens: /* Auto flow */

2017-08-28T07:18:54Z

‎Auto flow

2017-05-29T08:37:32Z

2017-05-29T08:11:29Z

‎Line-level approval

2017-05-29T08:11:14Z

‎Edit TOA rules

2017-05-29T08:10:47Z

‎Create TOA rules

2017-05-29T08:09:58Z

‎Usage of the "BETWEEN" operator

2017-05-29T08:09:08Z

‎Create TOA rules

2017-05-29T07:18:28Z

‎Manually

2017-05-29T07:17:48Z

‎Manually

2017-05-29T07:12:19Z

‎Via Excel

@@ Line 19: / Line 19: @@
 # Click the ''"Settings"'' option in the upper right corner of the screen (right next to ''"My account"'').
 # Choose [[image:workflow.png|link=]] "Workflow" from the settings screen.
-# Make sure you have a company selected (see [[Selecting a company|"Selecting a company"]] for more information).
+# Make sure you have a company selected (see [[Working_with_companies#Selecting_a_company|"Selecting a company"]] for more information).
 # Choose the document type for which you would like to edit the TOA rules.
 #* ''Incoming invoices''

@@ Line 1: / Line 1: @@
 Approving documents can be done in 2 different ways:
-* Automatically, via the [[Approval_manual#Auto flow|auto flow]]. This is done when documents are allowed to be processed automatically. For example: an invoice for electricity comes every month. The booking of such invoices is similar every month. These invoices can be processed automatically to save time.
+* Automatically, via the [[Approval_manual#Auto flow|auto flow]]. Based on the data on the invoice, the auto flow will automatically determine the approver(s) and send the invoice to the approval flow without some manual action. For example: an invoice for electricity comes every month. Every month, Employee A (Accounts Payable) has to manually send the invoice to Employee B (Approver). With the auto flow enabled, this manual action can be skipped and time will be saved.
-* Manually, via the [[Approval_manual#Manual flow|manual flow]]. This is done when documents are processed manually and they need to be approved. Mostly, this occurs for bookings that are a little more complicated.<br/>
+* Manually, via the [[Approval_manual#Manual flow|manual flow]]. When the booking of the invoices is a little more complicated, the invoices can be sent manually to the right approver.
 <br/>
 When a document is already in the approval flow, there are still two actions which can be performed on it:

@@ Line 197: / Line 197: @@
 Click the [[image:remove.png|link=]] "Remove rule" at the beginning of a line to remove the rule.
 ===Line-level approval===
 When using the [[Approval_manual#Auto_flow|auto flow]] and having multiple [[Validating_invoices#Adding.2C_editing_and_deleting_posting_data_in_the_document_view|posting lines]] in a document, it is possible to send certain posting lines to one approver and other posting lines to another.<br/>

@@ Line 188: / Line 188: @@
 Use the [[image:pageXls.png|link=]] "Export" button to download all the existing TOA rules. Edit the ones you would like to change and upload the file again via the [[image:upload.png|link=]] "Import" button.
 ====Manually====
-The available lines in the list of rules are editable. Edit the one you like and click [[image:save.png|link=]] "Save".
+The available lines in the list of rules are editable. Edit the one you like and click [[image:save.png|link=]] "Save".<br/>
 ===Remove TOA rules===

@@ Line 88: / Line 88: @@
 Add an '''OR''' relation by typing a hyphen (-) between the approvers.<br/>
 Add an '''INFORMATIVE''' by typing (i) before the name of the approver.<br/>
 <br/>
 ====Manually====
 '''Example''':
@@ Line 183: / Line 165: @@
 #* ''Approver 4'' has to approve the document.
 #* ''Approver 5'' receives the document informatively.
 <br/>

@@ Line 89: / Line 89: @@
 Add an '''INFORMATIVE''' by typing (i) before the name of the approver.<br/>
 ====Usage of the "BETWEEN" operator====
 When using the "BETWEEN" operator, you should take into account that the ''"Code"'' field of partners and lookup lists is a text field. This means that the values will be sorted alphabetically.
@@ Line 104: / Line 105: @@
 ** 21 Antwerpen
 ** 22 Mechelen
 ====Manually====

@@ Line 123: / Line 123: @@
 * '''Not empty''': the selected field cannot be empty.
 * '''Inactive''': inactivate the comparison of this field. '''This is the default value'''.
 <br/>
 The example explained:

@@ Line 114: / Line 114: @@
 <br/>
 For each field (except ''Approvers'') it's possible to define a condition. The posting line(s) have to meet the condition(s) in order to be sent to the right approver.
 * '''Empty''': the selected field has to be empty.
-* '''Equals''': the selected field has to equal a certain code. Choose the right code from the lookup list.
+* '''Not empty''': the selected field cannot be empty.
 * '''Inactive''': inactivate the comparison of this field. '''This is the default value'''.
 <br/>
 The example explained:
@@ Line 142: / Line 146: @@
 <br/>{{note|Keep in mind that when you remove the approver, it just clears the entered values. The TOA line stays.}}
 <br/>
 ====Use case====
 Taking into account the above configuration of a TOA rule, a document will be sent into the flow as follows:

@@ Line 59: / Line 59: @@
 <br/>
 For each field (except ''Approvers'') it's possible to define a condition. The header-/posting line(s) have to meet the condition(s) in order to be sent to the right approver.
 * '''EMPTY''': the selected field has to be empty.
-* '''EQUALS''': the selected field has to equal a certain code.
+* '''NOT_EMPTY''': the selected field cannot be empty.
 * '''INACTIVE''': inactivate the comparison of this field.
-* '''LIKE''': enter a value to which the input must look like.
+<br/>{{warning|The operators above are ordered from high to low importance. When two or more rules are matching with the document (or lines when using [[Approval_manual#Line-level_approval| line level approval]]), the importance of the operators will be taken into account. A higher importance of the operator means a higher importance of the rule.}}
-* '''NOT_EMPTY''': the selected field cannot be empty.
 <br/>
 The example explained: