Grant-Archibald-MS
commented
11 months ago Thanks for sharing your question on the Approvals Kit, and I can understand your concerns and feedback.
The Approvals Kit is designed to combine multiple components, including Power Apps, Power Automate, and Dataverse, to deliver a managed solution for approvals. While it's true that some of these components can be combined manually, the Approvals Kit offers a prepackages solution to provide additional features like multi-stage approvals, decision-making delegation, and progress monitoring that would need to be created and maintained over time if done manually. You can read more on this comparison at https://learn.microsoft.com/power-automate/guidance/business-approvals-templates/approvals-kit-comparison.
Overall, for the Approvals kit is just one approach for Approvals, depending on the features you need to use the standard Approvals connector may meet your needs. In other cases, customers may want to leverage the additional features to streamline the approval process.
Regarding your question about versioning, Microsoft is working on a platform wide as part of the current release wave plans. This approach to versioning, and the versioning support is shown with Power Automate. More information on Power Automate versioning changes is in https://learn.microsoft.com/power-platform/release-plan/2023wave2/power-automate/use-versioning-solution-cloud-flows.
The Approvals Kit also includes a Dataverse-based versioning strategy that allows you to have draft and publish approvals workflows versions. The https://learn.microsoft.com/power-automate/guidance/business-approvals-templates/content discussed the high-level architecture and data model used by the Approvals kit. As the platform-wide approach to versioning is still in progress, we will continue to update and integrate the current versioning support for Power Automate and the Approvals Kit.
What is your question?
Help me understand what is different in this kit that can't already be done with the same level of ease? I see this happening a lot at Microsoft low code products now.
For example, when do we get the "save as draft" and "publish" functions? Different environment still have issues where moving a solution between environments requires lots of rework (example, even if we use components and environment variables, just as one example).
I think Microsoft should focus more on fixing the product, than invest time in marketing and re-branding already packaged products under different names and classifications.
What solution version are you using?
No response
What app or flow are you having the issue with?
No response
AB#1739