Key Decisions

This project will not include a data model for benefits

• Fulfillment of benefits often accomplished through external systems that require integration
• The necessary data to describe who gets benefits can be captured via campaigns, products, or other details of the transaction
• Often the process level motivations for a user to tracking benefits are limited, it's data that people want, but there isn't a logical way to integrate it's use into the process.
• Benefit assignment's on an individual level can lead to very high data volumes with minimal utility
• Available benefits can be managed via association with other objects, campaign for promotional benefits, membership for standard benefits

August 2025: Use of the Opportunity object

• The project is shifting from requiring the use of the Opportunity object to the optional use of the Opportunity object to account for businesses that don't use opportunities. Any MVP package automation based on the Opportunity object is being moved to the Membership Form Submission (MFS) object with the option to create or omit creation of an opportunity record when creating an MFS.