Have the ability to setup workflow Escalation for a Work Item queue
In Dynamics 365 for finance and operations, there is an ability to setup the workflow and escalate if needed.
In the current design, the users can only select to escalate the workflow to the following options:
Hierarchy, Workflow user and users.
If users are using the Work...
D365F&O - Workflow event notifications to show in the user Action Centre
Within D365 Finance & Operations > User options > Workflow, there is a tick box / slider to enable 'send notifications to Action Centre'. When enabled, this will give you workflow notifications when something is assigned to you to action. However, this feature does not work for workflow event ...
Add conditions to project timesheet approval workflow
The project timesheet approval workflow has a very limited amount of workflow conditions. The following scenarios cannot be configured due to its restrictions: - different approver based on the project group or other project related field - different approver based on the resource or associate r...
Making Workflow History more user friendly and visible
Currently it is difficult for an end user to go through the workflow history to actually find out where in the process that particular workflow is and where else it needs to go before it is completed. It would be great if this was made more visual with a checklist or flow chart
We have added a list to the workflow history form in addition to the existing tree. The list is above the tree since we believe that should make the history easier to understand, more useful, and more user friendly. Those changes went into Platform Update 13.
Make Workflow History Link Available At All Times
The Workflow History option should be available on the workflow menu at all times for any record. There are many scenarios where a workflow is canceled / reset to draft, and it would be useful to be able to see that history prior to resubmitting the item. Currently, there is no way to do this w...
Workflow reject to be reassigned to previous steps.
Workflow with several approval steps is rejected on last one.
Actual behavior: Workflow will have to be resubmitted by initial user.
Expected result: Workflow should then be reassigned to a selected step (n-1)
All comment should be visible at each subsequent approval step
e.g. for a PR it may be submitted with an explanatory note, it may be rejected, be resubmitted, etc- there seems little point in having the feature to enter the comments if these are not easily visible to approvers.
Configuration allows last note as a parameter- this needs to be concat...
Worker field as origin of hierarchy
When triggering workflows using an automated step (like vendor invoice automation), you would want to use one of the fields in the actual record as the origin of the hierarchy when doing assignments.
The person requesting the invoice should be the base for the hierarchy.
Today ...
Extend customer approval workflow functionality to all fields on customers form
Microsoft delivered customer approval workflow with October release. Please include all fields on customers form in this functionality and also let users to configure workflow approval requirements for new customers as well. (Considering retail, please also exclude customers created from POS app...
New participants for Organisation hierarchy (new "start from" participants)
Organisation hierarchy has one big flaw: the "start from" function. There are generally only two options: 1) the workflow originator 2) or the workflow owner This has a few limitations. As people can submit AP documents centrally, the prime example being AP invoices. Organisations want to use t...
Administrator
Can I get some comments about what "escalate the workflow to a specific queue instead" means in terms of configuration and desired user experience? How is escalating to a hierarchy not the same as escalating to a queue?