app.yaml

[engineDir]/configuration/reference/app.yaml

# yaml-language-server: $schema=https://json-schema.axonivy.com/app/11.3.1/app.json
#
# -------------------------------------------
# Axon Ivy Application Configuration
# -------------------------------------------
# 
# This file shows configurations of an Axon Ivy Engine application.
# https://developer.axonivy.com/doc/11.3/engine-guide/configuration/files/app-yaml.html
#
# By default applications are pre-configured to run without any dependencies.
# However in productive environments applications often interact with many 
# external system such a Mail Servers (SMTP) or Directory services (LDAP). 
# 
# Each application has its own '<APPNAME>/app.yaml' in the configuration directory.
# e.g. the corresponding file for the application 'MyApp' is 
# '[engineDir]/configuration/applications/MyApp/app.yaml'.
#
# Furthermore 'app.yaml' can be deployed as part of application zip in a 'config' folder.
# The deployed 'app.yaml' is installed in the application directory and has a lower
# priority than the '<APPNAME>/app.yaml' in the configuration directory.
# https://developer.axonivy.com/doc/11.3/engine-guide/deployment
#
# SECRETS / PASSWORDS:
# Any configuration value can be encrypted just by enclosing it with "${encrypt:}".
# * to encrypt the string myPassword write "${encrypt:myPassword}"
#   https://developer.axonivy.com/doc/11.3/engine-guide/configuration/advanced-configuration.html#passwords
#
# OVERRIDING:
# Any configuration value provided here can be set in alternative sources. 
# * environment variables: of the operating system can set app config entries. 
#    Their key must be prefixed with 'IVY_APPLICATIONS_MYAPP_'. 
#    E.g. use 'IVY_APPLICATIONS_MYAPP_SECURITYSYSTEM' to override the security system.
#    https://developer.axonivy.com/doc/11.3/engine-guide/configuration/advanced-configuration.html#overriding-configuration
#

# The security system manages users and roles and must be referred by name.
# This setting is only evaluated at deployment time when the application not already exists!
# You can not change the security system of an application later on.
SecuritySystem: default
# Defines a project containing overriding SubProcesses, HtmlDialogs or CMS entries for a dependent project.
# This allows you to customize generic solutions with minimal effort.
# The overriding project must be declared in the format <group-id>:<project-id> (e.g. ch.ivyteam.ivy:overrideProject).
# These identifiers can be copied from the ivy project deployment definition (pom.xml).
# https://developer.axonivy.com/doc/11.3/designer-guide/how-to/overrides.html
OverrideProject: ""
Data:
  # Application folder where application files are stored. It overrides the root file folder setting.
  # A change in this setting will NOT automatically move existing application files to the new location, so you need to move files manually.
  # Absolute and relative (to the engine root directory) paths are supported.
  # If not set the files will be stored in an application specific directory underneath the root file folder.
  # [restart required] for existing apps
  FilesDirectory: ""

StandardProcess:
  # Standard processes are a set of predefined processes, which you can customize in your ivy project.
  # To enable these custom processes, the library id of the ivy project must be specified here.
  # The library id is <group-id>:<project-id> from the ivy project deployment definition.
  # e.g the library id of the portal template is "ch.ivyteam.ivy.project.portal:portalTemplate"
  # The default is 'auto' which means auto detection of standard process in your application
  # https://developer.axonivy.com/doc/11.3/designer-guide/user-interface/default-pages
  DefaultPages: auto

Jsf:
  # JSF Primefaces Theme that is used by HTML Dialogs
  # Standard themes:
  # vela, saga, arya
  # Freya themes:
  # freya-ivy-light, freya-ivy-dark
  # Deprecated themes:
  # serenity-ivy, serenity-amber, serenity-blue, serenity-bluegrey, serenity-brown, serenity-cyan, serenity-deeporange, serenity-deeppurple,
  # serenity-green, serenity-grey, serenity-indigo, serenity-lightblue, serenity-lightgreen, serenity-lime, serenity-orange,
  # serenity-pink, serenity-purple, serenity-teal, serenity-yellow,
  # luna-amber, luna-blue, luna-green, luna-pink, nova-colored, nova-dark, nova-light
  # This configuration has no effect if theme is specified in the xhtml template.
  # https://developer.axonivy.com/doc/11.3/designer-guide/user-interface/user-dialogs/html-dialog-themes.html
  primefaces.theme: freya-ivy-light

