BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
himalay
Calcite | Level 5

Could you kindly help us to demarcate Production, UAT and Development connection profiles with distinct colour codes for DI Studio, EG and Management Console?

I have tried to check the options in SAS Management console but it seems we dont have access for the the configuration management. Please advise. If it can be feasible at your end we will raise a service request for the same.

1 ACCEPTED SOLUTION

Accepted Solutions
LinusH
Tourmaline | Level 20

As stated, there is no prepared options for users to play with.

What type of server you have shouldn't make a difference, since all clients mentioned are running locally i Windows (excpetion SMC).

To out-rule any behind the curtain possibilities to teak client behavior, contact SAS tech support.

If it's very important to separate access to different environments, evaluate possibility run the clients from a Citrix server (or similar), the you can have separate sets of profiles depending on target environment.

Data never sleeps

View solution in original post

7 REPLIES 7
SASKiwi
PROC Star

An interesting question. As far as I can see up to SAS 9.4 M2 there appears to be no way to configure the display attributes of connection profiles for any SAS tool - it is just straight text with no options for different fonts, colours etc. You could add this as a suggestion in the SAS Community.

himalay
Calcite | Level 5

Can we install some .css script as hot-fix to give colored background? Please note that our applications are running in Unix server.

LinusH
Tourmaline | Level 20

As stated, there is no prepared options for users to play with.

What type of server you have shouldn't make a difference, since all clients mentioned are running locally i Windows (excpetion SMC).

To out-rule any behind the curtain possibilities to teak client behavior, contact SAS tech support.

If it's very important to separate access to different environments, evaluate possibility run the clients from a Citrix server (or similar), the you can have separate sets of profiles depending on target environment.

Data never sleeps
jakarman
Barite | Level 11

Interestuing and gooed question.  Production UAT and Development ares stages for developign the SAS System and a SAS deployment but also the areas of business developing business processes.

As developing business processes is only doen with an approved SAS System (other word the SAS system is having sate production IT-service) the indication profiles (colours) is associated with business naming convetions.

The demarcation with colours woudl be an free to set user-attribute or do you also want those managed centrally?      (%appdata% location user-profile)

---->-- ja karman --<-----
himalay
Calcite | Level 5

Dear Jaap,

Thank you for your kind response. Our application server in running in Unix. Can we manage it centrally by providing diffirent background colour for each environments(seperate coulour for Deveelopment, UAT and Production). Often our development team gets messed up if they open Development and Production and sometimes finally end up changing code in production code. Smiley Happy

ChrisHemedinger
Community Manager

For your SAS Enterprise Guide users, you can use command-line options and desktop shortcuts to help manage which environment you're using.  This can help to ease the burden of having to remember to switch between environments for different levels of work.

See Using SAS Enterprise Guide with different SAS environments.

Chris

It's time to register for SAS Innovate! Join your SAS user peers in Las Vegas on April 16-19 2024.
jakarman
Barite | Level 11

Himalya, As you have problems when the DEV and Prod are being confused why isn't there a separation by the security.

A developer should not have access rights for updating code in a production environment, and should not have change rights for production data.

A production business user should not access right in a development environment. Unless every-one is "sasdemo" you will not  have any problems when the security in the metadata is according to their (RBAC) roles.

As they could setup still wrong profiles the effect of that will be having no access or another protection by usage of the different environments. Mistakes by confusion or the on purpose ones cannot happen that easy anymore.   

---->-- ja karman --<-----

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 7 replies
  • 2057 views
  • 3 likes
  • 5 in conversation