Hide Test UUT button during execution

Is there an easy way to hide the entry point button "Test UUTs" once it is clicked? I want to prevent an operator from starting up duplicate test executions.
I am using TestStand 3.5
Solved!
Go to Solution.

Thanks for the help,
What I ended up doing was using the PostUI message in the custom user message range (above 10000). Then I created a callback vi to handle user messages. I passed a reference to the Test UUT entry point button and enable or disable it. Basicly I can have my sequence handle the state of this button. The Post UI messages happen in the process setup and cleanup of my sequence files.
I attached a snapshot of the callback vi.
Paul
Attachments:
UIMessageCallback.jpg ‏56 KB

Similar Messages

Hide Test UUT button in 4.1

I am looking for a property in test stand 4.1 to allow me to enable/disable Test UUT and Single Pass buttons dynamically on the RTOI.
Your help is appreciated.

Depending on what RTOI you're using, you may want to dim or remove the menu options for the entry point. In the process model, the Test UUTs and Single Pass Entry Point sequences have a section (Entry Point Enabled Expression that you can add a variable or expression that you then control through your RTOI. I believe that this will also manage access to your buttons in the same way that the permissions allow access to the Single Pass entry point.
-Jack
Message Edited by Capt. Jack on 09-17-2009 11:53 AM

Test UUTs button + others disabled in Operator Interface after deployment

I am using the Simple OI example in my code.
However after deployment to my deployment PC I can select my sequence but all of the TestUUT or run sequence buttons are grayed out?
I feel as this is something simple that, perhaps I have missed.

Hi Taylor,
From what you have described it sounds like you may not have the right permissions set up for that user. Another thing you could try is deploying the full featured version and determine if the problem is specific to the simple OI or just a deployment problem. I have attached two links that give more information about deploying in general and deploying the OI. If these things do not work or you have more questions please let me know and please supply the version of Teststand, development computer OS, and target computer OS.
Patrick H | National Instruments | Software Engineer

How can I show and hide an image or a decoration on the front panel during execution of the vi?

Hello,
I've made a user interface with a little grafic description.
That description should change depending on user actions, e.g. if the user switches a button, some lines should disappear and some other lines should appear.
I thought some decorations could be shown and hidden via something like a property node, but that is not possible. Images can also not be hidden during execution of the program.
Is there any posibility to change a grafic user interface?
Johannes
LV 7.1
Greetings Johannes
Using LabVIEW 7.1 and 2009 recently
Attachments:
LV_Grafic.JPG ‏21 KB

Thanks to Tim for drawing what I suggested as option while I had some real work to do.
There is a trick of overcoming the index problem that was presented/devloped in the forum in the last month's:
You can place the decoration inside a cluster, so you can use the lable of the cluster to adress the decoration you want. The data type of the cluster doesn't mather for this, so you will hide the control/indicator. And you colour the cluster transparent (hint: right click with the coloring tool and use space to toggle).
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Disable a test socket during execution (Batch Mode)

We are running a Batch Model with Batch Synchronization. I am wondering if it is at all possible to totally disable one or more of the test socket during execution. I know that the opening screen allows you to choose which sockets are active, but in the event that something goes astray like the RS-485 communication is non-responsive, I would like to disable one or more at anytime during the test. Thank you in advance for any ideas you come up with.
Regards
Scott
Environment: TestStand 2010
Solved!
Go to Solution.

I am not aware of how to stop a socket which is already running and facing an error midway.
But this setting will ensure that the socket is disabled for the next runs.
1) Override the preBatch callback.
2) Call this statement in the current executing thread to stop the socket from next run. ( precondition = on error)
RunState.Caller.Parameters.ModelData.TestSockets[RunState.TestSockets.MyIndex].Disabled=True

Test UUT and SIngle Pass missing during deployment

