Atrium use of Parameters
Posted: Wed Feb 06, 2013 7:36 pm
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).
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).