Workshop Variable Grouping Feature Request

Propose an Improvement
1

Hey All,

I have a feature request. I think it would be fairly simple, but in workshop it’s easy to have quite a lot of variables, and after a few iterations it can get quite confusing to build big workshops.

It would be nice if I can group variables together into buckets, to manage them easier, and allow for faster building time.

Let me know what you think!

Kind Regards
Sam

1 Like
2

Thank you for the request!

Right now, we recommend using embedded modules to break up large Workshop modules. We recently introduced copying sections/widgets across workshop modules, with that you should be able to extract the content of an overlay, tab or a page into a separate embedded module with its separate variable scope.

https://www.palantir.com/docs/foundry/workshop/embedding-workshop-modules-overview#maintainability

1 Like
3

In addition to @michaeld 's suggestion, I highly recommend to use the Dependency Graph (icon on the right):

image

This makes navigating / searching for variables / debugging much easier, in my experience.

Best!

4

Hey,

Thanks for the reply. I’ve used embedded modules before and like using them, however sometimes it makes it difficult to do things such as events, moving to different pages. For example you’re in the embedded module but want to go to another page but can’t because it’s a separate workshop. Additionally when you click on a page with an embedded module, it takes a few seconds for the embedded workshop to load, and this leads to a weird ui where half the screen is loaded, but not the embedded module.

So embedded modules is great and I love using them! But i think grouping variables is an easier way to solve the underlying problem than exploring embedded modules. Just my thoughts for the best way to solve the problem.

Kind regards
Sam

5

Hi Sam,

Thanks for the feature suggestion! Reaching out from the Workshop team to confirm that we are tracking this as an open ticket, but don’t have any near-term plans to action it just yet. Very much agreed that it’d be a nice quality-of-life improvement for larger modules.

I’ve added your notes and an additional +1 to this feature request so we can factor those into future priorization.

Paul

2 Likes