Tarilblazer Treasure Hunt App

Trailblazer Treasure Hunt app showing how to build scalable apps that integrate with Salesforce Lightning Platform.

Add-ons

The add-ons used are listed in the app.json but is here as well. It's fine to use the free tier for all add-ons.

CloudAMQP (tier: "lemur")
Heroku Connect (tier: demo)
Papertrail (tier: "choklad")
Heroku Postgresql (tier: "hobby-dev")
Heroku redis (tier: "hobby-dev")

Deploying

Deploying the app to Heroku is as simple as git push heroku master or deploying directly from Github using the Heroku dashboard. Please note that the app is built for demo so it doesn't absolutely require you to set any of the environment variables or add any of the add-ons the app require. This can be done during the demo. Below is the demo script I have used.

There is a version of the demo where I go from creating and showing the app in Staging and progress to Production using a pipeline. To avoid having to redo the configuration and show the power of automation and the Heroku CLI I use the promote_prod.sh script in the scripts directory. The script does the following:

Creates the Pipeline
Creates the Production app (in the a team if required)
Adds the Staging and Production apps to the Pipeline
Configures the Production app with environment variables and add-ons
Waits for you to authorize Heroku Connect with Salesforce (as the Heroku CLI Heroku Connect plugin sometimes act up here)
Imports the Heroku Connect mappings
Promotes from Staging to Production
Scales the web tier of the Production app

The script takes the following parameters:

The app name in Staging
The app name for Production (will be created)
The name of the pipeline to create and add the apps to (will be created)
The team name if any

Example

$ ./promote_prod.sh my-staging-app my-prod-app my-pipe my-team

Requirements

Heroku CLI
Heroku Connect plugin (heroku plugins:install heroku-connect-plugin)
jq (only required for the promote_prod.sh script)

Demo

Prep

Open and log into org
Open Setup in org
Open and log into Heroku to Personal apps
Open Github to repo (github.com/lekkimworld/trailblazer-treasure-hunt)
Clone Github repo and create configuration for scripts
- cd /tmp
- git clone https://github.com/lekkimworld/trailblazer-treasure-hunt.git
- cd trailblazer-treasure-hunt
- cd scripts
- Create .env-scripts file with the following key-value pairs
  - SF_USERNAME='[username to Salesforce org]'
  - SF_PASSWORD='[password for above user]'
  - SF_CLIENT_ID='[client id from Connected App in Salesforce]'
  - SF_CLIENT_SECRET='[client secret from Connected App in Salesforce]'

Salesforce Demo

Open Salesforce and show Questionnaire, Version, Questions and Answers
We do the configuration in Salesforce because it’s easy and it’s where our users work
Process Automation
- We have a Process Builder flow in Salesforce to communicate to the Heroku app when anything changes
- We have Triggers to verify that status changes are not incorrectly done etc.
We have a custom Lightning Component to draw the winner

Heroku Demo

Open Heroku
Go to the Team used for demo
Create staging app
Get source from Github directly
The app depends on some add-ons - let’s provision those
- Heroku Redis
- CloudAMPQ
Configuration of the app is done through environment variables as it allows us to have different configuration for test, staging, production and so on
- Show config variables
- Use script and scale the backend process (scripts/configure1.sh)
- App is now working
Log and traceability
- Open log in web ui (I can also tail the log from the CLI)
- Would like to have better traceability and ability to search the logs and have better retention
- Add Papertrail
- Open Papertrail and see events starting to pipe in (if it doesn’t start piping in restart the dynos)
Data is written back to Salesforce using Heroku Connect
- For Heroku Connect we need a database to provision it
- We also need the Heroku Connect add-on
- Create Connection to Salesforce
- Create Mappings
- Show how it’s done using the UI
- Too error prone for demo - use script (scripts/configure2.sh)
Show scaling the app

Environment variables

If none of the below variables are set the application will start but just shown text to the user indicating that configuration is missing.

Once CLOUDAMQP_APIKEY, CLOUDAMQP_URL, REDIS_URL, SF_USERNAME, SF_PASSWORD, SF_CLIENT_ID and SF_CLIENT_SECRET is set the app is functioning but will not write back to Salesforce,

For writing back to Salesforce DATABASE_URL is required (and Heroku Connect should be configured). If DATABASE_URL is not set we just log the completion of the flow to the console / Papertrail.

Name	Purpose
SESSION_SECRET	Secret to use when generating session ID's. If not set a value will be generated but this will cause issues for the client if multiple dynos are spun up for the web process
ENFORCE_TLS	Set to 1 to make sure all requests are redirected to TLS
SESSION_TTL	Session lifetime in hours (default is 2)
NODE_ENV	What environment are we running in. If set to "production" all requests are ensured over TLS. If set to "demo" the personal info form will be prefilled with data and the "lottery name" shown on the final confirmation page
SF_PERSONACCOUNT_RECORDTYPEID	Should hold the ID of the PersonAccount record type to use. The value is used through Heroku Connect when writing back to Salesforce using Heroku Connect to create accounts as PersonAccounts
SF_USERNAME	Username to use when logging into Salesforce to get data or listen for Platform Events
SF_PASSWORD	Username to use when logging into Salesforce to get data or listen for Platform Events
SF_CLIENT_ID	Client ID for Salesforce OAuth for connection when logging into Salesforce to get data or listen for Platform Events
SF_CLIENT_SECRET	Client Secret for Salesforce OAuth for connection when logging into Salesforce to get data or listen for Platform Events
SF_CALLBACK_URL	If specified this will cause the /admin/events endpoint of the application to require authentication. This is one by redirecting the user to the Salesforce org for authentication
SF_LOGIN_URL	If not set this defaults to login.salesforce.com but may be set to test.salesforce.com or similar to use with a sandbox
SF_APIVERSION	Salesforce API version to use (defaults to v44.0)
CLOUDAMQP_APIKEY	Added by CloudAMQP add-on
CLOUDAMQP_URL	Added by CloudAMQP add-on
DATABASE_URL	Added by Heroku Postgres add-on
PAPERTRAIL_API_TOKEN	Added by Papertrail add-on
REDIS_URL	Added by Heroku Redis add-on

jostmansfdc / trailblazer-treasure-hunt