#Summit Events0 personne en discute

@Ryan Blake | @Mike Walter | @Commons Project: Summit Events App

I have built a solution that works quite well. 

Answering the question: "

" 

Here is one way: 

I have built a Screen Flow that inclues the basic questions (Name, Email, Phone) and creates a Summit Events Registration record where Status = Declined.   

There's an input variable to accept the Summit Events Instance record from the URL; this is used to get the Instance record and save the new Registration record. 

I also had to add an entry to the Status picklist field on the Summit Events Registration object: "Declined". 

The flow runs in System Context Without Sharing, because a new record needs to be created and the Guest Site User cannot create records.   

Best practice is to build the mail flow with a subflow that runs in System Context and only does the Create Records.  That way, the main flow can run in user context, although you need to make sure the Site Guest User can read from all the objects using the Site Guest Profile and a Site Guest Sharing Rule. 

The flow is activated and deployed to a custom Visualforce page.  The Visualforce code is quite simple: 

SummitEventsInstanceDecline.vfp

<apex:page showHeader="false" sidebar="false" lightningStylesheets="true">
    <flow:interview name="Screen_Decline_Summit_Event_Invitation">
        <apex:param name="InstanceRecordID" 
                    value="{!$CurrentPage.parameters.InstanceRecordID}" 
        />
    </flow:interview>
</apex:page>

As you can see, it's very basic.  To make it look more like you Summit Events Registration page, you can manually add CSS and HTML to this code, which isn't too difficult.  Note that you need to include a parameter (the Instance's record ID) in the URL when you go to this page. 

This page needs to be added to the Summit Events Site definition  

Setup > User Interface > Sites & Domains > Sites > Site Label > Events (or whatever you called your Summit Events site) 

Scroll down to the Site Visualforce Pages list and add your new page from above. 

Next, you need an email template that includes two buttons:  

1. [Book Now] that takes you to the Instance Registration link (as found on the Summit Events Instance page)
2. [Decline] that takes you to the new Visualforce page 

<your URL>/events/SummitEventInstanceDecline?InstanceRecordID=<the record ID ofthe Summit Events Instance>

You will need to ensure the email template can access the Instance record so it can insert these merge fields: <Registration Link> and <Id> 

Finally, use that email template to send from a list view or campaign (or your favourite email sender tool like MCAE or MailChimp).

Hi @Reid Brownell, 

SEA does not support this out of the box. This is a much requested feature, but some of the implications go beyond what security review would allow us to do in a guest user status.  

I do think you could make this work from a template perspective. Remember, that you have full control of a custom Visualforce template if used in your event. The template could load with it's own apex class, grab the id out of the URL, make the query, and then inject, via JavaScript, the data in the correct fields. 

Thanks!

Great questions @Luison Lassala! This is exactly what the instance will do (image below).  After you create the Event Record, you have to create an instance which captures the date and time for event (amongst other things like capacity).  When that instance record is created, a QR code gets generated on the record as well as a hyperlink that says "Register".  Those are shareable to allow for anyone to complete the form.  Summit Events doesn't use Communities, but leverages Sites, so as long as that's configured, you can accept registrations non-community users.    

@Seth Vanderdrift​ The update_admin_profile task has an option for setting record type visibility. I'd recommend using that instead of including the whole Admin profile in your package metadata because it's a little more robust to differences that can exist between orgs in terms of which exact permissions are available (as well as to avoid the conflict). To specify the record types that update_admin_profile should make sure are visible, add a section like this to cumulusci.yml:

tasks:
    update_admin_profile:
        options:
            record_types:
                - record_type: Custom_Object__c.RecordType1
                  default: true
                - record_type: Custom_Object__c.RecordType2