Merge pull request #4 from heroku-examples/ga-updates

Initial GA updates

Author: kenwalger

README.md

@@ -1,7 +1,5 @@
 # Heroku Integration - Salesforce API Access (Node.js)
 
-> **Important**: For use with the Heroku Integration and Heroku Eventing pilots only
-
 ## Architecture Overview
 
 This sample application showcases how to extend a Heroku web application by integrating it with Salesforce APIs, enabling seamless data exchange and automation across multiple connected Salesforce orgs. It also includes a demonstration of the Salesforce Bulk API, which is optimized for handling large data volumes efficiently.
@@ -13,20 +11,20 @@ This sample application showcases how to extend a Heroku web application by inte
 * Heroku login
 * Heroku AppLink Pilot enabled
 * Heroku CLI installed
-* Heroku AppLink Pilot CLI plugin is installed
+* Heroku AppLink CLI plugin is installed
 * Salesforce CLI installed
 * Login information for one or more Scratch, Development or Sandbox orgs
-- Watch the [Introduction to the Heroku AppLink Pilot for Developers](https://www.youtube.com/watch?v=T5kOGNuTCLE) video 
 
 ## Local Development and Testing
 
 You do not need to deploy your application but you do need to configure it with Heroku.
 
 ```bash
 heroku create
-heroku addons:create heroku-integration
-heroku salesforce:connect my-org --store-as-run-as-user
+heroku addons:create heroku-applink
+heroku salesforce:authorizations:add my-org
 heroku config:set CONNECTION_NAMES=my-org
+heroku config:set HEROKU_APP_ID="$(heroku apps:info --json | jq -r '.app.id')"
 heroku config --shell > .env
 npm install
 npm start
@@ -36,15 +34,15 @@ Navigate to `http://localhost:5006` to observe a list of accounts from the conne
 
 ### Multiple Org Connections
 
-To access multiple Salesforce orgs, repeat the `salesforce:connect` command above with different org logins and connection names, then update the `CONNECTION_NAMES` environment variable within the `.env` file with a comma delimiated list of connection names (example shown below). The sample code will automatically query for `Account` in each org and display the results.
+To access multiple Salesforce orgs, repeat the `salesforce:authorizations` command above with different org logins and connection names, then update the `CONNECTION_NAMES` environment variable within the `.env` file with a comma delimiated list of connection names (example shown below). The sample code will automatically query for `Account` in each org and display the results.
 
 ```
 CONNECTION_NAMES=my-org,my-org-sales-a
 ```
 
 ### Bulk API Demo
 
-This sample includes a demonstration of using the Salesforce Bulk API using connections formed with the Heroku Integration add-on. To see this in action obtain an org that is empty or that you are using for testing purposes only. Repeat the `salesforce:connect` command above using the connection name `empty-org` and then update the `CONNECTION_NAMES` environment variable within `.env` with a comma delimiated list of connection names (example shown above).
+This sample includes a demonstration of using the Salesforce Bulk API using connections formed with the Heroku Integration add-on. To see this in action obtain an org that is empty or that you are using for testing purposes only. Repeat the `salesforce:authorizations` command above using the connection name `empty-org` and then update the `CONNECTION_NAMES` environment variable within `.env` with a comma delimiated list of connection names (example shown above).
 
 When you visit the `/bulk-demo` endpoint, the application will check for existing bulk-loaded records. If none are found, it will start an asynchronous bulk load process. You will see output in the console similar to this:
 
@@ -83,20 +81,21 @@ echo "delete [SELECT Id FROM Account WHERE Name LIKE 'Bulk Account%'];" | sf ape
 
 ```bash
 heroku create
-heroku addons:create heroku-integration
-heroku salesforce:connect my-org --store-as-run-as-user
+heroku addons:create heroku-applink --wait
+heroku salesforce:authorizations:add my-org
 heroku config:set CONNECTION_NAMES=my-org
+heroku config:set HEROKU_APP_ID="$(heroku apps:info --json | jq -r '.app.id')"
 git push heroku main
 heroku open
 ```
 
-To access multiple Salesforce orgs, repeat the `salesforce:connect` command above with different org logins and connection names, then update the `CONNECTION_NAMES` with a comma delimiated list of connection names. The sample code will automatically query for `Account` in each org and display the results.
+To access multiple Salesforce orgs, repeat the `salesforce:authorizations` command above with different org logins and connection names, then update the `CONNECTION_NAMES` with a comma delimiated list of connection names. The sample code will automatically query for `Account` in each org and display the results.
 
 ## Technical Information
 
-* Salesforce APIs are always accessed in the context of the authenticated user defined at the time of connection through the `--store-as-run-as-user` CLI parameter. This means that only the objects and fields the user has access to can be accessed by the code.
+* Salesforce APIs are always accessed in the context of the authenticated user. This means that only the objects and fields the user has access to can be accessed by the code.
 * This is a Node.js Express application, using EJS to render browser content. Other client libraries and frameworks can be used of course.
-* The application uses the `@heroku/salesforce-sdk-nodejs` package to handle Salesforce connections, authentication, and API interactions including SOQL queries and Bulk API operations.
+* The application uses the `@heroku/applink` package to handle Salesforce connections, authentication, and API interactions including SOQL queries and Bulk API operations.
 * The sample uses a custom environment variable `CONNECTION_NAMES` to enumerate the org connections to be used by the application. However this could easily be hardcoded in your own library code, or obtained from a configuration service or other preferred means of your choice.
 * The Bulk API demo intentionally showcases real-world duplicate handling scenarios. Some records may fail to insert due to Salesforce duplicate detection rules, which demonstrates proper error handling in bulk operations. Users can either accept this as a learning opportunity about integration resilience or temporarily disable duplicate rules in their Salesforce org for testing purposes. Successfully inserted records will still be visible on the main page, regardless of any duplicate-related failures.
 

index.js

@@ -1,7 +1,7 @@
 require('dotenv').config();
 const express = require('express')
 const path = require('path')
-const { init } = require('@heroku/salesforce-sdk-nodejs')
+const { init } = require('@heroku/applink')
 
 const port = process.env.PORT || 5006
 const app = express()
@@ -23,7 +23,7 @@ app.get('/', async (req, res) => {
       connectionNames.map(async (connectionName) => {
         try {
           // Initialize connection for this org
-          const org = await sdk.addons.herokuIntegration.getConnection(connectionName.trim())
+          const org = await sdk.addons.applink.getAuthorization(connectionName.trim())
           console.log('Connected to Salesforce org:', {
             orgId: org.id,
             username: org.user.username
@@ -101,7 +101,7 @@ app.get('/bulk-demo', async (req, res) => {
     }
 
     // Initialize connection for empty-org
-    const org = await sdk.addons.herokuIntegration.getConnection(emptyOrgName)
+    const org = await sdk.addons.applink.getAuthorization(emptyOrgName)
     console.log('Connected to empty-org:', {
       orgId: org.id,
       username: org.user.username