ORD/CONNECT One User Preference across multiple workspaces?

i'm back onto setting up my ORD workspaces for clients.

I plan to use the default location for userpreferences to simplify things. This will require me to lock down a few variables in our Organization configuration.

My question is, is there any HARM in using the same user preferences for multiple clients? As far as I can tell, user preferences are personal preferences, and shouldn't really be dependent on client setup, but I'm not certain about that. Some of the clients have user preference seeds, some of them do not. Can you think of anything in

MS_DOCKINGPREF = $(_USTN_PREFNAMEBASE).docking.xml
MS_GROUPPANELPREF = $(_USTN_PREFNAMEBASE).GroupPanels.xml
MS_SAVEMENU = $(_USTN_PREFNAMEBASE).Attached.men
MS_RIBBONPREFS = $(_USTN_PREFNAMEBASE).RibbonState.xml
MS_FKEYMNU = $(_USTN_PREFNAMEBASE).funckey.mnu
MS_USERPREF = $(_USTN_PREFNAMEBASE).upf

that would be essential to functioning in a specific client environment?

_USTN_PREFNAMEBASE does vary from client to client. I believe that is what I would need to lock down. Either that, or _USTN_HOMEPREFS...

I plan to %lock _USTN_USERNAME = $(USERNAME)

Can you think of anything wrong with this?
If I need to allow for separate preferences for each client, I can do that, but it would be cleaner and neater if I could just go around that.

Parents
  • I think you might be fighting a never ending battle with this one.

    I agree with Tim.

    I don't see anything wrong with what you're trying to do, but you're also creating a lot more maintenance issues for yourself that may not be necessary.

    The other potential issue is that clients may set some of the civil preferences to facilitate their workflows. By not using the client provided preferences you might get differences in how things look or operate.

    Some things are necessary to customize to fit your installation, some things are not. This is one of those things I think is in the not category.

    Rod Wing
    Senior Systems Analyst

    Answer Verified By: MaryB 

Reply
  • I think you might be fighting a never ending battle with this one.

    I agree with Tim.

    I don't see anything wrong with what you're trying to do, but you're also creating a lot more maintenance issues for yourself that may not be necessary.

    The other potential issue is that clients may set some of the civil preferences to facilitate their workflows. By not using the client provided preferences you might get differences in how things look or operate.

    Some things are necessary to customize to fit your installation, some things are not. This is one of those things I think is in the not category.

    Rod Wing
    Senior Systems Analyst

    Answer Verified By: MaryB 

Children