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
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)
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...
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 vendor approval workflow functionality to all fields on vendors form
Microsoft delivered vendor approval workflow with October release. Please include all fields on Vendors form in this functionality and also let users to configure workflow approval requirements for new vendors as well. For new vendors workflow, a simple solution might be: 1. Adding a checkbox in...
Workflow option to skip user who submitted workflo
Workflow is submitted by one of assigned approval user. An option should allow to assign worflow to users except the one who submitted
Unable to create/write "canSubmitToWorkflow" method (or) Standard override methods on table extensions in D365O
I need to create a workflow for which "canSubmitToWorkflow" method needs to be created on standard table which doesn't have canSubmitToWorkflow standard method but development is to be done using extensions.
In table extensions we can't override standard me...
This is currently in the backlog as deliverable 3888537. We are looking at whether the unimplemented method support would add performance cost since we don't want to degrade performance by adding this capability.
Administrator
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.