| Term | Description | Links |
|---|
| Alias | When submitting a form, the form data is send as key-value pairs <name>-<value>. Form element names are limited to certain characters and may not contain any special characters such as spaces or accented letters. Sometimes you may need special characters, for example when forwarding data to a web service that expects a certain name. The alias does not have any restrictions on which characters are allowed. If you want to change the alias of a form element, select the element in the Xima® Formcycle Designer and set the alias on the basic properties panel. | Base properties |
| Cluster | Xima® Formcycle can be run on multiple servers, called master servers and frontend servers. When one server fails, another server can take over and replace that server. All servers connected to each other this way are called a cluster. | Cluster, Master and frontend server, Server communications overview |
| Xima® Formcycle Designer | Form editor for creating forms. | Xima® Formcycle Designer |
| Xima® Formcloud | Xima® Formcycle on a cloud, allowing you to edit and manage your forms online. | |
| Form | A form is a web page where users can enter and submit data, such as a contact form, order form, or support request form. | My forms, Form settings |
| Frontend server | A frontend server provides users with access to forms and accepts or rejects forms that have been submitted. It does not handle management or administrative services, such as editing forms or viewing forms in the inbox. | Master and frontend server, Server communications overview |
| Inbox | Contains all forms that have been submitted, called form records. There are form specific inboxes containing only form records of a certain form, and general inboxes containing forms records of different forms. | Inbox |
| LDAP | Xima® Formcycle allows you to create and manage users directly, but users can also be managed by connection to an LDAP (MS active directory). | LDAP |
| Client | Clients are the top level instance with their own forms, users, user groups, inboxes etc. Different divisions of a company can use the same Xima® Formcycle system with a different client for each division. | Client |
| Master server | A master server can be used as a stand-alone and provides all of Xima® Formcycle's functionality. When frontend servers are used, the master server is also responsible for managing the connection to each frontend server. | Master and frontend server, server communications overview |
| NTLM | NTLM can be used for authenticating users of a form. This is commonly used for internal forms of a company to identify the employees using the form, allowing the form to access the user's data via NTML. | NTLM |
| Variable | Sometimes it becomes necessary to use the value of certain form fields within Xima® Formcycle. For example, you might want to send a mail to the address the user entered in the form. Variables can be used within fields supporting them. They will be replaced by the corresponding value by the system. | Variables |
| Plugin (client) | Plugins extend the Xima® Formcycle by providing custom functionality. Client plugins are available only to the client who uploaded them. Plugins are written in Java. | Client plugin |
| Plugin (system) | Plugins extend the Xima® Formcycle by providing custom functionality. System plugins are available only to all clients. Plugins are written in Java. | System plugins |
| General inbox | An inbox containing form records of different forms. Data columns cannot be customized. | General inbox, inbox configuration |
| Form specific inbox | An inbox containing only form records of a specific form. Data columns can be customized. This allows you to view certain form fields without having to open the form. | Form specific inbox, inbox settings |
| Role | A role is assigned to each user, controlling the permissions of that user. | Roles |
| Servlet | Servlets are run on the server when requested by the client, and can return data from the system or make changes to the system. | Data sources, database queries, LDAP queries, URLs |
| State | When a form is submitted, is in the special system state Received. Other custom states can be defined by adding them in the workflow processing. For example, a job interview form might have the two additional states Accepted and Rejected. | State (workflow) |
| Workflow processing | After a form has been submitted, workflow processing starts. Depending on the form's state, certain actions will be executed, such as generating PDF files, sending mails etc. State transitions can be performed manually in the inbox, or by the system. | Workflow processing |
| Repeatable element | A form element that was marked as repeatable. When a user fills out the form, they can create one or multiple copies of a repeatable element by pressing on the add  and delete  buttons. This is used, for example, to allow the user to enter multiple email addresses of phone numbers. | Base settings, jQuery.fn.dynamic |
| Template (form element) | A template for a preconfigured form element that is available in the Xima® Formcycle Designer. It is created by selecting an existing form element and saving it as a template. This template is then available for all forms of the same client. The template is available in the elements panel to the left of the Xima® Formcycle Designer. It can be added to the form like other standard element such as input fields or containers. | Form template |
| Template (form) | A template for a preconfigured form that is available on the form overview page in the backend. An existing form can be saved as a template. It is then available to all users of the same client. This includes the form itself as well as form files (uploaded files), the workflow configuration and other settings. When you create a new form, you can select a template you want to be used. | Save as template, Creating forms |
| Template (plugin) | A form template that is provided by a certain type of plugin type. This works similarly to form templates. The template itself is provided by a plugin and cannot be created by a user directly. In contrast to form templates, a template plugin can be installed as a system plugin to make the form template available to all clients. | client plugin |
| Widget (form element) | A custom form element provided by a certain type of plugin. When such a plugin is installed, new form elements become available in the elements panel to the left of the Xima® Formcycle Designer. These widget elements can ship their own custom JavaScript and Css. Widgets range from simple, custom input fields to more complex fields for handwritten signatures or captchas. | Xima® Formcycle Designer, client plugin |
