Search Results

Normal users Only active users are paid for, down to a minimum of 5. A service can be configured in order to automatically deactivate inactive users. Anonymous users Anonymous users are paid for per active interface (access to a solution): All users usi...

Usage Ever stood with a large mount of unstructured of documents, wanting to convert them into structured database. With our AI Filemorph that is actually possible: You upload large amounts of documents, that are converted and linked to database records. Th...

What it is Example: A hr-management system is used to hire new employees that have to be registered with information such as name and email address. During this registration mistakes can happen where an employee is registered multiple times, creating dupli...

What it is Example: A hr-management system is used to show information on employees who are assigned to projects. These employees are either currently working on a project or between projects. Or they might be in the process of being hired and would theref...

Usage In TS it is possible to configure very advanced and dynamic input form behavior. The goal is to minimize the effort required to enter data, and at the same time maximize data quality. In case you need step-by-step questionnaires or wizards, we recommen...

Create a new solution and test it Make sure that solution contains an field of the Email type Create an interface [solution] > Advanced > Interfaces ... ADD Interface Active: X Unique name: [unique name across all interfaces] Anonoumou...

Create a new solution and test it Create an interface [solution] > Advanced > Interfaces ... ADD Interface Active: X Unique name: [unique name across all interfaces] Anonoumous user Active: X Insert items: X Use questionaire style interf...

Status after first update: Designer > [Solution] > Advanced > [Interface] Update the value "Status after update" Status after questionaire completion: Designer > [Solution] > Advanced > Functionality - Questionaire - Messages Update the value "Final...

Interfaces allow access to the system with preset values for Wrapper Stylesheet Template Language User context When accessing the interface the user is redireceted to the main page with the correct parameters set. In case the user context is active, ...

Interfaces are access points for external users (someone using the system without a login). For a more detailed description, please read: Understanding interfaces Basic configuration An interface has the following configuration options Interface URL U...

Usages Questionnaires are used for data collection for external parties. TS questionnaires can be used in two modes A public page everyone with a link can access Specific requests sent to a user to add information to a record Access are given by addin...

Data exports can be done in a blink of an eye In list mode of an solution click the XL sheet icon. Choose relevant export options Note that the export provided respects currect filters, sort order and grouping. The export options are as follows All ...

Data inserts and updates are carried out by a system user, that has exactly the same priviledges as a normal user. If field permissions are missing field value changes will be ignored, and if restriction is not met the operation will fail as normally. Finally ...

In order to create a complex questionaire you first choose between copying a solution and creating from scratch. We strongly reccomend the copying if you are unfamiliar with designing solutions. Creating from scratch Steps to create a questionaire includes ...

Field types Complex questionnaires contain fields for sending the questionnaire and answering questions. Depending on how the questionnaire is distributed to the users, you will also need contact information such as name and email. Questions and scores For...

Fields in solution Normal questions "Complex question" Sum of scores in normal questions "Calc: Complex question (sum)" Setting up multiple response for a question "Multiline: Location editor" "Multiline: Complex question" Contact informati...

Each record in Tempus Serva has a status assigned. A status signifies the state of the record, in regard to maturity, responsibility and degree of completion etc., but also serves as an anchor for automated actions and permission for users. A default status ...

Status actions are addon functionality bound to a certain status. When an item fullfills certain criterions, the action is fired resulting in Sending of an email (Notification) Export and routing of documents (Export) Creation of tasks (Task create) C...

The actions are fired when a certain condition is meet AND the item is in the parent status An item enters the status An item leaves the status Time has passed while an item was in this status Timed actions The time specified is relative to a value of...

Status dependencies ensure that a certain status can assigned, after certain criterions are met. Example: Status "Pririoty handling" dependency: Customer type = "GOLD"