# Databases are defined in ivy projects with a name.
# Connection details from those databases can be overridden by addressing the database by name.
Databases:
#  # example Database
#  exampleDatabase:
#    # JDBC Url to use for connections. E.g. 'jdbc:{vendor}://{host}:{port}/{dbName}'
#    Url: ""
#    # JDBC driver Name: e.g. 'org.postgresql.Driver'
#    Driver: ""
#    # Reference to a custom image. E.g. 'res:/webContent/myIcon.png'
#    Icon: ""
#    UserName: ""
#    # Secret password, should be stored encrypted. Encrypted values have a ${decrypt:} prefix
#    # [password]
#    Password: ""
#    MaxConnections:
#    # Driver specific custom properties
#    Properties:
#  

# Rest Clients are defined in ivy projects with a name.
# Any configuration from those clients can be overridden by addressing the client by name.
RestClients:
#  # example ConfigurableRestClient
#  exampleConfigurableRestClient:
#    Url: ""
#    # Full qualified class names, that contribute REST-client features, such as authentication.
#    # [examples: ch.ivyteam.ivy.rest.client.mapper.JsonFeature, ch.ivyteam.ivy.rest.client.authentication.HttpBasicAuthenticationFeature]
#    Features:
#    # Properties that supply dynamic values for REST-client features.
#    Properties:
#  

# Web Service Clients are defined in ivy projects with a name.
# Any configuration from those clients can be overridden by addressing the client with its name.
WebServiceClients:
#  # example ConfigurableWsClient
#  exampleConfigurableWsClient:
#    # Full qualified class names, that contribute WS-client call features, such as authentication.
#    Features:
#    # Properties that supply dynamic values for WS-client features.
#    Properties:
#    # Endpoint names, to URIs
#    # [examples: myPort: - https://myCustomProdHost/hr/employee/soap]
#    Endpoints:
#  

# Currently active business calendar for this application.
BusinessCalendar: ""
# Business calendars are organized as trees, with one root / default calendar and an arbitrary number of child calendars.
# Child business calendars inherit the values of their parent. A parent can be the root calendar or any child calendar.
# 
# At least one root calendar needs to be defined. If non is configured, a root / default calendar will be created automatically
# with following default values:
# - Parent is empty
# - First day of week is: Monday
# - Working times are: 'morning: 8:00 - 12:00' and 'afternoon: 13:00 - 17:00'
# 
# You can reference a business calendars in a ivy projects by its name. E.g ivy.cal.get("myRootBusinessCalendar")
# https://developer.axonivy.com/doc/11.3/engine-guide/configuration/advanced-configuration.html#business-calendar
BusinessCalendars:
#  # example BusinessCalendar
#  exampleBusinessCalendar:
#    # First day of the week.
#    # If empty or not existing the parent calendar's value is inherited.
#    # If not defined by any parent the value is retrieved from the current locale settings
#    # [enum: monday, tuesday, wednesday, thursday, friday, saturday, sunday]
#    FirstDayOfWeek: ""
#    # Name-value pairs of non-working days.
#    # 
#    # Yearly days:
#    # Recurring non-working days during a year, falling on the same date, e.g. Jan. 1 or Christmas.
#    # Format: MM-dd, e.g. 01-01 (New Year), 12-25 (Christmas Day)
#    # 
#    # Relative Easter Days:
#    # Recurring non-working days relative to Easter Sunday, e.g. Good Friday or Pentecost.
#    # Format (case insensitive): easter +/- Number, e.g. 'easter - 2' (Good Friday), 'easter + 50' (Pentecost Monday)
#    # 
#    # Fixed Dates:
#    # Once-off non-working days, e.g. a company celebration day or a special local public holiday.
#    # Format: YYYY-MM-dd
#    # [examples: "New Year": 01-01, "Christmas Day": 12-25, "Good Friday": easter - 2, "Easter Monday": easter + 1, "Pentecost Monday": easter + 50, "50 Years Ivyteam": 2043-04-07]
#    FreeDays:
#      # End of days that are always off
#      # [enum: monday, tuesday, wednesday, thursday, friday, saturday, sunday]
#      # [examples: sunday]
#      WeekendEnd: ""
#      # Start of days that are always off
#      # [enum: monday, tuesday, wednesday, thursday, friday, saturday, sunday]
#      # [examples: saturday]
#      WeekendStart: ""
#    
#    # Name of the parent business calendar.
#    # If empty or not existing this business calendar will be the root calendar for this application.
#    # Only one root calendar is allowed.
#    Parent:
#    # Name-value pairs of working times during a business day.
#    # At least one working time needs to be defined here or in any of the parents for business calendar calculations to work.
#    # 
#    # Warning: Ensure that your working times in your calendar tree do not overlap.
#    # Otherwise the business calendar calculations may not work correctly!
#    # 
#    # Value format is : HH:mm-HH:mm
#    # [examples: myMorning: 8:00-12:00, myAfternoon: 13:00-17:00]
#    WorkingTimes:
#  

# Variables are defined in ivy projects.
# All of them can be overridden.
# [examples: myVar: myValue]
Variables: