Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
tutorial:adm:report_compare_value_idm_to_system [2019/09/11 09:05]
stloukalp 		tutorial:adm:report_compare_value_idm_to_system [2019/09/12 07:56]
stloukalp corected using overrided script
Line 17: Line 17:
   * Select report 'Compare values in IdM with values in system'   * Select report 'Compare values in IdM with values in system'
   * And now we need **system** we want compare values with, it is select box, so you can select right one from list of all connected system   * And now we need **system** we want compare values with, it is select box, so you can select right one from list of all connected system
-  * **Attributes** - we need identificators of mapped attributes separated by comma. If attribute has transformation script, after identificator of attribute write colon and code of script.+  * **Attributes** - we need identificators of mapped attributes separated by comma. Scripts in transformation are applied too.
   * **Mapping** - we need ID of mapping, where theese attributes are defined.   * **Mapping** - we need ID of mapping, where theese attributes are defined.
   * **Treenode** - you will select identities in this organization and identities in child organizations   * **Treenode** - you will select identities in this organization and identities in child organizations
Line 28: Line 28:
 {{ :tutorial:adm:comparereport_03.png |}} {{ :tutorial:adm:comparereport_03.png |}}
  
-  * Click on **Mapping**+  * Click on tab **Mapping**
   * There are attributes mapping, could there be more, specifically for synchronization, but rather select one for provisoning.   * There are attributes mapping, could there be more, specifically for synchronization, but rather select one for provisoning.
   * Click again on 'magnifying glass' button.   * Click again on 'magnifying glass' button.
Line 43: Line 43:
  
   * ID of this attribut is again in URL in your browser, copy it somewhere too.   * ID of this attribut is again in URL in your browser, copy it somewhere too.
 +  * You can copy more ID's of attributes from same mapping.
  
 {{ :tutorial:adm:comparereport_07.png |}} {{ :tutorial:adm:comparereport_07.png |}}
- 
-  * Look down on this page, if there is **Transformation to system** script. 
-  * Yeah we got one here, but we cannot directly use this script, because there can be used 'script authorities' and we need to use this workaround. 
-  * Copy that call of script 'displayNameScript'. 
- 
-{{ :tutorial:adm:comparereport_08.png |}} 
- 
-  * Click on **Setting** and **Script definitions** and click on **Add** 
- 
-{{ :tutorial:adm:comparereport_09.png |}} 
- 
-  * Past in call of that script, let it in Standard category. Write in description something like 'this script is used in report' and write code and script name. 
-  * Click on **Save and continue**. 
-  * Now you can copy more ID's of attributes from that mapping. 
- 
-{{ :tutorial:adm:comparereport_10.png |}} 
  
   * If you want get ID of tree node, click on **Organization** and on tab **Structure elements** click on 'magnifying glass' button of one of shown tree nodes.   * If you want get ID of tree node, click on **Organization** and on tab **Structure elements** click on 'magnifying glass' button of one of shown tree nodes.
Line 72: Line 57:
   * Now we have all necessary ID's, so we return to creating new 'Compare values in IdM with values in system'   * Now we have all necessary ID's, so we return to creating new 'Compare values in IdM with values in system'
   * Select System (the right one, which has the mapping we used)   * Select System (the right one, which has the mapping we used)
-  * Write in ID's of attributes as in picture bellow (like ID:scriptCode,ID,ID,ID:scriptCode2,ID)+  * Write in ID's of attributes as in picture bellow (seperated by comma)
   * Past Mapping ID   * Past Mapping ID
   * You can past tree node or as in our example select a fet identities.   * You can past tree node or as in our example select a fet identities.
   * Click on **Generate report**   * Click on **Generate report**
  
-{{ :tutorial:adm:comparereport_13.png |}}+{{ :tutorial:adm:comparereport_16.png |}}
  
   * Now report is generating, it could take a few minutes, based on how many attributes and how many identities are selected.   * Now report is generating, it could take a few minutes, based on how many attributes and how many identities are selected.
Line 96: Line 81:
    
 {{ :tutorial:adm:comparereport_15.png |}} {{ :tutorial:adm:comparereport_15.png |}}
 +
 +====Override script====
 +If you write new a script and want to change the current one, but it is in production. You can use this report, so you can be sure nothing bad happens. You can make report with the attribute and different script. Report will compare value transformed with this new script and value stored in system and you will have confirmation about changes that would happen.
 +
 +  * Click on **Setting** and **Script definitions** and click on **Add**
 +
 +{{ :tutorial:adm:comparereport_09.png |}}
 +
 +  * You need here call that new script, which will override the current one. You can generate it in mapped attribut or copy existing one and and edit it. So write in call of that new script.
 +  * Let it in Standard category.
 +  * Write in description something like 'this script is used in report'.
 +  * write code and script name.
 +  * Click on **Save and continue**.
 +
 +{{ :tutorial:adm:comparereport_10.png |}}
 +
 +  * Again fill in System and mapping ID's
 +  * Fill in attributes ID's, but after attribute ID, which you want override script, write colon and code of script like ID:newScriptCallScript (look bellow on picture)
 +
 +{{ :tutorial:adm:comparereport_13.png |}}
  
 Thank you for reading this tutorial and I hope this tutorial and report is useful for you. Thank you for reading this tutorial and I hope this tutorial and report is useful for you.
  • by doischert