Comments
This is a critical enhancement addressing a clear inefficiency in the current process.Restarting the entire workflow for every Change Request—regardless of how minor—creates unnecessary delays, redundant approvals, and operational overhead. Most changes (e.g., quantities, dates, dimensions) do not require a full re-approval cycle.In addition, this approach results in losing the workflow history, as a new workflow instance is created each time, which impacts traceability and auditability.Allowing the workflow to resume from the current state, with re-approval only for impacted steps, would significantly improve efficiency, preserve workflow history, reduce cycle time, and enhance user experience without compromising governance.
We are experiencing the same challenge in our organization.In our case, even minor updates to a Purchase Requisition trigger a full workflow restart, requiring all previous approvers to review and approve the request again. This significantly delays the procurement cycle and creates unnecessary workload, especially in scenarios with multi-level approvals.From a business perspective, many of these changes do not impact the original approval decisions, and restarting the workflow adds no real value. Instead, it leads to user frustration and reduces overall process efficiency.We strongly support the idea of introducing more flexible workflow behavior, such as resuming from the last completed step or re-triggering only the impacted approvals. This would better align the system with real business needs and improve user experience significantly.
Got to know from Microsoft support engineer that: Blank environment names: last point mentioned in the idea is actually a Microsoft bug. To quote "This is a known limitation of the Power Platform license usage report. In some cases, while the Environment ID is correctly captured, the Environment Name may appear blank due to how environment metadata is resolved at the time of report generation. This does not indicate a deleted or missing environment, and the usage data itself remains valid". Can you please check this this can be fixed?