Modify User Interface

Hi.
How could I modify the Admin User Interface, to remove those Tabs which I don't want displayed, whenever the Admin User signs into IDM?
This is the main Admin User Interface :
HOME --- ACCOUNTS --- PASSWORDS ---- WORK ITEMS ---- SERVER TASKS
Where and how can I modify/customize this Interface?
Thanks

I understand that you want to remove tabs, but i don't have working (and tested) code to do this.
I juste give you a working code to add tabs. You can modify it to make a code to remove tabs but you have to work on it and search method name.
code to add subtabs:
p.TASKS_PAGE.addSubPage(MY_PAGE);
code to remove subtabs (probably like this but not tested):
p.TASKS_PAGE.delSubPage(MY_PAGE); or :
p.TASKS_PAGE.removeSubPage(MY_PAGE); or :
p.TASKS_PAGE.deleteSubPage(MY_PAGE); or another...
and to remove tabs (probably like this but not tested):
p.delPage(ACCOUNTS_PAGE); or :
p.deletePage(ACCOUNTS_PAGE); or :
p.removePage(ACCOUNTS_PAGE); or another...
it's juste one lead from a tested and working code which make the the same type of operation.
I hope it will help you...

Similar Messages

Modify High Level User Interface

Respected Sir
i am using MIDP2.0 for my application. i want to modify some High
Level User Interface in my application. i mean that for TextBox
High Level User Interface i want to change(Modify) TextBox
predefined size , color,etc.... Is it Possible. if is then plz give
me some Clue.
thankx in advanse
Souvik

use setPreferredSize
and setLayout
functions
though for color there is nothing

Modifying sequence variables from Labwindows User Interface

Hi,
What is the correct procedure for modifying sequence variables from a
LabWindows CVI user interface.
I am currently using an enhanced version of the simple interface that is
shipped with TestStand.
I have tried SetValVariant etc. with a ref to the engine and this didn't
work for me.
Should I first be passing the sequence context via PostUIMessageEx ?
Thanks in advance,
Bill
Solved!
Go to Solution.

Hey Bill,
Yeah, I forget that this process is a little bit more straightforward in LabVIEW then it is in CVI (just one type cast is necessary). Here are the steps (and variables) to make it a usable SequenceContext object:
LPUNKNOWN tempActiveXRef;
VARIANT tempTSSeqContext;
CAObjHandle TSSeqContext;
     //Get ActiveX object from UIMessage
   tsErrChk(TS_UIMessageGetActiveXData (uiMsg, NULL, &tempActiveXRef));
     //Convert LPUNKNOWN to Variant
   tempTSSeqContext = CA_VariantIUnknown (tempActiveXRef);
     //Convert variant to object handle
   CA_VariantConvertToType (&tempTSSeqContext, CAVT_OBJHANDLE, &TSSeqContext);
tsErrChk(TS_PropertySetValString(TSSeqContext, &ErrorInfo, "MyLookup.String", 0, "Testing"))
I haven't tested this exact code, but I modified some code that I know works for the purpose of demonstration. Like I said, I wish there was a way to just type cast straight to the Object Handle, but since you are getting an LPUNKNOWN object, you have to first go the variant. Have a good one.
Adam

Customize / Modify the Admin User Interface

Hi.
I know that a couple of other people have already posted this question here. But, so far there haven't been any responses.
Is it possible that it is simply IMPOSSIBLE to modify the Administrator User Interface?
The main Admin User Interface looks like this :
HOME --- ACCOUNTS --- PASSWORDS ---- WORK ITEMS ---- SERVER TASKS
Where and how can this interface be customized (if, for example, I want to remove a couple of those Tabs) ?
Thanks

