ASAM XIL TestStand Steps 1.3 Bug Fixes

Visão geral

The following items are notable issues fixed between the release of ASAM XIL TestStand Steps 1.2 and ASAM XIL TestStand Steps 1.3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of ASAM XIL TestStand Steps.

Bug Number

Legacy ID

Description

Details

965226

SequenceContext does not recognize Globals

When using the Framework Get Variable Values step, you cannot use the returned value in a FileGlobal. When storing the value in a FileGlobal, the value remains as the default value.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

ASAM XIL TestStand Steps 1.1

Resolved Version:

ASAM XIL TestStand Steps 1.3

Added:

N/A

1074446

Copy/paste of steps from to a different sequence file breaks references

Copy/pasting a set of steps from one sequence file to another will result in broken references with "IDXXXXXXX" values.

Workaround:

Only copy and paste steps inside the same sequence file. Alternatively, one can manually fix all references.

Reported Version:

ASAM XIL TestStand Steps 1.2

Resolved Version:

ASAM XIL TestStand Steps 1.3

Added:

N/A

1074442

Extending ASAM XIL steps leads to runtime error

When an ASAM XIL step type is copy/pasted in the Step Types dialog with the intent of extending functionality, the resulting step will throw errors at runtime about being the wrong step type.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

ASAM XIL TestStand Steps 1.1

Resolved Version:

ASAM XIL TestStand Steps 1.3

Added:

N/A

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).