TS NoCode wiki - User contributions [en]

Developing codeunits

2025-04-01T13:36:39Z

Tvi: /* Using the provided Dev-image */

== Steps for creating a new codeunit ==

# Create a new Java project in your favorite IDE
# Import the p2eShared.jar in the project
# Create a new class:
## The abstract parts are found in: dk.p2e.blanket.codeunit
## Implement all abstract methods
## Code the method bodies (normally "execute")
# Compile and build
# Deploy to webservser: [Application]\WEB-INF\lib

After first test of the codeunit a server reboot is needed for each redeployment, as there is no way of removing the loaded classes from memory.

== Error handling ==

Exceptions are handled by themselves using the errorRegistration(Exception e) method.

In case the errors are not caught by the codeunit itself, the generic error handler takes over
# Logs the error in the eventlog
# Returns a standard error page to the user

Other debugging options include log4j and specialized TempusServa '''Systemout.print''' functions (yes, the class name is "Systemout").<syntaxhighlight lang="java">
Systemout.println("hello world");
Systemout.printSql(myStatment);
</syntaxhighlight>

== Configuration / parameters ==

Parameters are delivered through the method call, packed in a nice <String> Hashtable for easy access.

Please note that values are sent as-is, so make sure to escape values before DB operations using <syntaxhighlight lang="java">
DbConnection.escapeSql(String s);
</syntaxhighlight>Configurations can be stored using the getConfiguration methods of the command object. These values can be editedthrough the designer, depending on the Codeunit type

* System configurations: Designer > Modules > Static content
* Solution configurations: Designer > [Solution] > Advanced > Configurations

Value names will be prefixed with Class simple name - example + "."

com'''.tsnocode.MyExampleCodeunit.'''myParameter

== Variables ==

Variables can have a scope of either
* Request
* User session
* Application

For permanent variables user server configurations.

=== Request variables ===
Request scope variables should be stored in the Hashtable '''sharedObjects''' in the '''Command''' object.

Note that the HTTP request parameters are stored in '''requestParameters'''.

=== User session variables ===
Acces the '''sessionValues''' attribute in the '''Security''' object
* boolean hasSessionValue(String name)
* void setSessionValue(String name, boolean value)
* int getSessionInteger(String name, int defaultValue)
* int getSessionInteger(String name)
* void setSessionInteger(String name, int value)
* String getSessionString(String name, String defaultValue)
* String getSessionString(String name)
* void setSessionString(String name, String value)

All variables her are serilizable and will survive server restarts.

Certain special user properties can also be accessed from the '''Security''' object
* boolean hasProperty(String name)
* String getProperty(String name)

Finally it is possible to store objects in the Hashtable '''sessionObjects''' in the '''Security''' object, but be aware that data are transient and '''will not survive server restarts'''.

=== Application variables ===
Application variables are persistent and accessed through the '''Command''' object

Their storage position depends on wether theres is a solution context or not:
* Solution present: Variables are saved to the solution '''Configurations'''
* None (SagID = 0): Variables are saved to the '''Static content'''

Access the the variables goes through get methods with default values.
* String getConfigurationValue(String name)
* String getConfigurationValue(String name, String defaultValue)

If the variable does not exist it will be created, and set to the default value (if present).

Note that it is possible to force the use of Statis content by explicitly calling
* String getSystemConfigurationValue(String name)
* String getSystemConfigurationValue(String name, String defaultValue)

== Different codeunit types ==

Please read the: [[Codeunit reference]]

Most likely you will need to create a [[Codeunit/Formevents]] that will allow specific changes for a solution, during views, updates or exports.

Most interactions wil require interaction with the following objects
* Security
* Command
* DbConnection
* EventHandler

