General tab

In the General tab in Custom Settings, you make settings that affect only your system. Here, you can customize the system to your needs.

Development

npm Installation Path

Path to all npm modules saved in your server. This is a required field for the installation of npm modules using the npm Modules cockpit tool.

npm modules are installed at this location.

The path can be specified relative to the Neptune DXP - Open Edition installation directory or as an absolute path.

Relative paths need to start with the . or .. locator to denote the installation directory or its parent directory respectively, for example, ./customnpm.

Both relative and absolute paths should be specified using forward slashes on all operating systems. Example: /home/somewhere/customnpm (Linux, macOS) or C:/somewhere/customnpm (Windows).

After setting the path and saving the settings, the specified directory is created if it does not exist, and is initialized for the installation of npm packages.

Check that the directory exists at the expected location in the file system after saving the settings before installing npm modules.
Google API Key

Enter your Google API key for development reasons.

Deployment

Here, you can enable the deployment method for the deployment tool and define who has to sign a step during the deployment process.

Enable Two Step Deployment

Select to enable two-step verification for the deployment process.

Enable Three Step Deployment

Select to enable three-step verification for the deployment process.

Sign Deployment Transfer

Select to enable the approval of deployment package transfers. When you select this option, you can choose from the following options:

  • Sign with Source Server: Once a deployment is created and approved, and the transfer action is initiated, the system will require the user to authenticate by signing the transfer with the credentials of the source system (the system where the transfer starts). This process is configured to use the local user credentials for authentication.

  • Sign with Target Server(s): Once a deployment is created and approved, and the transfer action is initiated, the system will require the user to authenticate by signing the transfer with the credentials of the target server(s) (the systems where the transfer is being sent). This process is configured to use the local user credentials for authentication.

Sign Deployment Approval

Select to enable the deployment package approval.

Enhancements

User Management

Add an App Designer application that can be accessed at User > Select a user > Custom. This application will be visible to all users.

Language

Additional Languages - Comma delimited list with isocode:name (e.g. EN:English, NO:Norwegian)

Enter desired languages to activate them in your Cockpit.

External User Activation

Activation Code Email

Add a matching email template to send the activation code for registering users.

Use complex activation code

Select or clear, as necessary.

Minimum Code Length

Select the + and - buttons to set the minimum activation code length.

Maximum Code Length

Select the + and - buttons to set the maximum activation code length.

Next steps

Related Topics