Hi Michael.
Thanks for your response.
Believe me, if there was another way to do this, besides fiddling with the "Bodystart.jsp", I would gladly do it. I really do not want to mess around with JSP files, especially after what just happened (When I inserted that code, and tried to re-run IDM, my browser did not even open. I got an error message, saying that the JSP had been "contaminated". I quickly deleted all that mess I'd put there)
I actually hoped that it would be possible to do this somehow, through the Roles and/or Security Functions (as Sec_Tk suggested earlier in this posting).
However, as I mentioned, the administrators I created do not have any capabilities beyond merely *"Create, Delete, Update, View--User"*
Unless there is somewhere else I need to modify capabailties?

In simple user Interface modify the sequence view to show only executing step

I want to see only the Single executing step in sequence view of the user interface
are there any egs for the same!!

This is relatively trivial to implement yourself. Handle the UIMessageEvent of the ApplicationMgr and when you get a trace UIMessage do something like the following:
if (uiMsg.Event == UIMsg_Trace)
    int notUsed;
    String currentStepName = "";
    SequenceContext context = uiMsg.Thread.GetSequenceContext(0, out notUsed);
    if (context.NextStepIndex >= 0)
        currentStepName = context.NextStep.Name;
    /// Do something with currentStepName like update an indicator control.
Hope this helps,
-Doug

How can I display step info in User Interface with Tracing Disabled?

I'm trying to modify the CVI Operator Interface application to update the execute panel with some step information during the execution of the program. i.e. I want to display the measurement, high & low limits during the run WHEN TRACING IS DISABLED. (Doing this, when tracing is enabled is easy, all you do is access the step record that's been constructed (I can cope with that!))
I've successfully implemented a User defined execution event to signal the User Interface application when the current step is a result (using TS_UIMsg_UserMessageBase etc. I'm posting a UI Message in the Process Model under the ProcessModelPostStep so that I will only display if its a result step.) I've added a user defined
entry in the execute.c module execution event switch statement which will call a function in the exedisp.c module to update the display. However, I don't have a context to the step that I can use. (I can't use e.g. the exeRec record since this is only completed with the context if tracing is enabled.) I've got a handle to the correct panel to write the information to, but how do I get the context to the current step when tracing is disabled?
Regards,
Brian

Hi,
no problem - btw, if you wanted to acheive this in TS 1.x, you could always write to a local variable with the ActiveX reference for the step concerned, and then use the msg reference that you have in the OI within the UI Message handler, to dig through to the Execution ->Sequence File->Sequence->Locals, or Execution->Thread->SequenceContext (and you can get almost anywhere from that).
Hope that helps
S.
// it takes almost no time to rate an answer

User Interface Template for Interactive Report Region

In 3.2, where do we set the user interface template for Interactive Reports region?
No matter what out of the box theme I switch to, the Interactive Reports region shows the same. What and where do I change the template so that alternating rows use two different colors?

There is no template for Interactive Reports like for a "normal" report. You need to modify the CSS and supply your own for this to happen.
I believe most things are tagged with #apexir - firebug with Firebox is invaluable. This thread may help:
Re: changing the look and feel of interactive report.

Unable to load the user interface-please reinstall the application-Audigy 2 zs Platinum

