|
LasVegasSBUser
|
 |
« on: August 27, 2009, 08:48:34 AM » |
|
Hello,
I was wanting to know if its possible to change background colors when a user logs to a differnt ACCOUNT. We are doing upgrades and are running parallel and the use have 2 sessions running SCORPEO & SCORPEO.TEST and they keep changing the live accounts data by accident. So if after the user uses the LOGTO SCORPEO.TEST Background color = XXX.
Thanks
|
|
|
|
|
Logged
|
|
|
|
precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #1 on: August 27, 2009, 09:07:00 AM » |
|
The short answer is "no". However, there's always that untested "maybe" that might be worth trying. Here's the background:
The GUI defaults - colors, fonts, etc - are stored in DMSYSDEFN and are maintained by the /GDS tool. Each thing that gets rendered in GUI uses the configuration stored in this file. Screens in particular can name a record in this file on the F6-Params | F6-GUI Parameters | GUI Presentation Template prompt. If nothing is named there, the defaults named SCREEN.GUIDEFS is used by default.
But here's the problem... DMSYSDEFN is shared across all SB+ accounts, and it contains a lot more information than just these GUI defaults. Printers, printer classes, stationery, terminal types, fonts, and all sorts of other configuration is in this file. So while it IS possible to create a copy of this file that is local to the test account, I suspect that the effort involved to do that might be prohibitive and who knows what side effects might come about as a result. It's also possible to go through the test account and change all of your screens to reference a different default set, but that could require an even greater effort and then customizes the test account so it's no longer a duplicate of the live account.
What I have seen done with some success, however, is modifying the title bar when someone logs into the test account. Of course, they have to be looking at the title bar, but if you mark it up with plenty of ******************** people are usually pretty good about getting a clue. I'm not sure where you'd set this up in the Davison solution but you might talk to Davison support about it.
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|
LasVegasSBUser
|
 |
« Reply #2 on: August 27, 2009, 09:18:14 AM » |
|
Very nice answer it saves me a lot of looking and programming time. Thanks Kevin..
|
|
|
|
|
Logged
|
|
|
|
|
adewitt
|
 |
« Reply #3 on: August 28, 2009, 09:29:08 AM » |
|
What software are you modifying? I have done it in Avanté with no problem.
|
|
|
|
|
Logged
|
|
|
|
precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #4 on: August 28, 2009, 03:03:14 PM » |
|
I believe it's the Davison HRPyramid application.
How do you do it?
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|
adewitt
|
 |
« Reply #5 on: September 11, 2009, 09:49:30 AM » |
|
In Avanté I modify SYSS0001.1 by adding the line CALL SB.PROCESS('S.BACKGROUND') where S.BACKGROUND IS: LOCAL L.GUI IF OCONV(@USER.ID,'MCU') = "AVANTE95" THEN L.GUI = SETATTR(@MAINWIN,G.BACKGROUND,G.BLUE) END ELSE BEGIN CASE CASE @ACNT.NAME[1,3] = "TRN" OR @ACNT.NAME[1,5] = "PILOT" L.GUI = SETATTR(@MAINWIN,G.BACKGROUND,G.MAGENTA) CASE @ACNT.NAME = "LIVE04.DATA" L.GUI = SETATTR(@MAINWIN,G.BACKGROUND,G.RED) CASE @ACNT.NAME = "MMTRN.DATA" L.GUI = SETATTR(@MAINWIN,G.BACKGROUND,G.BROWN) CASE 1 L.GUI = SETATTR(@MAINWIN,G.BACKGROUND,G.GREY) END CASE END EXIT
Not real geeky, but it works.
|
|
|
|
|
Logged
|
|
|
|
precisonline
President/Chief Technologist
Administrator
Rock Star
    
Posts: 1532
|
 |
« Reply #6 on: September 11, 2009, 11:06:57 AM » |
|
And that's all that matters - thanks for sharing!
|
|
|
|
|
Logged
|
-Kevin Accidents "happen"; success, however, is planned and executed.
|
|
|
|
Colin Alfke
|
 |
« Reply #7 on: December 10, 2009, 01:12:05 PM » |
|
I have one called P.SETBACKGROUND LOCAL WINCOLOUR, SETCOLOUR * IF @GUI THEN IF @ACNT.NAME # "STD" THEN SETCOLOUR = G.RED ELSE SETCOLOUR = G.GREY END WINCOLOUR = SETATTR(@MAINWIN,G.BACKGROUND,SETCOLOUR) END
I have it in the Proc at Set Common slot in each system. Which is one of the things that makes it a pain - putting it in each system. The other is that I can't set the background back to the "default" colour (I tried the colour being blank and searching the terminal definitions - but no joy).
hth Colin
|
|
|
|
|
Logged
|
|
|
|
|