cascading attributes on ticketing forms - does hidden parent mean hidden children?
I'm using cascading attributes on forms. I'd like the parent attribute to be hidden (because I'm setting it to a non-changeable default value and I want the form to not be cluttered) but I'd like the child attribute to be editable. I'm hiding the parent attribute but the child attribute also gets hidden even though I have it as editable on the form designer. Is this working as designed or am I missing a setting?
Answer (1)
Hello Greg,
I believe this is working as intended because forms as they exist today weren't built to support the idea that a parent field would ever need to have its value hidden *and still* display a cascaded child field.
If the parent field is *always* to be hidden, and *always* to be set to a certain value, why not cut it out entirely and just assume that its condition was already met to display the child field? Or just don't allow either field to be edited in the portal and force them to be modified in TDNext upon the first edit of the ticket?
Going the route of removing the parent entirely, you could add help text to (what is currently) your child attribute to inform the user whatever was useful to know about the parent field's value OR place a static field on the form above the child field to contain this info and make it not visible to the client portal if these details are only pertinent to techs in TDNext.
Sincerely,
Mark Sayers
Sr Support Consultant, CS