Ya you are right. The link is not working for some resons unknown to me. But luckily I have the content saved with me. Following is the wiki content :
" I had faced a scenario where a drill down was required from a chart to a more detail view. Detail view wasn't on the same layer. And the navigation based on the select event wasn't possible either. I was showing a very minimal detail view(like basic summary) of various functions on the first page(like a dashboard). The user had the choice to drill down on a specific function to a more detail view.
It was easy to do over the same layer with the select event ...... but how about the navigation to another layer ? Initially to resolve the problem I created custom event for inter layer navigation and triggered it using a button. But clicking on chart and then on button wasn't a most appealing user interaction. It had to reduce to a single click over chart...but how ?
I tried to look for solution, like asking on sdn forums, but got no clue. So I decided to have a fresh look on the problem and applied a bit of logic with expressions and visibilty property(instead of navigation) and gosh ! it worked !!!. Now I have become true fan of Visual Composer. Its really a fun like solving puzzles.
Instead of using layer( Layers doesn't have visibilty property.), I used nested Iviews. This also made the model more manageable .
So here are the steps I followed to achieve that...................Lets do a basic one, demonstrating the idea.
1) So create a nested iview (say view1)and put a bar chart in it connected to some Query or RFC. Drag out of out port and create a signal out. Give it a name (signal1). Give event type as select.
2) Create another nested iview( view2). Create table or chart which takes input from the chart created in step 1. From the Query or RFC, drag out of in port and create a Signal In and name it same as in step1 (signal1).
3) Drill out of the iview to Design mode.
Create a Datastore. Create two fields of boolean type in it. name them (say v1, and v2). Set default value true for v1. Set false for v2.
4) Select view1. In the configure element task panel, For Visibilty Property,In the formula expression dialog box, Expand Datastore field. Drag v1 from it to the left expression area.
Repeat for the view2 with v2.
5) From view1, drag out of port signal1 and connect with the same port of view2.
Drag another line and connect it with the datastore. Click on the line. In the configure task panel, assign the v1 as false and v2 as true.
6) Switch to layout mode and strech the iview to superimpose on each other.
7) Compile and deploy the model.
Now when you click on a bar, the other iview should be displayed with the more detailed information and thus simulates the single click drilldown experience.
But this is not happening in this model........The first visible view is view2 instead of view1 !
This happened, Because the first select event is fired at the time model is rendered itself. Much before u can actually click a bar and raise the event.
So obviously, we need to avoid the first select event.
To achieve this, we use gaurd condition of the link as follows :
1) Create a field, say counter, in the Datastore of type number. Set default value as "0".
2) Select the link connecting the view1 and view2. In the configure task panel, select field counter and set its value to counter +1 through expression editor.
3) Select the link connectind Datastore. In the Gaurd Condition, enter the expression !bool(counter==0), to disable the link for the first select event
Kindly let me know in case of any doubts
Regards,
Vidit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.