Hello Patrik
We have been saving user options for commonly used programs for years.
It started out with a file per application and a character field hard
coded with the options. The file had User, Program and Options.
We then consolidated this information to a single file adding additional
identifiers like company, screen id etcetera.
A few years back we changed the history detail to be json which made it
much more readable and made it variable length.
There was significant improvement from a user perspective when say going
from a order inquiry to an account enquiry and the company and account
number were pre-populated based on the previous selected.
My 2 cents
cheers
Don
From: "Patrik Schindler" <poc@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 23/03/2021 08:48 PM
Subject: Application Specific User Settings: How to?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
Hello,
sometimes, it's desirable that users on an IBM i system can modify and
persistently save individual settings of applications. Example: A default
sorting order for some table view. But not necessarily limited to that.
Not every user necessarily has a personal library to create a PF for
saving things there. And, this approach unnecessarily clutters libraries.
Not every user necessarily has a home folder to create a file for saving
things there.
What's more, depending on how a user accesses the data, these approaches
might lack authority to access or update the files. AFAIK, the web server
runs with a separate user profile. This is less of an issue with "local"
(5250) users.
A central, application specific file would accumulate old entries (when
user profiles are deleted from the system, for example).
What is the best way to save local user preferences (mainly for 5250 users
of applications)? Any thoughts from the group on this topic?
Thanks!
:wq! PoC
midrange.com
