[GH-ISSUE #65] Implement Smart Filtering for Configuration Codes #21

New issue

Open

opened 2026-03-03 11:58:26 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 11:58:26 +03:00

Owner

Originally created by @olegprivate on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/finmars-platform/finmars-core/issues/65

Originally assigned to: @falendary on GitHub.

Is your feature request related to a problem?
When creating a new configuration meta-entity, the selection of a "configuration code" is not optimized for the user's role or history. All users see all codes, which can be overwhelming and lead to errors. We need a smarter, permission-aware filtering system to simplify this selection process for different user types.

Describe the solution you'd like
We propose implementing a new system for displaying and selecting configuration codes. This system will default to a "local" code for new users, prioritize recently used codes for existing users, and restrict the visibility of the full list based on user permissions (Admin or special role), with a "more" button to reveal all options for privileged users.

User Story
As a user creating a configuration meta-entity, I want the list of configuration codes to be intelligently filtered based on my permissions and past activity, so that I can quickly and easily select the correct code without being exposed to irrelevant or restricted options.

Acceptance Criteria

Default Behavior for New Configurations
Given a user is creating their very first configuration meta-entity in a Workspace.
Then the "Configuration Code" dropdown should default to the "local" configuration code.
"Recently Used" Default for Existing Workspaces

Given a user has previously created configurations using various configuration codes within the Workspace.
When they create a new configuration meta-entity.

Then the "Configuration Code" dropdown should default to the most recently used code by that user.
And the dropdown list should contain other codes they have previously used, with "local" also being an option.

View for Standard Users (No Special Permissions)
Given a user is not an Admin and does not have special permissions to view all configuration codes.
When they create a new configuration meta-entity.
Then the list of available configuration codes in the dropdown must be limited to:

The "local" code.
Any other configuration codes they have explicitly created or used before in their Workspace.

And they must not see an option to view the full list of system-wide configuration codes.

Extended View for Admins and Privileged Users
Given a user is an Admin or has a specific permission role (e.g., can_view_all_configs).

When they access the "Configuration Code" dropdown.

Then they will initially see the same filtered list as a standard user (recently used, local).

And a "More..." button or link should be visible below the standard list.

When the privileged user clicks "More...".

Then the list should expand to show the full list of all available configuration codes in the system.

Originally created by @olegprivate on GitHub (Jul 22, 2025). Original GitHub issue: https://github.com/finmars-platform/finmars-core/issues/65 Originally assigned to: @falendary on GitHub. **Is your feature request related to a problem?** When creating a new configuration meta-entity, the selection of a "configuration code" is not optimized for the user's role or history. All users see all codes, which can be overwhelming and lead to errors. We need a smarter, permission-aware filtering system to simplify this selection process for different user types. **Describe the solution you'd like** We propose implementing a new system for displaying and selecting configuration codes. This system will default to a "local" code for new users, prioritize recently used codes for existing users, and restrict the visibility of the full list based on user permissions (Admin or special role), with a "more" button to reveal all options for privileged users. **User Story** As a user creating a configuration meta-entity, I want the list of configuration codes to be intelligently filtered based on my permissions and past activity, so that I can quickly and easily select the correct code without being exposed to irrelevant or restricted options. **Acceptance Criteria** 1. Default Behavior for New Configurations Given a user is creating their very first configuration meta-entity in a Workspace. Then the "Configuration Code" dropdown should default to the "local" configuration code. 2. "Recently Used" Default for Existing Workspaces Given a user has previously created configurations using various configuration codes within the Workspace. When they create a new configuration meta-entity. Then the "Configuration Code" dropdown should default to the most recently used code by that user. And the dropdown list should contain other codes they have previously used, with "local" also being an option. 3. View for Standard Users (No Special Permissions) Given a user is not an Admin and does not have special permissions to view all configuration codes. When they create a new configuration meta-entity. Then the list of available configuration codes in the dropdown must be limited to: - The "local" code. - Any other configuration codes they have explicitly created or used before in their Workspace. And they must not see an option to view the full list of system-wide configuration codes. 4. Extended View for Admins and Privileged Users Given a user is an Admin or has a specific permission role (e.g., can_view_all_configs). When they access the "Configuration Code" dropdown. Then they will initially see the same filtered list as a standard user (recently used, local). And a "More..." button or link should be visible below the standard list. When the privileged user clicks "More...". Then the list should expand to show the full list of all available configuration codes in the system.