Page Comparison

...

1. When a user tries to create any course from the workspace:
   

   Image RemovedImage Added

Since, SH-3, we have segregated the create workflow into two parts:

...

So, When the user goes to the “Trainings” page, we won’t make the API call again.

Challenges:

Pros: This is an existing workflow. To be easy to implement.

Cons: Now going forward with this approach, all the creation related to training should take this custom framework (if any). Whether it is just a content creation from the training sub-tab or copying of a course or front-end creation of a curriculum course. Changes have to be done in all the places.

Solution 2 :

To get a new API which will give list of frameworks tagged with a tenant.

We, from the portal side, will call this API in the first place to get the list of frameworks and use these frameworks accordingly.

...

Pros: We will get the list of frameworks in the very first place.

Cons: Dependency on the back-end team to create this new API.

Solution 3:

We can have the list of frameworks in the getTenantInfo which we also call when the portal is loaded for the first time.