Skip to content

Conversation

@sei-vsarvepalli
Copy link
Contributor

Resolves bug in #943, changes to ensure mapping and data updates are properly done to match set variable.

@sei-bkoo
Copy link
Contributor

Adding a custom decision point works but saving it requires that the "Namespace" field be filled.
Since not all users will be immediately familiar with registered namespaces, suggesting that the namespace field be automatically default to the "x_<some_string>" format.

Screenshot 2025-09-11 at 11 15 59 AM

@sei-bkoo sei-bkoo closed this Sep 11, 2025
Copy link
Contributor

@sei-bkoo sei-bkoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good but as mentioned in my comment, suggest defaulting to the "x_<some_string>" format for namespace field

@sei-bkoo
Copy link
Contributor

Namespace field automatically populates when clicking Customize to create a custom decision model, but as soon as you add a custom decision point, the Namespace field becomes empty.

@sei-vsarvepalli
Copy link
Contributor Author

Namespace field automatically populates when clicking Customize to create a custom decision model, but as soon as you add a custom decision point, the Namespace field becomes empty.

This should be resolved also now.

Copy link
Contributor

@sei-bkoo sei-bkoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice everything is working as expected now, with auto-populating default namespace for custom decision models to boot!

@sei-vsarvepalli sei-vsarvepalli merged commit b906d51 into main Sep 12, 2025
4 checks passed
@sei-vsarvepalli sei-vsarvepalli deleted the bugfix_944 branch September 12, 2025 00:10
@ahouseholder ahouseholder added this to the 2025-09 milestone Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants