Actions
Task #2202
closed
Main form definition consistency solved on service level.
Start date:
04/08/2020
Due date:
% Done:
100%
Estimated time:
9.00 h
Owner:
Description
In general, there should be just 1 form definition with Main flag of a given type if it exists. This task has been already solved in task #2108 on the FE level and by protection from deleting in particular delete processor. Applying this rule generally is much complicated task because there exist parts in IdM using form definitions but where maintaining main definition doesn't make sense.
Related issues
Updated by Ondrej Husník about 4 years ago
- Category set to Eav
- Assignee set to Ondrej Husník
Updated by Radek Tomiška about 4 years ago
- Related to Defect #2108: Unchecking "Main definition" check box in Form definition causes IdM doesn't start added
Updated by Ondrej Husník about 4 years ago
- Status changed from New to In Progress
Updated by Radek Tomiška almost 3 years ago
- Status changed from In Progress to New
- Assignee changed from Ondrej Husník to Radek Tomiška
- Target version set to 11.2.0
Updated by Radek Tomiška over 2 years ago
- Status changed from New to In Progress
Updated by Radek Tomiška over 2 years ago
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Ondrej Husník
- % Done changed from 0 to 90
Validation is moved into service layer, commit:
https://github.com/bcvsolutions/CzechIdMng/commit/7a2af9de05c9e55e0544c9aace8f415cebcedd00
Could you provide me a feedback, please?
Updated by Ondrej Husník over 2 years ago
- Status changed from Needs feedback to Resolved
- Assignee changed from Ondrej Husník to Radek Tomiška
- % Done changed from 90 to 100
Tested via rest api. The main definition cannot be deleted whereas ordinary definition can. Works fine.
Updated by Radek Tomiška over 2 years ago
- Status changed from Resolved to Closed
Actions