Testing an Activation Platform Package

Test an activation platform package by installing it either in an Enterprise or Developer Edition org that has a provisioned Data 360 license. For more rapid testing and inspection of file outputs as you develop your app, use a Dev org to trigger manual activation publish. When testing your activation platform app in an Enterprise org, activation files are published every 24 hours if the activation output is grouped by user identifiers (PER_USER). If the activation output is grouped by segments (PER_SEGMENT), the refresh schedule is tied to the segment publish schedule.

Required Editions

Available in: Lightning Experience
  • Use a Package Subscriber Org for Testing
    When using a Developer edition org in the context of a packaged app, Salesforce uses the terms Packaging org and Package Subscriber org. The Packaging org is where the package is created. The Package Subscriber org is an org that has installed a package from a Packaging org. To speed up testing, developers can now install their package in another Dev org and manually trigger an activation publish.
  • Use a Package Subscriber Org to Trigger a Publish
    To speed up testing, use the package subscriber org and manually trigger an activation publish to inspect and validate the output files.