Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Simplified Version of PR 99, Version 3 to Verison 4

Open
  • Is something wrong?
#140 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
backend, documentation

Research direction

Start with the referenced PR 99 commit and its included flow, Apex action, Apex class, and test class. Review the requested Migrated_Record_Id__c field and write user-facing setup and copy/paste instructions. Done means the field, instructions, and Apex materials are covered and the migration is tried in an org with both version 3 and version 4 installed.

Written by the indexing model from the issue text.

Description

enhancement help wanted

@rosalindlopez wrote a really awesome solution for transitioning from the current V3 of the app to this new V4. But it requires people to already be familiar with CCI, devops, etc.

To simplify it we can:
look at this commit to PR 99. https://github.com/SFDO-Community/UnsubscribeLink/pull/99/commits/814fe30a5121e1067be0e44ed1979aeab3a42518#diff-abc0dc21f2901fb2b631a5520473e8d745c6a564ee4566106dec712b8ff52396

  1. create this field on the Unsubscribe object.
Migrated_Record_Id__c false If this record was migrated from the older Salesforce Labs application, the 18 digit Id of the original record will be stored here. Migrated Record Id 18 false false Text false
  1. Create instructions for users to themselves create the flow that is included in this commit. It basically calls an apex action, as far as I understand.
  2. Write instructions for how to copy and paste in the apex code from the same commit. That's an apex class and a test class.
  3. Try this out in an org that has both version 3 and version 4 installed.
Dominant language
Apex
Stars
7
Forks
21
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SFDO-Community/UnsubscribeLink

All issues in SFDO-Community/UnsubscribeLink

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.