Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:modules_extras [2019/10/14 13:27] kopro add information about skip check for systemState |
devel:documentation:modules_extras [2020/02/18 10:04] sourek |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== CzechIdM - extras ====== | ====== CzechIdM - extras ====== | ||
- | CzechIdM - extras contains various features, which are not suited to be in any other module. List of the currently supported features is bellow. | + | CzechIdM - extras contains various features, which are not suited to be in any other module. List of the currently supported features is below. |
Currently supported CzechIdM version : 9.2.2 | Currently supported CzechIdM version : 9.2.2 | ||
===== Developing and releasing ===== | ===== Developing and releasing ===== | ||
- | <note important> | + | How to develop a new feature in extras: |
+ | |||
+ | - Create a specification page in private section | ||
+ | - Usecases - why we or user need this feature, what problem does it solve? | ||
+ | - Why is it in extras and not in core, or other module? | ||
+ | - Functional specification - how should it work, edge cases | ||
+ | - Ask a module owner, if this feature can be a part of extras and in which version it will be published | ||
+ | - Create ticket | ||
+ | - Implement | ||
+ | - Create merge request to develop | ||
+ | - Get someone from product team, or module | ||
+ | - After successfull review, ask module owner to merge you code | ||
+ | |||
+ | Rules for code review: | ||
+ | * All new features have at least 80 percent test coverage | ||
+ | * All features are documented | ||
+ | * There are no sonar issues in commited code | ||
+ | * Changelog is updated | ||
+ | * Feature is by default turned off (can be enabled either by processor, or configuration property) | ||
+ | |||
+ | |||
+ | <note important> | ||
* When developing, use our standard gitflow: | * When developing, use our standard gitflow: | ||
Line 60: | Line 81: | ||
Report will compare value of attributes with connected system. Connected system does not need to be in read only. | Report will compare value of attributes with connected system. Connected system does not need to be in read only. | ||
More information is available here: [[tutorial: | More information is available here: [[tutorial: | ||
+ | |||
+ | ===== Notification about the end of identity' | ||
+ | A notification about the end of identity' | ||
+ | More information is available here: [[tutorial: | ||
+ | |||
+ | ===== Get titles before and after ===== | ||
+ | Almost every project receive all titles in one string and IdM allow separates titles before and after. For this case was created in *ExtrasUtils* two methods *getTitlesAfter* and *getTitlesBefore*. And transformation scripts *extrasGetTitlesBefore* and *extrasGetTitlesAfter*, | ||
+ | |||
+ | Dictionary with titles can be setup by configuration properties. Default values exists. | ||
+ | < | ||
+ | idm.sec.extras.configuration.titlesAfter=" | ||
+ | idm.sec.extras.configuration.titlesBefore=" | ||
+ | </ | ||
+ | |||
+ | ===== Import automatic roles on tree nodes ===== | ||
+ | You can use this tool to create automatic roles which are assigned based on the position within the organization structure using a CSV file as a source. | ||
+ | More information is available here: [[tutorial: | ||
+ | |||
+ | ===== Groups synchronization workflow | ||
+ | Since module version **1.4.0** was exists better workflow for groups synchronization than in core. This workflow has same features as product. In product will be available same feature as this workflow but with configuration from GUI. | ||
+ | |||
+ | Documentation for configuration is available [[tutorial: |