Unanswered

Page Approval Flow Move to other site collections (Same enviroment)

(0) Share

Report

Posted on by ashwane123

Hi All,

I have configured a page approval flow which has additional steps of checking metata and sending emails to different groups based on page properties. I am happy to meet the requirements and automated the approval.

Now, I want to move this to other site collections and followed below steps.

1. Created a customized Page Approval Flow "Modern-PageApproval-Clients" for "sites/xx" site collection
2. Go to another site collection "sites/yy" and configure/create another approval flow "Modern-PageApproval-Innovation"
3. Export step 1 Approval Flow "Page-Approval-Template_20190715054732.zip"
name -> Import Setup = Update
connections -> Import Setup = Select during import

4. Import step 3 package and updated step 2 Flow.

5. Replaced list guid and names manually in new Flow "Modern-PageApproval-Innovation".

6. Now, it stopped triggering from new site collection page creation/updation - Not sure why?

Then I tried to update guid, new site url's in exported package definition and re-package it by following below steps.

7. Extract and update "definition.json" with new list GUID and names.
8. Zip updated folder "Page-Approval-Template_Updated_20190715054732.zip"
9. Import step 8 package
10. Error ocurred "Something went wrong"

Please help If I am missing anything here - This is critical for us as we need to deploy this for 200+ site collections.

Regards,

Ashwane Singh

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

MarkStokes 561 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I can’t directly help you with your question, but would like to make a suggestion.

If you are looking to use this Flow across 200+ site collections then I truly think that you might be better off looking at Logic Apps.

The management and maintenance of this across that many sites is going to be horrible. I can just see the requirement.... “can you just add a full stop to a message”. 200+ Flow updates later?

Without a Logic App you can store the source code in Azure DevOps and then create a build / release pipeline that auto deploys any changes to all site collections automatically.

Or, have 200+ trigger Logic Apps or a Flows that call a central “worker” Logic App / Flow / Azure Function.

At that scale, I’d be looking at other alternatives. And we do have projects that spread this many instances and logical apps is the way we do it.

- Mark

Was this reply helpful? Yes No
ashwane123 3 on at

Like (0)

Report
Copy link

Link copied!

Thanks Mark for the suggestion.
I am new to Flow and don't know much about logic apps.
Can you please direct me to some documentation to use logic apps for SharePoint page approval Flow.

Regards,
Ashwane

Was this reply helpful? Yes No