Considerations for the Safety Cloud Packages

General Considerations

These considerations apply to Safety Cloud packages in general.

• Safety Cloud packages intend to provide tools that help accelerate the deployment of your COVID-19 Health Verification solutions.

  Make configuration decisions based on your particular use case.

• To enhance the security of recipients’ information, we recommend using Multi-Factor Authentication and enabling Shield Platform Encryption.
• Make sure that you follow secure coding guidelines. For more information, see the Salesforce Security Guide.
• To manage public access to your vaccine form, follow Experience Cloud security practices. See Secure Your Experience Cloud Sites and Guest User Record Access Developer Best Practices.
• Be mindful of the values that you store about your recipients. We recommend that you avoid collecting information that you don’t need and any sensitive information that can be used for discrimination or other unlawful purposes. For more information, see our Acceptable Use and External-Facing Services Policy.
• Adhere to the accepted data-retention policies and related privacy laws for your organization, wherever they apply.

Considerations for the Safety Cloud Package

These considerations apply to the Safety Cloud package specifically.

• Person accounts are mandatory for installing Safety Cloud and must be enabled in the org.
• When you install the Safety Cloud package, we enable Feed Tracking on the Health Verification object. For information on how to select and track specific fields on an object, see Feed Tracking.
• To use Safety Cloud, accept the installer terms for the Safety Cloud Template package.
• Safety Cloud generates QR codes when criteria on the QR Code Generation records match data on an individual’s Health Verification record. For information, see QR Code Generation.

  Sample QR Code for a Health Verification Record (JSON Format)

  
  {"v": "a021100000JdI7NAAV",”occ”: “a1U1B00000C9WcXUAV”, 
  "vs": "2021-12-16T08:00:00Z","ve": "2021-12-17T07:59:59Z"}

  Where:

  • The value for "v" is the Verification ID.
  • The value for occ is the Occasion ID.
  • The value for "vs" is the Verification Start Date and Time.
  • The value for "ve" is the Verification End Date and Time.

  Any system that reads a QR code must read these four pieces of information. Dates are for offline support. If your event has unstable WiFi, the QR codes can be scanned using the start and end dates or times.

  You can configure these fields so that the QR code is only valid for a specific set of hours, as shown in the sample.

  Access Start Time = Beginning of day for negative test (the day of the event).

  Access End Time = End of day for day of negative test (the day of the event).

• To incorporate the Wellness Questionnaire into your health verification strategy, install the Surveys Feedback Management Starter package and enable Surveys in your org.
• The user installing Safety Cloud must have the Salesforce Surveys Advanced Features Permissions.

  The Advanced Features Permission enables your organization to use the predefined data mappings in the Wellness Questionnaire with Health Verification records.

Prerequisites for the Safety Cloud Package

If you plan to use Marketing Cloud Engagement to send updates to recipients, set it up first. For details, see Marketing Cloud Engagement Setup.

Make sure that you have the correct licenses. For the Safety Cloud package, you need Service Cloud licenses.

In Setup, turn on Data Protection and Privacy, and select Make data protection details available in records.

What the Safety Cloud Package Changes in Your Org

If you have the person accounts enabled when a user submits a health verification, you can schedule a job to create a person account for that user. And for every subsequent health verification action, we assign the associated Health Verification record to the user’s person account.

For more information, see Person Accounts.

After you download the Safety Cloud package, several things happen.

• We turn on the Site.com page cache permission.
• We add a Visualforce page for the flow safetycloud.SafetyCloudVerificationForm.
• We create these permission sets that allow agents to view, approve, and reject health verification requests from your customers.
  • SafetyCloud Admin
  • SafetyCloud Agent
  • SafetyCloud Health Verification Form Site User
• We create a permission set called Health Verification Permission Set that lets agents view, approve, and reject health verification requests from your customers.
• We create a Health Verification and Needs Review queue.
• We create a platform cache org partition named HealthVerification in the safetycloud namespace.

  By default, we allocate 3 MB to the cache org partition. However, through computation, an admin can determine how much space the platform cache org partition requires and allocate the space manually. For information, see Allocate Space to the Platform Cache Org Partition.

Product Limits

Salesforce sets a character limit of 100 to the ExternalId custom field.

Salesforce sets a transaction limit of 216,000 per hour.

If you anticipate exceeding this limit, contact Salesforce.

To contact Salesforce, log a case, and provide this information:

• The production or sandbox Organization ID. To find the ID, from Setup, in the Quick Find box, enter Company Information, and then select Company Information.
• Your requested limit.
• A business reason for the limit increase.

Language Support for Safety Cloud Packages

Supported languages for Safety Cloud packages are English, French (France and Canada), German, Español, and Spanish (Mexico).

To provide the Safety Cloud solutions in another language, use Translation Workbench. We don’t support right-to-left languages.

Considerations for the Safety Cloud Template Package

Safety Cloud Templates rely on the Safety Cloud package for many key functions. Because the Safety Cloud Template package is Unlocked, you can change metadata, code, and configuration within the package. If you do change the Safety Cloud Template package, test your changes thoroughly in a sandbox with Safety Cloud before promoting them to production.

Changing the metadata or code in the Safety Cloud Template results in a private version of the Safety Cloud Template and risks not being included in future enhancements of Safety Cloud. Instead of changing Safety Cloud Template code or metadata directly, we recommend that you make a copy of the code and metadata and selectively override the Safety Cloud Template package with your implementations. When Salesforce Engineering releases a new version of the Safety Cloud Template, test and reimplement your overrides as part of a manual upgrade operation. If you modify the Safety Cloud Template package in any way, Salesforce can’t guarantee that we won’t introduce breaking changes into the package.

For information about unlocked packages, see Build Your First Unlocked Package