Neptune DXP Documentation
Neptune DXP - Open Edition · 25.0 MTS

Application Settings

There are the following tabs under Application Settings:

  • General

  • Properties

  • Roles

  • Agentic Apps

General

Application

Name of current application.

Description

Brief description about the app.

For Agentic Apps in a launchpad, the agent also uses this description to decide which app to open for a user’s request, so keep it clear and specific.
Title

Replaced the application’s name with the provided title. This change can be seen in the browser’s tab when you select Run.

Type

Select the type of application such as, Application, Adaptive Template, Launchpad, Building Block and Custom Component.

Package

Assign application to specific Development Package

Enable Anonymous Access to App

If enabled, you can allow users to access the app without any authentication measures.

This feature is only visible when your current license allows it. By enabling this, an endpoint will be created so the app can be accessed via /public/app/<name>.

Agentic Apps

Use these setting to control Agentic Apps for the app and which components the agent may use. For what Agentic Apps does, see Agentic Apps.

Disable Agentic Apps

Turned on by default. Turn it off to stop the agent interacting with the app. To use Agentic Apps in a standalone app, also add a Chatbox and assign an agent to it. The agent can be a normal agent or an Agentic Apps agent; if no agent is assigned, no chat panel appears. On a launchpad, the launchpad provides the agent.

Enable WebMCP

Exposes the app’s Agentic Apps tools, including custom tools, over the Model Context Protocol.

WebMCP for Agentic Apps is available as a beta feature. As the tool continues to develop, you may notice updates and improvements over time.

When the app runs inside a launchpad, the launchpad WebMCP setting takes precedence over this setting.

Properties

Open UI5 Version

Applies a specific UI5 version.

Theme

Applies theme over the application. This includes existing themes or Imported Themes.

Global Style

Select a defined global style to apply for an application.

Load code from launchpads and Load code from applications

This feature serves the purpose of exclusively loading the code, enabling autocompletion within the the preview App Designer (scripts, CSS and header). Its primary function is to provide convenient code suggestions while writing scripts in an app, particularly when working with a launchpad. Additionally, it can be beneficial when embedding one app within another, as it facilitates autocompletion from the parent app.

Tab width

Adjusts the tab width when formatting code.

Print width

The formatter will make line breaks after the given number of characters.

Compiler Target

The compiler target in TypeScript that determines the version of ECMAScript (JavaScript) that the compiler should generate as output.

Generate application version on activate

If activated, then you will be able to save versions of your application. You can select the number of versions to keep in history whenever you save and activate.

Disable Application

Disables the application and any attempt to reach it will result in a 404 error.

Run only in Launchpad

Disables the application allowing it only to run from a launchpad and any attempt to reach it will result in a 404 error.

Minify Source Code

Minifies all source code. Minifying source code in JavaScript reduces its file size by removing unnecessary characters and whitespace, optimizing performance and improving website loading times.

Enable File Storage

Enabling this option allows the application’s JSON definition to be automatically written to a file named your-app.json . This ensures that the JSON definition of the application is easily accessible and can be utilized as needed.

Roles

In Roles you can add roles to your application for security purposes.

Agentic Apps

Denylist

Components the agent must not interact with, so the user handles them. To add a component, open the Objects dialog, then search for the component or open it through the dependency tree of nested components. Components are identified by their App Designer IDs, so a container and its nested elements each have their own ID. For example, a SimpleForm contains nested components such as lbloSimpleFormORDERNUMBER and inoSimpleFormOrderNumber. Add the ID of the component you want to exclude.

Related topics