- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2024 11:29 AM - edited 07-02-2024 11:30 AM
I found a bug with variable sets.
Expected behavior: When you change the title, it'll autofill internal_name only IF EMPTY.
Actual behavior: When you change the title, it'll autofill internal_name no matter what.
The expected behavior is documented here. (We can also compare with variables since they share the same behavior)
It reads: "Note: If this field is empty, its value is auto-populated based on the Title field for all variable types except break, container split, and container end."
The root cause is in the autofill client script.
For variables, it checks if "name" is empty and if so autofills "name".
For variable sets, it checks if "name" is empty and if so autofills "internal_name".
Astute observers will have noticed that "name" != "internal_name".
variable sets: sys_script_client.do?sys_id=8bb7b06673220300f49d0690fdf6a760
variables: sys_script_client.do?sys_id=6ec988e05f0013003050802d3f731381
I've tried letting them know through a HI ticket but they keep saying it's expected behavior even though it goes against their own documentation and simple logic.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2024 02:45 AM
If technical support says it is working as designed, you should insist on an update to the documentation. Have them open a documentation task and ask for a reference number, so that you can track its status. Alternatively, you can submit feedback directly through the docs website by clicking on the feedback (thumbs up) icon in upper-right corner of the page. That will open a dialog window where you can enter your comments.
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2024 03:06 AM
Hi Guy
If Hi is saying that it is expected behaviour but the documentation doesn't match then I'd raise it on the documentation page. At the bottom of the page there's the chance to give feedback. Put your findings to them that way. I've done it a couple of times and they were fairly quick to respond.
Regards