I am working on a large automation project that incorporates multiple business applications. This will will require some monitoring of application activity with Power Automate cloud flows and SQL queries, Power Automate Desktop flows to do some website interaction to kick off a stage of a process, local application processes kicking off (Using Power Automate Desktop for this) and API calls using a custom connector.
I was thinking of setting up Multiple solution so I can work and deploy components pieces for each application instead of one large solution but is this the right path?
For instance my solutions would be...
- Application 1 Automation and Monitoring
- On a schedule kick off a Power Automate Desktop Flow
- A Power Automate Cloud flow would then monitor the progress of that Application
- If that completes successfully, use a webhook to kick of the next step in Application 2 Solution
- Application 2 Automation and Monitoring
- Start local windows process and wait for it to complete before starting the next stage. This would be kicked off with the webhook trigger.
- Monitor the progress of this task with the info it writes to a SQL DB. Alert if there are any errors reported.
- Once complete... if everything was successful, Kick off another Local Process once that process completes kick off App3 with webhook trigger.
- Application 3 Automation and Monitoring
- Kicks off another local process and wait for it to finish
- Then kick off another Power Automate Desktop Workflow to click through another web interface to start another process.
- Monitor and alert if there are errors
Or would it make sense to make most of these child flow in each "Application Solution" then import them into an "Master Solution" also. Then use that and Child flows to trigger everything to get away from the cross solution webhooks as triggers?
If I went this path... If I do some updates in say "Application Solution 1" and publish them, would "Master Solution" use those new workflows or would I have to publish and promote to get those changes? Can workflows exist in multiple solutions?
I would think it would be easier to manage the integrated steps in a single master solution but breaking into smaller solutions would let me permission them out so different teams could work on each or test component pieces easier.
236
Share
Report
All responses (
Answers (
