Environment Confirmations have been replaced by Real Data Permissions and should no longer be used.
For more information, see Setup, Real Data Permissions.
Environment Confirmations add an additional level of security to actions and processes to prevent test data from being accidentally interpreted as real data.
These additional secured actions and processes can only be executed if the current environment in which the action is executed is already confirmed or will be confirmed.
Example
Environment Confirmations are used, for example, by the NCCR Cash Register from the cash register posting process. This is to prevent test data from being accidentally forwarded to the external service of fiskaltrust as real data.
This case can occur, for example, especially when deploying via On-Premises, if a test or development database (or a test company) has been created based on the real data and is not defined as a sandbox environment. Without another level of security, cash register postings from this test system would also be forwarded to the fiskaltrust service as real data.
By using Environment Confirmations, the cash register posting recognizes that the test environment has not yet been confirmed and the user can now respond to the warning.
Testing and Confirmation
An environment is defined by the company name, the database name and the server name.
The action or process may be executed if the current environment is found in the environment confirmations and the setting entered in the Confirmed as field matches the setting of the current environment.
Environments set as Production can be confirmed as production environment or as sandbox environment.
If you confirm the environment as a production environment, all information will be interpreted as real data.
If you confirm the environment as a sandbox environment, all information will be interpreted as test data and the action or process may not be executed until the current environment is also set as a sandbox.
When deploying via On-Premises, test and development databases should or must be confirmed as a sandboxed environment.
Warning
Confirm your current environment only if you are absolutely sure.
Once the environment is confirmed, the action or process is confirmed for all users. While environments that have already been confirmed can be deleted at any time, this will not undo any action that has already been performed.
Environments set as Sandbox cannot be confirmed as production environment.
Confirmation as a sandbox environment is still necessary for security reasons.
Change a confirmation
All confirmed environments of an extension can be viewed from the extension's setup page via the System area.
An environment confirmation cannot be changed directly, but must be deleted first.
As soon as a secured action or process in the environment is executed, the environment must be reconfirmed.
Tip
The current environment can also be confirmed immediately using the Confirm Current Environment action.
Fields
Company Name
Specifies the company name of the confirmed environment.
Database Name
Specifies the database name of the confirmed environment.
Server Name
Specifies the server name of the confirmed environment.
Current Environment
Specifies whether the confirmed environment is the current environment.
Confirmed as
Specifies whether the environment was confirmed as a production environment (Real Data) or as a sandbox environment (Test Data).
Date Confirmed
Specifies the date when the environment was confirmed.
Time Confirmed
Specifies what time the environment was confirmed.
Confirmed By
Specifies the user ID of the person who confirmed this environment.
Actions
Confirm Current Environment
Confirms the current environment as a production environment or as a sandbox environment.
Environment Confirmations (Obsolete)
