Thanks for the info and link. Our webmaster runs compaction weekly and
was noticing the numbers steadily increasing and was wondering how the
naming conventions would be handled since we're up around 64832.
We're in the process of migrating to Touch UI and hope to be fully
converted by end of June. In the meantime, our authoring team is still
using the Classic UI. I just discovered an issue with the
html5smartimage widget type where the renditionSuffix property doesn't
get picked up by the widget once it's set. I'm able to set the
fallbackRenditionSuffix and it works, but not the renditionSuffix
Arun,I am aware of how to implement show/hide logic for widgets within a
dialog. That's not what i'm asking about here. I'm referring to the
specific showhide xtype which handles show/hide logic for the HTML
elements in a web form, not widgets in a dialog. The values captured in
this xtype are passed along to the Abacus JS which handles form logic
for components that extend OOTB form field components. Below is a
screenshot of the showhide xtype. Clicking that checkbox in the
background dialog op...
Hey Arun,Thanks for the reply but the examples provided won't work for
this scenario. The showhide is an OOTB xtype. It is used to capture the
show/hide logic for fields within a web form instead show/hide logic for
widgets within a dialog.
We're in the process of converting all of our Classic UI dialogs to
Touch UI using the dialog conversion tool. We're using the showhide
xtype in a lot of our form field components and we're looking for an
equivalent or alternative widget for the Touch UI. Any suggestions?