Retiring Workflow Rules

[msouther-lisc]

NPSP still includes 11 Workflow Rules on the Contact object in the "Contacts & Organizations" package. We have about 2 years left until end of support for Workflow Rules, but it would be good to see these replaced with a better option well ahead of that date.

Moving this logic to a before-save flow or before trigger would improve performance by removing an otherwise unnecessary round of DML.

[Raghav-Bell]

hi @msouther-lisc can you please assign this issue to me.
Thanks

[judisohn]

@Raghav-Bell Just so you know, the owner of this repository doesn't accept community pull requests.

[Raghav-Bell]

@judisohn I have started working on it & even created 10 Flows for that. Anyways, I don't know about that. Can you please tell me better way to contribute Salesforce (open source),

[judisohn]

@Raghav-Bell While I don't work for Salesforce anymore, I used to be the Open Source Community Manager for this project, which is why I'm familiar with it.

While NPSP repository is public so you can review (and of course, fork) the code, you can see on the ReadMe that there is no path to contribution. Therefore, even if you submitted a PR here, it's highly unlikely to get reviewed, much less merged. You are free to do what you like...but I'm just being realistic with you as one community member to another before you invest time in a path that will unnecessarily disappoint you.

I know the community is anxious to see new flows replace the workflow rules in the managed package, and given the plan to sunset workflow rules, they are generally on Salesforce's roadmap. In the meantime, if you'd like to share your work with the community, the best way (IMO) would be to create a repository under your account and share it with a post in the Nonprofit Success Pack group in the Trailblazer Community. There are a lot of ways to share Salesforce solutions with others which is out of the scope of this reply. There are Groups in TBC for that too. :-)

FYI, very few people actively follow and engage here on the project's issues.