Atrium use of Parameters

[leatherlips]

We have applications that include embedded security based on a database (user profile key used to retrieve the security records)
Same applications have built in structure that uses library lists to control functionality within the application.
Currently there is a green screen “menu” system that controls application security and functionality base on the database information and also controls the library lists for the application (which enables/disables certain functionality).
Now with PUI, we want to use Atrium for the “menu”. However, there seems to be some issues for us.
First was the fact we could only call a RDF program without parameters from the Atrium Navigation setup. Our intention was to use a single PUI program(which would encapsulate our existing security and library list functionality) for every menu item we create in Atrium, but use parameters to determine which RPG(application) program to access(the parameter would be a key to the existing menu database which has the information necessary to correctly call the RPG). This would allow us to use our existing structures built into our applications to control the library lists and security as the old menu system used to do.
It appears that we cannot include parameters when setting up an Atrium Menu navigation item(for an RDF pgm). The ability to pass parms here would be HUGE if added as Atrium functionality.
So if we can’t currently do that, what about using a URL and formatting it to call the PUI program, passing parameters? (using something like this: pgm=MYLIBRARY/MyOneInitPgm&p1=XXXXXXXXXX&l1=50&p2=XX&l2=2&p3=XXXXXX&l3=10 for parameters).
If the user is already logged into ATRIUM for this, we would want that user’s ID to be available to any program being called so we can implement appropriate security. Would this work? (We don’t want anonymous access to these programs).

[David]

There is a way you could do this. When you select "rich display application" type in the navigation item, this puts the program into Atrium's database for security purposes (i.e. Atrium menu permissions will control who can call it), but it does not allow you to pass a parameter.

You could set up the item as a 'web application' type, though. This would bypass Atrium menu security, but this is fine since you are just going to call 1 program which handles the security on it's own.

You could set up the web application URL like this:

/profoundui/auth/start?p1=XXXXXXXXXX&l1=50&p2=XX&l2=2&p3=XXXXXX&l3=10

Using the "/auth" URL will get you signed in automatically since you are signed into Atrium. This will invoke a PUI session to the user's initial program. Since the sign on panel is bypassed in this scenario, you can get parameters through.

You can then setup PUI (Launch->Maintain Initial Programs in the designer) so that it calls your default program when each user starts a session. This is the 'default initial program' setting there. This will be called for any user who does not have a specific record there.

So, this means you are not using Atrium menu permissions anymore, but just firing up a PUI session to the default initial program and passing parameters in.

Does this make sense?

[leatherlips]

This does make sense, and we'll give it a shot to see how it works for us.
THANKS!