User Interfaces - Simplified, Extended, Wizard

upgrade to SRM 5.0; R/3 4.6C; CCM 2.0
Hi everyone,
I have three questions regarding the UI templates that is in SRM.
1. Last client I knew used the extended form (BBPSC01). I am very familiar with this template, functionality-wise.  In regards to the other two, I have only seen the wizard UI (BBPSC02).  One of the issues that we are trying to address is the repetitiveness of entering the cost assignment information for multiple line items.
For the extended form, there is a functionality where you can copy the acct assignment, G/L, and IOs from the clipboard and apply it to all line items by pasting it (checking the box 'apply to all items before').
For other two templates do you have this option? 
2.  For the wizard and simplified form, there is no copy line item function (to create a copy (as line item 2) of the line item 1).  Is this statement correct?
3.  How difficult is it to change any of the templates?  For example if you were to add a field?  How would you go about doing this (brief explanation would be appreciated)?
If anyone can share some pros and cons of using a particular template from a project experience standpoint, I would greatly appreciate it.
-Benefits of using an extended form-
1. buy on behalf
2. copy line item functionality
3. can specify default settings
4. item over view (can work directly in it)
5. create limit item
-cons-
1. lots of scrolling
2. more confusing interface because there are many more mini panes/windows that can be opened
3. more time to open/refresh data
Thank you in advance,
Jay

Hi Jay,
3 shopping variants (BBPSC01, BBPSC02, BBPSC03) are all using the same source objects and screens.
They are just not displayed and controlled in the same way.
For example, item overview is used everywhere, but you can not make direct entry in wizard mode.
In each screen PBO, you can find some particular logic to control fields, against actual T-CODE (BBPSCXX).
Regards
Christophe

