![]() ![]() Each user can only see their approval entries. This page will show all the entries of the approval module that are on the fly. Let´s approve the invoice in the example. We can also delegate and the status will remain in ‘Pending Approval’ until somebody accepts or rejects. ![]() If we approve, the status of the document turns to ‘Released’.īut if we reject it, the status will turn to open meaning that this document has been rejected and can´t be posted. You can also see if there is any comment related to the approval.Īt this point, we can go to the document with the ‘Open Record’ action to verify the information about the approval. The following page will open with information about the approval, sender, due date, amount, and currency code. Is on this page where the approver will have to accept or reject the requests that have been received. You can find pending approvals from the cues of the role center or just by searching ‘Requests to Approve’. The status on the document changes to ‘Pending Approval’ and we can see the information of the approval on the factbox we just populated. Once we have the invoice ready we can send the approval request. First, you can show the approval factbox to see the status of the approval. We can create now a sales invoice to test the approval workflow. If the approval request is approved we can see that the first step is to remove the record restriction and then release the document. Learn more about restricted records here: ‘Add record restriction’ means that, in this case, the sales invoice can´t be posted until the restriction is removed. It shows this caption because it is the first step in the response. The first response in this workflow is ‘Add record restriction’. Each one of the responses can be customized. In this section, we can play with the conditions to conform to our workflow.Ī workflow response can have multiple steps itself. On top of the ‘parent’ event, the conditions of the events must also be met. In other words, none of the events indented below the first one will trigger if the first one isn´t initiated. For the rest of the events to trigger the first one has to be triggered first. We will use the Sales Invoice Approval template.Īs we can see, there is one main event which is the one that creates the request and initiates the workflow. ![]() Let´s follow a simple example to explain how an approval workflow works. or Salesperson/Purch.įor this simple test, we will use the following configuration. So they share some fields such as the e-mail, phone no. Note that the table is the same as on the user setup page (Table 91 User Setup). Set Up Approval Users – Business Central | Microsoft Docs Get more information about each one of them here: There are different fields for different purposes. Here we have to set up all the people involved in any approval workflow. This is the most important page in the approvals module of Business Central. The first thing we need to do in order to set up an approval workflow is to fill in the ‘Approval User Setup’ page. We can also create notifications and send overdue requests to remind approvers that an action is needed from them. Starting from approval users we can decide who needs to approve a document in order to continue the process that we have established. An approval workflow is the way we can automate approval processes within Business Central.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |