Add counter for subscriptions with invalid states - summary card

workfloworchestrator / orchestrator-ui-library

Component library for the orchestrator-ui (v2) which is published in npm

8 stars 4 forks source link

Add counter for subscriptions with invalid states - summary card #93

Closed wouter1975 closed 8 months ago

wouter1975 commented 1 year ago

Summary

At the moment all FW subscriptions are out of sync, while there is no failed validation task reported. This is a blind spot. It would be good to flag subscriptions which are out of sync AND active or initial and without a failed validation task or running WF.

[x] Add at the start page as a new summary card. Use red X icon
[x] TitleTotal out-of-sync subscriptions: #
[ ] Clicking this bottom button brings you to the subscription list page filtered on status active or initial and out of sync subscriptions.
[ ] nice to have - all good placeholder when subscriptions are in sync (can be reused for failed task as well) use 🚀 or something

hanstrompert commented 1 year ago

Instead of adding yet another counter, wouldn’t it be better to fix the validation for that specific product so it will go out of sync and show up in the existing out of sync counter?

wouter1975 commented 1 year ago

These subscriptions will not undergo a regular/daily validation WF, for example because the validation WF was aborted. We could consider a generic validation task which checks the existence of out of sync AND active or initial. In that way we could indeed also flag this. Only drawback might that this validation task is not out of the box available for all orchestrator users.

hanstrompert commented 1 year ago

The orchestrator was designed to give you the tools to keep all your administration correct. The abort button was intended to be used only as measure of last resort. When the abort button is used, either on a workflow or a task, all related data must be checked manually, that includes the data in the coreDB, all OSS en BSS and provisioning system(s). The users of the orchestrator should be aware of this, and this should be included in their MOPs. The abort button should only be used by experienced users. There is the possibility to show the abort button to experienced users only to help prevent accidental use.

Adding an extra icon does not help much here, the MOPs would still need to be updated with the instructions to solve the problem. This would have been the same instructions that should already be part of the MOP when pressing the abort button.