Naming conventions for application elements

In projects carried out 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:

• quickly search and filter components in the repository,

• recognize the function and purpose of a given element without the need to open it,

• avoid name conflicts and accidental overwriting of artifacts,

• manage 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 are consistent with best practices used in production projects and enable maintaining order in scalable solutions.

All names are given in English — in the case of top-down decisions regarding a form name, Polish is used.

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, keep in mind that the form/application name later appears, among other places, in the URL.