With the help of this forum, I managed to get a Teststand deployment working.... thanks for the help.
I do have one issue though...I am using the SImple User Interface in a parallel model. In my project, when I open the Testexec and sequence, I have 3 options. These options are Test UUT, Single Pass, and Run Sequence. After compilation and running Testexec, I only have Single pass.
Any idea why this would happen? I keep trying different things but it takes forever to create builds.
Thanks,
Ryan
Solved!
Go to Solution.

Norbert,
Thank you for your reply. I attached two screenshots....one before deployment (on my development PC) and one after (on my test machine). I did see something odd when capturing the screens. You will notice that the "Main Sequence is GREEN on the deployment PC, but once it is installed on the test machine, it is then BLUE.
I believe this is the issue but I don't know how to solve it. Please see photos.
Thanks!
Ryan
Attachments:
before_deploy.JPG ‏120 KB
deployed.JPG ‏57 KB

Run test uut entry point only once

Hi,
I want to avoid that users can run test uuts entry point more than once. I use an operator interface written in CVI 7.1.1 and netry point button is deactivated when run state changes. But after loading the application sometimes is too slow so the user can press this button twice before it is deactivated.
So is there any possibility to avoid running this entry point more than one time?
Regards
Steffen

Steffen,
Thank you so much for the help. You recommendations worked perfectly. Both of us implemented more or less the same behavior in our operator interfaces, although we used slightly different methods. Here is what I did:
I established a count variable in my operator interface that is initially set to 0. Each time the Test UUTs or Single Pass button is pressed, I increment the count by 1. I determine that the Test UUTs or Single Pass button is pressed by registering for and handling the Application Manager PreCommandExecute event. In my callback for this event, I examine the returned Command and look at its EntryPointIndex property to see if the index is 0 (Test UUTs) or 1 (Single Pass). If it is, I increment the count variable count by 1. If the index is not 0 or 1, I do nothing. Once execution has stopped, I reset the count variable back to 0. I do this by registering for and handling the ExecutionView Manager RunStateChanged event (as you recommended). In my callback for this event, I examine the returned newRunState to see if it stopped (numerical value of 3). If it is, I set the value of the count variable back to 0. If it isn't stopped, I do nothing.
This method is basically the same as the one you propose. This method allows you to use the built in TestStand buttons instead of having to use those found in your development environment. The only drawback is that they don't disable and gray out during execution; they just do nothing when an execution is in progress and the operator presses them.

How to prevent running a sequence two times by using "Test UUTs or F5"?

How can prevent that a user can press "F5 or Test UUTs" more than one time???
Greets
Matthias

Hi Matthias,
If you haven't made any changes to your SequentialModel.seq then before you start make a copy of the SequentialModel.seq found in C:\TestStand\Components\NI\Models\TestStandModels and copy this to C:\TestStand\Components\USER\Models\TestStandModels.
Now launch the SeqEditor.
If you open the SequentialModel.seq file found in the C:\TestStand\Components\USER\Models\TestStandModels folder. With the
Test UUTs sequence active. Select the Menu Item Edit | Sequence Properties.
You should have the Test UUTs Properties dialog visible. Select the Model Tab. Enable the Hide Entry Point Execution control. Ok the changes and save the SequentialModel.seq file.
Now when you run your Sequence you will only beable to run one execution.
Hope this helps
Regards
Ray Farmer
Regards
Ray Farmer

Removing Key Figures during Execution

Hi, is there any way to remove any type of Key Figure, from the Key Figure structure during execution time? If so, how about adding them into the Key Figure structure as well?
Ex. I have Calculated KF A, and B. I want to have a button on a Web Template that removes KF B from the entire KF structure. When it does this action, the only Key Figure shown is KF A.
Any suggestions? Is there even a function/method in a class to do that? Even a hide function would work for me.
Thanks.
Message was edited by: Angel Henriquez

