Defect #2385
closed
Audit of role requests - cannot filter by date, approvers are not displayed
90%
Description
Version 10.4.1
Audit -> Requests for roles
When filter by Date is selected, the page returns an error "Filter for attribute [face] not found." 
Also, the column "Can solve" is always empty in this table, even if there are approvers of the task (which is visible on the task detail). There are 2 places:
Dashboard of the logged user:
Audit of Role requests:
Files
Related issues
Updated by Vít Švanda over 4 years ago
- Assignee changed from Radek Tomiška to Vít Švanda
- Target version set to 10.5.0
Updated by Vít Švanda over 4 years ago
Exception withing filtering by date component is caused by face property (TODAY for example) sending to BE. For this property doesn't exist filter and filter checker throw exception.
I will remove face property form filter query (is not uses now).
But better solutions for you now is turn off this filter checker:
idm.sec.core.filter.check.supported.enabled=false
Commit: https://github.com/bcvsolutions/CzechIdMng/commit/64066728077cef932aa2fbce804fa91cb789e501
Updated by Vít Švanda over 4 years ago
- File role-request-can-solved.png role-request-can-solved.png added
- Status changed from In Progress to Needs feedback
- Assignee changed from Vít Švanda to Alena Peterová
Second problem with empty column "Can solve":
It works for me, solvers are shown. But I maybe know where is you problem. I think your request isn't approve by main WF process, but by some subprocess. By default, the column on request table shown approvers for main process only. Approvers are show on the request detail, because extra feature for show all approvers includes subprocess too was implemented here. Reason why, aren't all approvers show in table too, is performance (query can be very expensive here). I know, this is confused for user (I spent long time with debuging it today too).
Updated by Alena Peterová over 4 years ago
- Assignee changed from Alena Peterová to Vít Švanda
You are right, this was a subprocess for a role with criticality 2. There were no other types of requests in this project.
I understand it's for performance reasons and it can't solved for now.
Maybe you could add some additional info to the column header? So nobody else will lose their time trying to understand, why it's empty, as we did? :-) My main concern is the dashboard, which is the place where I noticed it first when I was logged as a common user.
Updated by Alena Peterová over 4 years ago
Alena Peterová wrote:
Maybe you could add some additional info to the column header? So nobody else will lose their time trying to understand, why it's empty, as we did? :-) My main concern is the dashboard, which is the place where I noticed it first when I was logged as a common user.
Or put there clickable "..." and after clicking, it will load the approvers from the subprocesses for the specific request, as it is on the task request detail. That would be nice :-)
Updated by Vít Švanda over 4 years ago
- Assignee changed from Vít Švanda to Radek Tomiška
- % Done changed from 0 to 90
Updated by Radek Tomiška over 4 years ago
- Assignee changed from Radek Tomiška to Vít Švanda
- Affected versions 10.4.0, 10.4.1 added
I skipped validation for 'face' attribute on BE. The previous solution does not save filled filter in redux.
Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/b0ce69de704fdeee1fab11d444d64b4d7040d269
Could you provide me a feedback, please?
Updated by Radek Tomiška over 4 years ago
- Related to Task #2282: Filter: Throw exception, when no registered filter is found added
Updated by Vít Švanda over 4 years ago
- Status changed from Needs feedback to Closed
- Assignee changed from Vít Švanda to Radek Tomiška
I did review and tested it. Thanks for this fix.