Installation
Install the Real Messaging Engine managed package into a sandbox first, validate, then promote to production.
Prerequisites
| Requirement | Detail |
|---|---|
| Salesforce edition | Enterprise, Unlimited, or Developer |
| My Domain | Deployed and active |
| Enterprise Intelligence Engine | Installed (RME depends on the EIE base package) |
| Permissions | System Administrator with "Install Packages" |
| Provider account | At least one delivery provider (SendGrid, SES, Azure ACS, Mailgun, Postmark, SparkPost) |
| DNS access | To publish SPF, DKIM, and DMARC records |
1. Install the package
- Open the AppExchange installation link supplied by Real Intelligence.
- Choose Install for Admins Only (recommended for the first install).
- Approve third-party access for the provider endpoints you plan to use.
- Wait for the install confirmation email before configuring.
# Optional: install via Salesforce CLI
sf package install \
--package 04t5f000000RmeXAAS \
--target-org my-sandbox \
--wait 20 \
--security-type AdminsOnly
2. Assign permission sets
| Permission set | Grants |
|---|---|
RME_Administrator | Provider configuration, domain setup, suppression management |
RME_Message_Sender | Send via Flow, Apex, and Lightning components |
RME_Analyst | Read-only access to messages, delivery status, and reports |
RME_Integration_User | REST API and webhook processing (integration user only) |
sf org assign permset --name RME_Administrator --target-org my-sandbox
3. Enable the delivery services
In Setup → Custom Metadata Types → RME Settings, enable:
- Delivery Service (master switch)
- Event Ingestion (webhook processing)
- Suppression Enforcement
- Consent Enforcement
4. Verify the install
Run the packaged smoke test from RME Admin → Diagnostics, or from Apex:
RME_Diagnostics.Result r = RME_Diagnostics.run();
System.debug(r.summary);
// Expected: PROVIDERS:0 CREDENTIALS:0 DOMAINS:0 STATUS:AWAITING_CONFIGURATION
A fresh install reports AWAITING_CONFIGURATION until at least one provider and one authenticated domain exist.
5. Upgrade path
Managed package upgrades are non-destructive. Custom metadata, provider configs, templates, and message history are preserved. Review Release Notes before every upgrade and install into a sandbox first.
Continue to Configuration.
Was this helpful?
Last updated 1 month ago