I often find myself creating apps with several different functionalities.
One step group might be several analysis views and one might have work instructions.
The work instructions could use a base layout to quickly create the same structure on all steps. But I don’t want the layout on all my other step groups.
I think it would be really helpful if it was possible to apply a base layout to a step group.
The current base layout could then be used as a layout for the whole app (Top navigation, logos and such) while the “step group” base layout can be put on top and used for specific step groups.
Hi @saga.losman, thanks for the product suggestion! I definitely understand the need for having multiple step layouts that you can reuse, rather than just a single layout that needs to apply to all steps.
We’ve noted this request in our system and will see what we can do.
For the short term, depending on the ratio of work instruction steps and steps with analyses, you could try defining the base layout to the “step type” most frequently needed in your app. So for example, if you have many more work instruction steps with a certain layout than others, you can make that design in your base layout. The downside being you’ll need to unlock and delete elements for the steps that need to deviate from the base layout.
Thanks again for your suggestion — hope this helps!
We would really benefit from having some “Base layout” for step groups. Not just for the visual layout, but especially for step and machine triggers. Right now, I’m creating a duplicate of our main MES page to use as a pop-up, but the main page has many machine triggers. In order to create the pop-up warning, I have to duplicate the main page along with all of the step triggers. If I make a change to any trigger on the main page, I then have to manually copy that change to every duplicate step, which is very cumbersome given the number of triggers we use.
I could add those triggers to the app level, but we use the app for other functions like BOM Search and Andon light requests. If some of my triggers were active on those other pages, it would disrupt the system.
It would be great to have a way to define a base layout for step groups so trigger logic can stay synchronized across steps without affecting the rest of the application.