Validation Should be Performed Automatically on Submit
When an item is submitted to workflow, it should be automatically validated. If the validation fails, the submittal should be terminated. If the validation generates a warning, the user should be prompted whether to continue with the submittal.
We've had several instances w...
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...
Ability to send workflow items to purchase order orderer
When submitting a vendor invoice to the workflow, it would be good to have the option to create a work item for the purchase orderer or the person that generated the purchase order receipt. In a normal business scenario, if the purchase invoice line fails because of a price discrepancy, the buyer...
Ability to delete a document if the workflow status is 'Unrecoverable'
If the workflow for a document (eg: Journal) turns to 'Unrecoverable', user cannot edit / Delete the document. System also does not allow user to resubmit the document. There should be provision to remove/delete the document which are unrecoverable.
Multiapproval
When a manager approves timesheets it should be possible to mark and approve multiple timesheets at once.
We are tracking multi-select approval as deliverable 336395.
Daily digest of workflow notifications and upcoming deadlines
have one e-mail a day with a daily digest of workflow notifications and upcoming deadlines instead of one e-mail per workflow item that is assigned to you.
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...
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...
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)
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.
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?