Salesforce Membership UAT Feedback
VIDEO TRANSCRIPT | Recorded: 2024-08-14 | Verify against current system state
Abstract¶
UAT testing feedback on Salesforce sandbox. Documents issues encountered including profile filter problem hiding AANP app options, inconsistent naming conventions (person/company vs business), need to consolidate dual address fields into single address with type, and confusion about how memberships, subscriptions, and orders relate to each other. Key concern is workflow difference from Aptify where orders drive membership creation.
Key Procedures¶
- Log into Salesforce sandbox
- Select AANP app from app selector (View All > AANP)
- Review person and business account record layouts
- Test membership and subscription creation
- Document naming convention inconsistencies
- Compare order workflow to Aptify expectations
Notable Statements¶
- 0:00:36 "I had to go here and then click view all and I realized that there is an AANP option down here"
- 0:00:47 "It was confusing... because they didn't know that there were all these extra things"
- 0:01:18 "In Aptify it was person and company. I'm fine if it's person and business, but if we're going to use business, we just need to make sure we're utilizing that phrase throughout the system"
- 0:02:49 "We were talking about, hey, I only want one address to show for a user"
- 0:03:32 "We're still recording two different addresses in two different sets of address data points"
- 0:03:50 "We really want to get away from that and just be down to one single address"
- 0:03:59 "What we're really looking for is this to be address with an address type and the address type would be home or work"
- 0:04:51 "Our understanding... the way it works now with Aptify is you create an order. Once the payment is processed, the order creates a subscription"
- 0:05:51 "It should not be changeable by most people. This should be just set by the order"
- 0:06:49 "They're used to going to an account, clicking on the account, going to orders, clicking new order and processing a membership transaction"
Systems & Configurations¶
Systems Mentioned¶
- Salesforce (sandbox)
- Aptify (comparison reference)
Issues Identified¶
| Issue | Current State | Desired State |
|---|---|---|
| App visibility | Hidden until AANP app selected | Default to AANP for users |
| Naming: Company | Mixed "company" and "business" | Consistent terminology |
| Phone fields | Main phone separate from phone type | Grouped together |
| Address fields | Two addresses (home/work) | Single address with type |
| Specialty cascading | Flat list | Subcategories under main categories |
Aptify Workflow (Expected)¶
| Step | Action | Result |
|---|---|---|
| 1 | Create order | Order with line items |
| 2 | Process payment | Payment processed |
| 3 | Automatic | Subscription created |
| 4 | Automatic | Membership type set |
| 5 | Automatic | Auto-renewal configured |
Salesforce Concerns¶
| Element | Issue |
|---|---|
| Membership | Can be created without order |
| Subscription | Not required to link to order |
| Membership categories | Shows all types on person record |
| Order-driven workflow | Unclear implementation |
Address Consolidation¶
| Current | Proposed |
|---|---|
| Home Address (all fields) | Address (single set of fields) |
| Work Address (all fields) | Address Type (home/work) |
| Preferred Address | Eliminated |
Credentials/Access Mentioned¶
- Salesforce sandbox access
- Team members: Nick, Tamara
Vendor Contacts Mentioned¶
None mentioned in this recording.
Errors & Troubleshooting¶
- Issue: AANP app options not visible in sandbox
- Cause: Profile filter or app visibility settings
- Resolution: Click View All and select AANP app
- Timestamp: 0:00:25
Transcript Gaps & Quality Notes¶
- UAT feedback recording (8 minutes)
- Early testing phase observations
- Comparison to Aptify expected behavior
- Team confusion documented
- Recorded for development team discussion