Project

General

Profile

Actions

Task #2105

closed

Dynamic form for identities

Added by Radek Tomiška about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Radek Tomiška
Category:
Frontend
Target version:
Start date:
03/09/2020
Due date:
% Done:

100%

Estimated time:
Owner:

Description

Feature will cover requirement to configure different form to create and edit different type of identity (externist vs. internist):
- new field with type (~codelist) will be added to identity - will control, which form will be used
- identity type can be switched - new identity permission will be added
- new type can be registered (~by codelist item)
- when new identity is created, then modal window with available identity types will be shown. If only one type is available => then form will be shown imediatelly (=> default / current form will be shown).


Files

projection_one_full.png (88.8 KB) projection_one_full.png Vít Švanda, 04/03/2020 01:26 PM
projection_one.png (76.9 KB) projection_one.png Vít Švanda, 04/03/2020 01:26 PM

Related issues

Related to IdStory Identity Manager - Task #2153: Autorization policies - add evaluator by user type (projection)ClosedRadek Tomiška03/26/2020

Actions
Related to IdStory Identity Manager - Task #2154: Automatic roles: Support user type field (projection) in automatic role by attributeClosedRadek Tomiška03/26/2020

Actions
Related to IdStory Identity Manager - Task #2155: Support user type field (projection) in synchronization and provisioningClosedVít Švanda03/26/2020

Actions
Related to IdStory Identity Manager - Task #2162: Bulk action - change user type (projection)ClosedOndrej Husník03/30/2020

Actions
Related to IdStory Identity Manager - Task #2163: Authorization policies - support secured contract eav attributes by defaultClosedRadek Tomiška03/30/2020

Actions
Related to IdStory Identity Manager - Task #2164: Authorization policies - support secured identity eav attributes by defaultClosedRadek Tomiška03/30/2020

Actions
Related to IdStory Identity Manager - Task #2165: Authorization policies - check change user type permission on backendClosedRadek Tomiška03/30/2020

Actions
Related to IdStory Identity Manager - Defect #2190: Read only on form doesn't work properly - AbstractFromClosedVít Švanda04/06/2020

Actions
Related to IdStory Identity Manager - Feature #891: Identity templates moduleClosedRadek Tomiška01/04/2018

Actions
Related to IdStory Identity Manager - Defect #2567: Automatic role by EAV is not assigned when setting the EAV together with entity (e.g. through form projection)ClosedRadek Tomiška11/09/2020

Actions
Actions #1

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2153: Autorization policies - add evaluator by user type (projection) added
Actions #2

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2154: Automatic roles: Support user type field (projection) in automatic role by attribute added
Actions #3

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2155: Support user type field (projection) in synchronization and provisioning added
Actions #4

Updated by Radek Tomiška about 4 years ago

  • % Done changed from 0 to 80
Actions #5

Updated by Radek Tomiška about 4 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Vít Švanda
  • % Done changed from 80 to 90
Actions #6

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2162: Bulk action - change user type (projection) added
Actions #7

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2163: Authorization policies - support secured contract eav attributes by default added
Actions #8

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2164: Authorization policies - support secured identity eav attributes by default added
Actions #9

Updated by Radek Tomiška about 4 years ago

  • Related to Task #2165: Authorization policies - check change user type permission on backend added
Actions #10

Updated by Radek Tomiška about 4 years ago

Fixed review notes:
- authorities was evaluated only on form projection => permissions were ignored
- user type is removed from basic fields available for form projection
- username is required for updata by projection (the same behavior as defaul form)
- doc improved, update identity permission is needed to submit projection form (can be improved in future)

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/e8b7d45802711ceb48a093a9b8bbf840eaa6f632

Actions #11

Updated by Vít Švanda about 4 years ago

I did review and test. This is very big and complex feature. Works nice and code looks also nice. Nice tutorial! Thanks for this.

I tested again the issues we consulted and what you fixed. Everything works well now, expect one thing:

If my user can updated his identity full detail (firstname...), then projection detail can be saved, but identity fields are read-only.

Notes:

  • Role with attributes are not fully supported for create new identity now. Maybe warning in the wiki should be created for it.
  • You changed version of the selectbox from 1.3 to 1.2. I was a intent?
  • Wiki: Should be not IdmFormDefiniton: Permission to autocomplete form projections: Forms - projections(IdmFormDefiniton) | View in select box (autocomplete) | BasePermissionEvaluator
Actions #12

Updated by Vít Švanda about 4 years ago

  • Related to Defect #2190: Read only on form doesn't work properly - AbstractFrom added
Actions #13

Updated by Vít Švanda about 4 years ago

My issues with wrong read only form, is related to AbstractForm and will be solved within #2190. I have removed the readOnly property "workaround". The form now works correctly.

Actions #14

Updated by Radek Tomiška about 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Thx for help! I retest permissions again and workaround works.

Actions #15

Updated by Radek Tomiška about 4 years ago

  • Status changed from Resolved to Closed
Actions #16

Updated by Radek Tomiška about 4 years ago

Actions #17

Updated by Radek Tomiška over 3 years ago

  • Related to Defect #2567: Automatic role by EAV is not assigned when setting the EAV together with entity (e.g. through form projection) added
Actions

Also available in: Atom PDF