Naming conventions for application items

In projects implemented in Eximee Designer, using consistent naming conventions for application elements is crucial for maintaining order, clarity, and effective team collaboration.

Well-chosen names make it easier to:

• quick searching and filtering of components in the repository,
• recognizing the function and purpose of a given element without having to open it,
• avoiding name conflicts and accidental overwriting of artifacts,
• managing large sets of forms, processes, scripts, etc., especially in environments with multiple applications and teams.

The table below presents the recommended naming conventions for all main types of application elements in Eximee. They follow best practices used in production projects and help maintain order in scalable solutions.

Names should normally be created in English. The exception is when the form name has been predefined in Polish.

Table of naming conventions for Eximee application elements

Element type	Name format	Example
Application	prefix_app	kontoJunior_app, 800plus_app
Form	prefixName	kontoJuniorStart, kontoJuniorForm, kontoJuniorAcceptance
Other elements (e.g. scripts)	prefixName	kontoJuniorCheckAmount
Processes	prefixNameProcess	kontoJuniorProcess, kontoJuniorSendNotificationProcess

General rules

• prefix - the business name of the given project, placed at the beginning of each application element in camelCase format
• Name - the name of the given element in camelCase format

For forms and applications, it should be taken into account that the form/application name later appears, among other places, in the URL.