You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When displaying the 'In-use by subscription(s)' on the subscription detail page we use the json value from that field to make a graphql call to resolve them to name, description and product name.
See:
rtk/endpoints/subscriptionDetail.ts
rtk/endpoints/subscriptionInUseByRelationQuery.ts
components/WfoSubscription/WfoInUseByRelations.tsx
This could be improved if the backend resolves the field subscriptiondetail >> producBlockInstances >> inUseByRelations with these fields instead of a json object as it is now.
The text was updated successfully, but these errors were encountered:
wouter1975
changed the title
Improve resolving of ' In-use by subscription(s)'
Improve resolving of ' In-use by subscription(s)' RT using dataloaders
Jul 8, 2024
wouter1975
transferred this issue from workfloworchestrator/orchestrator-ui-library
Jul 8, 2024
When displaying the 'In-use by subscription(s)' on the subscription detail page we use the json value from that field to make a graphql call to resolve them to name, description and product name.
See:
rtk/endpoints/subscriptionDetail.ts
rtk/endpoints/subscriptionInUseByRelationQuery.ts
components/WfoSubscription/WfoInUseByRelations.tsx
This could be improved if the backend resolves the field subscriptiondetail >> producBlockInstances >> inUseByRelations with these fields instead of a json object as it is now.
The text was updated successfully, but these errors were encountered: