https://wiki.czechidm.com/ 2026-04-29T01:52:42+00:00 https://wiki.czechidm.com/ https://wiki.czechidm.com/_media/wiki/logo.png text/html 2026-03-12T13:45:39+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.czechidm.com/devel/documentation/application_configuration/dev/backend?rev=1773323139&do=diff Configuration - backend configuration final property properties config setup The application uses a Spring boot configuration in the application.properties files. All the configuration items which are used solely for idm begin with idm. prefix. The configuration items from the file can be overloaded through a setting agenda in the gui ⇒ a server restart isn't needed for changing the configuration with text/html 2021-02-10T18:20:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.czechidm.com/devel/documentation/application_configuration/dev/dynamic-forms?rev=1612981211&do=diff Dynamic forms (eav) configuration eav form attachment Dynamic form instances (values) are saved in the individual tables according to the entity which they are linked to => which is their owner (e.g. the entity IdmIdentityFormValue, IdmRoleFormValue). Form values are not saved, if null text/html 2021-03-08T07:20:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.czechidm.com/devel/documentation/application_configuration/dev/frontend?rev=1615188017&do=diff Configuration - frontend configuration Frontend configuration is stored in czechidm-app module under czechidm-app/config folder and is separated by profile (by client) and stage (development / test / production) read more. When frontend is build by gulp, then selected configuration by profile and stage is moved (and transformed) into application as text/html 2018-03-22T13:39:28+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.czechidm.com/devel/documentation/application_configuration/dev/scheduled_tasks?rev=1521725968&do=diff TUTORIAL Long running tasks scheduler Long running tasks (LRT) in CzechIdM are available at the menu Settings -> Task scheduler. LRT is a task which start is planned in advance and the instance runs at the background. Examples of LRT are identity lifecycle processes. The run of the LRT can be planned as one time run or periodically.