Application Settings

Updated 2 months ago by Stephanie Krenz

Note
Every activation and deactivation of these switches available here is logged in the Activity Log.

The item E-Mail Configuration (SMTP) is available with version 1.12 and higher

Click on Settings at the top and then on Application Settings on the left to change the settings.

All available settings in the Application Settings are explained below:

  1. E-Mail Configuration (SMTP) -> Available with version 1.12 and higher
  • Here you can set whether the users should be notified by mail for Analytic Run updates
  • Enter the mail server and port here
  • Select the Connection Security and enter a user with password
  • In order for users to receive notifications, further settings are required from the users themselves (you can find all the information in this article)
  1. Activity Logging
  • Active -> The activation of this setting is recorded in the Activity Log and the Activity Log button in the settings is visible
  • Inactive -> The deactivation of this setting is recorded in the Activity Log and the Activity Log button in the settings is hidden
  1. Who can see Activities
  • Active -> dab Nexus users have the option of displaying the Activities next to an element (e.g. a Workspace) via the three dots
  • Inactive -> dab Nexus users have no option to display the Activities next to an element, the button is completely hidden
  1. Which Activities are logged
  • Here you can set separately for each element whether changes should be logged in the activity log or not
    • Active (blue) -> All changes to an element of this type are recorded
    • Inactive (grey) -> No changes to an element of this type are recorded
  1. Save Settings -> Save the adjustments

Enable Primary Key Override

Note
This option is available from version 1.13.1.
  1. Open Settings > Activity Settings

If this option is activated, a new column with the name NEXUS_ID is added to each extracted table, which serves as the primary key and bypasses the system's own primary key fields.

Hint
Activating the option here alone does not cause the NEXUS_ID column to be created. The user still has to activate the setting in the task.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)