Manual Inspection - Line Break

Follow
Aksel Åsheim
  • Edited

When I write text in the Sequence Designer for the Manual Inspection it's formatted. 
However, in the Operator Interface it's a wall of text without line breaks. 

First I assumed the formatting simply didn't transfer to the web client, but looking at the Test Report the formatting is there. Is it a reason for not having it in the Operator Interface or is this considered a bug.

0

Comments

3 comments

Date Votes
  • Official comment
    Andreas Kristensen

    Hi Aksel

    Could you please provide me with a bit more information about this? Are you talking about a specific step type? I see that the Description field in the Sequence designer is multiline, and this isn't reflected very well inside Manual inspection. I will add a backlog for us to improve this in our next biweekly hotfix release. Just want to make sure I understand where exactly you are missing the formatting.

    Comment actions Permalink
  • Aksel Åsheim

    I've had descriptions for Numeric Limit and Pass/Fail types that do not have line breaks applied in the Manual Inspection operator interface.

    I also have Message Box where I hadn't included any description. Added one now just as a test and noticed there still is no "Description" section for it.

    While I have you here: 

    SEQUENCE OVERVIEW | Load UUT misc info from previous report (product)

    • Serial number resets, revision doesn't (prefer both to reset). 
    • I would like the ability to set up this in the backend (Control panel)
    • I would like to be able to define function for sub-unit inputs, allowing multiple PN options for each defined function / position.
      F.ex. Controller, Resistor Board, Upper Sensor, Lower Sensor..

    As an example: 
    Controller = PN 123 or PN 345
    Upper Sensor = PN 678
    Lower Sensor = PN 678

    Things I lack

    • Add firmware for UUT or sub-units in the header (should be an option in Product Manager)
    • Add global test equipment (test cables, test boxes.. ) and type/revision for the same
      Would be in the header.

    Very often when something fails it comes down to test setup, I would like to be able to do a quick analysis to catch trends.

    • A test fails more often with a certain Test Box serial number.
    • A test fails more often with a specific PN used in a position where there is multiple options.
    • A sub-unit cause test failure in a specific position (sensor #1 rather than sensor #2) where same PN is used.

    If I dream a bit more, I wouldn't mind if the input in the header (such as PN used) would define which version of the test is run. Maybe I've changed the controller which alters the test but still have old products going through stock, RMA testing or similar.

    0
    Comment actions Permalink
  • Andreas Kristensen

    I would suggest adding these requests to our Idea exchange, and they will be considered for an upcoming version: https://support.virinco.com/hc/en-us/community/topics/200229623-WATS-Idea-Exchange 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post