Other Tests

This topic applies to the GainSeeker Inspections module. It features sub-inspection tests that may not require a lot of explanation.

This topic includes the following tests:

 Date/Time

 DMS Standard

 Text

 Line Break

 Comments

This topic also includes the following buttons:

 Save & Publish

 Run PC

 

Note: Not all of the sub-inspection test toolbar buttons are technically "tests." For simplicity, that term is used to describe all of the sub-inspection test toolbar buttons.

 

Contents  [Hide]

 

Adding a test to a sub-inspection

  1. Click a toolbar button to add that test to a sub-inspection.

  2. After the test has been added to the sub-inspection, use the Properties panel to change any properties for this test.

Test Properties

All properties apply to inspections run in the PC Collect module. Properties that apply to mobile inspections are indicated in the Mobile column below.

Test Name

Property and Category

Default setting or default display

Allows

Date/Time

 

Sets the date/time stamp that is stored with data.

Defaults to the current date and time of the PC or mobile device, but may allow the data entry inspector to set a specific date (not recommended for mobile inspections).

On PC, the date and time are formatted according to the Windows settings for Short Date and Short Time. To change the date and time format, see Changing the Date and Time format below.

GainSeeker will store date/time stamps to the minute, second, or hundredth of second based on your Show time to configuration setting.

 

Appearance

Label

Date/Time

Change the display label for this test.

You can double-click on the Date/Time test to edit this property.

Y

Behavior & Data

ForceCurrent

 

Note: All data for this sub-inspection and subsequent sub-inspections is stored using the date and time until it is overwritten by another Date/Time test.

False. Allows the inspector to select a date/time for the inspection.

True. Sets the value to the current date and time when this sub-inspection opens. This value cannot be edited.

 

Note: Do not use a Date/Time test if you want all data to be stored using the date and time when the data is actually submitted by the inspector.

 

Required

False. The inspector can Submit the sub-inspection without changing the value of this test.

True. The inspector cannot Submit the sub-inspection until they change the value of this test. (Changing the value and then changing it back to its original value is a valid change.)

The date/time change must be executed by the inspector, not by a Python script.

If this test's ForceCurrent property (above) is set to True, this Required property is ignored.

 

TestID

A unique TestID number is automatically assigned to each test in the inspection, but you can change this number to a more meaningful name.

The TestID property is only used in Python scripts for PC Collect inspections.

For more information, see About the TestID property

Enter a name for the TestID.

 

DMS Standard

 

Associate a DMS standard with the sub-inspection data.

All data for this sub-inspection and subsequent sub-inspections is stored using the selected standard until it is overwritten by another DMS Standard test.

By default, GainSeeker uses the inspection Process property to filter the list of Part Numbers you can choose from. However, if this sub-inspection contains a Defect List test that sets a different process, then that process is used instead when filtering the list of Part Numbers.

 

Behavior & Data

DMSStandard

[blank]. The inspector is required to pick a DMS standard from a list during data entry.

Choose the DMS standard for which data will be entered.

You can double-click on the DMS Standard test to edit this property.

Y

SearchMode

Search. When the inspector is typing a value into this test, GainSeeker will select the first standard that matches all of the characters typed. (Pausing for a second will start a new search, beginning with the next character typed.)

Use this option when using a barcode reader to enter the DMS standard.

Jump. When the inspector is typing a value into this test, GainSeeker will select the standard that begins with the most recent character typed. Typing the same character again will move to the next standard that begins with that character.

 

TestID

A unique TestID number is automatically assigned to each test in the inspection, but you can change this number to a more meaningful name.

The TestID property is only used in Python scripts for PC Collect inspections.

For more information, see About the TestID property

Enter a name for the TestID.

 

Text

 

Displays text such as operator instructions.

Appearance

Label

[blank]

Enter text for the display label. The tab character can be used to align and space the text.

(On mobile devices, this is limited to five lines of text.)

You can double-click on the Text test to edit this property.

Y

TextAlign

Center

Align text Left, Center, or Right.

Y

VerticalSize

Regular. Test is full-sized.

Short. Helps you to fit more tests on the screen. Test may be shorter, and white space above and below this test may be reduced.

 

Behavior & Data

MessageLocation

InLine. Displays the message in the Inspection Viewer .

Message displays the message text for the label in a pop-up window.

 

TestID

A unique TestID number is automatically assigned to each test in the inspection, but you can change this number to a more meaningful name.

The TestID property is only used in Python scripts for PC Collect inspections.

For more information, see About the TestID property

Enter a name for the TestID.

 

Line Break
Adding a Line Break to a sub-inspection adds a horizontal line that serves as a visual separator between rows on a sub-inspection page.

No properties available for this test

Y

Comments

APPEARANCE

Comment

[blank]

Enter notes about the inspection creation process. Notes will display only on the Inspection Editor Design panel, not on the running inspection.

You can double-click on the Comment test to edit this property.

Y

Changing the Date and Time format

To change the Short Date and Short Time formats used by the Date/Time test, follow these steps (provided for Windows 10 and for Windows 7):

In Windows 10

  1. Go to Settings.

  2. Click Time & Language.

  3. Click Additional date, time, and regional settings.

  4. Click Change date, time, or number formats.

  5. On the Formats tab, choose a different format for the Short date and/or Short time. Then click OK.



    If the list does not contain the format you want, you can add it:

    1. At the bottom of the Formats tab, click the Additional settings button.

    2. On the Time tab and/or the Date tab, enter the format you want to use. Then click OK.

In Windows 7

  1. Go to Control Panel.

  2. Ensure that View by is set to Category, and then click Clock, Language and Region.

  3. Click Change the date, time, or number format.

  4. On the Formats tab, choose a different format for the Short date and/or Short time. Then click OK.



    If the list does not contain the format you want, you can add it:

    1. At the bottom of the Formats tab, click the Additional settings button.

    2. On the Time tab and/or the Date tab, enter the format you want to use. Then click OK.

Executing a formula for a test

OnChange can be used to execute a formula for a specific test when certain conditions are met for the test in a running inspection. This works in conjunction with the Formula test. Python script is used to execute a formula for a PC Collect inspection. LiveCode code is used to execute a formula for a GS Collect inspection.

A formula can be executed for the following tests described in this topic:

See the OnChange topic for specifics about conditions that trigger the execution for these and other tests in a sub-inspection.

Save & Publish button

The Save & Publish toolbar button saves changes to the inspection, publishes the inspection, and leaves the Inspection Editor open.

Run PC button

The Run PC toolbar button runs the inspection as it would appear in the PC Collect module. You can use this to run an inspection - or a newer version of an inspection - before you publish it for data entry.

Related Topics