unable to load the user interface-please reinstall the application---this is the message I get when my pc starts------Someone messing around with my computer tried to delete creative media source player 3 when they saw I had both 3 and 5 in folder and i get this error message every time I start my pc. In addition to this I have lost my EAX and THX consoles and my speaker settings are gone so I cannot adjust my 5. system at all. After I delete that error message when I click on the creative icon is sys tray instead of opening up the creative media player I get the error message--unable to load needed componants. Please reinstall the application. this is media player 3[version 3.32.]. I dont know why during the auto?updates through the last couple of years I have media player 3 in sys tray and if I need version 5 it is in file with 3--start-all programs-creative--any way my pc is a Cyberpower AMD FX-53 using win xp pro-32 bit-- and of course its a OEM product so they tell me the only way to get it to work is use the restoration cd they gave me when I bought the pc and it will revert back to its original state as when purchased. I would lose all my games, music, pictures?ect and would have to start from scratch.[ OR of course back everything up on a portable hard dri've]?It seems like there should be an easier way --hell I might as well buy a new soundcard and it would make it easier. If anyone?has an answer for someone who is not a tech head so I can understand please help !!--thank you in advance for any assistance as it is greatly appreciated. Sorry this message is so long winded, just irritating to have spen so much for a pc and not have the original installation disc.-tried moving to another slot and the fixes I saw posted here with no luck---thank you folks again--Tom

All the issues you guys are talking about have been reported in beta stage of these new drivers. I would say none of them has been fixed yet. The only solution for now is to use previous drivers which work fine or use some modified drivers which fixes some issues, but not all. Your choice.
[url="http://connect.creativelabs.com/windows/Lists/Audigy%20Issues/AllItems.aspx">Bug List[/url]
Message Edited by ronon0 on 08-07-2008 :47 AM

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.
==============================================

How do I fix incorrect resolution for Firefox user interface on Retina display Mac?

I have a 15" retina display Mac (roughly a year old) running Mountain Lion. A couple weeks ago the user interface in Firefox seems have switched from using the normal zoom level of every other application to the native dpi of the retina display monitor. This means that the UI elements are all extremely tiny, etc. Is there anyway to reset this without simply reinstalling or reseting the rest of my configuration?
Currently running Firefox 27.0.

You can try to modify the gfx.hidpi.enabled pref on the <b>about:config</b> page (<=0: disable; 1:all screens same res; >1:enable always).
*http://kb.mozillazine.org/about:config
Try to disable hardware acceleration in Firefox (you need to close and restart Firefox).
*Firefox > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can set the layout.css.devPixelsPerPx pref on the <b>about:config</b> page to 1.0 and if necessary adjust layout.css.devPixelsPerPx starting from 1.0 in 0.1 or 0.05 steps (1.1 or 0.9) to make icons show correctly.
*http://kb.mozillazine.org/about:config
See also:
*https://support.mozilla.org/kb/forum-response-Zoom-feature-on-Firefox-22
Use an extension to adjust the text size in the user interface and the page zoom in the browser window.
You can look at this extension to adjust the font size for the user interface.
*Theme Font & Size Changer: https://addons.mozilla.org/firefox/addon/theme-font-size-changer/
You can look at the Default FullZoom Level or NoScript extension if web pages need to be adjusted after changing layout.css.devPixelsPerPx.
*Default FullZoom Level: https://addons.mozilla.org/firefox/addon/default-fullzoom-level/
*NoSquint: https://addons.mozilla.org/firefox/addon/nosquint/

BPM Workspace Customization & User Interface: Best Practice Question

Hi All,
This is our first BPM Project in house and we are on Oracle BPM 11g.
The business process involves request for approval for a permit from a public user and internal users need to approve/reject the same. Pretty simple and straightforward so far.
But we are now having lots of questions wrt to user interface.
1. Work Space Changes.
If we develop this application completely in Oracle BPM, the outside user (general public) will also see the 'workspace' with its current interface. It would be impossible to handle user training on this interface for a simple Joe Bloe, who may not be computer savvy) So the requirement documents demand that the look and feel of the outside users should be totally different than what the workspace provides. They want this to be customized in such a way that iit would strip all of the default lay out (left navigation bar, and get rid of the upper section completely. with its list of tabs) and also to modify the task list that appears below).
We have figured out how to achieve this (by modifying the workspace .jar files and recompiling the same), but is this a good approach? What happens if we are developing a brand new application on the BPM in our shop? This change will affect that application as well, as the workspace is shared and common to all the apps? I want some of you experts to let us know, your thoughts on this. If this is not a recommended practice, what would be best way to achieve what we want using Oracle BPM? (Where we want a simple intuitive user interface, without the default add ons that comes with the work space)...
2. What would be the best method to create a user registration page (where a user creates his own login and password and maintains his account) for an application using the BPM ? Right now we are thinking this should be in either a ADF page/ JSP page or (worst case a PL SQL cartridge) that can be launched on the browser, which will be open and does not require any kind of authentication to access. Is this a good practice or recommended one? Or are we missing out on something within BPM application itself, that we are not aware of and that would let us do this?
3. Also, if we go with an external ADF application for the 'public' user interface developement, then how can we (or can we) leverage the BPM's internal storage for the submitted data from the payload? I understand that it stores this information currently on the server 'soa infra' tables some where? Thru an external ADF app, can we write into these tables (Is this recommended or just sounds plain ridiculous)???
Knowing answers to these questions will help us decide, if this is the right tool for the job at hand.
Appreciate your time and xpertise.
Thanks
SR

Hi All,
This is our first BPM Project in house and we are on Oracle BPM 11g.
The business process involves request for approval for a permit from a public user and internal users need to approve/reject the same. Pretty simple and straightforward so far.
But we are now having lots of questions wrt to user interface.
1. Work Space Changes.
If we develop this application completely in Oracle BPM, the outside user (general public) will also see the 'workspace' with its current interface. It would be impossible to handle user training on this interface for a simple Joe Bloe, who may not be computer savvy) So the requirement documents demand that the look and feel of the outside users should be totally different than what the workspace provides. They want this to be customized in such a way that iit would strip all of the default lay out (left navigation bar, and get rid of the upper section completely. with its list of tabs) and also to modify the task list that appears below).
We have figured out how to achieve this (by modifying the workspace .jar files and recompiling the same), but is this a good approach? What happens if we are developing a brand new application on the BPM in our shop? This change will affect that application as well, as the workspace is shared and common to all the apps? I want some of you experts to let us know, your thoughts on this. If this is not a recommended practice, what would be best way to achieve what we want using Oracle BPM? (Where we want a simple intuitive user interface, without the default add ons that comes with the work space)...
2. What would be the best method to create a user registration page (where a user creates his own login and password and maintains his account) for an application using the BPM ? Right now we are thinking this should be in either a ADF page/ JSP page or (worst case a PL SQL cartridge) that can be launched on the browser, which will be open and does not require any kind of authentication to access. Is this a good practice or recommended one? Or are we missing out on something within BPM application itself, that we are not aware of and that would let us do this?
3. Also, if we go with an external ADF application for the 'public' user interface developement, then how can we (or can we) leverage the BPM's internal storage for the submitted data from the payload? I understand that it stores this information currently on the server 'soa infra' tables some where? Thru an external ADF app, can we write into these tables (Is this recommended or just sounds plain ridiculous)???
Knowing answers to these questions will help us decide, if this is the right tool for the job at hand.
Appreciate your time and xpertise.
Thanks
SR

