Package Substatus #330
Replies: 2 comments 3 replies
-
If we need a single status to display differently for CMS and State: {
subStatus: [
{ cmsStatus: "...", stateStatus: "..." },
...
]
} But if we show the same substatus value and just gate each substatus to specific user types (i.e. CMS is the only one to see second clock), then we can do: {
subStatus: [
{ status: "...", allow: CMS && STATE },
{ status: "2nd Clock", allow: CMS },
...
]
} |
Beta Was this translation helpful? Give feedback.
-
Baked into opensearch:
FE controlled:
I'm sure there's more. Will edit as i find them |
Beta Was this translation helpful? Give feedback.
-
We're of the opinion that we should set sub status in the main index, rather than inferring the field in the frontend and exports.
We have at least two independent components that affect sub status
Questions
main
index?Notes
cms
vsstate
Beta Was this translation helpful? Give feedback.
All reactions