The Recruitment Marketing (RM) Dev Environment, also referred to as Talemetry (TL) Dev, is a test environment used for activities such as:
- Initial implementation of Recruitment Marketing (RM) implementation
- Testing integrations
- Testing Career Website (CWS) changes
Audience
All users
Q&A
Q. What is the Recruitment Marketing (RM) Dev Environment?
A. When you purchase RM, the RM Dev environment is used during your implementation to import your ATS data (typically from your ATS Staging, Test, or User Acceptance Test environment) and configure your RM instance before moving to production. After the implementation, RM Dev is where you can test various integrations or CWS changes.
Q. How do I access RM Dev?
A. RM Dev is accessed using the same URL as your production environment. The difference will be the email address used to log in. If supported by your domain, the Employ implementations team will set up a separate email address (youremail+dev@company.com). NOTE: Any users added after your implementation should also be added using this email format.
If a separate email is not supported, the same email address will be used for both your production and dev environments. You will be prompted to choose the environment at the time of login.
Q. When should I use RM Dev?
A. RM Dev can and should be used for many things! The primary use cases after your initial implementation would be to test integrations or CWS changes before applying them in your production environment.
However, there are some limitations to be aware of:
- You will not be able to test auto-broadcast with real job boards.
- If you are testing campaigns, real messages will be sent. Due to how your data is imported during your implementation, the candidates in TL Dev are typically real people with real emails. This also impacts the ability to fully implement and test features, such as Auto Talent Rediscovery.
- Changes made within RM Dev will not automatically be applied to your production environment.
- RM Dev is not designed to evaluate data-driven information.
- There is no RM Dev environment refresh.
Q. Is RM Dev connected to my ATS?
A. Yes, RM Dev can be connected to your ATS. After your implementation, your RM Dev instance will be connected to either your JV ATS staging environment or the staging/dev environment of the ATS you currently use.