Double Navigation

[Sm1tje]

Hi all,

I would like to know if the following is possible to do, and how to go about.

I have a WD which has a window with two views. Depending on the person using this WD I want to navigate to the appropiate view in the window. Therefore I want to create two applications where the first application points to the first view on which some data will be entered after which the second view will be displayed.

The second application will go directly to the second view without having to enter any data.

Is this possible and what will be the best way to achieve this?

I tried a few things myself of course, but I can't get it to work properly.

Kind regards,

Micky.

[Former Member · Accepted solution]

Hi,

if i'm correct you already have the application with the two views,

one login type needs to see both one type needs to see the second one directly.

in your default inbound plug of your window, you can catch the login and the type,

and there you can fire the inboundplug you wish to get (the plug of the desired default view)

this you can achieve when both the views have an inbound plug

and your window has an outboundplug for each view

and by using the magic wand tool in the editor, pick the

outboundplug which was connected to the inbound plug of

your desired view and done

grtz

Koen

[Sm1tje · Accepted solution]

Hi Koen,

that's actually exactly what I was looking for (points will be awarded). However, I do have one question. How to determine the login? I do not want to use the name of the current user, because this would mean another call to the backend system (employer or customer). I want to do this on the 'client' side. So my idea was to determine the URL of the application (one application URL for Customer and one for Employer) in the Default plug of the window. Based on the URL I can determine whether it's a customer or an employer. Is there a way to determine the URL at runtime?

This is not going to work using CL_WD_UTILITIES=>CONSTRUCT_WD_URL, since this has Input the application name.

Kind regards,

Micky.

[Former Member · Accepted solution]

Hi,

If you are passing the type in your url,

you should insert a parameter in your default inbound plug with the same name,

that way it will be fetched automatically by the handling method

grtz

Koen

[Sm1tje · Accepted solution]

Hi Koen,

Many thanks for your quick and moreover, correct replies. Points awarded.

Kind regards,

Micky.

[Former Member]

Hi Micky.

Just as additional info to Koens input:

You can set the Inbound Plug to call in your application.

Just create an application and in the app view you can set the Plug Name of the inbound plug to call.

So it is possible to create multiple apps with different starting points for the same component.

Both inbounds have to be set as start up plugs.

Cheers,

Sascha

Message was edited by:

Sascha Dingeldey

[Sm1tje]

Sascha,

perhaps I made a mistake somewhere along the line, because that's what I've been trying to achieve up until now. However, I couldn't get it to work, since only the second view (default) was displayed and not the first view.

Regards,

Micky.

[Former Member]

Hi Micky.

I have a similar approach in my app.

InboundA which should trigger ViewA

InboundB which should trigger ViewB

So I created two outbounds in the window for each view. OutboundA and

OutboundB. These oubounds are connected to the corresponding inbound of the views.

in the inbound handler methods of the window inbounds I just fire the outbound

plug methods so that the navigation to the view is triggered.

InboundA fires OutboundA -> navigates to view1

InboundB fires OutboundB -> navigates to view2.

Application1 has InboundA as Plug Name.

Application2 has InboundB as Plug Name.

But seems that you have already solved you problem.

Cheers,

Sascha

[Sm1tje]

Sascha,

Indeed I (or better yet: Koen) solved my problem.

The approach you're using is exactly the same as mine, so your 'answer' (pointer) was very usefull.

Thanks,

Micky.