Similar Messages

  • User interface for Application Wizard Questionnaire - Order of Questionnair

    Hi
    Hi We have ECC6, eRecruitment 603 and have a query regarding the user interface for application wizard for the Application HRRCF_A_REF_APPLWIZRAD_EXT, Web dynpro component HRRCF_C_QUESTIONNR_UI. 
    We need to know if it is possible to influence the order in which the questionnaires appear for the user to complete.
    Example:  We have designed the process template to have quesitonnaires in a certain order, Reason for Application first and then Additional Information and then Equal Ops questionnaire.  But when the user applies and clicks on the road map questionnarie they do not appear in this order.
    many thanks
    Julie

    We have found that SAP note 1386825 fixes this issue.  For existing requisitions to pick up the fix they have to be resaved.

  • Error in report builder wizard user interface

    I am getting error 'REP-31954: Error in the Report Builder Chart Wizard user interface'.
    The help subsystem states that I should make sure that the Chart Builder Wizard libraries are properly installed.
    I am sure they are because all other wizards work fine, along with the Forms, Reports, etc.
    I searched using Google and found two messages that indicate this is a bug in the program and not library installation related.
    Does anyone know if this is indeed a bug that has not been resolved, or do I need to troubleshoot more on my end.
    I re-linked Oracle graphics and checked the env variables, but nothing gets the Chart Wizard to work within Reports or Forms.
    Any help/advice would be greatly appreciated.
    Thank you.

    Hi.
    I am running developer 6i on my home machine (with Oracle 8i, v 8.1.7). I am at work at the moment, and I can't recall what the Reports version is. The same error occurs with Forms.
    The filename that I downloaded is called 'd2k6irelease2.tar'.
    I downloaded the version that is currently on Oracle OTN's download site, so I presume that is the latest version that should contain all patches, updates, etc.
    Thank you for responding!

  • Re:error in report builder wizard user interface

    I am getting error 'REP-31954: Error in the Report Builder Chart Wizard user interface'.
    The help subsystem states that I should make sure that the Chart Builder Wizard libraries are properly installed. I am sure they are because all other wizards work fine, along with the Forms, Reports, etc. I searched using Google and found two messages that indicate this is a bug in the program and not library installation related. Does anyone know if this is indeed a bug that has not been resolved, or do I need to troubleshoot more on my end. I re-linked Oracle graphics and checked the env variables, but nothing gets the Chart Wizard to work within Reports or Forms. I am running developer 6i on my home machine (with Oracle 8i, v 8.1.7). The same error occurs with Forms. The filename that I downloaded is called 'd2k6irelease2.tar'. I downloaded the version that is currently on Oracle OTN's download site, so I presume that is the latest version that should contain all patches, updates, etc.
    Any help/advice would be greatly appreciated.
    Thank you for responding!

    Hi Adrian,
    Got the following when grepped through the web. You can give a try and see whether it works :
    1) Open the report in the Builder. In the properties for the graphic image, change to the proper UNIX path. Also, ensure the .ogd file which is referenced is also placed in the proper UNIX directory, so that the new path is reflected accurately.
    2) Ensure that your environment have the ORACLE_HOME set properly and then try re-linking with Graphics.
    Thanks,
    Vinod

  • Master Detail Wizard and User Interface Defaults

    Trying to create a master/detail form (on one page, no report).
    1. Wizard is giving the option to use User Interface Defaults for the master table, but not for the detail (I don't want to for either) - is this the expected behaviour? If so, why the inconsistency? Will/can this be changed in the future?
    2. Despite selecting NOT to use UI defaults, and entering new region titles, wizard is creating default region titles using the UI defaults. Is this a bug?
    3. Supplementary: Is it possible to get rid of UI defaults?
    HTML DB 1.6.0.00.87

    I asked about this last month:
    Master Detail Wizard and User Interface Defaults
    with no response.
    Anyone?

  • Extending Azure Pack User Interface by adding a new tab in a SideTab entry

    I'm extending Azure Pack User Interface, I have added a Custom Side Bar entry using "HelloWorld" Resource Provider. example
    After a new Side bar entry is create, I want to add a new tab in that side bar entry.
    In the "HelloWorld resource provider"  i have a project called "Admin Extension" in which i have to extend the UI.
    Initially I have added a new Html file in Content->Templates->Tabs called "Sampletab.html"
    In Manifests->HelloWorldAdminUIManifest.xml I have added
    <script src="~/Scripts/HelloWorld.SampleTab.js" />
    <template name="sampleTab"
    src="~/Templates/Tabs/SampleTab.html" />
    In Content->HelloWorldAdminExtension.js i have specified the new tab.
    navigation = {
    tabs: [
    id: "quickStart",
    displayName: "quickStart",
    template: "quickStartTab",
    activated: loadQuickStart
    id: "shares",
    displayName: "shares",
    template: "sharesTab",
    activated: loadSharesTab
    id: "settings",
    displayName: "settings",
    template: "settingsTab",
    activated: loadSettingsTab
    id: "sample",
    displayName: "sample",
    template: "sharesTab",
    activated: loadSampleTab
    types: [
    The template name i gave which i specified in Manifest file.
    function loadSampleTab(extension, renderArea, renderData) {
            global.HelloWorldAdminExtension.SampleTab.loadTab(renderData, renderData);
    The  Content->Scripts->HelloWorld.SampleTab.js  contains:
    /*globals window,jQuery,Exp,waz*/
    (function ($, global, Shell, Exp, undefined) {
    "use strict";
    function loadTab(extension, renderArea, renderData) {
    global.HelloWorldAdminExtension = global.HelloWorldAdminExtension || {};
    global.HelloWorldAdminExtension.SampleTab = {
    loadTab: loadTab,
    })(jQuery, this, this.Shell, this.Exp);
    When i load the tab, i get template not found error

    Hi Dinesh,
      The problem is solved. We are able to view the Accounting Preferences Tab now in the Settings screen.
      Actually the problem lied in calling the bbpfunction.html in the newly added html template i.e. 3500 screen. Actually the new screen 3500 is also defined in the BBPUM01 ITS service where we didnt write the code. So there we called the bbpfunctions.html from service bbpglobal.
      We have many other requirements linked to this Accounting Preferences which I shall post in a new thread.
       Thanks a lot anyways for your support !!
    Regards,
    Vikas.

  • Why do I get -18001 Errors using Customised TestStand User Interface

    Hi all
    I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
    The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
    I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
    If anyone
    has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
    Thanks
    Dave

    David,
    I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
    1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
    An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
    LabVIEW : VI is not executable.
    An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
    2) The same error will occur when
    a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
    b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
    I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
    For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
    Building The Operator Interface
    The following are steps if you are using a LabVIEW operator interface.
    1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
    Creating a LabVIEW Run-time Server
    If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
    1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
    Assembling the Test VIs for Run-Time Distribution
    This distribution process uses one of the shipping TS examples that calls LV VIs.
    1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
    2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
    3) Confirm that the sequence runs without problem.
    4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
    5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
    6) Set the target directory to be something distinct like C:\temp\AssblVIs.
    7) If you are using TestStand 2.0 skip adding Dynamic VIs
    8) Save with or without diagrams. Its your choice.
    Change Search Directories
    Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
    1) In the sequence editor select Configure>>Search Directories.
    2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
    3) Close the Edit Search Directories dialog box.
    4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
    5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
    6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
    Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
    1) In the sequence editor select Configure>>Adpaters.
    2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
    3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
    3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
    4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
    5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
    You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
    Distributing Components
    -To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
    -To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
    -You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
    Hope this helps.
    Regards,
    Kitt
    =========================================
    Title:
    Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
    The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
    Components that need to be distributed:
    TS engine
    Operator interface
    LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
    LabVIEW run-time engine
    LabVIEW test VIs
    Test sequence files
    Actions before distributing:
    It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
    Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
    Assemble the test VIs for distribution.
    Update the TestStand search directories so that the sequences reference the assembled VIs.
    Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
    Test the distribution components on the development machine.
    Enter section headings, separating each section with a line break:
    TS Engine Component
    Operator Interface Component
    LabVIEW ActiveX Server
    Configuring the LabVIEW Standard Prototype Adapter
    LabVIEW Run-time Engine Component
    Assembling your Test VIs for Distribution
    Note
    TS Engine Component
    With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
    These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
    You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
    Operator Interface Component
    You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
    LabVIEW ActiveX Server
    You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
    If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
    If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
    Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
    Configuring the LabVIEW Standard Prototype Adapter
    When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
    To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
    As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
    LabVIEW Run-time Engine Component
    If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
    You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
    Assembling your Test VIs for Distribution
    After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
    One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
    TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
    Links: See Distributing LabVIEW Test VIs below
    Note
    Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
    Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
    Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
    ==============================================

  • Reading the output values after each step executes in LabVIEW User Interface

    Hello all,
    Development environment: TestStand 2010 SP1 and LabVIEW 2010 SP1
    Problem: is there a way to execute the subsequent steps programatically and get the output values from each of them?
    I have already extended a little bit a Full OI interface for TestStand to load up any sequence, choose some of the steps and run them step by step (something like option to Run Selected steps). What I am trying to do is to add some actions between each step and do that in User Interface (I can't modify the sequence!), so I am starting the NewExecution with some previously configured InteractiveArgsParam and set an option breakAtFirstStep to True. Afterwards I am just doing something like Step Over when debugging the sequence and this works good, but I didn't fine a way yet to read the output values from the steps...
    Then, if I wait until the execution finishes I can read my Results by processing the ResultObject, but this works only after finalizing of the test sequence. Since I wanted to stop after each step, read the values, do some actions and continue to the next step I tried to register an event callback for Trace of Execution View Manager. I can see that after each executed step this event is triggered, but when I try to read a ResultObject returned in Event Data it is not filled with values (ResultList seems to be empty?). Is it a proper behaviour or maybe I am doing the readout in wrong way? (It is the same VI as for reading ResultObjects after sequence finishes and there it works fine for arrays, containers and other data types).
    Like I mentioned I can't modify the Test sequences, I can't add a UImessages.
    What are my options? Should the trace event returns all output values from each steps or is it just used for status checking? Or maybe there is completely different approach to that matter?
    Thanks in advance for any suggestions,
    Best Regards.
    CLA, CTD, CLED @ Test & Measurements Solutions Poland
    Solved!
    Go to Solution.

    Thanks for your replay, I have tried to build it in my LabView Block Diagramm, es seems like this image.
    But the variable GetNumSubProperties ist always 0. Why?
    PS: I need only the variable "Step.Result.PassFail" from the last step, do you know, how can I get it? I think, it is maybe easier than read all the "Result".
    Attachments:
    ReadStepResultInLabview.JPG ‏39 KB

  • How to use own style sheet in user interface templates to change buttons, fields look

    I want to use my own style sheet to change the appearance of buttons, form fields etc. while applying my own user interface template. I know I can create an unstructured UI template to change logos, body color etc. but how do I apply css to buttons, fields generated by the portal components form wizard ?
    If this is not possible, how do I create my own form and get the same functionalities of a wizard generated form ?
    Thanks.

    Mrinal,
    I have solved that problem fortunately.
    What I did was to create my own unstructured user interface template. In the unstructured UI template, you can use style.
    for example, in between the <head> tags, write <style> tages and create own classes for buttons, textboxes etc.
    Then write a javascript to assign those classes to the buttons. Call the javascript function on OnLoad event in <BODY> tag.
    That will do the job.
    for example you have a style class called buttonclass for buttons.
    <script langauge=javascript1.1>
    function setstyle(form) {
    for (var i=0; i<form.length; i++) {
    if (form.elements.type == 'button') {
    form.elements[i].className = "buttonclass";
    </script>
    <BODY onLoad = "setstyle(document.forms[0]);">
    hope this helps.
    Mainak

  • Labwindows/CVI 7.1 Remote user Interface using Enterprise Connectivity Toolkit

    I have an application programmed in Labwindows/CVI 7.1 controlling an Electromagnetic Instrument.
    Now am interested in extending its usability by adding remote user interface.The goal is to have the application available to be accessed 
    to remote users through website,with multiple users viewing it but one user controlling the instrument remotely at any given point.
    Since the possible methods would be 1.ActiveX 2.TCP/IP 3.DLL
    Which is the best technique to implement this with out having to manipulate much of my code also do we have any documentation available ?
    Thank you
    Solved!
    Go to Solution.

    Hi Mutha,
    This functionality was a part of the orignal Internet Toolkit for CVI.  However, the web server part of this was removed and isn't included in the Enterprise Connectivity Toolkit.  You might consider using LabVIEW with the Remote Front Panel feature.
    Cheers, 

  • Dreamweaver user interface controls appear small and hard-to-read on high-density displays.

    I have 3840x2160, 24" display and many of the user interface controls are small, hard to read and in some cases are cut off.
    I see this issue existed with Photoshop and Adobe introduced a "Introducing scale the UI 200% for high-density displays for Windows" under "Experimental Features"
    Photoshop: Introducing scale the UI 200% for high-density displays for Windows
    However I don't see this option available in Dreamweaver? Is there another work around?

    ArtJonak wrote:
    I have 3840x2160, 24" display and many of the user interface controls are small, hard to read and in some cases are cut off.
    Wow, 4K resolution within a 24" space. You need a 200% increase in UI size just to work, I would think. Can you post a screenshot of the issue? I would like to see that. ;-)
    With the changes the Dw team have made to the UI over the last few releases, and with the latest Workspaces, it almost feels like 720p is the main focus, or like the only Dw users that matter are on small Macbooks, with very limited screen real estate. I can still work on my laptop when I'm out of the office (17" at 1920x1080 on Windows 8.1), but the icons and controls are pretty small. Even with the added screen real estate, and the fact that the UI is still intact, I'd hate to have to use it for extended periods.
    I voted as well.

  • SAP SSM 2007 - Administrator's user interface

    Hello,
    I've a problem concerning SAP Strategy Managment 2007 (pilot).
    I get a "Page not found" when logging into the Administrator's user interface http://localhost/pilot/pipadmin .
    It opens a pop_up window with the path: http://localhost/pilot/scriptmain.pw?userinfo=/pilot/pipadmin/adminstart4.htm, but it doesn't work. IIS and Jboss are working correctly und the jboss_server.log contains no error.
    Has someone an idea?
    Thanks and best regards,
    Robert Männel

    Hi Chris,
    thanks for your reply! Pilot Extended Listener; Pilot Listener; WWW and JBOSS are running and I started Pilot Extended Listener before Jboss, but it doesn't work.
    It tries to open http://localhost/pilot/scriptmain.pw?userinfo=/pilot/pipadmin/adminstart4.htm but there isn't a file "scriptmain.pw" in the pilot directory, only the file "scriptmain.pip". Maybe it is missing?!
    best regards,
    Rob

  • Webserver user interface

    Hello,
    I've to code a user interface in order to launch a webserver based on WebServer.java
    (from sun example).
    At the moment, i did "class WebServer extends JFrame implements HttpConstants"
    but i think it s not the good way ...
    where must I create my JFrame ? in a new classe ?
    thanks

    WebServers are typically laucher in a stand alone fashion.
    If you close the window do you expect the webserver to die?
    What you may want is a standard Swing application which starts the webserver from the command line as a seperate process. As such you should not need any HTTP references in your code.

  • How can I tile up the execution window in the Labview Teststand user interface

    I am using the Labview User interface provided with the TestStand development environment.
    Running the BatchUUT.seq Example using the TestStand Sequence Editor, you will see that the Execution Window will be divided in 4 windows showing the execution status of the 4 UUTs.
    Running the same Sequence using the provided Labview User Interfaces (Simple or Full-Featured) will just show one window with the execution status.
    Is there a way to tile up the window to display the execution status in the Labview User Interface?

    Try something like this:
    You wouldn't use random numbers of course, but rely on already opened clones. So you would extend the "Manage Clones" to manage the data for the window position, but set it for each clone in the way the screenshot shows.
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Shared Component User Interface Templates not available for page use.

    Hello.
    I created a new User Interface Template using the wizard under shared components. All it's supposed to do is display a header image on the page. I can click on the title under User Interface Templates and it will display fine. If I try to use that template, it will not display as an option under Display Option use custom template LOV under the Main tab of page modifications. Shouldn't it be available here for selection? I couldn't find any access grant options under Shared Components that might have explained this problem.
    Thanks.
    Kurt

    Does anyone else have this problem? How did you fix it?

Maybe you are looking for