Post WSXF

Reports in the WATS Standard XML Format can be submitted to WATS by calling this method with a WSXF report in the body of the request:

POST https://your-wats-server.com/api/report/wsxf

 NOTE: This method is available from server version 20.2.

The method returns OK 200 if the report was received and validated successfully, or 400 Bad Request along with a validation error text if the report does not validate.

This method can be used to submit Test reports or Repair reports.

Read more about WSXF here: https://virinco.zendesk.com/hc/en-us/articles/207424643-Wats-Standard-Xml-Format-WSXF-

 NOTE: This method is stricter than the original WSXF specification.

 NOTE: Attributes called Text should be text inside the element.

The following is a description of what elements and attributes are used in this format.

Reports

Reports is the root element.

xmlns is the XML Namespace, it can be thought of as the name of the XML format. The convention is to use a URL to a domain you own, so that all namespaces will be unique and the namespace describes who is responsible for the format. Some make the XML schema definition available from the namespace URL, but it is not required. Virinco does not do this.</p

Report

Process

Validation Rules

• Code and Name are required to be valid values.

MiscInfo

Validation Rules

• If type is UUR, Description is required to be a valid value.

ReportUnitHierarchy

Validation rules

• When type is UUR, one ReportUnitHierarchy is required to have Idx = 0,it is required to have PN, SN, and Rev equal to Report, and it cannot have ParentIDX.
• Idx is required to be unique.
• ParentIDX cannot be the same as Idx. 
• ParentIDX must refer to an Idx.
• ReplacedIDX cannot be the same as Idx or ParentIDX.
• ReplacedIDX must refer to an Idx.

Asset

AssetStats

UUT

Step

Validation Rules

• The first Step's Status is required to match Report Status and have a SequenceCall.
• Id is required to be unique.
• At least one of SequenceCall, NumericLimit, StringValue, PassFail, Chart, Attachment or AdditionalResults is required.
• SequenceCall, NumericLimit, StringValue, or PassFail cannot be nested together.
• Step can only be nested if a SequenceCall is also nested, and at least one Step is required if a SequenceCall is nested.
• Chart and Attachment cannot be nested together.
• If one nested NumericLimit, StringValue, or PassFail; Status and NumericLimit, StringValue, or PassFail Status is required to match.
• If multiple nested NumericLimit, StringValue, or PassFail; Status cannot be Failed unless at least one of the NumericLimit, StringValue, or PassFail have Status Failed.
• If status is Skipped, numericMeas, stringMeas, booleanMeas, callExe, messagePopup, chart, attachment, additionalResults and steps will be ignored. This provides better analysis of skipped steps. 
• If multiple nested NumericLimit, StringValue, or PassFail, Status cannot be Passed unless none of the NumericLimit, StringValue, or PassFail have Status Failed.
• NumericLimit, StringValue, or PassFail MeasIndex is required be unique within a Step.
• NumericLimit, StringValue, or PassFail Name is required be unique within a Step.
• Step Name within a Step is required to be unique.
• Step Index within a Step is required to be unique.

SequenceCall

NumericLimit 

NumericLimit is a measurement, where the measurement is a number.

 Validation Rules

• LOG is a none limit CompOperator; when used, LowLimit and HighLimit are not supported.
• EQ, NE, LT, LE, GT, and GE are single limit CompOperators; when used, LowLimit is required and HighLimit is not supported.
• LTGT, LTGE, LEGT, LEGE, GTLT, GTLE, GELT, GELE are dual limit CompOperators; when used, LowLimit and HighLimit are required. LowLimit and HighLimit are missnamed, think of them as Limit1 and Limit2 respectively.
• MeasOrderNumber is required to be unique.

StringValue

StringValue is a measurement, where the measurement is text.

Validation Rules

• LOG is a none limit CompOperator; when used, StringLimit is not supported.
• EQ, NE, CASESENSIT, and IGNORECASE are single limit CompOperators; when used, StringLimit is required.
• MeasOrderNumber is required to be unique.

PassFail

PassFail is a measurement, where the measurement is true or false.

Validation Rules

• MeasOrderNumber is required to be unique.

Chart

Validation Rules

• Cannot have more than 10000 data points total.

Series

xdata and ydata

The text in xdata and ydata is a semicolon separated list of numbers.

Attachment

AdditionalResults

Loop

Validation Rules

• Steps that are part of the same loop is required to have the same Name.
• One Step in a loop is required to be a Summary Step.
• ending_index in Summary Step is required to be the same as the index in the last Index Step.
• passed in a Summary Step is required to match the number of Index Steps with Status Passed.
• failed in a Summary Step is required to match the number of Index Steps with Status Failed.
• num is required to match the number of Index Steps.
• index in an Index Step is required to be unique within a loop.
• A SequenceCall. NumericLimit, StringValue, PassFail, or Step within an Index Step is required to have a matching SequenceCall. NumericLimit, StringValue, PassFail, or Step, respectively, in the Summary Step.
• A SequenceCall. NumericLimit, StringValue, PassFail, or Step within a Summary Step is required to have a matching SequenceCall. NumericLimit, StringValue, PassFail, or Step, respectively, in each Index Step.
• The last Index Step is required to have matching Statuses and measurement values as well.

UUR

Comment

Failures

Validation Rules

• Idx is required to be unique.
• PartIdx is required to refer to a ReportUnitHierarchy Idx.
• Category and Code are required to be valid values.

Binary

BinaryData

Validation Rules

• FailIdx is required to refer to a Failures Idx.