Calling Rich Display File programs using *LIBL?

[PaulDV]

I have my first Rich Display File program (yay!) and added a menu item for it, using *LIBL as the library list, but when I click on the menu item, I get the following error screen:

2019-01-09 10_36_04-SICS Web Portal.png (29.44 KiB) Viewed 1710 times

This seems to indicate that Profound can't find the program, but I have set up the navigation to use the library list from a JOBD, and the program library is there, so it would appear that either I have done something wrong with the config or there's a problem with Atrium.

By contrast, if I specify a hard-coded library on the menu item, the program works fine, but due to this being our development environment, a program could be in any one of 3 libraries, hence wanting to use the library list.

Can anyone tell me what I'm doing wrong? Is this even possible in Atrium?

Cheers,
Paul.

[Scott Klement]

The library name in Atrium needs to be an actual library, we do not support the special value of *LIBL at this time.

[PaulDV]

Thanks Scott.

Is this on the roadmap at all? Not being able to use *LIBL is going to be a real pain for us in development.

We use a change management system, whereby objects start in a development library and then get moved into a system integration library, and then moved to a QAT library (all in our library list). Most programs will be in the pseudo-live QAT library, and only those being worked on will exist in the other libraries.

Having to manually update the program library for screens being worked on (and remembering to set them back again!) is going to be a major headache.

[Scott Klement]

This isn't on a road map.

If you want it to be, place a feature request. This is done by contacting Profound Logic Support at support@profoundlogic.com

[PaulDV]

Will do - thanks Scott.