Hi,
for filtering, please have a look on
http://help.sap.com/saphelp_nw04/helpdata/en/59/edfe395dd76846e10000000a114084/frameset.htm
For an explanation how to get filter_iobjnm (the uid of the structure) and filter_value (the uid of the structure element) please see:
http://help.sap.com/saphelp_nw04/helpdata/en/76/80a1393e3a6942e10000000a11402f/frameset.htm.
To remove the filter just use the command remove_filter
http://help.sap.com/saphelp_nw04/helpdata/en/82/edfe395dd76846e10000000a114084/frameset.htm
Heike

Frozen screen during execution

Hi there,
I developed a VI to acquire pressure data from 48 sensors. During execution, the front panel freezes and the acquisition just stops. No error message appears and i just can interact with other objects, like graphs and buttons. Remember that the VI keep running, but the acqusition stucks. I'm using LabView 6.1. I'd apreciate if you could help me.
Thanks,

Attachments:
boolean azul(control).ctl ‏6 KB
teste (beta 15).vi ‏2037 KB
Prompt.vi ‏20 KB

ORA-04088: error during execution of trigger

Error Description :
We have more than 100 of records in a csv file which we are processing through a script. At the first execution let
say it generates trigger exception for five records ... when I execute the script second time those five records
are not throwing any exception but may be some other records. But consecutive trigger exception is not happening for any record . If a particular record is throwing exception at first attempt then in the second attempts it's not throwing the trigger exception.
Input file
PROPRTY_ID,NAME,OLD STREET,CITY,STATE,ZIP,NEW STREET,NEW CITY,NEW STATE,NEW ZIP
88527091,SAM PAUL SUMMU ,1061 XYZ,CITY1,ST,95626,5512 XX YY ZZ,TOWN,PA,12345-9812
Error :
88527091,SAM PAUL SUMMU ,1061 XYZ,CITY1,ST,95626,5512 XX YY ZZ,TOWN,PA,12345-9812 - PROPERTY Update Error : ORA-00001: unique constraint (PROD.PK_AUDIT_LOG) violated
ORA-06512: at "PROD.PROPERTY_AUD", line 159
ORA-04088: error during execution of trigger 'PROD.PROPERTY_AUD'
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> desc property
Name                                      Null?    Type
PROPERTY_ID                               NOT NULL NUMBER(20)
TYPE_CODE                                          VARCHAR2(10)
TYPE_PREFIX                                        VARCHAR2(10)
DWELLING_TYPE_CODE                        NOT NULL VARCHAR2(10)
DWELLING_TYPE_PREFIX                      NOT NULL VARCHAR2(10)
STREET_NUMBER                                      VARCHAR2(25)
STREET_DIRECTION                                   CHAR(2)
STREET_NAME                               NOT NULL VARCHAR2(45)
UNIT_NUMBER                                        VARCHAR2(15)
CITY_CODE                                          VARCHAR2(10)
STATE                                     NOT NULL CHAR(2)
ZIP_CODE                                           VARCHAR2(10)
UNIT_TYPE                                          VARCHAR2(10)
UNIT_PREFIX                                        VARCHAR2(10)
COUNTY_CODE                                        VARCHAR2(10)
COUNTRY_CODE                              NOT NULL VARCHAR2(10)
SQUARE_FEET                                        NUMBER(6)
NUMBER_MOTHER_LAW_UNITS                            NUMBER(6)
YEAR_BUILT                                         DATE
PROPERTY_VALUE                                     NUMBER(12)
ZIP_PLUS_4                                         VARCHAR2(4)
SFI_REQ_FLAG                                       CHAR(1)
LAST_MODIFIED                             NOT NULL DATE
LAST_MODIFIED_BY                                   VARCHAR2(31)
STANDARDIZED_STATUS                                VARCHAR2(10)
STANDARDIZED_DESC                                  VARCHAR2(200)
SQL> desc audit_log
Name                                      Null?    Type
SEQ_NO                                    NOT NULL NUMBER(20)
TABLE_NAME                                         VARCHAR2(31)
USER_STAMP                                         VARCHAR2(31)
TIME_STAMP                                         DATE
TRAN_CODE                                          CHAR(2)
RECORD1                                            VARCHAR2(2000)
RECORD2                                            VARCHAR2(2000)
FLAG_FLD                                           CHAR(1)
SFI_FLAG_FLD                                       CHAR(1)
ERROR_NUMBER                                       NUMBER
Update Query which is getting executed :
UPDATE PROPERTY
SET DWELLING_TYPE_CODE = 'SFR',
DWELLING_TYPE_PREFIX = 'DWELLING',
STREET_NUMBER = NULL,
STREET_DIRECTION = NULL,
STREET_NAME = ln_new_street_name,       -- <From input file>
UNIT_NUMBER = NULL,
CITY_CODE = ln_city_code,               -- <From other Table>
STATE = ln_new_state,                   -- <From input file>
ZIP_CODE = ln_new_zip_code,
UNIT_TYPE = NULL,
UNIT_PREFIX = NULL,
COUNTY_CODE = ln_county_code,           -- <From Other table>
COUNTRY_CODE = 1,
ZIP_PLUS_4 = ln_zip_plus_4            -- <From Input file>
WHERE PROPERTY_ID = ln_property_id;   -- <From Other table>
*NOTE :* Property.LAST_MODIFIED field is auto populate through other trigger. It does not causing any problem.
This might be helpful :
SQL> select OWNER, CONSTRAINT_NAME, TABLE_NAME,COLUMN_NAME from dba_cons_columns where CONSTRAINT_NAME='PK_AUDIT_LOG';
OWNER                          CONSTRAINT_NAME                TABLE_NAME COLUMN_NAME
PROD                           PK_AUDIT_LOG                   AUDIT_LOG          SEQ_NO
PROD_ARCH                      PK_AUDIT_LOG                   AUDIT_LOG          SEQ_NO
SQL> select SEQ_NO, trim(RECORD1), trim(RECORD2),TIME_STAMP
from audit_log where RECORD1 like '%BUTTE%' order by TIME_STAMP;
SEQ_NO
1675677212
TRIM(RECORD1)
00000000000031814095...SFR       .DWELLING ...5512 BUTTE VIEW CT                           ..15532
    .CA.95765     ...1377      .1         .....5000..20100922.SUSMSAHA                       ..
