Example 17

Type: Check before Transaction is completed

Department: Sales

Learning Objectives

Hook-in:

Within Dynamics NAV there are specific Insert Codes such as Before Sales Post, After Sales Post, etc., these Insertion Codes can be used to set examinations in transaction processes (e.g. Posting).

Break Condition:

The condition when a transaction shall be stopped are defined in the Break Condition.

Business Process “Post Sales Order”:

Specific fields which are Mandatory Fields are controlled before posting a sales order. If the employee tries to post, an error message will open as soon as Mandatory Fields are not completely fulfilled.

Aptean Advanced Workflow Setup

Reference Type

No.: 36 (Sales Header)

Buffer Time on Function Call Server: 10 Seconds

Automatic Workflows: Yes

Workflows Template

Reference Type No: 36 (Sales Header)

Code: WF170

Description: Check Sales Order at Posting

Event Trigger (via “Choose Columns”): By Hook-in

Hook-in Code: Before Sales Post

Break Condition Code: WF170-C010

Condition

Table ID: 36 (Sales Head)

Code: WF170-C010

Description: Check before Posting

Type: Break

Condition Line 1

Active: Yes

Type: Field

Table ID: 36 (Sales Header)

Field ID: 43 (Employee Code)

Filter: =‘‘

Check Condition Group: A

Condition Line 2

Active: Yes

Type: Field

Table ID: 36 (Sales Header)

Field ID: 5700 (Responsibility Center)

Filter: =‘‘

Check Condition Group: B