Advanced Configuration
Passwords
You may want to encrypt sensitive data like passwords in your configuration
files. To do this, you can enclose any value with "${encrypt:}"
. The
Axon Ivy Engine will automatically encrypt and replace that value in the file when the
configuration is loaded. The system database password can be encrypted as
follows:
1# ivy.yaml
2SystemDb:
3 Password: "${encrypt:myPassword}"
There is a smooth Secrets integration, which is very useful in container environments such as Docker. Be aware that passwords of administrators always should be hashed.
Language
In each security system a default content language and a default formatting language can be defined. The content language is used to display the content in HTML dialog when loading content from the cms. This setting is also used to generate notification mails. The formatting language can be set additionally and is used to format values, for example the decimal point is displayed differently in different regions of the world.
1# ivy.yaml located in e.g. <configuration>/ivy.yaml
2SecuritySystems:
3 default:
4 Language:
5 Content: de
6 Formatting: de_CH
Users can customize the content language and formatting language in their
profile independently. You can add new translations for the built-in task
mail notifications in [engineDir]/system/cms
.
Business Calendar
A business calendar defines the official business hours and business days. These settings are used for business calendar calculations, e.g. what date will it be in three business days. See at Designer Guide and IBusinessCalendar for more information.
It is defined in the application’s app.yaml. An application contains at least one business calendar; if none is defined, a default calendar is automatically generated.
Here is an example of a business calendar definition; see app.businesscalendar.yaml for more detailed information.
1# Business Calendar
2# [engineDir]/configuration/applications/<APPNAME>/app.yaml
3BusinessCalendars:
4
5 # Company wide calendar definition
6 AxonIvy:
7 FirstDayOfWeek: monday
8
9 WorkingTimes:
10 morning: 8:00-12:00
11 afternoon: 13:00-17:00
12
13 FreeDays:
14 WeekendStart: saturday
15 WeekendEnd: sunday
16 "New Year": 01-01
17 "Christmas Day": 12-25
18
19 # Calendar definition for Switzerland
20 Switzerland:
21 Parent: AxonIvy
22 FreeDays:
23 "Good Friday": easter - 2
24 "Easter Sunday": easter
25 "Easter Monday": easter + 1
26 "Ascension Day": easter + 39
27 "Swiss National Day": 08-01
28
29 # Calendar definition for Zurich region, inheriting from Switzerland and AxonIvy calendar
30 Zurich:
31 Parent: Switzerland
32 FreeDays:
33 "Day after New Year": 01-02
34 "Labour Day": 05-01
35 "Pentecost Monday": easter + 50
36 "Saint Stephens Day": 12-26
37
38 # Calendar definition for Zug region, inheriting from Switzerland and AxonIvy calendar
39 Zug:
40 Parent: Switzerland
41 FreeDays:
42 "Ascension Day": easter + 39
43 "Pentecost Monday": easter + 50
44 "Corpus Christi": easter + 60
45 "Maria Assumption Day": 08-15
46 "All Saints Day": 11-01
47 "Immaculate Conception Day": 12-08
48 "Saint Stephens Day": 12-26
49
50 # Calendar definition for IvyTeam, with an additional special celebration day
51 IvyTeam:
52 Parent: Zug
53 FreeDays:
54 "50 Years Ivyteam": 2043-04-07
HTML Theme
The look and feel of HTML Dialogs is defined by its theme. You can change the appearance of any dialog on several scopes:
1# app.yaml located in e.g. <configuration>/applications/myApp/app.yaml
2Jsf:
3 primefaces.theme: modena-ivy
Or at session level via the IvyPrimefacesThemeResolver.
Overriding Configuration
Configuration entries of YAML files can be overridden with environment variables
of the operating system. Configuration keys in YAML are hierarchic object trees
separated by :
characters. While the environment variable must be
written uppercase and separated by _
characters. You need also to prefix
the environment variable with IVY_
.
So to overwrite the SystemDb:Url
of the ivy.yaml file, the
environment variable IVY_SYSTEMDB_URL
must be set.
Application Environments Overriding
You can override app.yaml configuration files by adding an additional
app.yaml
in a sub-directory _<environment>
in parallel to the
normal app.yaml.
<engine>/configuration/applications/<app>
├── app.yaml
└── _<environment>
└── app.yaml