Skip to main content

Process Template

Each mseDoc365 process is created on the basis of the respective suitable process template, in which the process steps and dispatch types are defined. Here, new process steps are configured and existing ones are edited, for example a parameter can be added or a completely new process step can be created for a newly added document type.

After clicking +New; from General tab you can define No., Description and Document Type. Also you can see the Steps and manage the process.

Fields​

  • No. Specifies the value of the No. field.
  • Description Specifies the value of the Description field.
  • Document Type Specifies the value of the Document Type field.

Step Filters​

Step Filters apply to an individual process step. The available fields are determined by the process template document type. For example, if the template is based on Sales Invoice, the field selection comes from the Sales Invoice table. A step with filters is only executed when the document data matches all defined filter conditions. If the condition is not met, the step is skipped and the process continues with the next step.

To manage filters, open the step list and use the Filters action. Add one or more filter lines for the step.

Step Filter fields​

  • Field Caption The table field the filter applies to. Use AssistEdit to select the field.
  • Filter String The filter expression for the selected field. Use standard Business Central filter syntax.

Notes​

  • Filters are evaluated together; all must match for the step to run.
  • The Filter set indicator shows whether filters exist for the step.

AutoFlow step​

With AutoFlow installed, every active AutoFlow flow that uses the trigger When manually started on the eDocument table is available as a process step of its own. The step's Parameter Name is the flow's Code, its description is AutoFlow: followed by the flow's description. Add it to a process template like any other step.

When the step runs, it runs the flow for the eDocument to its end, in the same session as the process – it does not depend on the Job Queue or the AutoFlow setup Manually start flows, and there is no time limit. The flow gets only the eDocument; everything else – the source document, the customer, … – it reads itself from there. If the flow fails – for example in an Error step – the step fails with the flow's error. A flow with a Sleep step cannot run as a process step. The step's responses show the flow's execution number in AutoFlow.

The list of steps is refreshed every time you open a process template: new flows are added, deleted or deactivated flows disappear. A flow appears only if its Code has at most 20 characters and is not already used by another step.