Any best practice to a multi-status component?

Hi guys, I have a question about the best practice to a multi-status component.

I’m going to show different status of a component to my dev team.
Normally, I’m supposed to show all the status in one (Axure) page with description in an all-in-one page to it.

Currently, I archieved my goal by creating a component composing a dynamic panel. For example, the component A has 4 status (live and blue; live and not blue; consumed and blue ; consumed and not blue), I will duplicate it 4 times, break them from component and reorder the default status, hence all the status could be showed in one page.

However, this is not easy to maintain the component, every time you change the component, you need to change them twice, once in the component, and then change it in the all-in-one page. In my opinion, this kind of way violates the point of component.

What I want is I can show all the status in that all-in-one page, and meanwhile, I can mark the description along each state. Once I change one of the status, the corresponding state in the all-in-one page.

BTW, what would you do for creating multiple status like above?
For example, you have 2 status for one part of the component (like live and consumed), and 2 status of another part of the component (like blue and not blue), which results in 2*2 = 4 status totally, and this combination could be a large number when there’re like 5,7 status for each part of a component.

You can accomplish this using raised events inside your components. Take a look at this:

live example | download RP file (81.5 KB)

The trick is to use actual instances of your component on your all-in-one page instead of breaking them away. In this example, I’ve “bubbled up” the dynamic panel’s loaded event so that I can do things to component instances on pageload.

Hope this helps!

1 Like