Participant list should be dynamic

Currently, when a participant list is generated and all fields are mapped, they are “locked” with those values.  This makes it prohibitive to use Journeys for communications over time.  Here are some examples of issues:

• CSM changes after the Journey starts
  • CTA is assigned to the CSM when the participant list was created instead of the current CSM
  • Emails are sent from a previous CSM, and the client may even respond to a previous CSM
• Client’s email address changes
  • Email is sent to an old email, potentially exposing company information to a non-customer
• Other fields become outdated
  • Tokenized fields in CTAs and email templates surface inaccurate information the day the communication is created

The participant List is mapped to fields with real-time updates and the file should be upserted at minimum before each time an action within the program is occurring for those participants.