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_reports [2020/03/11 09:59] doischert |
devel:documentation:modules_reports [2021/10/15 07:42] doischert |
||
---|---|---|---|
Line 9: | Line 9: | ||
{{ : | {{ : | ||
- | The module is fully dependent on [[devel: | + | The module is fully dependent on the [[devel: |
====== Overview of implemented reports ====== | ====== Overview of implemented reports ====== | ||
Line 15: | Line 15: | ||
==== Identities and their roles ==== | ==== Identities and their roles ==== | ||
- | This report . Learn more | + | This report |
+ | |||
+ | ==== Identities, their roles and contract ==== | ||
+ | |||
+ | This report is similar to the one above but contains more information. The generated XLSX file has a clear separation between attributes of identity, contract, and role. [[devel: | ||
==== Roles and their identities ==== | ==== Roles and their identities ==== | ||
- | This report . Learn more | + | This report |
==== Identities, their main contract and their roles ==== | ==== Identities, their main contract and their roles ==== | ||
- | This report . Learn more | + | This report |
+ | |||
+ | ==== Identities and their assigned roles changes ==== | ||
+ | |||
+ | This report allows you to export all changes in assigned roles for users in a given time period. You can use filter to only show changes caused by automatic roles (both by position and attribute). [[devel: | ||
+ | |||
+ | ==== Identities and their password changes on a system ==== | ||
+ | |||
+ | This report allows you to export all password changes in end systems. You can filter by system, time period, and success of the change. [[devel: | ||
+ | |||
+ | ==== Identities and their system account (state) changes ==== | ||
+ | |||
+ | This report allows you to export all account changes in end systems of the type CREATE, DELETE and ENABLE. You can filter by system, time period, type of operation, | ||
- | ===== Developing and releasing | + | ==== Virtual system archived request report |
- | How to develop a new feature in reports: | + | |
- | - Create a specification page in private section and consult it with module owner and other colleagues | + | This report allows you to export all archived |
- | - Usecases - which data should the report contain, what problem does it solve, which client needs it? | + | |
- | - Functional specification - how should it work, edge cases | + | |
- | - Ask a module owner, if this feature | + | |
- | - Create ticket in product Redmine with final requirements and with correct target version | + | |
- | - Implement the feature in a separate GIT branch | + | |
- | - Create merge request to develop | + | |
- | - Get someone from the product team, or the module owner to review your changes | + | |
- | - After successful review, ask module owner to merge you code | + | |
- | Rules for code review: | + | ==== Identity complex |
- | * There are [[tutorial: | + | |
- | * All features are documented - the report | + | |
- | * Changelog is updated | + | |
- | <note important> | + | This report allows you to export complex information about users, their contract and their identity form values (EAVs). [[devel: |
- | * When developing, use our standard gitflow: | + | ==== Complex report |
- | * Branch per feature. Branch naming as usual. | + | |
- | * Develop on top of the '' | + | |
- | * Master branch contains tagged releases. | + | |
- | * The **only** way for code to get into master is by pull request '' | + | |
- | * Release process | + | This report allows you to export complex information about users, their contract |
- | - After merging all features wanted for the release, one (selected) developer builds the develop. If it builds fine and tests are also OK, the developer edits module version in the '' | + | |
- | - Developer creates pull request on GitHub to merge '' | + | |
- | - Repo admin (or any other authorized user) reviews the pull request, can request changes if necessary. Unresolved TODOs, missing comments, bad codestyle or documentation, suspected bugs, etc. - all those things can be grounds for change request. | + | |
- | - If the pull request is OK, repo admin merges it. | + | |
- | - Repo admin creates a new release in GitHub interface, version is set to '' | + | |
- | - After release, repo admin makes changes on the '' | + | |
====== Read more ====== | ====== Read more ====== | ||
Line 64: | Line 58: | ||
* [[tutorial: | * [[tutorial: | ||
===== Devel guide ===== | ===== Devel guide ===== | ||
+ | * [[devel: | ||
* [[devel: | * [[devel: | ||
* [[devel: | * [[devel: | ||
===== Devel tutorials ===== | ===== Devel tutorials ===== | ||
* [[ tutorial: | * [[ tutorial: |