Commonly used terms

Last modified by superadmin on 24.01.2017

ClusterXima® 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 server and frontend server, Server communications overview
Xima® Formcycle DesignerForm editor for creating forms.Xima® Formcycle Designer
Xima® FormcloudXima® Formcycle on a cloud, allowing you to edit and manage your forms online. 
FormA form is a web page where users can enter and submit data, such as a contact form, order form, or support request form.Forms, Form settings
frontend serverA 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 server and frontend server, Server communications overview
InboxContains 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
LDAPXima® Formcycle allows you to create and manage users directly, but users can also be managed by connection to an LDAP (MS active directory).LDAP
ClientClients 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 serverA 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 serverand frontend server, Server communications overview
NTLMNTLM 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 
VariableSometimes 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.Placeholder, Alias
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 inboxAn inbox containing form records of different forms. Data columns cannot be customized.General inbox, Inbox
Form specific inboxAn 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
RoleA role is assigned to each user, controlling the permissions of that user.Roles
ServletServlets are run on the server when requested by the client, and can return data from the system or make changes to the system.IPluginServletAction, Queries, Working with form URLs
StateWhen 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.
Workflow processingAfter 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.Inbox, Workflow processing.
Created by superadmin on 13.10.2015
Translated into en by superadmin on 18.05.2016
Copyright 2000-2018