There has been ongoing discussion recently to enhance the features currently available in the Field Editor “Section Header” as well as provide the same type of capability (section headers) for other components in the form of a collapsible wrapper.
In dire need of this type of functionality, I wrote a custom component that solves for most (hopefully all) of the use cases I’ve seen posted and decided to share it for anyone that might find it useful.
Disclaimer:
This component is not built by nor supported by Skuid so please don’t ask them to fix anything that might be wrong with it
This component uses publicly exposed Skuid APIs, however a lot of them are not documented nor officially supported. This means that in a future release, this component might break. While it’s unlikely that this would occur, it is possible so please be aware.
This component was just finished and has not gone through a full test cycle. I did my best to use the Skuid APIs properly, however since they are not official nor documented, it’s possible that there are use cases/scenarios that I have not accounted for. If you find any issues please do let me know and I’ll try to resolve as quickly as possible.
This is written for Skuid 7.x
Ok, enough with the formalities, let’s dig in…
The Collapsible Wrapper Custom Component is the same thing as a Skuid Wrapper component except it also has a “Header” that has lots of customization options. You can show a header, not show a header, conditionally show a header, show it open, show it closed, etc. You can also use the action framework when wrapper opens, closes, etc. You can also interact with the wrapper via it’s API.
I was looking to use your custom component with a chart. However, when I open the collapsible section the chart doesn’t show up; other components do show up, though. I wish I could give you more information beyond that, I checked the JavaScript console and there weren’t any errors.
That said, this is a really cool custom component that you made. I’m sure the community will get a lot of use from it.
If there’s any other information you need, just ask.
Sorry about the issue you are having with the Chart component. I know exactly what the root cause is (thanks to some help from Zach). I’ve had it on my list to get fixed but haven’t had the cycles to do it yet. I’ll get it fixed and upload a new version as soon as possible.
I tried to reproduce the issue you are having with the CW and the Chart component but unfortunately, I wasn’t able to reproduce the behavior your experiencing. That said, I did fix the issue that I was aware of with the CW Component and have uploaded a new version. I’m hopeful that it will resolve your issue as the symptoms that you are describing would present the same as the issue that I knew existed.
Can you download the latest version of the component pack and let me know if it resolves your issue?
If it does not, if there is a way that you can create a repro of the issue you are having using standard objects, etc. I can set it up in my DE Org to isolate and resolve.
Hey Dave - Thanks for the feedback. I’ve seen a scenario where when the CW is initially collapsed, when you open the chart expands beyond the containing ‘div’ element of the CW itself. I think this is due to an issue with the chart itself but it definitely could be something in the CW. Is this what you are describing by “zoomed in”? If you can share a small repro of this using standard objects I’d be happy to work to isolate the issue and see if I can resolve it. If it’s something in the chart component itself (which I fear it is), there might not be anything I can do but if it’s in the CW, I can definitely address.
Btw, are you using the latest version of the CW. I fixed an issue a couple of weeks ago where the chart itself wouldn’t even display when the CW was initially collapsed.
Hey Dave - Thanks for the answers and providing the sample. Unfortunately, it looks like the entire page didn’t paste properly or possibly there might be a limit to the number of characters in a post. Can you post the page XML to a dropbox URL or equivalent?
Dave - Thank you again for putting together the sample, made reproducing the issue very easy. Happy to report that your sample led me to the source of the issue and I have implemented a fix and updated the component pack.
Can you download the latest version of the component pack and let me know if it resolves your issue?
