Project

General

Profile

Actions
Copy link

Task #1247

closed

Info components - optimize number of request to backend

Added by Radek Tomiška over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Radek Tomiška
Category:
Frontend
Target version:
Jade (8.1.7)
Start date:
09/10/2018
Due date:
% Done:

100%

Estimated time:
Owner:

Description

When info component without entity is rendered on front end, then request to load entity is send to backend. When more info components (10+) are one the one page, then browser is stuck for a while.
Find and implement a way, how to show more info component on the one page:
- prepare entities on the backend
- use some request queue on frontend.

Related issues

Related to IdStory Identity Manager - Task #978: Dto mappers - new layerClosedRadek Tomiška02/21/2018

Actions
Related to IdStory Identity Manager - Defect #1276: Cannot manually link accountClosedRadek Tomiška09/27/2018

Actions
Related to IdStory Identity Manager - Defect #1313: Dashboard not loading after loginClosedRadek Tomiška10/11/2018

Actions
Related to IdStory Identity Manager - Defect #1835: GUI sometime freezing when new role-request should be createdClosedRadek Tomiška09/05/2019

Actions
Actions
Copy link
 #1

Updated by Radek Tomiška over 5 years ago

  • Related to Task #978: Dto mappers - new layer added
Actions
Copy link
 #2

Updated by Radek Tomiška over 5 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Ondřej Kopr
  • % Done changed from 0 to 80
Both ways were improved:
  • Entity was added into embedded json on BE, when it was possible:
    • Audit - both
    • Virtual system requests
    • Accounts on target system
    • Provisioning queue
    • Events
    • Role requests
    • LRT items and queue
  • Request queue on FE was implemented - loading entities info cards and permissions are put into queue (max 3 simultaneous request are executed):
    • wf definitions
    • managers info component
    • wf candidate info component

Commits:
https://github.com/bcvsolutions/CzechIdMng/commit/7aad1497fb260485bf43a7d44316055a4672088d
https://github.com/bcvsolutions/CzechIdMng/commit/086c6d967a5433055fcf249b10ec84beca9d6665

Could you do a feedback pls, if all contents (or add missing content) are ok?

Actions
Copy link
 #3

Updated by Ondřej Kopr over 5 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Radek Tomiška
  • % Done changed from 80 to 100

Thank you very much!! This is probably main feature/fix for the hotfix. Thank you. Now is possible run 100 record with entity info components. Very nice thing is that any request to backend was send, this is goood. Thank you.

Actions
Copy link
 #4

Updated by Ondřej Kopr over 5 years ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #5

Updated by Radek Tomiška over 5 years ago

  • Related to Defect #1276: Cannot manually link account added
Actions
Copy link
 #6

Updated by Radek Tomiška over 5 years ago

  • Related to Defect #1313: Dashboard not loading after login added
Actions
Copy link
 #7

Updated by Radek Tomiška over 4 years ago

  • Related to Defect #1835: GUI sometime freezing when new role-request should be created added
Actions
Copy link

Also available in: Atom PDF