How to create Labview User Interface with buttons?

Hello,
I try to create a user interface, where the TestStand sequencies can be selected one by one not only Test UUT, Single run and run Mainsequence (about 20 buttons needed).
I'm playing with the simple UI shipped with TS and can load the sequence file and run automatically a sequence (Main or another).
How can I create and assign buttons to all sequence files in my TS project?
Any help would be appreciated.
Thanks. (TS 4.0, LV 8.0)

I've modified my main VI with the below steps.
I still don't know how to create and assign front panel buttons to the user interface.
Anybody could explain to me how do I need to modify the attached part of my main vi and how to assign buttons.
Thanks.
Attachments:
InteractiveArgs_2.png ‏12 KB

Calendar User Interface (X7)

I'm a new X7 owner, fighting my way through a confusing user interface. On my second call to my telco, I got sent the PDF of the user manual for my phone. It answered some questions, but nothing for the calendar.
It tells me to fill in the fields. Not a single word on what the fields mean! So what DO these fields mean? When I click through into the data entry for an icon, it should add a title for that field.
I'm in edit mode for a single-shot appointment. I have an icon of a calendar page with a right-pointing arrow in the lower right. I have an icon of a calendar page with a right-pointing arrow in the lower left. I assume that these are controlling the repeat characteristics of the appointment. But this is a no-repeat appointment as indicated further down the page as "circle-arrow Not repeated". If that's what these fields are, why are they shown before selecting repeat?
What does private or public syncronization mean?
Is there any way to link the phone book to my appointments? I already have my doctor's address in the phone book -- why should I re-enter it here? If I want to phone him to modify my appointment, can I click through from the calendar? Why not in the twenty-teens? My doctor has a nice dozen-character Polish name -- shouldn't I be able to right-click (oops -- long-press) his name in my phone book and choose "schedule meeting" from there, rather than typing in a name and address all over again?
I discovered 1-for-AM, 2-for-PM by experimentation. Shouldn't this be in the user manual?

In calendar interface, standard is 30, but if you need 15 etc you need to a modification etc, use the normal interface with clock times or in details screen you can enter clock times enable fore the cats profile using CAC1 http://scn.sap.com/thread/3678682

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 avoid long user interface response time in long measurements ?

Hi
I tried to find more information regarding techniques how to avoid long user interface response times in case of extremely long measurement times with an external instrument communicating over GPIB, so I post this hoping to get some hint or a link to a guideline. I guess this is quite normal problem.
Problem is that when I want to measure long time in order to get an average result from the instrument, I have to wait until the result is returned from the instrument. Obviously that makes the user interface response very slow in traditional technique.
My restriction is the old GPIB 488 instrument driver that I would not want to modify, but I have source code to it.
What would be the best way to improve the response time for user interface ? I have looked into the few things:
* multithreading
* callback in main program for GPIB events
* modifying instrument driver e.g. to support VISA and creating a VISA callback
regards,
Petri

Several ways to do this:
If you're getting several measurements, you could have the instrument generate an asynchronous interrupt (an "SRQ" in GPIB terms), then collect the data in response to the SRQ callback. While you're waiting for the SRQ's, you can have your main thread running the interface so responsive GUI. You don't have to spinlock on the GPIB read waiting for instrument data.
Or, as you mentioned, you could spawn a thread to manage the measurements, and use a timer in the main thread to periodically allow you to check the status of the measurement thread. Again, the main thread mostly just runs the user interface.
Either way, the idea is to keep the main thread freed up most of the time to run the GUI, and have it periodically check for completion of your measurement sequence. While you're waiting in the main thread, you may want to make sure the user can't inadvertently re-trigger another measurement sequence until the active one is complete.
If you do find yourself doing a dead wait, you'd want to break this up into a series of shorter waits, and in between each wait, do a ProcessSystemEvents from the main thread to keep the GUI active.
Menchar

Modify User Interface

Similar Messages

Maybe you are looking for