feature/Usability and design updates to unsubscribe link setup flow

[spilzer]

Critical Changes

Changes

• added progress bar
• added explanation of implications when changing company name
• resolved unhandled faults related to org-wide email address creation by preventing users to back track to previous screens and updated the record choice set to include non-verified email addresses
• updated final screen to clarify the flow is finished but can be run again if needed
• added explanation text to all preview screens

Issues Closed

#93
#105
#113
#114
#144

[DKeatonDC]

@spilzer -- one thing I noticed is that the "Show a Progress Indicator" is not activated by default after installation (I've tried it in 2 different orgs). At minimum, we should probably document this.

All other changes are very good and would be approved, otherwise.

PS I did some more research, and it seems like one can set this via the metadata API. Given the additional layer of complexity, it seems like documenting it in setup is the best option. I'll raise it as an issue that we can address in the future.

https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_visual_workflow.htm#FlowCustomProperty

[spilzer]

@spilzer -- one thing I noticed is that the "Show a Progress Indicator" is not activated by default after installation (I've tried it in 2 different orgs). At minimum, we should probably document this.

@DKeatonDC good catch! I updated the instructions google doc to include steps for activating the progress indicator before running the setup flow. Let me know if what I wrote is sufficient. Thanks!

[DKeatonDC]

Approving now that documentation has been added.

[salgsstyrke]

Hey @spilzer and @DKeatonDC . Unfortunately the progress bar didn't actually advance for me during the flow.

[spilzer]

Hey @spilzer and @DKeatonDC . Unfortunately the progress bar didn't actually advance for me during the flow.

Hrm, I wonder if I somehow didn't update the code in the pull request to use the latest version of the flow. I will try to recreate the error in a fresh dev org since it's currently working in mine.

[salgsstyrke]

moving this to draft so we can move ahead with making a new package.