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/12/17 07:59] fiserp [CzechIdM - extras] |
devel:documentation:modules_extras [2020/03/25 07:02] kucerar added link to cross domain |
||
---|---|---|---|
Line 5: | Line 5: | ||
===== 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 39: | Line 60: | ||
===== Status task ===== | ===== Status task ===== | ||
Documentation is available here: [[tutorial: | Documentation is available here: [[tutorial: | ||
+ | Information about content is here: [[devel: | ||
===== SSO authenticate ===== | ===== SSO authenticate ===== | ||
Documentation is available here: [[documentation: | Documentation is available here: [[documentation: | ||
+ | |||
+ | ===== Role force provisioning to particular system ===== | ||
+ | The tutorial is available here: [[tutorial: | ||
===== Guarantees of roles can assign their roles to everybody ===== | ===== Guarantees of roles can assign their roles to everybody ===== | ||
Line 64: | Line 89: | ||
A notification about the end of identity' | A notification about the end of identity' | ||
More information is available here: [[tutorial: | More information is available here: [[tutorial: | ||
+ | Edit: full IdmIdentityDto was added for use in a template in 1.7.0 | ||
===== Get titles before and after ===== | ===== 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*, | 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*, | ||
Line 82: | Line 107: | ||
Documentation for configuration is available [[tutorial: | Documentation for configuration is available [[tutorial: | ||
+ | |||
+ | ===== Workflow to disable contract on MISSING_ACCOUNT ===== | ||
+ | Setting this workflow (extrasDisableMissingContract) as workflow for action in contract reconciliation will disable contract, when its being synchronized. It can be used for example, in situations when contracts are being deleted from source data after expiration and they keep being stuck in MISSING_ACCOUNT state. | ||
+ | |||
+ | ===== Groups membership in multi domain (cross domain) AD environment ===== | ||
+ | Since module version **1.8.0** | ||
+ | |||
+ | Documentation is available [[tutorial: |