The customer administrator runbook for production: installing the Kemicard package in a production org, migrating your validated sandbox configuration across, and upgrading an existing production org that runs an older version of Kemicard.
Who implements? Your internal Salesforce admin can follow this runbook end to end — or hand it to any of our SI partners or the Kemisoft Professional Services team.
Part A — Installing Kemicard in Production
This part details the formal process for deploying Kemicard into a Salesforce Production environment, using Salesforce-native pathways to ensure configuration integrity.
Phase 1 — Pre-installation & prerequisites
Before initiating installation, verify that the following prerequisites are met to prevent integration failures.
1.1 Environment readiness
- Administrator access — ensure you have the System Administrator profile in the target production org.
1.2 Org detail provisioning
Critical: you must request API credentials from Kemisoft before proceeding to Phase 2. Send the following details to Kemisoft:
- Production Org ID.
- The specific username designated as the integration user.
Phase 2 — Configuration & package installation
2.1 Install the managed package
- Access the production install URL: navigate to install.kemicard.app/products/kcard/latest.
- Click “Install Package Only (New Installs or Upgrades)”.
- Click the “Login into Start Pre-Install Validation” dropdown and select the appropriate org.
- Log in as a Salesforce administrator.
- Select Install for All Users and click Install.
- When prompted to Approve Third-Party Access, check “Yes, grant access to these third-party web sites” and click Continue.
- Wait for the installation process to complete.
Verify the installed version matches the version shown on the installation page under Setup → Installed Packages.
2.2 Configure named credentials
- Navigate to Setup → Named Credentials.
- Edit the Kemicard App entry.
- Input the Username and Password provisioned by Kemisoft (from step 1.2).
2.3 Authorize the Kemicard user
- Open Kemicard from the App Launcher.
- In the Kemicard Console, select Authentication.
- Click Authorize Kemicard User and select Allow in the Salesforce popup.
- After successful authorization, you should see the authenticated integration user displayed.
Phase 3 — Migration & order of execution
Rule: migrate metadata first via Change Sets, then designs via Export/Import. Templates rely on existing fields.
3.1 Metadata migration (Change Sets)
- In sandbox: create an Outbound Change Set.
- Add custom fields (e.g.,
Member_Pass__c), Flows (Send/Scan), custom email templates, custom permission sets (Kemicard Custom), and any other supporting metadata. - Deploy in production via Inbound Change Sets.
3.2 Template migration (Export/Import)
- Export template definitions from the sandbox Kemicard Console.
- Import the files into the production Kemicard Console.
Watch it done: Kemicard Template Import/Export — video walkthrough.
Phase 4 — Post-migration validation
Conduct the following functional tests to sign off on the production environment.
- Integrity check — verify Named Credentials show a status of “Authorized”.
- Custom permission sets — assign custom permissions to users depending on their role.
- Pass generation — pick a sample record and generate a digital pass.
- Rendering — confirm branding and QR codes appear correctly in Apple Wallet and Google Wallet.
- Flow execution — scan a pass with the Kemicard Scanner to ensure the scan flow triggers.
Part B — Upgrading an Existing Production Org
This part covers upgrading an existing Salesforce production org that is running an older version of Kemicard to the latest release.
- Test in sandbox first — the new version should be tested in a sandbox before upgrading production.
- Administrator access — System Administrator profile in the production org.
Upgrade the package
Use the same installer as Part A: open install.kemicard.app/products/kcard/latest, choose “Install Package Only (New Installs or Upgrades)”, log into the production org, and complete the installation. Verify the new version under Setup → Installed Packages.
Apply package updates (Kemicard Console → Updates)
Required in release 2.28. Installing or upgrading the package does not, by itself, apply all of Kemicard's metadata and schema changes for the new version. After the package upgrade you must run the upgrade steps from the Console so they execute under your active administrator session — this avoids Salesforce's post-installation restrictions.
- In the Kemicard Console, open the Updates → System Upgrades area.
- The Updates card shows your Current Version and a What's New link.
- If the System Upgrades panel shows “Upgrade Pending”, click Run Upgrade. The button is disabled while running — let it complete.
- Confirm every step in Last Upgrade Run Results succeeded; a successful run shows “System is Up to Date”.
Do not skip this step on an upgrade (e.g., 2.27 → 2.28). Until “System is Up to Date” is shown, the org is running on incomplete metadata and passes may not generate correctly.
After upgrading, re-run the Phase 4 validation checks above.
Where to go next
- Bulk Actions — roll passes out to your full production base.
- Release notes — what changed in the version you just installed.
- Troubleshooting & KB — including named-credential status-code diagnosis.
