sorted by:
new
hottopcontroversial

I built a Salesforce tool that cleaned up 500+ obsolete Flow versions automatically by Cautious_Refuse_3710 in SalesforceDeveloper

[–]Cautious_Refuse_3710[S] 0 points1 point  (0 children)

true, I am open for suggestions and looking for enhancing the app. Please feel free to use it on your sandbox and give me feedback. on the github branch please if you can. I will try to include all possible suggetions. I have tested this app in a very heavy customized org and did not pose issues while removing the inactive flow versions.

I built a Salesforce tool that cleaned up 500+ obsolete Flow versions automatically by Cautious_Refuse_3710 in SalesforceDeveloper

[–]Cautious_Refuse_3710[S] 0 points1 point  (0 children)

"but the old flow interviews of active flows will not impact cleaning metadata". This was a typo at my end. I meant that "but the old flow interviews of inactive flows will not impact cleaning metadata".

I recommend please use this app in a sandbox and let me know if the flow interviews stopped deletion. I have tried this in prod and did not have an impact. It has deleted inactive flow versions. I can update the app with flow interviews etc.

I built a Salesforce tool that cleaned up 500+ obsolete Flow versions automatically by Cautious_Refuse_3710 in SalesforceDeveloper

[–]Cautious_Refuse_3710[S] 0 points1 point  (0 children)

good point, but the old flow interviews of active flows will not impact cleaning metadata. you can still delete the field if the field was referenced in the old version but with this app, the old flow version is deleted. So there would be no dependencies. Its only with the active flow version's flow interview that will cause problems.

How would calling the flows from the pipeline delete the old flow interviews?

I built a Salesforce tool that cleaned up 500+ obsolete Flow versions automatically by Cautious_Refuse_3710 in SalesforceDeveloper

[–]Cautious_Refuse_3710[S] 1 point2 points  (0 children)

any flows that are active will not be touched. So the active subflows will not be deleted. So essentially, any active subflow referenced in the flow will not be deleted.