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 		Previous revision
tutorial:adm:user-type [2020/05/03 21:13]
tomiskar 		tutorial:adm:user-type [2021/03/30 09:48] (current)
husniko
Line 17: Line 17:
   * Module - we can leave it empty, **core** module is used by default.   * Module - we can leave it empty, **core** module is used by default.
   * Frontend target - we can leave it by default **/form/identity-projection**. This target leads to prepared product projection page on frontend. Only developer can register new target page.   * Frontend target - we can leave it by default **/form/identity-projection**. This target leads to prepared product projection page on frontend. Only developer can register new target page.
-  * Basic attributes - select  **User name**, **First name**, **Surname**.+  * Basic user attributes - select  **User name**, **First name**, **Surname**, **Personal number**. 
 +  * Basic contract attributes - select  **Work position**, **Valid from**, **Valid till**. 
 +  * Basic attributes validation - configure validations for fields: 
 +    * **Personal number** - required, minimum and maximum length **5** (~ 5 letters only) 
 +    * **Valid till** - required, minimum contract validity **0** (~ current date), maximum contract validity 385 days (~ 13 monts in future). Sometimes it is demanded to avoid the possibility to set empty date for contract which means unlimited. Then it is advised to set validation of such attribute also as **required**.
   * Form definitions - we need to prepare extended attributes form definition before to use then here, we will use this definitions and attributes as example:   * Form definitions - we need to prepare extended attributes form definition before to use then here, we will use this definitions and attributes as example:
     * **default - IdmIdentity** - default form definition for users, select attributes:     * **default - IdmIdentity** - default form definition for users, select attributes:
       * **Mobile phone** - text attribute       * **Mobile phone** - text attribute
       * **Reqistration** - boolean attribute       * **Reqistration** - boolean attribute
-    * **default - default - IdmIdentityContract** - default form definition for cntracts, select attributes:+    * **default - default - IdmIdentityContract** - default form definition for contracts, select attributes:
       * **Environment** - codelist ith available environments       * **Environment** - codelist ith available environments
       * **Manager** - user select box       * **Manager** - user select box
 +  * **Set direct guarantee for new contract** - Set currently logged user as direct guarantee for newly created contract
   * Description - **Create and edit externe user.** Description is shown in projection list (into about projection and for filter).   * Description - **Create and edit externe user.** Description is shown in projection list (into about projection and for filter).
   * Inactive - inactive projection will not be available for creating new user.   * Inactive - inactive projection will not be available for creating new user.
Line 35: Line 40:
  
 <note tip>Attributes generated by system can be hidden. For example we not provide to set or change user password - we expect password will be generated after user will be provisioned on target system (one password will be set to all user account and for IdM too). Read how to [[#set_or_change_user_password|set or change user password]] by product projection.</note> <note tip>Attributes generated by system can be hidden. For example we not provide to set or change user password - we expect password will be generated after user will be provisioned on target system (one password will be set to all user account and for IdM too). Read how to [[#set_or_change_user_password|set or change user password]] by product projection.</note>
 +
 +<note tip>Configured basic field validations will be evaluated on every place in application for users in given user type (~ projection).</note>
  
 ==== Choose projection ==== ==== Choose projection ====
Line 46: Line 53:
 === User detail for create user by configuration above ==== === User detail for create user by configuration above ====
  
-{{ :devel:documentation:identities:adm:projection-user-create.png |}}+{{ :tutorial:adm:projection-user-create.png |}}
  
 We can create new user with all attributes are filled. We can choose roles, which will have to be assigned (requested) for created user. Used form (projection) is set as user type. After form is saved, the same form is shown and user can be edited if needed. The same form is used and shown as user detail. We can create new user with all attributes are filled. We can choose roles, which will have to be assigned (requested) for created user. Used form (projection) is set as user type. After form is saved, the same form is shown and user can be edited if needed. The same form is used and shown as user detail.
  
-=== User detail for edit user by configuration above ====+=== User detail for edit user by configuration above ===
  
-{{ :devel:documentation:identities:adm:projection-user-edit.png |}}+{{ :tutorial:adm:projection-user-edit.png |}}
  
 === Default full detail === === Default full detail ===
  • by tomiskar