Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Workspace] Implement "All use case" functionality #7319

Closed
wanglam opened this issue Jul 19, 2024 · 0 comments
Closed

[Workspace] Implement "All use case" functionality #7319

wanglam opened this issue Jul 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@wanglam
Copy link
Contributor

wanglam commented Jul 19, 2024

Is your feature request related to a problem? Please describe.

This is a feature request related to the use case selection behavior within workspaces. In current version, users can select multiple use cases for a specific workspace. However, in the upcoming version, the selection will be limited to a single use case per workspace. We also provide an "all use case" option to select multi use cases for user.

Describe the solution you'd like

  • Store selected use case in features property
    The workspace already support store selected use cases in the workspace saved object's features property. We are going to using the same property to store the selected use case. The first use case in features array will be treated as the selected use case.

  • Change workspace use case selector to single selection
    The WorkspaceUseCase component take an use case array before. It will change to only accept a string value. It will call an onChange with selected use case id after use case card been selected. The features property in workspace saved object will be updated after selected use case changed.

  • Not update nav group to hidden and application to inaccessible
    The navGroupUpdater and appUpdater will be executed when enter specific workspace. The nav group should not been updated to hidden if workspace using all use case. All registered nav groups should be visible. The application should not been inaccessible if application id inside any of registered use cases and current workspace using all use case.

Describe alternatives you've considered

N/A

Additional context

#4944

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant