-
Notifications
You must be signed in to change notification settings - Fork 42
Bugfix 943 #945
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
Bugfix 943 #945
Conversation
|
Adding a custom decision point works but saving it requires that the "Namespace" field be filled.
|
sei-bkoo
left a comment
There was a problem hiding this 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
|
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. |
sei-bkoo
left a comment
There was a problem hiding this 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!

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