Collapsible sections

Certified Lead Developer

Hi

Here is my scenario,

I am having section layouts in a interface both were collapsible initially,

When I select the one section it has to expand as usual, Same manner when I select the second section it should expand and other section should go back to collapsible state,

I looking for suggestions to done my task

  Discussion posts and replies are publicly visible

Parents
  • Hey srinivas.

    There is no built in functionality for this. I would recommend pushing back against the requirement if possible, because any work-around you do will contrast with any other collapsible sections in your app.

    If that is not an option, I think that the best way to do this would be to use a!dynamicLink within an a!richTextItem to make a fake section header. You can set the style of the richTextItem to "HEADER_MEDIUM" or "HEADER_LARGE" to get something similar to a section header. The saveIntos should be similar to Rakesh's example. I think having a Link replace the section header would look a bit better, and be a bit more intuitive than having buttons near the section headers.

    I don't recommend doing this, but if you have to fulfill the requirement it should work.

    Thanks,
    Jake
  • Srinivas,

    I agree with Jake that pushing back on the requirement is the best course of action. If you need additional fodder to push back with, one of the biggest drawbacks to the dynamicLink approach is that if you have any validations within the sections, the user would be able to submit the form despite a failed validation if they hide the section in error, whereas the isCollapsible parameter of Appian would ensure that all validations are mitigated before submission. For this reason, the dynamicLink option is possible, but not scalable or in adherence to best practices. There are ways around this, by creating a separate validation framework within a with() statement, but it is over-engineering and is not very maintainable.

    With all of that being said, if you must move forward with the requirement, I agree with Jake's idea of the HEADER_MEDIUM richTextItem.

    Best,
    Ashvin
Reply
  • Srinivas,

    I agree with Jake that pushing back on the requirement is the best course of action. If you need additional fodder to push back with, one of the biggest drawbacks to the dynamicLink approach is that if you have any validations within the sections, the user would be able to submit the form despite a failed validation if they hide the section in error, whereas the isCollapsible parameter of Appian would ensure that all validations are mitigated before submission. For this reason, the dynamicLink option is possible, but not scalable or in adherence to best practices. There are ways around this, by creating a separate validation framework within a with() statement, but it is over-engineering and is not very maintainable.

    With all of that being said, if you must move forward with the requirement, I agree with Jake's idea of the HEADER_MEDIUM richTextItem.

    Best,
    Ashvin
Children
No Data