Advanced Search
Search Results
1057 total results found
Alternative entry (if present in the profile/role)
If your role/home page offers an entry point, you will often find the "Approvals & Workflows" area "Advanced Workflow" with links to: AWF Workflow Management AWF Workflow Templates In addition, you will typically find the standard area there, "Pending Appr...
Permissions
You typically need: DEXPRO AWF Admin: for setup/template maintenance DEXPRO AWF User: for usage/monitoring DEXPRO Core Administrator or DEXPRO Core User: For rule creation/usage The app also includes the internal permission set DEXPRO AWF Objects - Exec. T...
Workflow user groups
As a rule you will use Workflow User Groups to organize the distribution of approvals/reviews. Make sure the user group exists has members If groups are missing/empty, execution can fail (the workflow may be moved to the error step).
The minimum configuration: when is a workflow template "valid"?
A workflow template is only fully usable in this app once at least these criteria are met: Active = Yes (the template must be active) Primary Table is set Rule Set exists (is created/updated automatically when the primary table is set) At least one norma...
Step 0 – Check supported tables & events (must-know)
What are "AWF Supported Tables"? In "AWF Supported Tables" you maintain which tables can be selected as the primary table at all. Important: In the workflow template, only supported tables can be chosen as the primary table. Per supported table, the followin...
Create a workflow template
Create a new workflow template Open AWF Workflow Templates. New. Fill in the area General: Code (unique) Description Active initially No (recommended) Set the primary table (decisive, as this is the table the workflow is started for) In the workfl...
Configure related tables (optional)
Why do I need related tables? The rule engine can check conditions not only on the primary table, but also on related tables (e.g. header/lines). You define these related tables in the template in the area: Related Tables (technically: "DXP Rule Set Tables"...
Define steps
Basic structure of the steps In the template there is the section Steps. A step contains, among others: Step Code Step Name Order Step Type (Normal / Error / Final) Allow Record Editing Assignment logic Approvals / Related Approvals: optionally enable lin...
Step rules: how does the workflow move to the next step?
The app uses the DEXPRO Rules Engine to determine: which rule matches to which next step it switches whether the assignee is overridden whether it auto-approves and whether the action applies to the header approval, related approvals (lines), or both. If n...
Configure workflow triggers
Workflow triggers determine when a new workflow instance is started. In the template the section is called "Workflow Triggers". Template triggers: basic fields In the template → section Workflow Triggers. New. Field Workflow Event select (AssistEdit → list "A...
Workflow action on completion
In the template there is the section "Workflow Action". Run action on completion enable. Action on Completion choose (depending on the primary table): Release / Reopen (only for certain document tables) Custom action (codeunit/report) Define field value assi...
Cleanup (retention & cleanup)
Under Cleanup Configuration: Automatic Cleanup Enabled Retention Period for Cleanup (DateFormula, e.g. -1M) In addition there is the action: "Clean Up Old Instances"
Find workflow instances
Open AWF Workflow Management (e.g. via "Approvals & Workflows" → "Advanced Workflows"). There you see, among others: Template Code Status Current Step Date/Time Started Here you can, among other things: See details Show audit trail Cancel workflow (if activ...
Process approvals (without a dedicated document page)
For day-to-day work as an approver, the workflow management is often not the key page, but the page "Requests to Approve": You see the record in the FactBox "Record Preview". You use the Approval Actions (Approve/Reject/Delegate). For group approvals you typi...
Integration into common standard pages (default tables)
For common tables that are delivered as default in AWF Supported Tables , there is additionally a direct integration into the respective standard pages of the record. Typical examples (depending on setup/role profile): Cards such as customer/vendor/item Sales...
Export a template
On the template: Action "Export Template" A JSON file is created (e.g. AWF_Template_<Code>.json).
Import / overwrite a template
On import, the system checks the JSON structure. If the template already exists, an overwrite can be prompted.
Copy a workflow
There is a function "Copy Workflow", to duplicate a template including steps/triggers/rules.