Peakon Instances for Testing
Peakon has 2 different environments available to customers:
- Implementation (IMPL)
- Production.
Implementation and production environments are completely separate, and do not share any resources or services. Implementation and production environments are identical in security measures and protocol.
Implementation accounts only have default configurations and therefore do not mirror any of the configurations in your production environment. You can manually configure the implementation account to recreate any integration-related issues you may face in your production instance.
When you implement the Workday HCM integration for the first time, connect your Workday production tenant to your Peakon production tenant. When you switch an existing Peakon account to the Workday HCM integration, connect your Workday production tenant to a Peakon implementation account first to test the integration before cutover. We don't recommend connecting Peakon to a Workday sandbox tenant, because Workday refreshes sandbox tenants from production every week.
If you need an implementation environment for testing purposes, work with your Named Support Contact (NSC) to submit a Customer Care request via Community with the following path: .
Customers may sometimes receive a demo account during the procurement process. Demo accounts give you an opportunity to see features using fictitious data. Demo environments do not have the same security measures and protocols as production and implementation environments, as such you must not load real or testing data into the demo environment. You should only use an implementation environment for any testing purposes.