<p class="indent1"><strong>1. Call for Nominations</strong></p> <p class="indent2">Email templates approved and created in Salesforce</p> <p class="indent2">Email recipients added to campaigns in Salesforce</p> <p class="indent2">Target send date established</p> <p class="indent1"><strong>2. Nomination Form </strong></p> <p class="indent2">Nomination form confirmed, tested, and finalized</p> <p class="indent2">Email notification to nominator</p> <p class="indent2">Email notification to nominee</p> <p class="indent2">Confirmation form confirmed, tested, and finalized</p> <p class="indent2">Nomination form linked on website</p> <p> </p>

<div>Create a new case letting me know how you did with the tasks in the "<a href="http://agln.screenstepslive.com/s/guide/m/54420/l/503743-test-yourself">Test Yourself</a>" section! In particular, if you created any fake records, please log a case to request that they be deleted. For your reference, steps for creating a case follow below.</div>

<ol><li><span style="color: rgb(31,73,125)"><strong>Test the link</strong></span><span style="color: rgb(31,73,125)"> with the contact ID for as many of the people you will be sending it to. It's important to experience the form from the end user's perspective so you can understand what their experience will be like and identify any questions or issues that might arise.</span></li> <li><span style="color: rgb(31,73,125)"><strong>Test the submission</strong></span><span style="color: rgb(31,73,125)"> to see how it behaves in Salesforce. Understand what will happen when the form is submitted. In this case, the submission should create a Venture Update record on the most recent Venture where the Fellow is marked the Lead Contact. Make sure it’s populating the right fields on that Venture Update record (e.g. tagline &nbsp;tagline, description &nbsp;description, update &nbsp;update).</span></li> <li><span style="color: rgb(31,73,125)"><strong>Test the flow</strong></span><span style="color: rgb(31,73,125)"> in Salesforce to make sure that when you check the “Set as current version” box on the Venture Update record that is created, it updates the appropriate fields on the Venture record itself (e.g. tagline &nbsp;Description (200 words), Description &nbsp;Description (800 words), general update &nbsp;Current Venture Update). Note that these mappings right now DO NOT align &nbsp;we need to map the tagline to the Description (200 words) field on the Venture record and the description to the Description (800 words) field on the Venture record as this is how the current integration with MSDS is set up. Once we move off that integration, we will have these map to the appropriate fields.</span></li> <li><span style="color: rgb(31,73,125)"><strong>Test the link</strong></span><span style="color: rgb(31,73,125)"> for the contact ID again, just to make sure that the form is pulling the newly updated Venture fields into the form. For any potentially cyclical process, it’s important to make sure we are accounting for repeated submissions &nbsp;so we will particularly want to test what happens when you use that form link again to make additional changes. Another Venture Update record should be created that you will need to review; if approved, try checking the “Set as current version” box on that record to make sure it updates the Venture record. I haven’t set it to uncheck the previous record but the flow will update the Venture record based on the most recent Venture Simple Update record to be marked true so it isn’t a problem technically.</span></li> </ol>