This Blog is developed for sharing MS Dynamics NAV Technical knowledge of my work experience and also some other professionals.
Myself Today Microsoft Dynamics NAV Programmer in ICS Technology Services Pvt Ltd. Hyderabad. Started with C++, ORACLE, VB, Java and today well-versed with top Microsoft Technologies ASP.NET,C#.NET also VB.NET, SQL SERVER. Interested to implement always new and wanted technologies.
Love to hear comments from U 4 my posts
Microsoft Dynamics NAV Workflows enable you to model real-life business processes like best
practices or industry-standard practices. Ensuring a customer’s credit limit
has been independently verified or requiring a two-person approval for a
significant vendor payment are both examples of these. Workflow can be thought of as the movement of
documents or tasks through a work process. Workflows in Dynamics NAV focus on three
main building blocks and almost any workflow process, short or long, is likely
to be comprised of steps related to these three blocks. They are:
approval leaves a work task, item or document in an blocked or unapproved state
until approved by a suitable person in your organization
notifications tell users that something has happened and/or that they need to
take some kind of action
automation, process automation means executing a process routine and have the
Dynamics NAV system calculate something or perform an action
The workflows in Dynamics NAV are represented by Workflow
Events and Responses. The smallest
workflow is the pairing of a single Event and a Response. Simple workflows could be
·When a new customer is created, email the sales
person responsible for that region to alert them to the new customer.
·When a new vendor is created, email the
purchaser person responsible for that region to alert them to the new vendor.
·When a purchase invoice exceeds $250, email the
financial controller to alert them
More complex workflows are built of chains of events and
responses. Examples could be
·When a Purchase Invoice exceeds $250, put the
purchase invoice on hold until it is approved by a manager.
·When new customers are created, block them until
they have had a credit check performed.
·Once a purchase document has been approved by
the accounting manager, automatically post it to the Dynamics NAV system.
Note: in all the
examples above, you can see a “when something happens, do something”
pattern. This is the “Event and
Response” model and is the simple but effective design behind Dynamics NAV
Events and Workflow Events
Perhaps confusingly, Dynamics NAV 2016 introduces two new
event concepts. Events and Workflow
events. The two are distinct but often
coupled together to build solutions. Dynamics
NAV Events allow you to write code which will be called when an event occurs –
this is called subscribing to an event.
An example could be to subscribe to the OnCreate
trigger for a table and writing code which will be called whenever a new record
Workflow Events typically use Platform Events as their
trigger, but are richer. Workflow events
are registered in the workflow engine and show up in the workflow
designer. Microsoft recommends that
Workflow events be written at a higher level of abstraction than Platform
Events, for example while OnCreateNewCustomerRecord
makes a suitable platform event, a good workflow event could be AfterOverduePaymentIsPosted.