Testing eQuest configuration
Summary:
Hello,
We would like to proceed with testing eQuest in our TEST environment. Following the recent P2T refresh, the eQuest configuration in TEST is now an exact copy of the configuration in PROD.
Based on our understanding, eQuest is currently inactive in TEST because a new reference key is required. Before we ask the client to contact eQuest and request a new reference key on our behalf, we would like to confirm the recommended approach:
A. Should we edit the existing eQuest configuration (or delete and recreate it, if deletion is supported)?
B. Should we create a new eQuest configuration by selecting Add Job Distribution and complete the setup using the new reference key?
0