TRIM(RECORD2)
00000000000031814095...SFR       .DWELLING ...5512 BUTTE VIEW CT                           ..15532
    .CA.95765     ...1377      .1         .....5000..20100922.SUSMSAHA                       ..
TIME_STAMP
22-sep-2010
Trigger Body which is fired and throwing the exception :
create or replace trigger PROPERTY_AUD
before insert or update on PROPERTY
for each row
declare
rec1            varchar2(2000);
rec2            varchar2(2000);
tcode           char(1);
ln_seq_id       NUMBER:=Null;
ls_sql VARCHAR2(2000):=Null;
begin
select temp_audit_seq.nextval into ln_seq_id from dual;
rec1 := null;
rec2 := null;
     if user = 'NONREP_USER' then
        return;
     end if;
     if (dbms_reputil.from_remote = FALSE) then
          :NEW.last_modified := sysdate;
          if (user = 'SALESFORCE_SYNC') then
                  :new.last_modified_by := NVL(:new.last_modified_by,USER);
          else
               :new.last_modified_by := user;
          end if;
     end if;
if inserting then
rec1 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'I';
elsif deleting then
rec1 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'D';
else
rec1 :=
LPAD(:old.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:old.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:old.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:old.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:old.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:old.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:old.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:old.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:old.STATE, 2, ' ' ) || '.' ||
RPAD(:old.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:old.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:old.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:old.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:old.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:old.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:old.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:old.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:old.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:old.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:old.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:old.STANDARDIZED_DESC, 200, ' ' );
rec2 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'U';
end if;
ls_sql :='
INSERT INTO AUDIT_LOG
( seq_no,
table_name,
user_stamp,
time_stamp,
tran_code,
record1,
record2)
VALUES
( :id,
:s_table_name,
:s_user_name,
:d_sysdate,
:s_tcode,
:s_rec1,
:s_rec2
EXECUTE IMMEDIATE ls_sql
USING ln_seq_id,
'PROPERTY',
user,
sysdate,
tcode,
rec1,
rec2;
end;
Your suggestion is highly appreciated ..
Edited by: Bipul on Sep 23, 2010 12:40 AM

TEMP_AUDIT_SEQ generates number with the increment of +1
Although there seems other sequence populating the AUDIT_LOG table through a different sequence with the increment of +10. So till now there are already 1179 different numbers residing in audit_log.seq_no and yet to be generated by the TEMP_AUDIT_SEQ sequence. I will look into more details.
SQL> select max(seq_no) from audit_log;
MAX(SEQ_NO)
1675689121
SQL> select TEMP_AUDIT_SEQ.nextval from dual;
   NEXTVAL
1675677285
SQL> select count(*) From audit_log where seq_no>1675677285;
COUNT(*)
      1179
SQL> select count(*) from audit_log where seq_no>1675677283 and mod(seq_no,2)=1;
COUNT(*)
      1179
SQL> select seq_no from audit_log where seq_no>1675677283 and mod(seq_no,2)=1 and rownum<12;
    SEQ_NO
1675677291
1675677301
1675677311
1675677321
1675677331
1675677341
1675677351
1675677361
1675677371
1675677381
1675677391
11 rows selected.
Thank you Lee and Herald ten Dam   ...

Step post action works only in 'Test UUts' mode

Hi,
My main sequence file has a list of steps, all sequence type. I specify a post action on each one to jump to end if the seq fails and if a flag is set:
FileGlobals.StopOnFail == True && RunState.SequenceFailed == True
I found out that it only works if I run my test in 'Test UUTs' mode. If I select 'Run Selected tests using Single Pass', then, it igonre this.
Is this how it supposed to be?
How can i fix it?
Thanks
Rafi
TS4.1
Solved!
Go to Solution.

Rafi2003 wrote:
[...]Why do you need a previous step?[...]
Rafi,
you are correct that you do not need a previous step; it is sufficient if the step itself fails and sets the RunState.SequenceFailed flag.
On my machine, this test also works as expected so i asume that either your step itself does not set the RunState.SequenceFailed flag or you have another issue in your Run Selected Steps using Single Pass execution....
Norbert
[EDIT] Added small example sequence
Message Edited by Norbert B on 05-13-2009 06:26 AM
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Attachments:
PostAction.seq ‏5 KB

Where is hide/show toolbar button?

Hello all,
I have purchased Aperture as a retail package, and I am running Snow Leopard. I have a "hide/show Toolbar" button in the upper left of the title bar, as indicated in the included screenshot.
I used Aperture on a friend's machine, and he does not have the oblong "hide/show toolbar" button. His OS is Lion with Aperture installed from the Mac Store.
Does anyone have any ideas about why he would not have this convenient button, while I do?
nathan

Hello Nathan,
if you want a button in the toolbar to toggle it on and of, you could do the following:
Create an AppleScript to toggle the Toolbar on and off
Save the script as an application
Assign a nice icon to it, just like the drop of toothpaste, the button used to look like
Drag the Apple Script to your Finder toolbar
This AppleScript seems to toggle the toolbar - I have not done much testing so far:
(* Toggle the Finder Window Toolbar , Autor LDF *)
tell application "Finder"
activate
          set wi to front window
          set vis to (get toolbar visible of wi)
          if vis then
                    set (toolbar visible of wi) to false
          else
                    set (toolbar visible of wi) to true
          end if
          return vis
end tell
The only problem is, you can easily hide the toolbar this way, but once the toolbar is hidden, you cannot turn it on again, since the button now is hidden , so you may wish to put a link to the script in the Dock as well
Cheers
Léonie

In LabVIEW OI the Run Selected Step Using Test UUTs does not work

TestStand LabVIEW Operator Interface (old style) - TestStand Version 2.0.1 & 3.0
The Interactive option was enabled for the Process Model Entry Point - Test UUTs in the SequentialModel.seq.
When selective steps were selected to run within the LV OI using the menu item 'Run Selected Step Using - Test UUTs' it was found not to work.
The reason for it not working was because the main event string was "Run Selected Step 0" but this isn't available in the case statement. Changing the "Run Selected Step 1".."Run Selected Step 9999" to "Run Selected Step 0".. didn't produced the desired result. Instead of the selected steps running using the entry point Test UUTs, the steps ran without the process model.
The Case Statement string was retored back to "Run Selected Step 1".
The changes that are required to make the "Run Selected Step 1".."Run Selected Step 9999" work with either of the Entry Points are as follow.
In the VI TestStand - Create Entry Point Menus for Interactive Exec.vi
Insert an Increment from the iteration terminal of the FOR loop. This ensures the Message Queue string generated is in the range 1 - 9999 not 0 - 9999.
In the TestStand - Sequence Display.vi
For the Main Message Event "Run Selected Steps", "Run Selected Step 1".."Run Selected Step 9999"
In the case "1, Default", decrement the input 'Entry Point Index' to the VI TestStand - Start Interactive Entry Point Execution.vi. This ensures the Entry Point Index starts from the value 0.
Now when the selected steps are run using a Pocess Model Entry Point, they run correctly.
This problem only appears to affect the LabVIEW Operator Interface and only the old style. The new style that comes with TestStand 3.0 runs correctly.
There is one other problem. When an Operator is logged in to TestStand, the Entry Point - 'Single Pass' is disabled. But this is not reflected to the menu item 'Run Selected Step Using'. Both 'Test UUTs' and 'Single Pass' are available to the operator.
The reason for this is because in the VI 'TestStand - Create Entry Point Menus for Interactive Exec.vi' the sub menu item is enabled as a result from the property Sequence.AllowInteractiveExecutionOfEntryPoint. This is not enough to disable the 'Single Pass'. The Engine.CurrentUserHasPrivilege needs to be checked as well. Which means modications to the VI 'TestStand - Create Entry Point Menus for Interactive Exec.vi'.
Hope is maybe of help to anyone that may need to use this option.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
In_Labview_OI_-_Run_Selected_Steps_Using_Test_UUTs_doesnt_work.txt ‏3 KB

Thanks Ray for the "heads-up". )
I am about to implement a vi which calls TestStand functions. This vi will allow to select tests and permits test re-entry (loops) if the user has supervisor privileges.
I will consider what you recommend in this string.
I will also provide feedback on this thread if I discover anything .... let's say "unusual"..
On another note, I am using TestStand 3.0 I have not observed any problems when running selected steps or run selected steps using single pass. I have also within TestStand set privileges for certain Operators to do the same. They have not reported any problems.
Thanks,
JLV

Can I hide tree disclose button basing on node.attr?

Hi OTN,
I have an af:treeTable with dynamic node levels. It is not determined how many levels there are, but basing on node attribute I can find out weather the node is a leaf.
So I would like to hide disclose triangle button for those nodes that have certain attribute values.
Is that possible?
Thanks.
JDeveloper 11.1.1.4

Hi,
Try with inlinestyle property,
by setting the style class based on the #{node.attr}
Like : inlineStyle="#{node.attr='test' ? test:test1}";
af|tree::selector-icon.test{
content:;
}

Hide Test UUT button during execution

Similar Messages

Maybe you are looking for