topic Re: GUIXT issue's in Application Development and Automation Discussions

GUIXT issue's

Former Member — Wed, 27 Jan 2010 12:14:11 GMT

Hi Experts,

I am trying to change the label for a field in the standard transaction ME21N.

I created a screen variant & Modified the label for the field "Assignment no." using GUIXT.

When i test it, i am able to see the changes, but there are two problems that i am facing:

1) The changes are not visible if login in other system. I initially assumed that the GUI script is getting stored locally in my system. But i was able to see the changes i made to GUIXT in my colleagues system (By pressing the GUIXT button available in the screen variant). When i try to test the screen variant in his system, the changes are not getting reflected.

2) If i de-activate the GUIXT in my system, i am not able to see the changes made by me.

I don't want to always keep the GUIXT active.

Can any one help me to solve these two issue's.

Any other alternatives are welcome.

Let me know if i am missing some kind of activation or config to be done.

Thanks,

Sreedhar.

Re: GUIXT issue's

Former Member — Thu, 28 Jan 2010 03:07:50 GMT

Any one can find this

Re: GUIXT issue's

Former Member — Thu, 15 Sep 2011 09:12:19 GMT

THANK U

Re: GUIXT issue's

Former Member — Wed, 14 Dec 2011 18:55:02 GMT

You should check our guixt configuration. It will tell you the location of where it gets the files from. In our system we have separate directories for Dev, QA and PROD. example.... c:\programfiles\sap\guixt\scripts\DEv or QA or PRD... then input scripts or guixtsripts

Re: GUIXT issue's

Former Member — Thu, 02 Feb 2012 13:46:08 GMT

Although this question is marked as "Answered" maybe just some insight.

Scripts can be stored locally, on web servers/FTP servers, and even the SAP Web Repository.

Scripts are driven by a license key, which determines on which Application Server, and SID they can run.

GuiXT Can be started in a hidden mode, so that it will not bug users that log on and that dont use GuiXT.

Additionaly, by building conditions into your scripts, you can test against a condition, and only have the scripts run if that condition is met.

As an example, if you have two groups of users creating a material, and the one group uses SAP Standard to create a material and the other uses a GuiXT modified method for creating, then you would test against the User Group.

I hope this makes sense.