You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Home > moovs > The Importance of a moov Configuration's Status
The Importance of a moov Configuration's Status
print icon

When you implement a new moov configuration, one of the choices you make is the status of the configuration. Setting a particular status could have major implications in how the moov executes. This article will describe the available status choices and how they can impact a moov execution.

 

When you create a new moov configuration (or edit an existing one), you will see the following UI where you can set the status.

 

 

 

 

The available status choices include:

Status Description
Draft the moov configuration is still being configured and is not ready for execution
Testing the moov configuration is in a testing process with the third party you're exchanging data with
Active the moov configuration is actively processing in a "production" mode
Inactive the moov configuration is not expected to execute any longer (detamoov will not execute this moov configuration even if data is received for it)

 

It's important to set the proper status and know you can change it at any point. In speaking to many third party vendors that detamoov integrates with, a testing process is typical when configuring a new integration. This is why the Test moov configuration status was designed to not only easily show you which configurations you're testing, but also because of the impact being in a test mode can have. 

 

The following steps of a moov can be impacted based on the moov configuration status:

 

1. File naming
 

Certain third parties that detamoov interacts with require a different file name for test files versus production files. Therefore, if you set a moov configuration to be in a test status, the test file naming rules will be utilized. Some providers who have differences in their file names for test vs. production files include:

  • Empower
  • John Hancock
  • Voya
  • And more...

 

Naming rule used in production:

 

Naming rule using in testing:

 

2. SFTP Delivery
 

Just like file naming can be impacted by moov configuration status, SFTP delivery may be impacted as well. Some third parties designate different folders on their SFTP site to utilize when sending test versus production files. If a provider you work with has different "production" and "test" folders on their SFTP site, you can easily configure this.

 

 

So there you have it, the moov configuration status can have an impact in how detamoov executes so be sure to set the correct status. And remember, you can change the status at any point in time in the future.

scroll to top icon