== Using the provided Dev-image ==
We provide a ready-to-go image of a virtual machine, running Debian 12, for [https://www.virtualbox.org/wiki/Downloads VirtualBox].

The machine is setup with all the required software and helper scripts, to enable development of custom codeunits.

=== Getting the image running ===
The image is build for VirtualBox, so install that.

Once you have the image downloaded, start the import wizard in VirtualBox (ctrl + i) and follow it.

Now you should be able to boot the VM. The username and password for the user is noted in the comment on the VM.

The machine includes the following programs:

* Firefox, to access the local Tomcat server
* NetBeans 11.3, to develop codeunits
* DBeaver CE 24, to access the local DB

=== Deploying codeunits ===
To deploy you code to the local Tomcat instance do the following:

# build the project (right-click it in the project-browser on the left and select build)
# copy the generated .jar file from <code>/home/developer/NetBeansProjects/[ApplicationName]/dist</code> to <code>/mnt/sda/deploy</code>
# Clear the cache (open http://localhost:8080/app/service?CacheClear)

=== Debugging codeunits ===
Attach the NetBeans debugger to the local Tomat server:

Click "debug" in the top-left menu -> click "attach debugger" -> click "OK", the default settings should work

Add a breakpoint to you code and try to invoke it from the browser.

=== Updating the API and platform ===
To update the local environment to the latest version of the TS-API and TS Platform, open a terminal and execute the following commands.<syntaxhighlight lang="bash">
updateAPI
ts -w app upgrade-alphaapp
</syntaxhighlight>You will be prompted to input the password for the user.

User Group Membership

2025-03-24T15:47:46Z

Tvi: subgroups added

Tempus Serva uses a classic permission structure with some minor extensions

'''Users'''
* User profiles can be bound to existing AD/LDAP repositories
* Special properties on users include
** Administrator: Allow access to backend
** Data handler: Bulk upload data
** User creator

'''Membership''' is the relation between a user and a group
* Previous membership are logged in the database for forensic purposes

'''Groups''' are list of users tied to certain permissions in solutions

[[File:Overview_permissionstructure.PNG]]

== Subgroups ==
If the policy doAdvancedGroupSecurity is enabled subgroups is enabled. Eg. groups can be nested under each other.

=== Assigned Groups ===
When using subgroups with Assigned groups, the parent group gains access equal to all the subgroups.

This can be used to create a super-user group that has all other groups as subgroups, thus allowing access to the entire system, without granting the super-user group direct access.

=== Exclusive Groups ===
When using subgroups with Exclusive groups, the parent group gets access to all records tagget with the sub-groups.

This can be used to create sub-departments and having a supervisor with access across.

Dashboard diagram widget configuration

2025-03-21T15:30:18Z

Tvi: post-parsing

This information is also applicable to the field [[FieldSubselectDiagram|Visual extra: SQL: Diagram query]].

This site only describes the specifics of the diagram widgets, for general widget configuration [[Dashboard widget configuration|click here]].

This article will only cover the newest version of graphs implemented.

To enable these, toggle the [[Policy]] useGoogleChart to false and useNewChart to true.

As of writing (version 8813) these renderings are supported.

* Circle
* Doughnut
* Bar vertical (Columns)
* Bar horizontal
* Area
* Line
* Area (stacked)

== Data and Internationalization ==
An SQL Query may extract almost anything from the database.

This process ignores the security restrictions in the system, so you will have to implement them yourself.

=== Structure ===

The structure is the same for all graphs.

The first row of data will be used for headers.

The column named "Title" will be used for titles. On circular diagrams that is the labels, next to the chart, and on xy-graphs that is the labels on the x axis.

The rest of the headers will be used when hovering over the graph, to give information about the data. On xy-graphs it will also be displayed as labels.

The rest of the lines in the data will be added as datapoints in the graph.

If the datapoint is a number, the graph will auto-scale to match the data.

Strings are also supported, but the outcome is unknown.

If a datapoint is null, the graph will bridge the gap, if it is an xy-line-graph, [[FieldSubselectDiagram|see sample here]].

==== Sample pie/doughnut-graph ====
{| class="wikitable"
!Title
!TitleEnglish
!This moth
!Last month
|-
|GOOG
|Alphabet
|100.23
|25.23
|-
|TSLA
|Tesla
|10.23
|20.23
|-
|AAPL
|Apple
|50.23
|50.23
|}

==== Sample line-graph ====
{| class="wikitable"
!Title
!TitleEnglish
!Alphabet
!Tesla
!Apple
|-
|THIS
|This Month
|100.23
|10.23
|50.23
|-
|LAST
|Last month
|25.23
|20.23
|50.23
|}

==== Multiply y-axis ====
Multiple y-axis are supported as of version 9390.

To use this feature, prepend the name of the new axis to the data that should be on that axis, eg <code>y1|Apple</code>.

The default y-axis is named <code>y</code>. If no axis is specified, this will be used.

You can specify as many axis as ChartJS supports.

==== Post-Parsing data ====
There is two possible post-processing methods available. They can't be combined.

===== Transpose =====
Start the query with a line containing: <code>-- @TRANSPOSE</code>

This transposes (inverts columns and rows) the data fetched by the query, before handing it of to the chart-engine.

===== Parse =====
Start the query with a line containing: <code>-- @PARSEDATASET</code>

This expects the query to generate data in the following format (headers are optional), and removes the support for links.
{| class="wikitable"
!X-axis
!Group by
!Y-axis
|-
|2024
|Sales
|2000
|-
|2024
|Budget
|2000
|-
|2025
|Sales
|2500
|-
|2025
|Budget
|4000
|-
|2026
|Budget
|5000
|}

=== Internationalization ===
Add extra columns named "Title", followed by the name of the language, eg ''TitleEnglish''.

If a column with this name is found, it will be used, otherwise the grath will fallback to the "Title" column.

If no title-column is found, the first column will be used, for compatibility reasons.

== Adding functionality ==
It is possible to add some simple funktionality to charts, by adding links.

This feature is limited to one link pr x-axis value.

To add a link, add a column named "Link" to the query.

Whatever this column contains will become a link, that can be navigated to, when that x-value is clicked.

== Graph defaults ==
The graphs all reference the js object ''tsChartDefaultOptions'', with a couple of tweaks.

To see the defaults, open the terminal in you browser, on a page that has a graph and type the name of the object.

=== Specifik defaults ===
These can't be overwritten.

==== Area stacked ====
<syntaxhighlight lang="js">
options.scales = {
y: {
stacked: true
}
}
</syntaxhighlight>

==== Area stacked, area and line ====
<syntaxhighlight lang="js">
options.interaction = {
intersect: false,
mode: 'index',
}
</syntaxhighlight>

==== Bars ====
<syntaxhighlight lang="js">
options.indexAxis = 'y'
</syntaxhighlight>

=== Overwriting defaults ===
To overwrite the default of all charts:

Define an object in js, named tsChartOverwriteOptions.

Set it based on the documentation fund [https://www.chartjs.org/docs/3.7.1/ here].

To overwrite the options for a specific chart:

Define an object in js, named tsChartOverwriteOptions.

Add an object with an index matching the chartID.

Set it based on the documentation fund [https://www.chartjs.org/docs/3.7.1/ here].

To test your overwrite:

From the console in the browser call ''tsChartOptions'' with the only parameter being the chartID.

The return will be the final options, that will be used for that chart.

== Colors ==
The colors used, can be overwritten in the Policy ''diagramChartJSColors.''

The structure of the policy is very strict.

The policy has to be formatted as a js array of strings that represent an rgb color.

Thus: It has to start with <code>[</code> and and with <code>, ]</code>.

Each color has to be formatted as an rgb color and wrapped with <code>'</code>, and separated by <code>,</code> eg <code>'rgb(255, 255, 255)',</code> for a white color.

Command line tools

2025-03-12T10:47:21Z

Tvi:

A new version of the CLI was released on 21. december 2023.

If you are looking for the old CLI you can find the documentation [[Legacy command line tools|here]].

== Compatibility ==
The tools are compatible with the following distributions.

* Amazon Linux, version 1, 2 and 2023
* Debian, version 10, 11 and 12
*Ubuntu, version 20.04, 22.04 and 24.04
* CentOS, version 8 and 9

The script will check to see if it is running on one of these OSes and stop executing if not.

== Usage information ==
The Tempus Serva Linux script tools are open source (LGPL), and you are free to use and modify them however you see fit. The tools are defined by one python3 script and a single json file that stores the config.

As the tools themselves are subject to semiautomatic upgrades, we strongly recommend that you keep backups of files you have modified. Future versions of the scripts are not guaranteed to be compatible, with earlier versions or your own modifications.

== Installing the tool ==
To install the tools, run:
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash
This will check compatibility and install the required plugins.

To use the tool, execute <code>ts</code>.

On first execution the tool will ask a couple of questions.

If you choose to run java 8, <code>alpha</code> and <code>beta</code> is the same release, previously known as <code>nightly</code>.

===Running on CentOS 9 ===
You should run this command first.
dnf install -y wget nano

==Tool reference==
To get the full list of commands, and a description, run <code>ts --help</code>.

===quick-install===
Installs all the required software to run TS NoCode Platform, a default webapp named 'app' and a redirect from root to 'app'.

It will not ask for anything, but uses default values.

===install===
Installs all the required software to run TS NoCode Platform.

It will ask questions about optional stuff.

===install-app===
Will install a new TS NoCode Platform webapp. It ask what release to install from and what name the webapp should be deployed under, if that webapp exists it will ask if you would like to upgrade that installation instead.

===upgrade-app ===
Will upgrade an existing TS NoCode Platform webapp. It will ask what release to upgrade from and what name the webapp should be deployed under, if that webapp doesn't exist it will do nothing.

===set-admin-password===
Will set the admin password for an existing TS NoCode Platform webapp. Will ask what webapp to modify and what the password should be set to.

===install-ssl===
Will install all dependencies that are needed to setup a LetsEncrypt SSL certificate. Will ask if SSL should be setup once the install completes.

===setup-ssl===
Will ask about domain(s) and contact-email, request and install an SSL certificate and setup auto-renewal.

==Quick install==
To quick-install the tool and a webapp run this
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash && ts quick-install
If you also want to setup SSL, run this
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash && ts quick-install && ts install-ssl

==Removing the tools==
Remove the two files, eg by running:
sudo rm /usr/bin/{ts,tsconfig.json}

Main Page

2025-02-07T13:59:17Z

Tvi: Changed redirect target from Index.php?title=TS NoCode online documentation to TS NoCode online documentation

#REDIRECT [[TS NoCode online documentation]]

Main Page

2025-02-07T13:58:55Z

Tvi: Changed redirect target from Tempus Serva online documentation to Index.php?title=TS NoCode online documentation

#REDIRECT [[index.php?title=TS NoCode online documentation]]

Tempus Serva online documentation

2025-02-07T13:55:28Z

Tvi: Tvi moved page Tempus Serva online documentation to TS NoCode online documentation

#REDIRECT [[TS NoCode online documentation]]

TS NoCode online documentation

2025-02-07T13:55:28Z

Tvi: Tvi moved page Tempus Serva online documentation to TS NoCode online documentation

Welcome to the TS NoCode online documentation

On this site you will find the documentation to aid you in your development of safe and flexible solutions.

== Insight and ressources ==
{|

| '''[[Startup FAQ|Getting started]]'''
| Frequently asked questions during startup
|-

| '''[[Features|Platform features]]'''
|Modules and features in the platform
|-

| '''[[Security_setup|Security setup]]'''
| Security and compliance features in the platform
|-

| '''[[Applications|Application overview]]'''
| Overview of common uses of the platform
|-

| '''[[Guides and tutorials]]'''
| Step by step guides to developers
|-

| '''[[Related materials]]'''
| External ressources and related materials
|-

|}

== Technical reference ==
{|

| '''[[API v1.0|Java API (v1)]]'''
| Backend API for building new codeunits
|-

| '''[[JavaScript functions v1.0|JavaScript functions]]'''
| Frontend API for tweaking interface behavior
|-

| '''[[Integration/REST|REST interface]]'''
| Using built-in solution webservices
|-

| '''[[Field type reference]]'''
| Documentation for all data model building blocks (content types)
|-

| '''[[Policy reference]]'''
| Documentation for shared server configuration options
|-

| '''[[Command reference]]'''
| Overview of commands and main functionality
|-

| '''[[Codeunit reference]]'''
| Reference for common funtionality extensions
|-

| '''[[Service|Scheduled services]]'''
| Scheduled services tools
|-

| '''[[Integration|Integration services]]'''
| System integration options including REST services
|-

| '''[[Command line tools]]'''
| Tools for maintaining your UNIX platform
|-

| '''[[Server maintenence]]'''
| Tips for hosting TS servers
|-

| '''[[Known issues]]'''
| Behaviour per design, issues and system warnings

|}

== Application support ==

{|

| '''[[Basic setup]]'''
| Basic customization
|-

| '''[[TalentPiper]]'''
| Recruitment software
|-

| '''[[Whistleblower]]'''
| Multitenant solution for whistleblowing
|-

| '''[[Intect Flow]]'''
| Multicompany salary management
|-

| '''[[COMPASS]]'''
| IT governance
|-

|}

== Training and certification ==
[https://www.tempusserva.dk/training/ Training overview]

[[Course notes for today]]

[[Coding standards]]

[[Continous delivery]]

TS NoCode online documentation

2025-02-07T13:55:00Z

Tvi:

Email templates

2025-02-04T13:45:38Z

Tvi:

== Email templates ==
If you need to include graphics in the design we recommend using inline base64 images.

CSS is easily embeddable inside ''style'' tags

== Wrapping emails ==
It is possible to wrap all emails sent by the system in an [https://mjml.io/try-it-live/ MJML] or HTML wrapper.

Our implementation of the MJML engine is a bit unstable, so it is recommended to build the wrapper using MJML, then exporting the HTML version and uploading that to the platform.

Two tags are available: <code>[SUBJECT]</code> and <code>[BODY]</code>

SUBJECT will be replaced with the subject of the given email.

BODY will be replaced with the email-content of the given email.

To enable email-wrapping, set the Policy <code>defaultEmailTemplateID</code> to the ID of the template.

You can control whether the content of the email is inserted into the template before or after rendering, via the Policy <code>emailDoInsertBeforeRender</code>.

== Inserting data ==
To insert data from a record,,into an email, the following syntax is used.

<code>{FIELDNAME}</code>

=== Custom functions ===
A couple of functions are implemented, allowing minor modification of data from fields, before inserting it.

Syntax: <code>@[FUNCTION]({FIELDNAME} [PARAMETER])</code>

==== Function: FALLBACK ====
Sample: <code>@FALLBACK({NAME} Friend)</code>

If the given field does not have a value, or is not found, the PARAMETER value will be used instead.

==== Function: DATEADD ====
Sample: <code>@DATEADD({DATE} 3 weeks)</code>

If the given field is a Date, Time or DateTime field, the value is modified by the given amount (positive or negative)

Supports wrapping inside FORMAT (see below).

Supported periods: minute(s), hour(s), day(s), week(s), month(s), year(s)

==== Function: DATESUB ====
Sample: <code>@DATESUB({DATE} 3 weeks)</code>

If the given field is a Date, Time or DateTime field, the value is modified by the given amount (positive or negative)

Supports wrapping inside FORMAT (see below).

Supported periods: minute(s), hour(s), day(s), week(s), month(s), year(s)

==== Function: FORMAT ====
Sample: <code>@FORMAT({NUMBER} 000.000)</code> or <code>@FORMAT({DATE} MMM, d YYYY)</code>

Formats a given number or date to the specified format.

Number formatting uses [https://docs.oracle.com/javase/8/docs/api/java/text/DecimalFormat.html DecimalFormat] and date formatting uses [https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html SimpleDateFormat].

It is possible to wrap this function around DATESUB and DATEADD like this: <code>@FORMAT(@DATEADD({DATE} 3 weeks) MMM, d YYYY)</code>

== System templates ==
Templates can be changed in the designer: '''Modules > Configuration'''

=== Invitation template ===
HTML can be edited in '''Template.WelcomeUser''' and '''Template.WelcomeUserLink'''

Supported tags
* {APPLICATION}
* {LOGINURL}
* {USERNAME}
* {PASSWORD}

=== Password reset template ===
HTML can be edited in '''Template.PasswordReset''' and '''Template.PasswordResetLink'''

Supported tags
* {LOGINURL}
* {PASSWORD}

=== Reset via link-templates ===
Additional supported tags

* {PASSWORDLINK}
* {LINKLIFETIME}

Email templates

2025-02-04T13:45:00Z

Tvi: Info about inserting data and calling functions

== Email templates ==
If you need to include graphics in the design we recommend using inline base64 images.

CSS is easily embeddable inside ''script'' tags

== Wrapping emails ==
It is possible to wrap all emails sent by the system in an [https://mjml.io/try-it-live/ MJML] or HTML wrapper.

Our implementation of the MJML engine is a bit unstable, so it is recommended to build the wrapper using MJML, then exporting the HTML version and uploading that to the platform.

Two tags are available: <code>[SUBJECT]</code> and <code>[BODY]</code>

SUBJECT will be replaced with the subject of the given email.

BODY will be replaced with the email-content of the given email.

To enable email-wrapping, set the Policy <code>defaultEmailTemplateID</code> to the ID of the template.

You can control whether the content of the email is inserted into the template before or after rendering, via the Policy <code>emailDoInsertBeforeRender</code>.

== Inserting data ==
To insert data from a record,,into an email, the following syntax is used.

<code>{FIELDNAME}</code>

=== Custom functions ===
A couple of functions are implemented, allowing minor modification of data from fields, before inserting it.

Syntax: <code>@[FUNCTION]({FIELDNAME} [PARAMETER])</code>

==== Function: FALLBACK ====
Sample: <code>@FALLBACK({NAME} Friend)</code>

If the given field does not have a value, or is not found, the PARAMETER value will be used instead.

==== Function: DATEADD ====
Sample: <code>@DATEADD({DATE} 3 weeks)</code>

If the given field is a Date, Time or DateTime field, the value is modified by the given amount (positive or negative)

Supports wrapping inside FORMAT (see below).

Supported periods: minute(s), hour(s), day(s), week(s), month(s), year(s)

==== Function: DATESUB ====
Sample: <code>@DATESUB({DATE} 3 weeks)</code>

If the given field is a Date, Time or DateTime field, the value is modified by the given amount (positive or negative)

Supports wrapping inside FORMAT (see below).

Supported periods: minute(s), hour(s), day(s), week(s), month(s), year(s)

==== Function: FORMAT ====
Sample: <code>@FORMAT({NUMBER} 000.000)</code> or <code>@FORMAT({DATE} MMM, d YYYY)</code>

Formats a given number or date to the specified format.

Number formatting uses [https://docs.oracle.com/javase/8/docs/api/java/text/DecimalFormat.html DecimalFormat] and date formatting uses [https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html SimpleDateFormat].

It is possible to wrap this function around DATESUB and DATEADD like this: <code>@FORMAT(@DATEADD({DATE} 3 weeks) MMM, d YYYY)</code>

== System templates ==
Templates can be changed in the designer: '''Modules > Configuration'''

=== Invitation template ===
HTML can be edited in '''Template.WelcomeUser''' and '''Template.WelcomeUserLink'''

Supported tags
* {APPLICATION}
* {LOGINURL}
* {USERNAME}
* {PASSWORD}

=== Password reset template ===
HTML can be edited in '''Template.PasswordReset''' and '''Template.PasswordResetLink'''

Supported tags
* {LOGINURL}
* {PASSWORD}

=== Reset via link-templates ===
Additional supported tags

* {PASSWORDLINK}
* {LINKLIFETIME}

Email templates

2025-02-04T13:22:48Z

Tvi:

== Email templates ==
Templates can be changed in the designer:
'''Modules > Configuration'''

If you need to include graphics in the design we recommend using inline base64 images.

CSS is easily embeddable inside ''script'' tags

=== Invitation template ===
HTML can be edited in '''Template.WelcomeUser''' and '''Template.WelcomeUserLink'''

Supported tags
* {APPLICATION}
* {LOGINURL}
* {USERNAME}
* {PASSWORD}

=== Password reset template ===
HTML can be edited in '''Template.PasswordReset''' and '''Template.PasswordResetLink'''

Supported tags
* {LOGINURL}
* {PASSWORD}

=== Reset via link-templates ===
Additional supported tags

* {PASSWORDLINK}
* {LINKLIFETIME}

Embed TS in other sites

2025-01-21T14:09:21Z

Tvi: Created page with "To embed the output of a public codeunit, on another website, the following code can be used.<syntaxhighlight lang="html"> <div id="tsContent"></div> <script type="text/javascript"> $.ajax({ url: 'https://[SYSTEM-DOMAIN]/[APP-NAME]/mainpublic?command=[CODEUNIT-NAME]]', success: function(data) { $('#tsContent').html($(data).find(".mainContent").html()); }, }); </script> </syntaxhighlight>It requires jQuery to be loaded beforehand."

To embed the output of a public codeunit, on another website, the following code can be used.<syntaxhighlight lang="html">
<div id="tsContent"></div>
<script type="text/javascript">
$.ajax({
url: 'https://[SYSTEM-DOMAIN]/[APP-NAME]/mainpublic?command=[CODEUNIT-NAME]]',
success: function(data) {
$('#tsContent').html($(data).find(".mainContent").html());
},
});
</script>
</syntaxhighlight>It requires jQuery to be loaded beforehand.

Dashboard diagram widget configuration

2025-01-10T14:46:31Z

Tvi: Added functionality section

This information is also applicable to the field [[FieldSubselectDiagram|Visual extra: SQL: Diagram query]].

This site only describes the specifics of the diagram widgets, for general widget configuration [[Dashboard widget configuration|click here]].

This article will only cover the newest version of graphs implemented.

To enable these, toggle the [[Policy]] useGoogleChart to false and useNewChart to true.

As of writing (version 8813) these renderings are supported.

* Circle
* Doughnut
* Bar vertical (Columns)
* Bar horizontal
* Area
* Line
* Area (stacked)

== Data and Internationalization ==
An SQL Query may extract almost anything from the database.

This process ignores the security restrictions in the system, so you will have to implement them yourself.

=== Structure ===

The structure is the same for all graphs.

The first row of data will be used for headers.

The column named "Title" will be used for titles. On circular diagrams that is the labels, next to the chart, and on xy-graphs that is the labels on the x axis.

The rest of the headers will be used when hovering over the graph, to give information about the data. On xy-graphs it will also be displayed as labels.

The rest of the lines in the data will be added as datapoints in the graph.

If the datapoint is a number, the graph will auto-scale to match the data.

Strings are also supported, but the outcome is unknown.

If a datapoint is null, the graph will bridge the gap, if it is an xy-line-graph, [[FieldSubselectDiagram|see sample here]].

==== Sample pie/doughnut-graph ====
{| class="wikitable"
!Title
!TitleEnglish
!This moth
!Last month
|-
|GOOG
|Alphabet
|100.23
|25.23
|-
|TSLA
|Tesla
|10.23
|20.23
|-
|AAPL
|Apple
|50.23
|50.23
|}

==== Sample line-graph ====
{| class="wikitable"
!Title
!TitleEnglish
!Alphabet
!Tesla
!Apple
|-
|THIS
|This Month
|100.23
|10.23
|50.23
|-
|LAST
|Last month
|25.23
|20.23
|50.23
|}

==== Multiply y-axis ====
Multiple y-axis are supported as of version 9390.

To use this feature, prepend the name of the new axis to the data that should be on that axis, eg <code>y1|Apple</code>.

The default y-axis is named <code>y</code>. If no axis is specified, this will be used.

You can specify as many axis as ChartJS supports.

=== Internationalization ===
Add extra columns named "Title", followed by the name of the language, eg ''TitleEnglish''.

If a column with this name is found, it will be used, otherwise the grath will fallback to the "Title" column.

If no title-column is found, the first column will be used, for compatibility reasons.

== Adding functionality ==
It is possible to add some simple funktionality to charts, by adding links.

This feature is limited to one link pr x-axis value.

To add a link, add a column named "Link" to the query.

Whatever this column contains will become a link, that can be navigated to, when that x-value is clicked.

== Graph defaults ==
The graphs all reference the js object ''tsChartDefaultOptions'', with a couple of tweaks.

To see the defaults, open the terminal in you browser, on a page that has a graph and type the name of the object.

=== Specifik defaults ===
These can't be overwritten.

==== Area stacked ====
<syntaxhighlight lang="js">
options.scales = {
y: {
stacked: true
}
}
</syntaxhighlight>

==== Area stacked, area and line ====
<syntaxhighlight lang="js">
options.interaction = {
intersect: false,
mode: 'index',
}
</syntaxhighlight>

==== Bars ====
<syntaxhighlight lang="js">
options.indexAxis = 'y'
</syntaxhighlight>

=== Overwriting defaults ===
To overwrite the default of all charts:

Define an object in js, named tsChartOverwriteOptions.

Set it based on the documentation fund [https://www.chartjs.org/docs/3.7.1/ here].

To overwrite the options for a specific chart:

Define an object in js, named tsChartOverwriteOptions.

Add an object with an index matching the chartID.

Set it based on the documentation fund [https://www.chartjs.org/docs/3.7.1/ here].

To test your overwrite:

From the console in the browser call ''tsChartOptions'' with the only parameter being the chartID.

The return will be the final options, that will be used for that chart.

== Colors ==
The colors used, can be overwritten in the Policy ''diagramChartJSColors.''

The structure of the policy is very strict.

The policy has to be formatted as a js array of strings that represent an rgb color.

Thus: It has to start with <code>[</code> and and with <code>, ]</code>.

Each color has to be formatted as an rgb color and wrapped with <code>'</code>, and separated by <code>,</code> eg <code>'rgb(255, 255, 255)',</code> for a white color.

FieldNumberBoolean

2024-12-11T13:06:45Z

Tvi:

= Yes/No =
Check box. Yes/No. The values can be shown with other words or icons

Properties
* Type: [[Field type reference#Basic|Basic]]
* Groupable: Yes
* Show in lists: No
* Searchable: Yes

== User interface ==
Field in show mode

[[File:FieldNumberBoolean_show.png]]

Field in edit mode

[[File:FieldNumberBoolean_edit.png]]

User interface as displayed in picture

As of version 9943 adding a <code>TRUE value text</code>, when displaying the field as a checkbox, the value will be used as a label for the checkbox.
== Configuration ==
[[File:FieldNumberBoolean_BE.png]]

Required:
* ''As shown above''

Options:
* ''As shown above''

== Developer info ==
* FeltTypeID: 13
* SQL datatype: tinyint(1)
* Class name: FieldNumberBoolean
* Field is allowed in inline tables
* Pattern: ^(X|JA|NEJ|YES|NO|TRUE|FALSE)$

Developing codeunits

2024-12-10T15:53:21Z

Tvi: Added section about dev-vm

== Steps for creating a new codeunit ==

# Create a new Java project in your favorite IDE
# Import the p2eShared.jar in the project
# Create a new class:
## The abstract parts are found in: dk.p2e.blanket.codeunit
## Implement all abstract methods
## Code the method bodies (normally "execute")
# Compile and build
# Deploy to webservser: [Application]\WEB-INF\lib

After first test of the codeunit a server reboot is needed for each redeployment, as there is no way of removing the loaded classes from memory.

== Error handling ==

Exceptions are handled by themselves using the errorRegistration(Exception e) method.

In case the errors are not caught by the codeunit itself, the generic error handler takes over
# Logs the error in the eventlog
# Returns a standard error page to the user

Other debugging options include log4j and specialized TempusServa '''Systemout.print''' functions (yes, the class name is "Systemout").<syntaxhighlight lang="java">
Systemout.println("hello world");
Systemout.printSql(myStatment);
</syntaxhighlight>

== Configuration / parameters ==

Parameters are delivered through the method call, packed in a nice <String> Hashtable for easy access.

Please note that values are sent as-is, so make sure to escape values before DB operations using <syntaxhighlight lang="java">
DbConnection.escapeSql(String s);
</syntaxhighlight>Configurations can be stored using the getConfiguration methods of the command object. These values can be editedthrough the designer, depending on the Codeunit type

* System configurations: Designer > Modules > Static content
* Solution configurations: Designer > [Solution] > Advanced > Configurations

Value names will be prefixed with Class simple name - example + "."

com'''.tsnocode.MyExampleCodeunit.'''myParameter

== Variables ==

Variables can have a scope of either
* Request
* User session
* Application

For permanent variables user server configurations.

=== Request variables ===
Request scope variables should be stored in the Hashtable '''sharedObjects''' in the '''Command''' object.

Note that the HTTP request parameters are stored in '''requestParameters'''.

=== User session variables ===
Acces the '''sessionValues''' attribute in the '''Security''' object
* boolean hasSessionValue(String name)
* void setSessionValue(String name, boolean value)
* int getSessionInteger(String name, int defaultValue)
* int getSessionInteger(String name)
* void setSessionInteger(String name, int value)
* String getSessionString(String name, String defaultValue)
* String getSessionString(String name)
* void setSessionString(String name, String value)

All variables her are serilizable and will survive server restarts.

Certain special user properties can also be accessed from the '''Security''' object
* boolean hasProperty(String name)
* String getProperty(String name)

Finally it is possible to store objects in the Hashtable '''sessionObjects''' in the '''Security''' object, but be aware that data are transient and '''will not survive server restarts'''.

=== Application variables ===
Application variables are persistent and accessed through the '''Command''' object

Their storage position depends on wether theres is a solution context or not:
* Solution present: Variables are saved to the solution '''Configurations'''
* None (SagID = 0): Variables are saved to the '''Static content'''

Access the the variables goes through get methods with default values.
* String getConfigurationValue(String name)
* String getConfigurationValue(String name, String defaultValue)

If the variable does not exist it will be created, and set to the default value (if present).

Note that it is possible to force the use of Statis content by explicitly calling
* String getSystemConfigurationValue(String name)
* String getSystemConfigurationValue(String name, String defaultValue)

== Different codeunit types ==

Please read the: [[Codeunit reference]]

Most likely you will need to create a [[Codeunit/Formevents]] that will allow specific changes for a solution, during views, updates or exports.

Most interactions wil require interaction with the following objects
* Security
* Command
* DbConnection
* EventHandler

== Using the provided Dev-image ==
We provide a ready-to-go image of a virtual machine, running Debian 12.

The machine is setup with all the required software and helper scripts, to enable development of custom codeunits.

=== Getting the image running ===
The image is build for VirtualBox, so install that.

Once you have the image downloaded, start the import wizard in VirtualBox (ctrl + i) and follow it.

Now you should be able to boot the VM. The username and password for the user is noted in the comment on the VM.

The machine includes the following programs:

* Firefox, to access the local Tomcat server
* NetBeans 11.3, to develop codeunits
* DBeaver CE 24, to access the local DB

=== Deploying codeunits ===
To deploy you code to the local Tomcat instance do the following:

# build the project (right-click it in the project-browser on the left and select build)
# copy the generated .jar file from <code>/home/developer/NetBeansProjects/[ApplicationName]/dist</code> to <code>/mnt/sda/deploy</code>
# Clear the cache (open http://localhost:8080/app/service?CacheClear)

=== Debugging codeunits ===
Attach the NetBeans debugger to the local Tomat server:

Click "debug" in the top-left menu -> click "attach debugger" -> click "OK", the default settings should work

Add a breakpoint to you code and try to invoke it from the browser.

=== Updating the API and platform ===
To update the local environment to the latest version of the TS-API and TS Platform, open a terminal and execute the following commands.<syntaxhighlight lang="bash">
updateAPI
ts -w app upgrade-alphaapp
</syntaxhighlight>You will be prompted to input the password for the user.

FieldFilesVideos

2024-12-02T13:15:28Z

Tvi:

== Videos ==
Video gallery with thumbnails and player.

The video-player only works when Policy [[Policy|filesystemStorageActive]].

To enable down-scaling to 720p and 1080p, the storage has to be on S3, and the Encoding Lambda-function has to be enabled.

== User interface ==
Field in show mode

[[File:FieldFilesVideos show.png]]

Field in edit mode

[[File:FieldFilesVideos edit.png]]

== Configuration ==
[[File:FieldFilesPictures_BE.png]]

Required:
*''Nothing''
Options:
*Config1: Number of columns, default is 3
*Config2: Not used
*Config3: Not used
==Developer info==
*FeltTypeID: 52
*SQL datatype: int(11)
*Class name: FieldFilesVideos

FieldFilesVideos

2024-12-02T13:14:57Z

Tvi: Created page

== Videos ==
Video gallery with thumbnails and player.

The video-player only works when Policy [[Policy|filesystemStorageActive]].

To enable down-scaling to 720p and 1080p, the storage has to be on S3, and the Encoding Lambda-function has to be enabled.

== User interface ==
Field in show mode
[[File:FieldFilesVideos show.png]]

Field in edit mode

[[File:FieldFilesVideos edit.png]]

== Configuration ==
[[File:FieldFilesPictures_BE.png]]

Required:
*''Nothing''
Options:
*Config1: Number of columns, default is 3
*Config2: Not used
*Config3: Not used
==Developer info==
*FeltTypeID: 52
*SQL datatype: int(11)
*Class name: FieldFilesVideos

File:FieldFilesVideos edit.png

2024-12-02T13:13:53Z

Tvi:

Field in edit mode

File:FieldFilesVideos show.png

2024-12-02T13:13:19Z

Tvi:

Field in show-mode

File:FieldFilesPictures edit.png

2024-12-02T13:04:53Z

Tvi:

File:FieldFilesPictures show.png

2024-12-02T13:04:19Z

Tvi:

FieldFilesPictures

2024-12-02T13:03:40Z

Tvi: /* Configuration */

= Pictures =
Photo gallery with thumbnail index

Properties
* Type: [[Field type reference#Files|Files]]
* Groupable: No
* Show in lists: Yes
* Searchable: Yes

== User interface ==
Field in show mode

[[File:FieldFilesPictures_show.png]]

Field in edit mode

[[File:FieldFilesPictures_edit.png]]

User interface as displayed in picture

== Configuration ==
[[File:FieldFilesPictures_BE.png]]

Required:
* ''Nothing''

Options:
* Config1: Number of columns, default is 4
*Config2: Export width, default is 40%
*Config3: Enable lightbox, default is 0 (off)

== Developer info ==
* FeltTypeID: 51
* SQL datatype: int(11)
* Class name: FieldFilesPictures

File:FieldFilesPictures BE.png

2024-12-02T13:00:13Z

Tvi:

Field type reference

2024-12-02T12:58:38Z

Tvi: Added videos-field

TS has more than a 150 different content types. Some are based on primitive types (eg. integers) while others deliver complex functionality (eg. document librarys).

==Basic==
{|
|[[FieldNumberInteger|Integer]]
|Integer value
|-

|[[FieldNumberDecimal|Decimal]]
|Numbers with decimal comma
|-

|[[FieldNumberDecimalPercent|Percentage]]
|Percentage value (decimal)
|-

|[[FieldNumberBoolean|Yes/No]]
|Check box. Yes/No. The values can be shown with other words or icons
|-

|[[FieldSerial|Serial]]
|Unique serial number
|-

|[[FieldNumberIntegerResponse|Response]]
|Interval in questionnaire
|-

|[[FieldNumberIntegerEnumeration|Enumeration]]
|Named numbers ex. Grades
|-

|[[FieldNumberIntegerGlyph|Symbol]]
|Use icons as status flow and categories
|-

|[[FieldTimeDate|Date]]
|Date with calendar look-up
|-

|[[FieldTimeTime|Time]]
|Selector for point in time
|-

|[[FieldTimeDatetime|Datetime]]
|Date with calendar/time look-up
|-

|[[FieldTimePartMonth|Month]]
|Choice of month, including translation
|-

|[[FieldTimePartYear|Year]]
|Choice of year
|-

|[[FieldText|Text]]
|A single line of a text (ex. Name)
|-

|[[FieldTextMemo|Text mulitline]]
|Mulible line of text (ex. Adresses)
|-

|[[FieldTextMemoEditor|Notepad]]
|Editor shown in the interface
|-

|[[FieldTextHieraki|Hierachy/tree]]
|Hierarchy of values
|-

|[[FieldTextEmail|Email]]
|User email-adress
|-

|[[FieldTextURL|Website (URL)]]
|Internet adress
|-

|[[FieldUniqueIdentity|Unique key (GUID)]]
|Global Unique ID (GUID) for records, inserted automatically on record creation.
|-

|[[FieldTextSuggest|Text with lookup]]
|A single line text with look-up in exciting values
|-

|[[FieldTextPhone|Phone]]
|phone number with the possibility for look-up
|-

|[[FieldTextCPR|CPR nummer]]
|validation of control digits with the personal identification number
|-

|[[FieldTextCVR|CVR nummer]]
|CVR number with look-up in the CVR register
|-

|[[FieldContentStatic|Static content]]
|Read-out of various content
|-

|[[FieldContentButton|Static button]]
|Buttom with functionality
|-

|[[FieldContentMessage|Static message]]
|Notification on top of the page
|-

|[[FieldContentScript|Static script]]
|Execution of the code when changing other boxes
|-

|[[FieldContentFunction|Script function]]
|Execution of the code with value insertion into other fields
|-

|[[FieldTextSuggest|A line of text with lookup on existing values]]
|A line of text with lookup on existing values
|-

|[[FieldNumberIntegerPriority|Prioritize cases among themselves directly from lists]]
|Prioritize cases among themselves directly from lists
|-

|}

==Lookup==
{|
|[[FieldLookupListShare|Lookup (shared)]]
|Look-up in common list of values
|-

|[[FieldLookupListLocal|Lookup]]
|Look-up in local list of values
|-

|[[FieldLookupUser|User]]
|Users of the system. Those who are being added, can as an option be notified
|-

|[[FieldLookupGroup|Group]]
|Groups in the system. Those who are being added, can as an option be notified
|-

|[[FieldLookupListLocalNested|Dependent list (lokal)]]
|Choise based on another local list
|-

|[[FieldCategory|Dependent category]]
|Categories based on value
|-

|[[FieldLookupListLocalReplika|List replica]]
|Copy of another list (same option)
|-

|[[FieldLookupStaticCurrency|Lookup: Currency code]]
|List of currency code
|-

|[[FieldLookupUserExclusive|User Exclusive]]
|User from af certain Exclusive group
|-

|[[FieldVariant|Variant selector]]
|List of types, which are controlling which other boxes are being showed
|-

|[[FieldRemoteKey|Database: Opslag indtastning]]
|Look-up of values in foreign database
|-

|[[FieldRemoteKeyLookup|Database: Opslag liste valg]]
|Table of values from foreign
|-

|[[FieldSubselect|SQL: Subselect]]
|Enquiry in own or foreign database
|-

|[[FieldLookupListRecordKey|Lookup: Data item]]
|Create reference to item in another solution
|-

|[[FieldLookupListRecordKeyNested|Lookup: Data item nested]]
|For use with Lookup: Data item
|-

|[[FieldReplicate|Value copy]]
|Showing other values based on a key
|-

|[[FieldReplicateText|Value copy (text)]]
|Coping TEXT value based on key (searchable)
|-

|[[FieldReplicateInteger|Value copy (heltal)]]
|Coping INTEGER value based on key (searchable)
|-

|[[FieldReplicateDecimal|Value copy (decimal)]]
|Coping DECIMAL value based on key (searchable)
|-

|[[FieldReplicateBoolean|Value copy (yes/no)]]
|Coping Yes/No values based on key (searchable)
|-

|[[FieldReplicateDate|Value copy (date)]]
|Coping DATE values based on key (searchable)
|-

|[[FieldReplicateCPR|Value copy (cpr)]]
|Coping CPR number based on key (searchable)
|-

|[[FieldLookupListLocalNestedReplika|Copy field lookup options for another field in this solution]]
|Copy field lookup options for another field in this solution
|-

|[[FieldLookupUserExclusive|User from the case owner group or related to active user]]
|User from the case owner group or related to active user
|-

|}

==Lookup AJAX==
{|
|[[FieldAjaxPostalcode|Lookup: Postnr / by]]
|Autofilling of postal number and city
|-

|[[FieldAjaxUNSPSC|Lookup: UNSPSC]]
|Autofilling of the product category system of UN
|-

|[[FieldAjaxNACE|Lookup: NACE code]]
|Autofilling of NACE business codes
|-

|[[FieldAjaxCountry|Lookup: Country]]
|Autofilling of land
|-

|[[FieldAjaxDiagnose|Lookup: ICD diagnose]]
|Autofilling of ICD diagnosis code
|-

|[[FieldAjaxSksUndersoegelse|SKS Undersøgelse]]
|Dynamic lookup of values from SKS Undersøgelse
|-

|[[FieldAjaxSksDiagnose|SKS Diagnose]]
|Dynamic lookup of values from SKS Diagnose
|-

|[[FieldAjaxSksOperation|SKS Operation]]
|Dynamic lookup of values from SKS Operation
|-

|[[FieldAjaxSksBehandling|SKS Behandling]]
|Dynamic lookup of values from SKS Behandling
|-

|[[FieldAjaxSksATC|SKS ATC]]
|Dynamic lookup of values from SKS ATC
|-

|[[FieldAjaxSksUlykke|SKS Ulykke]]
|Dynamic lookup of values from SKS Ulykke
|-

|[[FieldAjaxSksSygehusafdeling|SKS Afdeling]]
|Dynamic lookup of values from SKS Afdeling
|-

|}

==Files==
{|
|[[FieldFiles|Documents]]
|Upload / download of files including versioning
|-

|[[FieldFilesPictures|Pictures]]
|Photo gallery with thumbnail index
|-

|[[FieldFilesGenerate|Document builder]]
|Build document base on solution file template
|-

|[[FieldFilesShared|Filesystem files]]
|Download of local files on the intranet
|-

|[[FieldFilesSigning|Documents with signing]]
|Documents with integration to DocuSign
|-
|[[FieldFilesVideos|Videos]]
|Video gallery with thumbnails and player
|-

|[[FieldReplicateFiles|Copy list of files based on key]]
|Copy list of files based on key
|-

|[[FieldFilesSharedFtp|FTP / download helper for structures and large files]]
|FTP / download helper for structures and large files
|-

|}

==Tabular data==
{|
|[[FieldTable|Table]]
|Table with a range of subfield
|-

|[[FieldTask|Tasklist]]
|Tasklist with export to vTodo
|-

|[[FieldContact|Contact list]]
|Contact list with export to vCard
|-

|[[FieldMail|Mailbox]]
|Inbox for each data item with many security options. Please refer to advanced configuration.
|-

|}

==Parent/child==
{|

|[[FieldSubformMaster|Parent reference]]
|Link/resume to above placed data
|-

|[[FieldSubformList|List of children]]
|List of all underplaced data
|-

|[[FieldSubformListStatus|List of children (status filter)]]
|Filtered selection of subitems
|-

|[[FieldSubformListFieldSelection|List of children (select fields)]]
|Filtered selection of fields including sortorder
|-

|[[FieldSubformListVariant|List of children (type filter)]]
|For use with 'Children type selector'
|-

|[[FieldSubformVariant|Children type selector (type filer)]]
|For use with 'List of children (type)'
|-

|[[FieldSubformLinesSum|Calc children: Sum]]
|Sum of values in underplaced data
|-

|[[FieldSubformLinesCount|Calc children: Count]]
|Sum of elements in underplaced data
|-

|[[FieldSubformLinesDistinct|Calc children: Unique]]
|Sum of unique values in underplaced data
|-

|[[FieldSubformLinesMin|Calc children: Minimum]]
|Minimum value in underplaced data
|-

|[[FieldSubformLinesMax|Calc children: Maximum]]
|Maximum value in underplaced data
|-

|[[FieldManyToMany|Many records pointing to many other records]]
|Many records pointing to many other records
|-

|[[FieldSharedParentRecord|Not written]]
|Parent reference(shared)
|-

|}

==Complex==
{|
|[[FieldMultiSelect|Checklist lookup]]
|Number of categories
|-

|[[FieldSignature|Signature]]
|Digital signature or approval
|-

|[[FieldCalcFormula|Calc: Formula]]
|Formula based on other fields
|-

|[[FieldCalcTest|Calc: Test value]]
|Test of the value of another field
|-

|[[FieldCalcConcatenate|Calc: Concatenate]]
|Making a test based on values from other fields
|-

|[[FieldJavaScripting|Calc: JavaScript]]
|Executing Javascripts client AND serverside
|-

|[[FieldCalcAge|Calc: Time lifecycle]]
|Time spent since the beginning of the case or since last correction
|-

|[[FieldCalcMeasure|Calc: Time measured]]
|Total waiting time
|-

|[[FieldCalcScore|Calc: Score interval]]
|Translation of values in intervals
|-

|[[FieldCalcTestMany|Calc: Check fields]]
|Check if a list of fields has been filled out
|-

|[[FieldComplexComment|Comments]]
|Entry of a list of comments from the users of the case
|-

|[[FieldMultiSelectSubform|Related form multiselect]]
|Filter with single parameters including standard security.
|-

|[[FieldMultiSelectSubformSQL|Related form multiselect SQL]]
|Freeform definition with multiple parameters with optional security.
|-

|[[FieldXmlData|XML data]]
|XML data in lists, table or own output format
|-

|[[FieldBarcodeAutomation|Barcode (status change)]]
|Barcode to change status automatically
|-

|[[FieldSqlData|Display grid of values from local database table]]
|Display grid of values from local database table
|-

|[[FieldCalcTestFlag|Not written]]
|Calc: Flag
|-

|[[FieldPageRequest|Output in subforms from other searches and statistics]]
|Output in subforms from other searches and statistics
|-

|[[FieldCalcMessage|Selective text composition (EXPERIMENTAL)]]
|Selective text composition (EXPERIMENTAL)
|-

|[[FieldMultiInputSubformListSQL|Fill multiple lines with numbers (decimals)]]
|Fill multiple lines with numbers (decimals)
|-

|[[FieldTokenShow|Show token to a specific interface]]
|Show token to a specific interface
|-

|[[FieldDatabaseScript|Run script]]
|Run script
|-

|}

==System==
{|
|[[FieldSystemStatus|Status]]
|The present status of the case
|-

|[[FieldSystemDatetimeCreated|Created]]
|The creation date of the case
|-

|[[FieldSystemDatetimeModified|Modified]]
|The change date of the case
|-

|[[FieldSystemDatetimeCompleted|Completed]]
|The termination date of the case
|-

|[[FieldSystemDatetimeStatusSet|Status set]]
|The last status update of the case
|-

|[[FieldSystemUserCreated|Created by]]
|User who created the case
|-

|[[FieldSystemUserModified|Modified by]]
|User who modified the case
|-

|[[FieldSystemUserCompleted|Completed by]]
|User who completed the case
|-

|[[FieldSystemUserStatusSet|Status set by]]
|User who updated the case
|-

|[[FieldSystemStatusMaster|Master status]]
|Masterstatus based on the status of the case
|-

|[[FieldSystemFormType|Solution type]]
|Selection of a solution type
|-

|[[FieldSystemExclusiveGroup|Exclusive group]]
|Selection of an Exclusive group
|-

|[[FieldSystemMemberList|Member list]]
|Users with access to the element
|-

|[[FieldSystemRevision|Not written]]
|FieldSystemRevision
|-

|[[FieldUserPermission|Not written]]
|FieldUserPermission
|-

|[[FieldSystemMemberGroupList|Groups with access to element]]
|Groups with access to element
|-

|}

==Medico==
{|
|[[FieldCalcAgeOnCPR|Age calc (date/CPR)]]
|Estimating the age of the user based on date and CPR number
|-

|[[FieldCalcBMI|Body Mass Index]]
|Estimating BMI based on height and weight
|-

|[[FieldTrainingSurvey|Activity measure]]
|Measurement of weekly activity
|-

|[[FieldGenderOnCPR|Gender (CPR)]]
|Deduction of gender based on CPR number
|-

|[[FieldCheckboxCollection|Checkbox counter]]
|Check mark of month, days or other
|-

|[[FieldCompoundMET|MET scoreboard]]
|Measurement of month, amount and size
|-

|}

==Action button==
{|
|[[FieldTokenMailto|Button: Token URL builder]]
|Building link to external users
|-

|[[FieldExportTemplate|Button: Export template]]
|Export of data to a certain template
|-

|[[FieldExecuteJavaScript|Button: Script execution]]
|Execute script on page and/or saving data
|-

|[[FieldParameterLookup|Button: Parameterized URL]]
|Look-up in foreign webbased system
|-

|[[FieldParameterListSearch|Button: Related list search]]
|Look-up in related list with parameter
|-

|[[FieldGrandChildSearch|Button: Grand child search]]
|Look-up in related data (Grand children)
|-

|[[FieldCodeunitPage|Button: Codeunit execution]]
|Execute proprietary code
|-
|[[FieldStateChanger|Button: Status changer]]
|Change state via button-click
|-

|[[FieldSessionFilterSelector|Filter selector static]]
|Set value in user session. For example for data filters.
|-

|}

==Visual extra==
{|
|[[FieldGaugePerformance|Visual: Target gauge Total]]
|Show lifetime performance speedometer
|-

|[[FieldGaugePerformanceStep|Visual: Target gauge Step]]
|Show performance speedometer for this step
|-

|[[FieldCanvasDrawing|Canvas: Freehand]]
|Draw anything in a box
|-

|[[FieldCanvasMarking|Canvas: Marking]]
|Mark a spot on an image
|-

|[[FieldSliderBarDecimal|Visual: Sliderbar]]
|Sliderbar for integer or decimal input
|-
|[[FieldSubselectDiagram|SQL: Diagram query]]
|Show the result of an SQL-query as a graph
|-

|}

==Extension==
{|
|[[FieldComplexQuestionIndex|Word heatmap index]]
|Specialised index field only showned in reports
|-

|[[FieldComplexQuestion|Question and answer]]
|Complex question with recommendation, numerical score and coloring
|-

|[[FieldComplexQuestionWillis|Complex question]]
|Complex question with recommendation, numerical score and coloring
|-

|[[FieldComplexQuestionMultiLocation|Multiline: Complex question]]
|MULTIPLE LOCATION: Complex question
|-

|[[FieldMultiLocation|Multiline: Location editor]]
|MULTIPLE LOCATION: Name of location
|-

|[[FieldYearRepeatCompare|Year comparator]]
|Comparing fields from previous years
|-

|[[FieldCalcFormulaWillis|Calc: Complex question (sum)]]
|Formula based on other fields
|-

|[[FieldMissingValues|Calc: Count missing fields]]
|Number of missing fields in a form or questionaire
|-

|[[FieldTestingAgeItem|Testing: Age record]]
|Change the age of a record for testing puposes
|-

|[[FieldJobnetOccupationConceptUri|Required for jobnet integration]]
|Required for jobnet integration
|-

|[[FieldDocumentSnippetLookup|Export document content based on selected value]]
|Export document content based on selected value
|-

|[[FormComplexQuestionMultiLocationIndex|Word rapport index for multilocations]]
|Word rapport index for multilocations
|-

|[[FieldYearRepeatCompare|Comparison of fields from previous years]]
|Comparison of fields from previous years
|-

|}

WebDAV

2024-10-10T11:14:41Z

Tvi:

== About our WebDAV implementation ==

Supported document types: Word, Excel, Powerpoint.

The implementation does not require SSL to be enabled on the server, but it is recommended.

Sometimes the action of saving a file, that was opened using WebDAV will fail, but only the fist time, if it happens at all.

To fix this, you just have to save the document again, and the issue will be gone for you, until you re-signin.

== How to enable ==
Toggle the policy <code>webdavSupport</code> and <code>webdavSessionTokens</code> to <code>true</code>.
[[File:WebDav files.png|thumb|WebDAV enabled on a files-field]]

When WebDAV is enabled, the files-field, will add tiny pencils next to the supported file-types.

Clicking on the file icon will prompt the file to be opened in the associated application. Clicking on the filename, will prompt a download of the file.

You can control how long the auth-tokens are valid for, using policy <code>webdavSessionLifetime</code>.

You can control whether a token should automatically be re-validated if it times out using policy <code>webdavSessionTokensRevalidate</code>.

== Enabling basic auth to your server ==
Office has stopped officially supporting Basic-auth, which is the backup authentication for our implementation.
To allow Office to connect to your server, and authenticate using Basic-auth, execute the following command, as admin, from the commandline.<syntaxhighlight lang="console">
REG ADD HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Common\Identity /t REG_EXPAND_SZ /v basichostallowlist /d "HOSTNAME"
</syntaxhighlight>Where HOSTNAME is the domain of your server, eg. <code>wiki.tsnocode.com</code>.

WebDAV

2024-10-10T10:44:33Z

Tvi: Created page with "== About our WebDAV implementation == Supported document types: Word, Excel, Powerpoint. Sometimes the action of saving a file, that was opened using WebDAV will fail, but only the first time, if it happens at all. To fix this, you just have to save the document again, and the issue will be gone for you, until you re-signin. == How to enable == Toggle the policy <code>webdavSupport</code> and <code>webdavSessionTokens</code> to <code>true</code>. File:WebDav fil..."

== About our WebDAV implementation ==

Supported document types: Word, Excel, Powerpoint.

Sometimes the action of saving a file, that was opened using WebDAV will fail, but only the first time, if it happens at all.

To fix this, you just have to save the document again, and the issue will be gone for you, until you re-signin.

== How to enable ==
Toggle the policy <code>webdavSupport</code> and <code>webdavSessionTokens</code> to <code>true</code>.
[[File:WebDav files.png|thumb|WebDAV enabled on a files-field]]

You can control how long the auth-tokens are valid for, using policy <code>webdavSessionLifetime</code>.

You can control whether a token should automatically be re-validated if it times out using policy <code>webdavSessionTokensRevalidate</code>.

== Enabling basic auth to your server ==
Windows has stopped officially supporting Basic-auth, which is the backup authentication for our implementation.

To allow Office to connect to your server, and authenticate using Basic-auth, execute the following command, as admin, from the commandline.<syntaxhighlight lang="console">
REG ADD HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Common\Identity /t REG_EXPAND_SZ /v basichostallowlist /d "HOSTNAME"
</syntaxhighlight>Where HOSTNAME is the domain of your server, eg. <code>wiki.tsnocode.com</code>.

File:WebDav files.png

2024-10-10T10:39:57Z

Tvi:

Shows the interface, when WebDAV is enabled

Full UTF8 support

2024-10-04T11:53:44Z

Tvi:

== Special characters causing errors ==

=== Problem ===
The default support for UTF8 is 3 byte.

Using 4 byte UTF content in text areas, can cause errors, that looks like

java.sql.SQLException: Incorrect string value: '\xC2\x96 Z. ...' for column 'NOTES' at row 1

=== Solution ===
Update the database to full UTF8 support using the following command

main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8

Note an administration profile is needed to complete the operation.

You might also have to update the tomcat server.xml file.

You have to add <code>useBodyEncodingForURI="true"</code> to the connectors.

Command line tools

2024-09-16T14:40:56Z

Tvi:

A new version of the CLI was released on 21. december 2023.

If you are looking for the old CLI you can find the documentation [[Legacy command line tools|here]].

== Compatibility ==
The tools are compatible with the following distributions.

* Amazon Linux, version 1, 2 and 2023
* Debian, version 10, 11 and 12
*Ubuntu, version 20.04, 22.04 and 24.04
* CentOS, version 8 and 9

The script will check to see if it is running on one of these OSes and stop executing if not.

== Usage information ==
The Tempus Serva Linux script tools are open source (LGPL), and you are free to use and modify them however you see fit. The tools are defined by one python3 script and a single json file that stores the config.

As the tools themselves are subject to semiautomatic upgrades, we strongly recommend that you keep backups of files you have modified. Future versions of the scripts are not guaranteed to be compatible, with earlier versions or your own modifications.

== Installing the tool ==
To install the tools, run:
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash
This will check compatibility and install the required plugins.

To use the tool, execute <code>ts</code>.

On first execution the tool will ask a couple of questions.

If you choose to run java 8, <code>alpha</code> and <code>beta</code> is the same release, previously known as <code>nightly</code>.

== Tool reference ==
To get the full list of commands, and a description, run <code>ts --help</code>.

=== quick-install ===
Installs all the required software to run TS NoCode Platform, a default webapp named 'app' and a redirect from root to 'app'.

It will not ask for anything, but uses default values.

=== install ===
Installs all the required software to run TS NoCode Platform.

It will ask questions about optional stuff.

=== install-app ===
Will install a new TS NoCode Platform webapp. It ask what release to install from and what name the webapp should be deployed under, if that webapp exists it will ask if you would like to upgrade that installation instead.

=== upgrade-app ===
Will upgrade an existing TS NoCode Platform webapp. It will ask what release to upgrade from and what name the webapp should be deployed under, if that webapp doesn't exist it will do nothing.

=== set-admin-password ===
Will set the admin password for an existing TS NoCode Platform webapp. Will ask what webapp to modify and what the password should be set to.

=== install-ssl ===
Will install all dependencies that are needed to setup a LetsEncrypt SSL certificate. Will ask if SSL should be setup once the install completes.

=== setup-ssl ===
Will ask about domain(s) and contact-email, request and install an SSL certificate and setup auto-renewal.

== Quick install ==
To quick-install the tool and a webapp run this
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash && ts quick-install
If you also want to setup SSL, run this
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash && ts quick-install && ts install-ssl

== Removing the tools ==
Remove the two files, eg by running:
sudo rm /usr/bin/{ts,tsconfig.json}

Command line tools

2024-09-11T10:27:07Z

Tvi:

A new version of the CLI was released on 21. december 2023.

If you are looking for the old CLI you can find the documentation [[Legacy command line tools|here]].

== Compatibility ==
The tools are compatible with the following distributions.

* Amazon Linux, version 1, 2 and 2023
* Debian, version 10, 11 and 12
* CentOS, version 8 and 9

The script will check to see if it is running on one of these OSes and stop executing if not.

== Usage information ==
The Tempus Serva Linux script tools are open source (LGPL), and you are free to use and modify them however you see fit. The tools are defined by one python3 script and a single json file that stores the config.

As the tools themselves are subject to semiautomatic upgrades, we strongly recommend that you keep backups of files you have modified. Future versions of the scripts are not guaranteed to be compatible, with earlier versions or your own modifications.

== Installing the tool ==
To install the tools, run:
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash
This will check compatibility and install the required plugins.

To use the tool, execute <code>ts</code>.

On first execution the tool will ask a couple of questions.

If you choose to run java 8, <code>alpha</code> and <code>beta</code> is the same release, previously known as <code>nightly</code>.

== Tool reference ==
To get the full list of commands, and a description, run <code>ts --help</code>.

=== quick-install ===
Installs all the required software to run TS NoCode Platform, a default webapp named 'app' and a redirect from root to 'app'.

It will not ask for anything, but uses default values.

=== install ===
Installs all the required software to run TS NoCode Platform.

It will ask questions about optional stuff.

=== install-app ===
Will install a new TS NoCode Platform webapp. It ask what release to install from and what name the webapp should be deployed under, if that webapp exists it will ask if you would like to upgrade that installation instead.

=== upgrade-app ===
Will upgrade an existing TS NoCode Platform webapp. It will ask what release to upgrade from and what name the webapp should be deployed under, if that webapp doesn't exist it will do nothing.

=== set-admin-password ===
Will set the admin password for an existing TS NoCode Platform webapp. Will ask what webapp to modify and what the password should be set to.

=== install-ssl ===
Will install all dependencies that are needed to setup a LetsEncrypt SSL certificate. Will ask if SSL should be setup once the install completes.

=== setup-ssl ===
Will ask about domain(s) and contact-email, request and install an SSL certificate and setup auto-renewal.

== Quick install ==
To quick-install the tool and a webapp run this
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash && ts quick-install
If you also want to setup SSL, run this
wget -qO - <nowiki>https://builds.tsnocode.com/helpers/install</nowiki> | bash && ts quick-install && ts install-ssl

== Removing the tools ==
Remove the two files, eg by running:
sudo rm /usr/bin/{ts,tsconfig.json}

MitID Integration

2024-09-05T13:40:31Z

Tvi: Added Signer.StatusUploaded

== What it does ==
We have a generic integration to Criipto (a MitID, and other eID, broker) and an account, allowing for sign in and document signing with MitID/nemID.

=== Sign in ===
Sign in can be setup as a webinterface or as SSO from the login-page (not fully supported yet), the authentication method isn't available in the dropdown for the webinterface, as of writing, it has to be set through the database (the live database).<syntaxhighlight lang="mysql">
UPDATE forminterface SET AuthenticationType = 5 WHERE InterfaceID = [ID];
</syntaxhighlight>

=== Document signing ===
One or multiple documents can be send for signature, one or more people can sign the batch and it is possible to enforce CVR or CPR. This process can be initiated from a StatusAction or be accessing a url.

A page is appended to the signed documents showing who signed it and when, in the order they signed it.

== Prereq ==
To setup this an "Application" has to be set up in Criipto, one for sign in and one for signatures, and a CNAME dns-record has to be created.

The ID's and secrets created here will be needed later.

== Setup in Criipto ==
First, a domain has to be added.

Haed to the Criipto Dashboard, select "Domains" in the menu, make sure that you are in "Production", click "Add production domain".

Name it <code>[customer]-eid.tsnocode.com</code> and head to CloudFlare and add a CNAME record that points to <code>idp.criipto.id</code>.

Once the domain is active you can progress.

=== Sign in ===
Coming

=== Document signing ===
Requires version 7336 or newer.

Head to "Application" in the Criipto menu, click "Add signatures application" (if it excists), otherwise click "Add login application" and add <code>?tags=signatures</code> to the end of the url.

Name the application <code>[customer] eSign</code>, select their domain and check the eID's that should be available, select <code>java</code> as technology.

A secret might pop up or be shown, take note. It is possible to add more after the fact and re-issue them.

== Setup in TS ==
There are a lot of parameters available. Some of these must be set for the integration to work, depending on the integration.

=== Sign in ===
Coming

===== Policies =====

* oauthCriiptoAllow
* oauthCriiptoHost
* oauthCriiptoClient
* oauthCriiptoSecret

=== Document signing ===
To start the signing process, setup the configuration and execute a Status Action that executes the codeunit <code>dk.tempusserva.signing.criipto.CriiptoStatusAction</code> or <code>dk.tempusserva.signing.criipto.CriiptoStatusActionGenerator</code> or <code>dk.tempusserva.signing.criipto.CriiptoStatusActionGeneratorAlt</code> or access a url with <code>command=dk.tempusserva.signing.criipto.CriiptoPage&SagID=[SagID]&DataID=[DataID]</code> (not ready).

This will try to lookup and send the document(s) out for signing.

==== Configurations ====
{| class="wikitable"
!Configuration
!Description
|-
|Signer.MultipleSigners
|Whether multiple signers is allowed (true/false)
|-
|Signer.MaximumSigners
|How many signatures are needed. Defaults to "COUNT", which counts the number of signers, when using MultipleSigners, otherwise 1. Can otherwise be set to a number.
|-
|Signer.ExpiresInDays
|Number of days the recipient has to sign the document. Default is 30.
|-
|Signer.FieldMaximum
|Not implemented
|-
|Signer.FieldFil *
|System name for the field with documents that should be send, all documents found here will be send. Defaults to "FILES". Also used to store generated files.
|-
|Signer.FieldCPR
|System name for the field with a CPR, that the signer has to have to sign the document. Also used with MultipleSigners.
|-
|Signer.FieldCVR
|System name for the field with a CVR, that the signer has to have to sign the document. Also used with MultipleSigners.
|-
|Signer.FieldEmail *
|System name for the field with an email, that will be notified about the signature request. Also used with MultipleSigners. Defaults to "EMAIL".
|-
|Signer.FieldSigners
|System name for a list-of-children-field. All records found here will be required to sign the document. Required when using MultipleSigners.
|-
|Signer.StatusError
|Status that the record should enter if the signature request failed (was rejected or timed out). Defaults to 0.
|-
|Signer.StatusSigned
|Status that the record should enter when all signatures are collected. Defaults to 0.
|-
|Signer.StatusUploaded
|Status that the record should enter when it has been uploaded to signing service. Defaults to 0.
|-
|Signer.StatusDisableCodeunits
|Whether codeunits should be executed or not, when the signing completes or fails. Defaults to false (do execute).
|-
|Signer.EmailSubject
|The subject of the email send to the signer. Defaults to "Dokument til signering".
|-
|Signer.EmailBody
|The email-body of the email send to the signer. Defaults to "Du kan underskrive her: {LINK}".
|-
|Signer.NotificationSubject
|The subject of the email send to EmailWarner, when all signatures have been collected. Defaults to "Dokument til signering er blevet underskrevet"
|-
|Signer.NotificationBody
|The body of the email send to EmailWarner, when all signatures have been collected.
Defaults to "Alle parter har nu underskrevet dokumentet. {LINK}". Links to the record.
|-
|Signer.NotificationBodyExt
|The body of the email send to all signers of a document, when all have signed.
Defaults to "Alle parter har nu underskrevet dokumentet. Du kan downloade det underskrevne dokument her: {LINK}". Links to the signed document at Criipto.
|-
|Signer.EmailWarner
|Can be an email or the system name of a field containing an email.
The email found here will be notified when a signature fails and completes. If an email is not found, the email of the current user will be used, if not a status action. Required for status action.
|-
|Signer.WarningSubject
|The subject of the email send to EmailWarner, when a signature request fails. Defaults to "Dokument til signering blev afvist".
|-
|Signer.WarningBody
|The body of the email send to EmailWarner, when a signature request fails. Defaults to "En underskrift blev afvist. {LINK}". Links to the record.
|-
|Signer.CriiptoClientID *
|The client ID from Criipto application.
|-
|Signer.CriiptoClientSecret *
|The client secret from Criipto application.
|-
|Signer.OverwriteOnReupload
|true/false, default false. If enabled the system allows re-sending a record for signing, overwriting the old one.
|-
|Signer.FileName
|Name of generated file, defaults to kontrakt.docx, used by CriiptoStatusActionGenerator
|-
|Signer.TemplateID
|ID of template to be rendered and saved before sending it of to be signed, used by CriiptoStatusActionGenerator
|-
|Signer.FileNameAlt
|Name of generated file, defaults to kontrakt.docx, used by CriiptoStatusActionGeneratorAlt
|-
|Signer.TemplateIDAlt
|ID of template to be rendered and saved before sending it of to be signed, used by CriiptoStatusActionGeneratorAlt
|}

Dashboard diagram widget configuration

2024-08-19T09:49:22Z

Tvi: multiple y-axis

This information is also applicable to the field [[FieldSubselectDiagram|Visual extra: SQL: Diagram query]].

This site only describes the specifics of the diagram widgets, for general widget configuration [[Dashboard widget configuration|click here]].

This article will only cover the newest version of graphs implemented.

To enable these, toggle the [[Policy]] useGoogleChart to false and useNewChart to true.

As of writing (version 8813) these renderings are supported.

* Circle
* Doughnut
* Bar vertical (Columns)
* Bar horizontal
* Area
* Line
* Area (stacked)

== Data and Internationalization ==
An SQL Query may extract almost anything from the database.

This process ignores the security restrictions in the system, so you will have to implement them yourself.

=== Structure ===

The structure is the same for all graphs.

The first row of data will be used for headers.

The column named "Title" will be used for titles. On circular diagrams that is the labels, next to the chart, and on xy-graphs that is the labels on the x axis.

The rest of the headers will be used when hovering over the graph, to give information about the data. On xy-graphs it will also be displayed as labels.

The rest of the lines in the data will be added as datapoints in the graph.

If the datapoint is a number, the graph will auto-scale to match the data.

Strings are also supported, but the outcome is unknown.

If a datapoint is null, the graph will bridge the gap, if it is an xy-line-graph, [[FieldSubselectDiagram|see sample here]].

==== Sample pie/doughnut-graph ====
{| class="wikitable"
!Title
!TitleEnglish
!This moth
!Last month
|-
|GOOG
|Alphabet
|100.23
|25.23
|-
|TSLA
|Tesla
|10.23
|20.23
|-
|AAPL
|Apple
|50.23
|50.23
|}

==== Sample line-graph ====
{| class="wikitable"
!Title
!TitleEnglish
!Alphabet
!Tesla
!Apple
|-
|THIS
|This Month
|100.23
|10.23
|50.23
|-
|LAST
|Last month
|25.23
|20.23
|50.23
|}

==== Multiply y-axis ====
Multiple y-axis are supported as of version 9390.

To use this feature, prepend the name of the new axis to the data that should be on that axis, eg <code>y1|Apple</code>.

The default y-axis is named <code>y</code>. If no axis is specified, this will be used.

You can specify as many axis as ChartJS supports.

=== Internationalization ===
Add extra columns named "Title", followed by the name of the language, eg ''TitleEnglish''.

If a column with this name is found, it will be used, otherwise the grath will fallback to the "Title" column.

If no title-column is found, the first column will be used, for compatibility reasons.

== Graph defaults ==
The graphs all reference the js object ''tsChartDefaultOptions'', with a couple of tweaks.

To see the defaults, open the terminal in you browser, on a page that has a graph and type the name of the object.

=== Specifik defaults ===
These can't be overwritten.

==== Area stacked ====
<syntaxhighlight lang="js">
options.scales = {
y: {
stacked: true
}
}
</syntaxhighlight>

==== Area stacked, area and line ====
<syntaxhighlight lang="js">
options.interaction = {
intersect: false,
mode: 'index',
}
</syntaxhighlight>

==== Bars ====
<syntaxhighlight lang="js">
options.indexAxis = 'y'
</syntaxhighlight>

=== Overwriting defaults ===
To overwrite the default of all charts:

Define an object in js, named tsChartOverwriteOptions.

Set it based on the documentation fund [https://www.chartjs.org/docs/3.7.1/ here].

To overwrite the options for a specific chart:

Define an object in js, named tsChartOverwriteOptions.

Add an object with an index matching the chartID.

Set it based on the documentation fund [https://www.chartjs.org/docs/3.7.1/ here].

To test your overwrite:

From the console in the browser call ''tsChartOptions'' with the only parameter being the chartID.

The return will be the final options, that will be used for that chart.

== Colors ==
The colors used, can be overwritten in the Policy ''diagramChartJSColors.''

The structure of the policy is very strict.

The policy has to be formatted as a js array of strings that represent an rgb color.

Thus: It has to start with <code>[</code> and and with <code>, ]</code>.

Each color has to be formatted as an rgb color and wrapped with <code>'</code>, and separated by <code>,</code> eg <code>'rgb(255, 255, 255)',</code> for a white color.

Integration/REST

2024-05-30T12:04:57Z

Tvi: /* Version 2 (Json) */ Swagger UI

== Introduction to the REST interface ==

The rest interface has two versions.
* v1, XML-version (default)
* v2, JSON-version

== Version 1 (XML) ==

This article has not yet been fully converted to Wiki format.

Please download the original article: [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf]

=== Netbeans quick start guide ===

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== Version 2 (Json) ==

Download the swagger file from:

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/v2/swagger.json
</syntaxhighlight>

You can browse and try the api, using the built in SwaggerUI (from version 9147):

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/v2/swagger
</syntaxhighlight>

== URL structure ==

When logged in the following URLs are available without further authentication

Data list operations: GET, PUT, POST

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>
</syntaxhighlight>

Data item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>
</syntaxhighlight>

File list operations: PUT, POST

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>/<FieldName>/<FileName>
</syntaxhighlight>

=== Executing codeunit ===

Operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/codeunit/<codeunitName>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

CloneSystem

2024-05-27T09:12:19Z

Tvi:

== What it does ==
Clones the entire webapp to another server.

Only works on linux.

== First setup ==

# Generate an SSH key for the tomcat-user on the source server <code>sudo -u tomcat ssh-keygen</code>
# Add the public key to a user on the target server that has sudo-access
# Connect from the source server, as tomcat, to the target server and accept the certificate
# Add configurations

== How to invoke ==
Invoke the codeunit, as an admin. eg.

<code>[SERVER]/main?command=common.CloneSystem</code>

=== Options ===
Control the behavior with the following url-parameters.
{| class="wikitable"
!Parameter
!Desctiption
|-
|with-users
|Also clones the users and their groups
|-
|with-files
|Also clones the files uploaded
|-
|dont-backup-target
|Does not create a copy of the database on the target server with the name <code>_backupyyyyMMddHHmm</code>
|-
|dont-clean
|Does not remove the sql files on both systems
|}

== Configuration ==
{| class="wikitable"
!Config
!Default
!Description
|-
|CloneSystem.targetServer
|
|IP or domain of target server
|-
|CloneSystem.targetUser
|ec2-user
|Name of the user that is being used on the target server
|-
|CloneSystem.targetBasePath
|Policy:applicationBasePath
|Webapps, folder on target server
|-
|CloneSystem.targetApp
|Policy:applicationName
|Application name on target server
|-
|CloneSystem.targetDb
|DbLive-name
|Name of live server on target server
|}

== Developer info ==

* Type: CodeunitPagecontent
* Security: Requires session

CloneSystem

2024-05-27T09:09:42Z

Tvi: Created page with "== What it does == Clones the entire webapp to another server. Only works on linux. == First setup == # Generate an SSH key for the tomcat-user on the source server <code>sudo -u tomcat ssh-keygen</code> # Add the public key to a user on the target server that has sudo-access # Connect from the source server, as tomcat, to the target server and accept the certificate # Add configurations == How to invoke == Invoke the codeunit, as an admin. eg. <code>[SERVER]/main?c..."

== What it does ==
Clones the entire webapp to another server.

Only works on linux.

== First setup ==

# Generate an SSH key for the tomcat-user on the source server <code>sudo -u tomcat ssh-keygen</code>
# Add the public key to a user on the target server that has sudo-access
# Connect from the source server, as tomcat, to the target server and accept the certificate
# Add configurations

== How to invoke ==
Invoke the codeunit, as an admin. eg.

<code>[SERVER]/main?command=common.CloneSystem</code>

=== Options ===
Control the behavior with the following url-parameters.
{| class="wikitable"
!Parameter
!Desctiption
|-
|with-users
|Also clones the users and their groups
|-
|with-files
|Also clones the files uploaded
|-
|dont-backup-target
|Does not create a copy of the database on the target server with the name <code>_backupyyyyMMddHHmm</code>
|-
|dont-clean
|Does not remove the sql files on both systems
|}

== Configuration ==
{| class="wikitable"
!Config
!Default
!Description
|-
|targetServer
|
|IP or domain of target server
|-
|targetUser
|ec2-user
|Name of the user that is being used on the target server
|-
|targetBasePath
|Policy:applicationBasePath
|Webapps, folder on target server
|-
|targetApp
|Policy:applicationName
|Application name on target server
|-
|targetDb
|DbLive-name
|Name of live server on target server
|}

== Developer info ==

* Type: CodeunitPagecontent
* Security: Requires session

Integration/REST

2024-05-13T12:40:37Z

Tvi:

== Introduction to the REST interface ==

The rest interface has two versions.
* v1, XML-version (default)
* v2, JSON-version

== Version 1 (XML) ==

This article has not yet been fully converted to Wiki format.

Please download the original article: [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf]

=== Netbeans quick start guide ===

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== Version 2 (Json) ==

Download the swagger file from:

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/v2/swagger.json
</syntaxhighlight>

You can upload the content to this site to browse it: [https://editor.swagger.io/ SwaggerIO Editor]

== URL structure ==

When logged in the following URLs are available without further authentication

Data list operations: GET, PUT, POST

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>
</syntaxhighlight>

Data item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>
</syntaxhighlight>

File list operations: PUT, POST

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>/<FieldName>/<FileName>
</syntaxhighlight>

=== Executing codeunit ===

Operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/codeunit/<codeunitName>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Integration/REST

2024-05-13T12:38:03Z

Tvi: Info about v2

== Introduction to the REST interface ==

This article has not yet been fully converted to Wiki format.

Please download the original article: [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf]

The rest interface has two versions.
* v1, XML-version (default)
* v2, JSON-version

== Version 1 (XML) ==

=== Netbeans quick start guide ===

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== Version 2 (Json) ==

Download the swagger file from:

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/v2/swagger.json
</syntaxhighlight>

You can upload the content to this site to browse it: [https://editor.swagger.io/ SwaggerIO Editor]

== URL structure ==

When logged in the following URLs are available without further authentication

Data list operations: GET, PUT, POST

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>
</syntaxhighlight>

Data item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>
</syntaxhighlight>

File list operations: PUT, POST

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/<entity>/<DataID>/<FieldName>/<FileName>
</syntaxhighlight>

=== Executing codeunit ===

Operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
http(s)://<server>/<application>/rest/<version>/codeunit/<codeunitName>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Integration/REST

2024-05-13T09:56:30Z

Tvi: Notet version changes and new endpoints

== Introduction to the REST interface ==
This article has not yet been fully converted to Wiki format.

Please download the original article: [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf]

The rest interface has two versions.
* v1, XML-version (default)
* v2, JSON-version

== Version 1 ==

=== Netbeans quick start guide ===

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== URL structure ==
When logged in the following URLs are available without further authentication

Data list operations: GET, PUT, POST

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<version>/<solution>
</syntaxhighlight>

Data item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<version>/<solution>/<DataID>
</syntaxhighlight>

'''Note: The fowllowing file handling endpoints are scheduled for Q2 2020'''

File list operations: PUT, POST

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<version>/<solution>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET, PUT, POST, DELETE

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<version>/<solution>/<DataID>/<FieldName>/<FileName>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Policy

2024-04-24T09:57:12Z

Tvi:

Policies are shared between all solutions in each Tempus Serva installation. Note that each property can be [[Overloading policies|overloaded in the Servlet context]] (same file as the connection pool configuration).

Note: In the following sections only links in the color blue will contain additional information.

=== Server configuration ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''applicationBasePath'''
|Application folder
|Location of WAR / deployed web application
|
|-

|'''applicationDisplayName'''
|Application display name
|Name of application displayed to users
|
|-

|'''applicationlPort'''
|Server port for HTTP
|Port used running regular requests. Needs to match the setting in webcontainer definition (server.xm in Tomcat)l
|
|-

|'''applicationlPortSSL'''
|Server port for HTTPS
|Port used running SSL encrypted requests. Needs to match the setting in webcontainer definition (server.xm in Tomcat)l
|
|-

|'''applicationName'''
|Application name
|Name of application / folder - example <nowiki>http://myserver.com/APPLICATIONNAME/login</nowiki>
|
|-

|'''applicationServer'''
|Application server hostname or IP
|Base refernce for the server. IP example: 89.56.12.14. Network name: localhost. Domain: bpms.acme.com
|
|-

|'''applicationURL'''
|Application machine / URL
|Base URL of the server as seen by the end user. Overlaps with value in applicationServer
|
|-

|'''cacheActive'''
|Caching enabled (recommended)
|Enable caching of system ressources. Alternative: Collect all ressources every time (very slow)
|
|-

|'''cacheBrowserExpireSeconds'''
|Static content cache time (seconds)
|Amount of time that images and scripts are cached i client browser.
|
|-

|'''cacheMaxObjectSize'''
|Cache maximum size (bytes)
|Maximum amount of memory consumed by the cache. Set as high as possible.
|
|-

|'''connectionPoolActive'''
|Use connection pools (recommended)
|Strongly recommended. Use webcontainer connection pools. Alternative: Application builds own connections (very slow)
|
|-

|'''defaultCharEncoding'''
|Default Character Encoding
|Recommended: ISO-8859
|
|-

|'''doExtraUrlDecoding'''
|Decode autocompletion / quicksearch
|Use if experiencing problems with autocompletion / quicksearch
|
|-

|'''doRedirectAfterUpdate'''
|Redirect user after updates
|Strongly recommended. Slight performance hit, but enables browser BACK button
|
|-

|'''multiServerCoordination'''
|Server cluster coordination
|Coordinate cache flushing, user list etc. through database communication (polling).
|
|-

|'''serverTypeAutodetect'''
|Server type detection
|Autodetect compliance type
|
|-

|'''serverTypeJ2EE'''
|Server type J2EE
|Compliance type if autodetect is disabled
|
|-

|'''sessionCheckInterval'''
|Session cleanup interval (minutes)
|Time between online list sweeping, removing user with no recent activity.
|
|-

|'''sessionLifetimeMaximum'''
|Session lifetime (minutes)
|Maximum time before last activity before users must log in again
|
|-

|'''sessionLifetimeMinutes'''
|Session lifetime minutes
|Length of user sessions (changeable at runtime)
|
|-

|'''systemOptimizeMemory'''
|Minimize HEAP size
|Always recommended < 1Gb RAM. Tradeoff between RAM and CPU time
|
|-
|}

=== Interface behaviour ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''allowAliasQueryParameters'''
|Allow Query alias parameters
|Allow alternate names for parameters used in LIST searches. Alternate names can be set programmtically.
|
|-

|'''allowFieldSelectionInLists'''
|Allow field selection in lists
|Allow user to select which fields are displayed in LIST views
|
|-

|'''allowListQuickFilter'''
|Allow for Quick filters i list views
|Enable serach in lists by writing part of the name (a search box will appear)
|
|-

|'''allowListSubtableRendering'''
|Data subtables in lists
|Subtables can negatively affect performance
|
|-

|'''allowSubtableLists'''
|Allow subtables in items (recommended)
|Allow related child records to be displayed in ITEM level views
|
|-

|'''concurrencyWarnings'''
|Warn on simultanous item editing
|Users poll server for changes using AJAX in browser client (some performance impact). Note that only different users editing the same item will trigger a warning.
|
|-

|'''defaultLanguageID'''
|Default Language (ID)
|Language to use if nothing else is specified and autodetection is disabled. Test by adding &Language=[number] to URL
|
|-

|'''defaultStyleID'''
|Default Style (ID)
|Style (buttons) to use if nothing else is specified. Test by adding &Style=[number] to URL
|
|-

|'''defaultStylesheetID'''
|Default Stylesheet (ID)
|Stylesheet to use if nothing else is specified. Test by adding &Stylesheet=[number] to URL
|
|-

|'''defaultTemplateID'''
|Default Template (ID)
|Form template to use in ITEM mode if nothing else is specified. Test by adding &Template=[number] to URL
|
|-

|'''defaultWrapperID'''
|Default Wrapper (ID)
|WrapperID to use if nothing else is specified. Test by adding &Wrapper=[number] to URL
|
|-

|'''doFormAutosave'''
|Autosave changed forms
|Allow editor to autocommit data before session times out
|
|-

|'''doItemBrowserTitle'''
|Display item resume in browser title
|Change browser title/tab title to current records Resume value in ITEM mode
|
|-

|'''doItemCreateAddMore'''
|Button to add more records
|Add multiple records during new record creation (button)
|
|-

|'''doItemMenuCopyPaste'''
|Show copy/paste in during record edits
|Extra buttons for copy/paste operations in ITEM mode
|
|-

|'''DoLinkedCSS'''
|CSS style links
|Link CSS content so that browsers can cache the content. Recommended.
|
|-

|'''doListShowAllFields'''
|Allow show all fields button
|Optional button i menu for selecting all columns / fields in LIST mode
|
|-

|'''doListShowAllRecords'''
|Allow show all records in list view
|Optional button i menu for selecting all records in LIST mode
|
|-

|'''doListShowLinkHeader'''
|Display link in headers
|Display link to list as part of header name
|
|-

|'''doListShowNameHeader'''
|Display header in lists
|Display the name of the solution above the list
|
|-

|'''doListShowSearchHeader'''
|Show search headers
|Display descriptive header in search form
|
|-

|'''doPageNavigatorAllways'''
|Allways show navigator in lists
|Page navigator can be disabled if all records can displayed in one page
|
|-

|'''doPersonalFlagsOnItems'''
|Display user flags on items
|Allow users to make bookmark / personal comments on single items
|
|-

|'''doPersonalLinksOnItems'''
|Display personal links on single items
|Display submenu of personal options in ITEM mode. By default only displayed i list / main mode
|
|-

|'''doPersonalLinksOnLists'''
|Display personal links on lists
|Display submenu of personal options in LIST mode.
|
|-

|'''doRecentItemsBookmarks'''
|Show recent items list
|Trach and diaply recently accessed items.
|
|-

|'''doStatusFinalDisableEditing'''
|Disable editing if status is final
|Allow records to be edited even after the item has reached a status that is final
|
|-

|'''DoTimeDecimal'''
|Display date sums with decimals
|Is time measured on items displayed using decimal og integer values
|
|-

|'''errorAdvancedView'''
|Advanced error handling
|Display explanation and contact details if exceptions occur
|
|-

|'''errorUnkownImage'''
|Advanced error logo
|Logo to display i advanced error handling
|
|-

|'''guiClickableList'''
|Click/doubleclick lists
|List views can be clicked to edit (double) or show (single)
|
|-

|'''guiDialogAdvanced'''
|Use advanced popups
|Uses JQuery style dialog for poup windows with inline scrolling
|http://jqueryui.com/dialog/
|-

|'''guiFieldHelpOffsetLeft'''
|Field help popup offset LEFT
|Window relative position to link on X axis
|
|-

|'''guiFieldHelpOffsetTop'''
|Field help popup offset TOP
|Window relative position to link on Y axis
|
|-

|'''guiPreventDoubleClick'''
|Prevent doubleclick
|Deactivate multi click on codeunit buttons
|
|-

|'''guiSetFormFocus'''
|Set form focus
|Set focus to first element in edit mode
|
|-

|'''guiSmartKeystrokes'''
|Use keyboard navigation
|Navigate with arrow keys, escape and tabulation
|[[Features/Key navigation]]
|-

|'''guiTouchEnhancement'''
|Enhance touch experience
|Make larger buttons and enable quicksearch by default
|
|-

|'''headerSeperator'''
|Seperator sign for headers
|Dot between header parts - ex. MySolution - Dashboard
|
|-

|'''mainRedirect'''
|Main menu redirect active
|Redirect to alternative main menu active
|
|-

|'''mainRedirectUrl'''
|Main menu redirect URL
|Local path ex. main?command=list&SagID=0
|
|-

|'''renderMenuItemClass'''
|Use CSS class for menu items
|Give unique class property to each menu item.
|
|-

|'''subformLinesDefault'''
|Number of lines in subforms
|Default number of records displayed in subforms
|
|-

|'''toolBarcodeParameters'''
|Barcode additional parameters
|Extra parameter for barcode, for tweaking size, type etc.
|
|-

|'''userOnlineList'''
|Maintain list of online users
|Monitor users online - ie. users with an active session on the server. Recommended in single front server environments.
|
|-

|'''userRequireAcceptTerms'''
|Require new user to accept usage terms
|Configure text in System configurations
|
|-
|}

=== Active directory ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''ldapAuthentication'''
|Use LDAP authentication
|Is LDAP logon active ?
|[[Integration/LDAP]]
|-

|'''ldapAuthenticationFallback'''
|Use fallback authentication if LDAP fails
|Allow internal database verfication using stored passwords, in the event that the LDAP server fails to respond properly.
|[[Integration/LDAP]]
|-

|'''ldapCreateUsers'''
|Allow creation of new users
|Create users logging in, that cannot be found inside the LDAP. User must belong to ldapDomainDefault
|[[Integration/LDAP]]
|-

|'''ldapDomainDefault'''
|Default domain
|
|[[Integration/LDAP]]
|-

|'''ldapMaintainGroupsOnLogon'''
|Maintain groups on logon
|LDAP validation also synchronizes groups found for logged in user.
|[[Integration/LDAP]]
|-

|'''ldapServer'''
|LDAP setup: LDAP server
|Use IP or network name
|[[Integration/LDAP]]
|-

|'''ldapUsername'''
|LDAP setup: USERNAME
|Service account username. User needs only read access.
|[[Integration/LDAP]]
|-

|'''ldapPassword'''
|LDAP setup: PASSWORD
|Service account username. Note this password is stored cleartext.
|[[Integration/LDAP]]
|-
|}

=== Security ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''doAdvancedGroupSecurity'''
|Advanced group security
|Enables: A) Groups inside groups B) Multiple exclusive groups
|
|-

|'''policyHideValues'''
|Hide overloaded policies
|Hide values for policies that have been overloaded in the application deployment file
|
|-

|'''securityAllowPublicCodeunits'''
|Allow anonoumus codeunit execution
|It is considered safe to use special codeunits
|
|-

|'''securityEnforceExclusiveGroup'''
|Require normal users to have Exclusive groups
|All users except Admins must have at least 1 exclusive group
|
|-

|'''securityLoginFailedAttempts'''
|Login max failed logins
|Number of failed logins before accounts will be disabled
|
|-

|'''securityLoginFailedAutoReset'''
|AutoReset users
|Automatically reset users that have failed maximum number of logins (sends new password)
|
|-

|'''securityPasswordAcceptMD5digest'''
|Allow MD5 hashed passwords
|Recommended in transition between MD5 (minor flaws) and SHA256 (very secure)
|
|-

|'''securityPasswordCleartext'''
|Store passwords cleartext
|Allow passwords to be stored without one-way encryption
|
|-

|'''securityPasswordCleartextAllowed'''
|Allow cleartext passwords
|Optionally encode all password using admin services
|
|-

|'''securityResetPasswordWithoutLogin'''
|Reset password without login
|
|
|-

|'''securitySslLogin'''
|SSL encryption for login page
|Enforce usage of SSL connections on login page using internal redirect. Recommended.
|[[Setting up SSL/HTTPS]]
|-

|'''securitySslPages'''
|SSL encryption for ALL pages
|Enforce usage of SSL connections on all page using internal redirect. Not recommended.
|[[Setting up SSL/HTTPS]]
|-

|'''securityTokenExpiryEnforce'''
|Deny old style access tokens
|
|
|-

|'''ssoSpnegoAuthenticate'''
|SSO via domain controller
|Allow SPNEGO filter to automatically log in authenticated Windows users
|
|-

|'''ssoCryptoTokenActive'''
|SSO token authentication
|Allow single sigon from externatal components (ex. TS SSO webpart)
|
|-

|'''ssoCryptoTokenSecret'''
|SSO token shared secret
|Shared secret password between TS and external services. Value must match exactly.
|
|-
|}

=== Scheduled services ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''accountAnonoumousMeasure'''
|Anonoumous account (UserID)
|UserID used for normal system iteractions using the solution interfaces
|
|-

|'''adminWarningSmsList'''
|Warning SMS number list
|List of administrator mobile phone lists (for notifications)
|
|-

|'''healthMonitorPassword'''
|Health monitor password
|Parameter/password to access basic monitor service without a login (usage: service?healtMonitorPassword)
|
|-

|'''integrationInvokeCodeunit'''
|Integration execute codeunit
|Execute codeunits during dataintegration / webservices
|
|-

|'''maintenenceEmergencyDelay'''
|Emergency shutdown delay
|Number of minutes to warn users when af EMERGENCY signal is sent to the server from the admin services
|
|-

|'''maintenenceLockdoorDelay'''
|Maintenence disable login delay
|Number of minutes before af shutdown where users are no longer allowed to log in
|
|-

|'''maintenenceShutdownDelay'''
|Maintenence shutdown delay
|Number of minutes to warn users when af MAINTENENCE signal is sent to the server from the admin services
|
|-

|'''measureAnonoumous'''
|Measure anonoumous users
|
|
|-

|'''measureInsertDelayCount'''
|Measure insert delay (items)
|
|
|-

|'''measureInsertDelayMinutes'''
|Measure insert delay (minutes)
|
|
|-

|'''measureInsertUsingBatch'''
|Measure insert in batches
|
|
|-

|'''serviceAdminStatusEmail'''
|Administrator email
|Administrator email for sending status updates
|
|-

|'''serviceStatusActionSendDirectly'''
|Send status actions directly by mail
|False: Insert into user notifications. True: Send per email
|
|-

|'''serviceWebsiteMonitorGW'''
|Website monitor goodword
|Information that needs to be found in a page located at serviceWebsiteMonitorURL
|
|-

|'''serviceWebsiteMonitorURL'''
|Website monitor URL
|Address to monitor where the serviceWebsiteMonitorGW should be found
|
|-

|'''userOnlineAlertOnNewNotification'''
|Notify online users directly
|Display new button when users are allready logged in
|
|-

|'''userOnlineListDisplayCount'''
|Display number of online users
|Display number of online users at bottom of all pages
|
|-
|}

=== Debug ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''debugCacheResponse'''
|Caching succes / failure
|Log effects of caching.
|
|-

|'''debugDaemonActivity'''
|Debug daemon runs
|Log all runs for Service and Server daemon
|
|-

|'''debugDataLoads'''
|Debug while loading data (CSV/XML)
|Debugging option for designers and developers
|
|-

|'''debugExceptions'''
|Debug all Exceptions
|Writes stacktrace to logfiles. Alternative: Only write to eventlog.
|
|-

|'''debugIntegration'''
|Debug integration messages
|Debugging option for designers and developers
|
|-

|'''debugLdapCommunication'''
|Debug LDAP communication
|Debugging option for designers and developers
|
|-

|'''debugLdapStacktrace'''
|Debug LDAP error details
|Debugging option for designers and developers
|
|-

|'''debugLdapValidation'''
|Debug LDAP validation
|Debugging option for designers and developers
|
|-

|'''debugLoginResults'''
|Debug all user logins
|Debugging option for designers and developers
|
|-

|'''debugOlapDefinitions'''
|Debug OLAP definitions
|Write all schemas and querys to logfiles on boot
|
|-

|'''debugQuerySQL'''
|Debug all SQL queries
|All queries are written to System.out / logfile
|
|-

|'''debugQuestionaire'''
|Debug questionaire steps
|Display extra information in questionaire mode
|
|-

|'''debugRequestPerSecond'''
|Debug requests/second
|Calculate server load on run. Results are sent to System.out / logfile
|
|-

|'''debugRequestTime'''
|Debug response time
|
|
|-

|'''debugRequestTimeToPage'''
|Debug response time on page
|Display response time in bottom of all pages (no performance impact).
|
|-

|'''debugScriptFunctions'''
|Debug JavaScript
|Allow JS errors to be displayed
|
|-

|'''debugServiceDaemon'''
|Debug the Service runner Daemon
|Write extra information from service clients to log files
|
|-

|'''debugTemplateHandling'''
|Debug template parsing
|Debugging option for designers and developers
|
|-

|'''debugTokenEvaluation'''
|Debug token evaluation
|Debugging option for designers and developers
|
|-

|'''debugWebservices'''
|Debug the Webservice interface
|Debugging option for designers and developers
|
|-
|}

=== Filesystem ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''folderImportFile'''
|Folder: Import files
|Processing folder. Will be set to default value if left empty.
|
|-

|'''folderIntegrationCSV'''
|Folder: CSV data files
|Processing folder. Will be set to default value if left empty.
|[[Policy/folderIntegrationCSV]]
|-

|'''folderIntegrationMail'''
|Folder: Mail integration (temporary)
|Processing folder. Will be set to default value if left empty.
|
|-

|'''folderIntegrationXML'''
|Folder: XML integration processing
|Processing folder. Will be set to default value if left empty.
|[[Policy/folderIntegrationXML]]
|-

|'''folderTemplateLoad'''
|Folder: Template cache
|Processing folder. Will be set to default value if left empty.
|
|-

|'''folderTemplateSave'''
|Folder: Template processing
|Processing folder. Will be set to default value if left empty.
|
|-

|'''folderUpload'''
|Folder: Upload
|Will be set to default value if left empty.
|
|-

|'''folderUploadTemp'''
|Folder: Upload processing
|Processing folder. Will be set to default value if left empty.
|
|-

|'''mediaFilterDelayMS'''
|Media files download latency
|Use if filesystem is slow to pick up changes
|
|-

|'''overloadApplicationFolder'''
|Application folder
|Option to override. Empty value = autodetect
|
|-

|'''uploadPictureResize'''
|Reduce uploaded pictures
|Resize all pictures sent to server to size defined in uploadPictureSizeMaximum
|
|-

|'''uploadPictureSizeMaximum'''
|Picture maximum size
|Scale pictures to this maximum of pixels. Maximum height/width determines size. Only works if uploadPictureResize is set
|
|-

|'''uploadPictureSizeThumbnail'''
|Thumbnail maximum size
|
|
|-

|'''uploadClientScaling'''
|Use clientside graphic scaling
|Let browser resize pictures before upload
|
|-

|'''uploadClientScalingExclude'''
|Clientside exlusion test for scaling
|Set to "false" or exclusion pattern:
/Android(?!.*Chrome)|Opera/ .test(window.navigator && navigator.userAgent)
|[https://github.com/blueimp/jQuery-File-Upload/wiki/Client-side-Image-Resizing]
|-

|'''uploadThreadProcessing'''
|Upload processing threads
|Beta function. Handle file processing with threads to improve Ui responsiveness.
|
|-

|'''uploadThreadOnlyPictures'''
|Upload processing threads: Graphics only
|Restrict upload threads to resizeable graphics. Requires Upload processing threads
|
|-

|}

=== Service daemon ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''serviceAutostart'''
|Autostart service daemon
|Start the service daemon after boot.
|
|-

|'''serviceDaemonHeartbeatSeconds'''
|Run daemon every seconds
|Frequency of daemon runs. Value should match the frequency of the most demanding service.
|
|-

|'''serviceLogentriesConsolidate'''
|Compress logs
|
|
|-

|'''serviceLogentriesMaximumAge'''
|Maximum age logs
|
|
|-

|'''serviceNotificationDeleteAfterDays'''
|Maximum age notifications
|
|
|-
|}

=== Eventlog ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''eventDelayWrite'''
|Burst-write events
|Collect Events together in bundles in order to optimize dataload. Events can be written forcefully using the service servlet.
|
|-

|'''eventDelayWriteItemMaximum'''
|Burst-write event count
|Number of events before burstwrite executes. Events can be written forcefully using the service servlet.
|
|-

|'''eventPrintToStandardOut'''
|Copy errors to server log
|Write errors to logfiles when logging to builtin eventlog in the database
|
|-

|'''eventWriteSuccesfullLogins'''
|Write succesfull logins
|Log all user logins to the event log. Note that all logins regardless are logged on the user profile.
|
|-
|}

=== Mail server ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''mailDomain'''
|POP3: Domain
|
|
|-

|'''mailPassword'''
|POP3: Password
|Mail account password. Note this password is stored cleartext.
|
|-

|'''mailServer'''
|POP3: Server
|
|
|-

|'''mailUsername'''
|POP3: Username
|Mail account username.
|
|-

|'''smtpMailDelaySec'''
|SMPT: Message delay
|Delay in SECONDS between sending emails
|[[Email server setup]]
|-

|'''smtpPassword'''
|SMTP: Account password
|Password for SMTP account set in smtpUsername. Note this password is stored cleartext.
|[[Email server setup]]
|-

|'''smtpSendRetries'''
|SMTP: Number of retries
|Number of attempts to send email from queue before giving up
|[[Email server setup]]
|-

|'''smtpServer'''
|SMTP: Server address
|Network location of the SMTP server
|[[Email server setup]]
|-

|'''smtpSystemEmail'''
|SMTP: System mail address
|Sender address (from) set on all automatically generated emails.
|[[Email server setup]]
|-

|'''smtpTestEmail'''
|SMTP: Test email address
|Recipient of all mails when test mode is activated. Activate by enabling smtpTestMode
|[[Email server setup]]
|-

|'''smtpTestMode'''
|SMTP: Test mode (send to test email)
|Enable test mode where ALL emails are sent to address specified in smtpTestEmail
|[[Email server setup]]
|-

|'''smtpUsername'''
|SMTP: Account name
|Example: k.pedersen@lsvgroup.com
|[[Email server setup]]
|-
|}

=== Remote services ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''doLookupEnabledLinks'''
|Allow lookup links for fields
|
|
|-

|'''lookupServiceCvrRegisterUrl'''
|URL to lookup CVR
|
|
|-

|'''lookupServiceGeneral'''
|URL to lookup text
|
|
|-

|'''lookupServicePhonePersonUrl'''
|URL to lookup contacts
|
|
|-
|}

=== Protection ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''bruteforceCooldownMinutes'''
|Bruteforce reject logins (minutes)
|Time that logins are rejected after the bruteforce protection i activated.
|[[Security/Bruteforce]]
|-

|'''bruteforceMaxBadLogins'''
|Bruteforce maximum failed logins
|Amout of logins failed before new logins are rejected. Relative to bruteforceMeasurePeriod.
|[[Security/Bruteforce]]
|-

|'''bruteforceMeasurePeriod'''
|Bruteforce measure period (minutes)
|Timeframe for measuring amount of bad logins. Relative to bruteforceMaxBadLogins.
|[[Security/Bruteforce]]
|-

|'''bruteforceProtection'''
|Bruteforce detection active
|Enable brute force detection mechanisms
|[[Security/Bruteforce]]
|-

|'''securitySantizeAllUserInput'''
|Check all user input for JScripts
|Allow only if session variable protection is enabled
|
|-
|}

=== License ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''licenseHolder'''
|License: Owner
|Company/intitution name on the license
|
|-

|'''licenseNumber'''
|License: Number
|ID received from your Tempus Serva distrbutor
|
|-

|'''licenseReportAdministrator'''
|2nd recipient of license reports
|Secondary recepiant of license reporting. Normally the license seller.
|
|-

|'''licenseReportingEmail'''
|1st recipient of license reports
|Primary recepiant of license reporting. Normally the responsible CIO.
|
|-

|'''licenseReportLicenseServer'''
|License reporting active
|License reporting active
|
|-

|'''licenseSerial'''
|License: Serial code
|Code received from your Tempus Serva distrbutor
|
|-
|}

=== Database ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''dbAutoUpdate'''
|Update database on boot (recommended)
|Strongly recommended. Allows system to update the database when new builds are deployed.
|
|-

|'''dbNameBase'''
|SHARED database name
|Schema name of database with common settings. Database can be shared between multiple installations.
|
|-
|}

=== SMS service ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''smsConnectUrl'''
|SMS Service gateway URL
|
|
|-

|'''smsErrorMessage'''
|SMS error message
|
|
|-

|'''smsMaxLength'''
|SMS maximum message length
|
|
|-

|'''smsParamMessage'''
|SMS parameter name: Message
|
|
|-

|'''smsParamNumber'''
|SMS parameter name: Number
|
|
|-

|'''smsPhoneCountryCode'''
|SMS phonenumber prefix
|
|
|-

|'''smsPhoneMinLength'''
|SMS phonenumber min length
|
|
|-

|'''smsTestMode'''
|SMS testmode active
|
|[[Email server setup]]
|-

|'''smsTestNumber'''
|SMS testmode number
|
|[[Email server setup]]
|-
|}

=== Main menu ===
{|
!System name
!Display name
!Explantion
!Extra info
|-

|'''doInformationInMasterMenu'''
|Allow news articles
|Display relevant news articles and messages on main page
|
|-

|'''doMainMenuAccordion'''
|Use animated main menu
|Use slick JQuery dropdown accordion based on sections
|http://jqueryui.com/accordion/
|-

|'''doMainMenuCreateItems'''
|Display create link in main menu
|Display button to create records directly from the mail menu
|
|-

|'''doMainMenuDescription'''
|Display descriptions in main menu
|Display solution description in the main menu. Alternatively you can just leave the desciption empty.
|
|-

|'''doMainMenuRecentItems'''
|Display recent items in main menu
|Display list of recent items accessed for each solution in the list.
|
|-

|'''doMainMenuSections'''
|Divide menu into solution groups
|Split the main menu into sections.
|
|-

|'''doViewListInMasterMenu'''
|Show user views in master menu
|Display list of shared and personal views in the main menu
|
|-
|}

=== Special fields ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''allowMultilookupInLists'''
|Allow multilookup in list views
|Minor performance impact
|
|-

|'''allowRecursiveDelete'''
|Allow recursive record deletion
|Allow deletion of parent items to propagate (configure each solution)
|
|-

|'''allowRelationDuringCreation'''
|Create related records before save
|Allow users to create new child records before the parent is submitted / created.
|
|-

|'''doSmartDateInput'''
|Smart sate input
|Use relative date inputs (example: -1 = yesterday)
|[[Policy/doSmartDateInput]]
|-

|'''lookupCheckKeysAllways'''
|Lookup allways check key values
|
|
|-

|'''lookupIgnoreErrors'''
|Lookup ignore errors
|
|
|-

|'''lookupIgnoreErrorsAjax'''
|Lookup ignore AJAX errors
|
|
|-

|'''lookupRecordSingleItemChange'''
|Display 1 record in lookup list changes
|Lookup list elements will only display 1 reference after being set the first time
|
|-

|'''medicoCloakPersonUniqueID'''
|Cloak person identification data (ex. CPR)
|Partially hide sensitive information when not in ITEM edit mode. Example 112233-4455 becomes 112233-XXXX.
|
|-

|'''questionaireAutostart'''
|Questionaire autostart
|Make sure the user cannot navigate to anything else that the first question
|
|-

|'''questionaireLastButton'''
|Last button in questionaires
|Display a button to navigate to questionaires final page
|
|-

|'''questionaireLastResume'''
|Questionaire missing field summary
|Display missing fields on final page
|
|-

|'''questionaireProgress'''
|Questionaire progress
|Turns progress indication (bar/percentage/steps) on and off
|
|-

|'''questionaireProgressIcons'''
|Questionaire progress: Bar
|Display blue/grey arrows based on progress
|
|-

|'''questionaireProgressPercent'''
|Questionaire progress: Percentage
|Calculate the completion rate based on progress
|
|-

|'''questionaireProgressSteps'''
|Questionaire progress: Steps
|Display number of completed and leftover questions
|
|-
|}

=== Designer ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''deletionBackup'''
|Deletion backups
|Perform backups before deleting solutions / fields
|
|-

|'''deletionBackupDefinition'''
|Deletion copy definition
|Copy metadata of solution before deletion
|
|-

|'''deletionBackupRecordLimit'''
|Deletion backup record limit
|Maximum number of records before tables are backup up before deletion
|
|-

|'''designerDisplayHelp'''
|Display help section in designer (this menu)
|
|
|-
|}

=== Layout ===
{|
!System name
!Display name
!Explantion
!Extra info
|-

|'''cssStylesheetBasic'''
|Include Basic stylesheet
|Disable if you want 100% style control
|
|-

|'''cssStylesheetJQuery'''
|Include JQuery stylesheet
|Disable if you want 100% style control
|
|-

|'''diagramLargeHeight'''
|Diagram height large
|Ex. Runchart details
|
|-

|'''diagramLargeWidth'''
|Diagram width large
|Ex. Runchart details
|
|-

|'''diagramSmallHeight'''
|Diagram height small
|Ex. Runchart overview
|
|-

|'''diagramSmallWidth'''
|Diagram width small
|Ex. Runchart overview
|
|-

|'''renderListGroupColumns'''
|Use grouping columns
|Group column i moved to the first in the list
|
|-

|'''renderListGroupHeaders'''
|Use grouping headers
|Alternative: Group values displayed as column
|
|-

|'''renderListSortColumns'''
|Use sorting columns
|Sort column i moved to the first in the list
|
|-

|'''standardHeightMemo'''
|Standard textarea Height
|Default height of TEXTAREA. Value can be overloaded in each field configuration.
|
|-

|'''standardTextCropLength'''
|Text default crop length
|
|
|-

|'''standardWidthHeader'''
|Header standard width
|
|
|-

|'''standardWidthMemo'''
|Standard textarea Width
|Default width of TEXTAREA. Value can be overloaded in each field configuration.
|
|-

|'''standardWidthText'''
|Standard inputbox size
|Standard INPUT field size. Value can be overloaded in each field configuration.
|
|-

|'''windowDefaultHeight'''
|New window height (pixels)
|Standard height for IFRAME and popup windows
|
|-

|'''windowDefaultWidth'''
|New window width (pixels)
|Standard width for IFRAME and popup windows
|
|-
|}

=== Rendering ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''defaultHtmlDoctype'''
|HTML DOCTYPE
|First line of HTML response. Change if you need specific HTML compliance. System is natively xhtml 1.0 compliant.
|
|-

|'''defaultHtmlEncoding'''
|General encoding for server
|Codepage displayed inside the html tag
|
|-

|'''defaultHtmlVersion'''
|HTML version number
|Version information displayed inside the html tag
|
|-

|'''doIncludeJQuery'''
|Include JQuery library
|Include JQuery in compability mode
|
|-

|'''doPageSelectViaJquery'''
|Page selectors via JQuery
|Use JS components for page selectors (default: static html)
|
|-

|'''doIncludeScriptUserInfo'''
|Insert user info JS variables
|Inject user information in pages for use with custom JavaScripts
|
|-

|'''heatmapCellColorIcon'''
|Heatmap cell icon
|Special content inserted into all heatmap cells
|Moved to buttons/style in version 8945
|-

|'''heatmapInvertAxis'''
|Heatmap invert axis
|Display variables on Y axis and records on X axis
|
|-

|'''heatmapItemLinks'''
|Heatmap links to items
|Allow direct links from heatmap records
|
|-

|'''heatmapLegendMap'''
|Heatmap legend
|Display legend map of full variable names
|
|-

|'''pageselectorTableLayout'''
|Pageselector in tables
|Render pagesselectors as tables (normal = div)
|
|-

|'''renderLinksCompliant'''
|Render links HTML 4.0 compliant
|Encode links to satisfy HTML4 specification
|
|-

|'''useGoogleChart'''
|Technology diagram: Google
|Alternative use ChartJS (not recommended any more)
|
|-
|'''useNewChart'''
|Beta: Use new chart implementation
|
|[[Dashboard diagram widget configuration]]
|-
|'''diagramChartJSColors'''
|Colors for charts
|Set the colors used by ChartJS
|[[Dashboard diagram widget configuration]]
|-

|'''useScriptulous'''
|Technology script: Scriptulous
|Alternative use JQuery (recommended)
|
|-
|}

=== Staging ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''buildTestLinesDefault'''
|Build test data default size
|Amount of lines copied from live system when building sets of test data
|
|-

|'''testSessionBackground'''
|Testsession use background
|Markup when in test mode:. Set background image with this URL.
|
|-

|'''testSessionInlineText'''
|Testsession page information
|Markup when in test mode:. Put extra HTML specified in page.
|
|-

|'''testSessionTitleChange'''
|Testsession use title
|Markup when in test mode:. Set browser title to this text.
|
|-
|}

=== Codeunit ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''codeunitLoadExternal'''
|Load external codeunits
|Allow server to load JAR files outside webapplication WEB-INF folder
|
|-

|'''codeunitPathJarFile'''
|Filesystem folder for codeunits
|Folder that is considered safe to use for built-in class loader
|
|-

|'''codeunitPathJarLink'''
|Http URL folder for coedunits
|URL that is considered safe to use for built-in class loader
|
|-

|'''safeCreateAddGroup1'''
|Fullauto: Add group A
|Option for full auto user/exclusivegroup creation
|
|-

|'''safeCreateAddGroup2'''
|Fullauto: Add group B
|Option for full auto user/exclusivegroup creation
|
|-

|'''safeCreateIsDatahandler'''
|Fullauto: Assign DataHandler role
|Option for full auto user/exclusivegroup creation
|
|-

|'''safeCreateIsUserCreator'''
|Fullauto: Assign UserCreator role
|Option for full auto user/exclusivegroup creation
|
|-
|}

=== Language / I18N ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''languageGetFromBrowser'''
|Determine langauge from browser
|Pick up language settings from the browsers settings
|
|-

|'''languageUseI18N'''
|Use Internationalization
|Allow solutions to take advantage of I18N. Configure each solution seperately.
|
|-
|}

=== OLAP cubes ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''olapDateDimensionYearEnd'''
|OLAP Time dimension last year
|
|
|-

|'''olapDateDimensionYearStart'''
|OLAP Time dimension first year
|
|
|-

|'''olapEngineFolderURL'''
|OLAP engine URL (optional)
|
|
|-

|'''olapRebuildOnBoot'''
|Rebuild OLAP on boot
|Rewrite cube defintions and queries
|
|-

|'''olapUseSingleSignon'''
|OLAP Single Sign On
|Allow external users with security tokens (set OLAP folder to use dedicated server)
|
|-

|'''allowRemoteOlapSchema'''
|OLAP schema service
|Activate schema delivery service (remote OLAP servers)
|
|-

|'''olapSchemaPassword'''
|OLAP schema service password
|Experimental: Password for use with the schema delivery service (remote OLAP servers)
|
|-

|'''olapJPivotEnabled'''
|JPivot OLAP enabled
|Is the internal OLAP engine enabled (JPivot)
|
|-

|'''olapJpivotIncludeDefaultCubes'''
|Jpivot schema include default cubes
|Include autogenerated cubes with generated permissions
|
|-

|'''olapSaikuEnabled'''
|Saiku OLAP enabled
|Experimental: Is the external OLAP engine enabled (saiku)
|
|-

|'''olapSaikuIncludeCustomCubes'''
|Saiku schema include custom cubes
|Include custom cubes with default permissions
|
|-

|'''olapSaikuSettingWebapp'''
|Optional saiku web application name
|Default if value is left empty: <current webapp name> + "Saiku"
|Example: /SaikuWebapp
|-

|'''olapSaikuSettingServerUrl'''
|Optional saiku server URL
|Default if value is left empty: <same server>
|Example: <nowiki>http://myserver.com</nowiki>
|-

|}

=== REST webservice ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''restActive'''
|REST is activated
|Option: Disable in web.xml
|
|-

|'''restAllowAnonoumous'''
|Annonumous REST sessions
|Webuser can interact if given permission
|
|-

|'''restAllowAnonoumousSchema'''
|Annonumous REST metadata
|Webuser can interact if given permission
|
|-

|'''restListPageSize'''
|REST list service page length
|Maximum mnuber of items displayed in a search
|
|-

|'''restStrongTypeRequest'''
|Strong types REST requests
|Use strong types in WADL
|
|-

|'''restStrongTypeResponse'''
|Strong types REST response
|Use strong types in XSD
|
|-
|}

=== Password policy ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''passwordExpiry'''
|Password Expiry
|Allow passwords to expire according to value set in passwordExpiryAge
|
|-

|'''passwordExpiryAge'''
|Password Expiry age
|Maximum age of passwords
|
|-

|'''passwordExpiryWarning'''
|Days to warn for password exipry
|Dars to start warning the user about their password expirng, as defined by passwordExpiryAge
|
|-

|'''passwordReqCheckOnLogon'''
|Password check rules OnLogon
|Enforce password rules on all logons
|
|-

|'''passwordRequireLength'''
|Password require length
|Minimum total length of password
|
|-

|'''passwordRequireLowercase'''
|Password require Lowercase
|Content rule lowercase letters (ex. abc)
|
|-

|'''passwordRequirements'''
|Password requirements
|Enforce password rules
|
|-

|'''passwordRequireNumbers'''
|Password require Numbers
|Content rule numbers (ex. 123)
|
|-

|'''passwordRequireSpecial'''
|Password require Special
|Content rule special characters (ex. !#%&)
|
|-

|'''passwordRequireUppercase'''
|Password require Uppercase
|Content rule uppercase letters (ex. ABC)
|
|-
|}

=== Statistics ===
{|
!System name
!Display name
!Explantion
!Extra info
|-
|'''statisticsRegressionInfo'''
|Extra regression info
|Display advanvced regression correllation information
|
|-

|'''statisticsTargetPValue'''
|Target p-value for tests
|At what p-values are tests considered significant
|
|-
|}

=== Satelite server handling ===
{|
!System name
!Display name
!Explantion
!Extra info
|-

|'''serverSateliteMaster'''
|Master: Server is MASTER
|The master server controls the satelite, and contains ALL data
|
|-

|'''sateliteDatabaseHost'''
|Master: Satelite DB hostname
|Connection information for satelite database (requires R/W access)
|
|-

|'''sateliteDatabaseJDBC'''
|Master: Satelite DB database
|Connection information for satelite database (requires R/W access)
|
|-

|'''sateliteDatabaseUser'''
|Master: Satelite DB username
|Connection information for satelite database (requires R/W access)
|
|-

|'''sateliteDatabasePass'''
|Master: Satelite DB password
|Connection information for satelite database (requires R/W access)
|
|-

|'''serverSateliteSlave'''
|Satelite: Server is SATELITE
|Warning: The satelite is controlled by the master server, and contains a SUBSET of data
|
|-

|'''allowRemoteCacheReset'''
|Satelite: Cache reset allowed via URL
|Allow anonoumous cache reset using only password
|
|-

|'''cacheResetNowPassword'''
|Satelite: Cache reset password
|Password to include in the URL for the cache reset
|
|-

|}

=== FTP server ===

{|
!System name
!Display name
!Explantion
!Extra info
|-

|'''ftpDbConnection'''
|CrushFTP database Connection
|Connection string for CrushFTP authorization database. Example: ''jdbc:mysql://127.0.0.1/crushftp''
|
|-

|'''ftpDbUsername'''
|CrushFTP database Username
|Username CrushFTP database
|
|-

|'''ftpDbPassword'''
|CrushFTP database Password
|Password CrushFTP database
|
|-

|'''ftpServerPortFtp'''
|CrushFTP port for FTP
|Default 21
|
|-

|'''ftpServerPortHttp'''
|CrushFTP port for HTTP
|Default 8081 for side by side installation
|
|-

|}

=== Menu customization ===

{|
!System name
!Display name
!Explantion
!Extra info

|-

| '''menuLayoutDefault'''
|Menu default layout name
| Choose between: layoutClassic layoutRibbon layoutBlockLeft layoutBlockRight
|
|-

| '''menuLayoutSelector'''
|Allow user to select menu layout
| Layout position selectors will displayed in the main menu
|
|-

| '''menuLevelAdvancedDefault'''
|Menu default advanced
| Display all menu items by default
|
|-

| '''menuLevelSelector'''
|Allow user to select menu level
| Simple / advanced selectors will displayed in the main menu
|
|-

|}

=== WebDAV ===

{|
!System name
!Display name
!Explantion
!Extra info

|-
| '''webdavMapDriveInMenu'''
|Map drive button
| Add map network drive button in main menu
|
|-
| '''webdavSessionLifetime'''
|Session token lifetime
| Age before session tokens expire
|
|-
| '''webdavSessionTokens'''
|Session token
| Session tokens allows direct editing from UI with doing authentication again
|
|-
| '''webdavSessionTokensRevalidate'''
|Session token revalidate
| Allow user to do basic authentication if a token expires or gets deregistered
|
|-
| '''webdavSupport'''
|Allow WebDAV
| Activate WebDAV for files stored i solution records
|
|-
|}

=== Single Sign On ===

{|
!System name
!Display name
!Explantion
!Extra info

|-

| '''oauthLoginDisplay'''
|SSO from login page
| Display SSO links on login page
|
|-

| '''oauthFacebookAllow'''
|Facebook SSO active
|
|
|-
| '''oauthFacebookClient'''
|Facebook API username
| https://developers.facebook.com/apps/
|
|-
| '''oauthFacebookSecret'''
|Facebook API password
| https://developers.facebook.com/apps/
|
|-
| '''oauthGoogleAllow'''
|Google SSO active
|
|
|-
| '''oauthGoogleClient'''
|Google API username
| https://developer.linkedin.com/documents/authentication
|
|-
| '''oauthGoogleSecret'''
|Google API password
| https://developer.linkedin.com/documents/authentication
|
|-
| '''oauthLinkedinAllow'''
|LinkedIn SSO active
|
|
|-
| '''oauthLinkedinClient'''
|LinkedIn API username
| https://console.developers.google.com/project/ts-oauth2-v1000/apiui/credential?clientType
|
|-
| '''oauthLinkedinSecret'''
|LinkedIn API password
| https://console.developers.google.com/project/ts-oauth2-v1000/apiui/credential?clientType
|
|-

|}

Integration/Content source

2024-04-22T09:35:01Z

Tvi:

THIS ARTICLE IS UNDER DEVELOPMENT

== Setting up a content source ==
Many parameters are straight forward
* Related solution
* Max cache age
* Is active

=== Unique NAME ===
This is the calling name of the interface, that must be provided accessing the content service.

Example for calling the view '''myview'''
... /cmsservice?q=myview& ...

=== Query command ===
Relevant commands include
*General records
** list: List of records
** show: Single record
* HTML formatted views
** heat: Heatmaps
** gant: Gant charts
** xtab: Pivot tables
** calm: Calendar

=== Query parameters ===
Parameters are provided without URL encoding

QUERY_FIELD_1=TITEL&QUERY_OPERATOR_1=8&QUERY_VALUE_1=Hello&QUERY_SHOWFIELD=TITEL StatusID DEADLINE

Procedure for easy parameter setup
# Build views in frontend.
# Activate the link and copy the URL
# ´Remove unneeded parameters
#* command
#* SagID
#* QUERY_NEW

=== Possible parameters ===

{|

| QUERY_FIELD_n
| Part of the search/filter. The field to filter by.
|-

| QUERY_OPERATOR_n
| Part of the search/filter. The way to filter. Full list [[Dashboard widget configuration]]
|-

| QUERY_VALUE_n
| Part of the search/filter. The value to filter by.
|-

| QUERY_SHOWFIELD
| The fields to show in the list, separated by space.
|-

| QUERY_PageSize
| Number of records to show pr page.
|-

| QUERY_PageOffset
| The page number to show.
|-

| QUERY_SortOrder
| The field to sort ascending by. Use either this or SortOrderDesc.
|-

| QUERY_SortOrderDesc
| The field to sort descending by. Use either this or SortOrder.
|-

| QUERY_Grouping
| The field to group records by.
|-

| QUERY_GroupingDesc
|
|-

|}

=== Dynamic parameter ===
This specifies a parameter that will be set by the value provided in the '''v''' parameter.

Example: Using this interface

Unique NAME: mylist
Query command: list
Dynamic parameter: QUERY_PageOffset

Making a call to

.../cmsinterface?q=mylist&v=2

Will fetch a list of data and display page 2, because '''2''' is injected into '''QUERY_PageOffset'''.

Parameters and values are injected directly into the http request.

'''Note: Using the "show" command the variable will ALLWAYS get mapped to "DataID"'''

== Using a content source ==
Calling the '''cmsinterface''' servlet will provide you with an overview on how to use it.

Example:

https://www.acme.com/TempusServa/cmsinterface

The interface requires just the name of the source, but additional parameters can be provided.

Parameters
* '''q''': Name of the interface (required)
** This name must match "Unique NAME"
* '''f''': Format of the result (optional)
** Valid values: html json xml
* '''v''': Parameter for dynamic values (optional)
** The value will be substituted to the parameter in "Dynamic parameter"

Example:

https://www.acme.com/TempusServa/cmsinterface?q=mysource&f=json

== Troubleshooting ==
THIS ARTICLE IS UNDER DEVELOPMENT

=== Configuration caching ===
For performance reasons information about the content sources is kept cached.

Adding or changing sources will propegate automatically : You will need to clear the system cache to pick the changes.

=== Parameter encoding ===
Note that URL's copied from a browser address bar are often encoded in HTML format.

The content will not decode values and request strings, so all encoded strings will fail.

API v1.0

2024-04-22T09:21:28Z

Tvi: Added limit

== Sessions and security ==

For interacting with Tempus Serva you need a session

<syntaxhighlight lang="java">
Session session = SessionFactory.getSession(this);
</syntaxhighlight>

All sessions need to be terminated after use (releasing DB connections etc.)

<syntaxhighlight lang="java">
session.close();
</syntaxhighlight>

== Constructing queryies ==
First of create a query object

<syntaxhighlight lang="java">
SolutionQuery myQuery = session.getSolutionQuery( "mynewsolution" );
</syntaxhighlight>

A query is built much like an SQL query by appending different fields to be SELECT'ed

<syntaxhighlight lang="java">
myQuery.addSelectField("MYNUMBER");
</syntaxhighlight>

Additionally WHERE components are added

<syntaxhighlight lang="java">
myQuery.addWhereCriterion("StatusID", "In progress");
myQuery.addWhereCriterion("INCOME", QueryPart.MORE, "22");
myQuery.addWhereInList("PARENTITEMS", arrayListOfDataID);
</syntaxhighlight>

Likewise operators can be added

<syntaxhighlight lang="java">
...
myQuery.addWhereOR();
...

...
myQuery.addWhereAND();
...
</syntaxhighlight>

Note that lookup values etc. will be translated silently.

<syntaxhighlight lang="java">
myQuery.setSortOrder("INCOME", true);
</syntaxhighlight>

Order records by income in descending order (true).

By default the API limits solution queries to 100 rows. To increase this:<syntaxhighlight lang="java">
myQuery.setLimit(100000);
</syntaxhighlight>To do pagination use this:<syntaxhighlight lang="java">
myQuery.setLimitAndOffset(100, 100);
</syntaxhighlight>Finally execute the query and return the results

<syntaxhighlight lang="java">
SolutionQueryResultSet records = myQuery.executeQuery();
</syntaxhighlight>

== Retrieve data ==
Data are extracted from the query resultset using a relative reference to the record number

<syntaxhighlight lang="java">
for( int i=0; i<resultSet.size(); i++ ) {
String text = "Value nr " + i " = " + '''resultSet.getRecordValue( i, "MYVALUE" );'''
System.out.println( text );
}
</syntaxhighlight>

Retriever methods exist for different datatypes

<syntaxhighlight lang="java">
public int getReference( int recordNr )
public Hashtable <String,String> getRecordValueList( int recordNr )
public String getRecordValue( int recordNr, String fieldName )
public int getRecordValueInteger( int recordNr, String fieldName )
private SolutionRecord getRecord(int recordNr, boolean isWrite)
</syntaxhighlight>

== Change / create data ==

AWAITING REVIEW

== Code example ==

The following example shows how data is retrieved from af collection of templates and used to create a collection of records (with values copied from the template).

<syntaxhighlight lang="java">
String thisKeyToParentTemplate = "VALGTSKABELON"; //Entity
String templateSolutionName = "tasktemplate"; //Entity
ArrayList fieldsTemplate = new ArrayList(String [] {"TASK","DEADLINE","RESPONSIBLE"}); //list of fields
String templateKeyToParentTemplate = "SKABELON"; //Entity
String instanceSolutionName = "taskinstance";
String instanceKeyToParent = "LIST";
</syntaxhighlight>

Now to the code ...

<syntaxhighlight lang="java">
int parentTemplateDataID = Parser.getInteger( c.fields.getElementByFieldName(thisKeyToParentTemplate).FieldValue );

Session session = SessionFactory.getSession(this);
try {
//Get data
SolutionQuery opsaetning = session.getSolutionQuery(templateSolutionName);
for(int i=0; i<fieldsTemplate.size(); i++ )
opsaetning.addSelectField(fieldsTemplate.get(i));
opsaetning.addWhereCriterion(templateKeyToParentTemplate, parentTemplateDataID);
SolutionQueryResultSet recordsToCopy = opsaetning.executeQuery();

int recordCount = recordsToCopy.size();
for( int i=0; i<recordCount; i++ ) {
SolutionRecordNew instance = session.getSolutionRecordNew(instanceSolutionName);

for(int fi=0; fi<fieldsTemplate.size(); fi++ ) {
String fieldNameToCopy = fieldsTemplate.get(fi);
String value = recordsToCopy.getRecordValue( i, fieldNameToCopy );
instance.setValue( fieldNameToCopy, value );
}
instance.setValueInteger( instanceKeyToParent, c.DataID );
if( ! Parser.isEmpty(instanceKeyToTemplate) )
instance.setValueInteger( instanceKeyToTemplate, recordsToCopy.getReference(i) );

instance.persistChanges();
}
}
catch(Exception e) {
e.printStackTrace();
}
catch (TsCloseObjectRequired ex) {}
finally {
session.close();
}
</syntaxhighlight>

Integration/REST

2024-04-22T09:15:17Z

Tvi:

== Introduction to the REST interface ==
This article has not yet been fully converted to Wiki format.

Please download the original article: [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf]

== Netbeans quick start guide ==

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== URL structure ==
When logged in the following URLs are available without further authentication

Data list operations: GET, PUT

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>
</syntaxhighlight>

Data item operations: GET, POST

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>
</syntaxhighlight>

'''Note: The fowllowing file handling endpoints are scheduled for Q2 2020'''

File list operations: GET, PUT

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>/<FieldName>/<ID>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Integration/REST

2024-04-22T09:04:55Z

Tvi: Blanked the page

Integration/REST

2024-04-22T09:04:38Z

Tvi: Replaced content with " === Query parameters === The REST API supports the same filtering and search parameters, as the list-command Integration/Content_source."

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Integration/REST

2024-04-22T09:04:14Z

Tvi:

Integration/REST

2024-04-22T09:03:39Z

Tvi:

Integration/REST

2024-04-22T09:03:18Z

Tvi:

== Introduction to the REST interface ==
This article has not yet been fully converted to Wiki format.

== Netbeans quick start guide ==

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== URL structure ==
When logged in the following URLs are available without further authentication

Data list operations: GET, PUT

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>
</syntaxhighlight>

Data item operations: GET, POST

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>
</syntaxhighlight>

'''Note: The fowllowing file handling endpoints are scheduled for Q2 2020'''

File list operations: GET, PUT

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>/<FieldName>/<ID>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Integration/REST

2024-04-22T08:51:48Z

Tvi:

== Introduction to the REST interface ==
This article has not yet been fully converted to Wiki format.

Please download the original article: [http://www.tempusserva.dk/articlebase/Tempus%20Serva%20REST%20interface.pdf Tempus Serva REST interface.pdf]

== Netbeans quick start guide ==

Steps to create a simple interaction
# Add Webservice to ide (wadl import)
#* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].wadl
#* If import causes trouble: Download the wadl file
# Create a new project
## Add REST Client to project
##* Point to newly created webservice: [SolutionSystemName]
## Add JAXB bindings to project (use XSD schema)
##* URL: [ServerName]/[ApplicationName]/rest/[SolutionSystemName].xsd
##* If import causes trouble: Download the xsd file

==== Sample code for list view (BASIC athentication) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();
session.setUsernamePassword("admin", "password1223");

//Set search parameters (first parameter is a dummy)
FirmabilerList result = session.getList(FirmabilerList.class, "", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

==== Sample code for list view (parameter credentials) ====

<syntaxhighlight lang="java">
//Create session
FirmabilerClient session = new FirmabilerClient();

//Login and set search parameters
FirmabilerList result = session.getList(FirmabilerList.class, "admin", "password1223", "TITEL=Kasper" );

//Retrieve data and print
List <FirmabilerListItem> list = result.getFirmabilerListItem();
for(int i=0; i<list.size(); i++) {
//Handle single item
FirmabilerListItem item = list.get(i);
System.out.println( item.getDataID() + "\t" + item.getNUMMERPLADE() );
}

//Close connection
session.close();
</syntaxhighlight>

== URL structure ==
When logged in the following URLs are available without further authentication

Data list operations: GET, PUT

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>
</syntaxhighlight>

Data item operations: GET, POST

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>
</syntaxhighlight>

'''Note: The fowllowing file handling endpoints are scheduled for Q2 2020'''

File list operations: GET, PUT

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>/<FieldName>/
</syntaxhighlight>

File item operations: GET

<syntaxhighlight lang="ini">
https://<server>/<application>/rest/<solution>/<DataID>/<FieldName>/<ID>
</syntaxhighlight>

=== Query parameters ===

The REST API supports the same filtering and search parameters, as the list-command [[Integration/Content_source]].

Status actions

2024-04-09T10:13:01Z

Tvi:

== Status actions ==
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 the item
* Creation date
* Last change
* Last status update
* Dynamic '''date field'''

Time is specified in days and can assume both negative and positive values.

== Action types ==

=== Notification ===
This action sends an email for users or groups.

Various options for the target email exists, including
* Raw email: Static reference
* User: A specific user in the database
* Field value: The contents of another field
** Email
** Phone (sent by SMS)
** CPR nr (sent by eBoks)

Different types of content can be includeded in the emails
* Data from the record
* Document generated using data of the record
* Links to the record (internal users)
* Interface tokens (external users)

Read about special tags and formatting her [[Tutorial/Status_notifications]]

=== Task create ===
This will dynamically create new tasks for any '[[FieldTask|Task list]]' fields found in the solution.

=== Codeunit ===
This action triggers the execution of a special codeunit: [[Codeunit/Statusaction]].

Except for timed actions you would implement this inside a [[Codeunit/Formevents]].

=== Export ===
The template is optional: If no template is found raw XML will be generated (FTP/mailto will not work).

The following types of routing are supported for template based exports
* Local file system (optionally a mapped share)
* Remote FTP server
* Sent by email

Please note that export actions are handled in seperate threads (performance), and there is no guarantee the operation succeds (tjeck the event log)

==== Values from record ====
The target reference may contain field references in the {FIELD} format, that will be populated at runtime.

Other special tags include
* {SagID}
* {DataID}
* {Resume}
* {NanoTime}

Note that values in records are not filtered for illegal og troublesome characters (such as \ or . )

==== Usage examples ====

{|
!Routing
!Syntax
!Syntax example
|-
|File system
|''local filesystem path''
|c:\exportFolder\{GROUP}\{TITLE}.docx
|-
|FTP server
|''ftp location and connection string''
|ftp://username:password@acme.com/exportFolder
|-
|Send by mail
|"mailto:"+[email]+":"+[subject]+":"+[filename]
|mailto:boss@acme.com:Attention:your_2013_report
|-
|}

=== Shift status ===
A status merely changes the status to a new value.

This type of action only makes sense to use in timed actions.

=== Webhook ===
This action performs an HTTP-request with parameters from the updated item and update the item based on the result.
{| class="wikitable"
!Datapoint
!
!Type
!Notes
|-
|url
|Required
|String
|The url that is to be called. This supports input of parameters from the item.
|-
|method
|Optional
|String
|The HTTP-method of the call, one of: "POST", "GET", "PUT" or "DELETE". Default: "GET".
|-
|type
|Optional
|String
|The datatype of data returned, supported types: "json", "raw" or "XML". Default: "json".
|-
|headers
|Optional
|Map
|A map of extra headers that should be set
|-
|params
|Optional
|Map
|Path parameters that should be set and send.
|-
|body
|Optional
|String
|A string that will be set and send. Not available for "GET".
|-
|update
|Optional
|Map
|Fields that should be updated based on the data returned.
If type is "raw", only the first item in this list will be updated, and it will be set to the entire response.

If type is "json", attributes with keys formatted as <code>[FIELDNAME]</code> will be updated from the given key in the returned data.
|}
In <code>params</code> and <code>body</code>, values formatted as <code>[FIELDNAME]</code>, will be filled with data from the record.

==== Sample ====
<syntaxhighlight lang="json">
{
"url": "http://localhost:3001/users/1",
"method": "PUT",
"type": "json",
"headers": {
"authorization": "Bearer XYZ",
"Content-type": "application/json"
},
"params": {
"param": "DATA"
},
"body": {
"id": 1,
"name": "[NAME]",
"email": "john.doe@example.com"
},
"update": {
"[NAME]": "name"
}
}
</syntaxhighlight>