Differences

This shows you the differences between two versions of the page.

--- devel:documentation:modules_reports [2020/03/11 11:14]
doischert
+++ devel:documentation:modules_reports [2021/05/31 11:27]
doischert
@@ Line 9: / Line 9: @@
 {{ :devel:documentation:rpt.png | [reports] and [rpt] modules}}
-The module is fully dependent on [[devel:documentation:modules_rpt|reports [rpt]]] module and only contains implemented reports, not the logic of creating reports in general.
+The module is fully dependent on the [[devel:documentation:modules_rpt|reports [rpt]]] module and only contains implemented reports, not the logic of creating reports in general.
 ====== Overview of implemented reports ======
@@ Line 16: / Line 16: @@
 This report allows you to export the list of identities together with their assigned roles. [[devel:documentation:modules_reports:reports:identities_and_their_roles|Learn more]]
+==== 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:documentation:modules_reports:reports:identity_role_complex_report|Learn more]]
 ==== Roles and their identities ====
@@ Line 23: / Line 27: @@
 ==== Identities, their main contract and their roles ====
-This report allows you to export the list of identities (with information about their contracts, incl. one contract EAV) together with their assigned roles. [[devel:documentation:modules_reports:reports:identities_their_main_contract_and_their_roles|Learn more]]
+This report allows you to export the list of identities (with information about their contracts, incl. one contract EAV) together with their assigned roles (and values of role attributes). [[devel:documentation:modules_reports:reports:identities_their_main_contract_and_their_roles|Learn more]]
-===== Developing and releasing =====
+==== Identities and their assigned roles changes ====
-How to develop a new feature in reports:
-  - Create a specification page in private section and consult it with module owner and other colleagues (on Slack). Specification page should contain:
+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:documentation:modules_reports:reports:identities_and_their_automatically_assigned_roles_changes|Learn more]]
-   - 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 can be a part of the module and in which version it will be published
-  - 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:
+==== Identities and their password changes on a system ====
-  * There are [[tutorial:dev:create_report|tests]] (test coverage of 80% for reports is hard to achieve but do your best)
-  * All features are documented - the report is mentioned above and has a dedicated page describing its use and configuration
-  * Changelog is updated
-<note important>If your code does not meet the requirements mentioned above, it may be rejected.</note>
+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:documentation:modules_reports:reports:identities_and_their_password_changes_on_a_system|Learn more]]
-  * When developing, use our standard gitflow:
+==== Identities and their system account (state) changes ====
-    * Branch per feature. Branch naming as usual.
-    * Develop on top of the ''develop''.
-    * Master branch contains tagged releases.
-    * The **only** way for code to get into master is by pull request ''develop -> master''.
-  * Release process
+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,and success of the change. [[devel:documentation:modules_reports:reports:identities_and_their_system_account_changes|Learn more]]
-    - 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 ''pom.xml'' file and sets it to ''X.Y.Z''.
-    - Developer creates pull request on GitHub to merge ''develop -> master''.
-    - 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 ''X.Y.Z'' to correspond with version set in project sources.
-    - After release, repo admin makes changes on the ''develop'' branch: upps module version to ''X(+1).Y(+1).Z(+1)-SNAPSHOT'' in the ''pom.xml'' and ''package.json''. What the next version of the module will be is up to discussion preceding the release.
 ====== Read more ======
@@ Line 64: / Line 46: @@
   * [[tutorial:adm:modules_reports| Reports module [rpt] - How to create a report]]
 ===== Devel guide =====
+  * [[devel:documentation:modules_reports:developing_and_releasing|Developing and releasing in the module reports]]
   * [[devel:documentation:modules_rpt:dev:report_manager|How reports work]]
   * [[devel:documentation:modules_rpt:dev:attachment_manager|Attachment manager]]
 ===== Devel tutorials =====
   * [[ tutorial:dev:create_report | Create a report ]]