modify report xml to delete 'Done' Steps

[nanor]

Hi,

I am trying to modify my Xml report in order to :

Add an array of calibration datas : Ok

Add an array of instrument datas : Ok

Delete every 'done' steps of the report.  Nok (and delete the table if there's no step inside)

Because my problem is that the table is created before testing/matching the results and i am afraid to be lost in the xsl file.

 Could someone help me with it ?

I join the Xsl file i try to modify and a Xml example file (extensions needs to be modified)

Thanks a lot !

[nanor]

Hi,

I have partially resolved my problem using "SequenceFilePostResultListEntry" and having a step with :

Parameters.DiscardResult = (Parameters.Result.Status == "Done")

But is there a way to do that in the process model to avoid adding this callback in each sequence ??

Thanks

[RayFarmer]

Just a point, if you know the step is just going to record "Done" then switch off the Record Result for the step.

That usually means most action, message-pops statement steps, steps in the Setup and Clean-up groups.

Regards

Ray Farmer

[Scott_Richardson]

You can use the same logic from the SequenceFilePostResultListEntry and place a ProcessModelPostResultListEntry callback in the model instead and this callback will be invoked for every step executed in the client and the files that it calls. The model aready uses this callback for on-the-fly result collection for reporting and database logging.

If you are not using on-the-fly reports, and you are concerned that the overhead of calling a callback sequence after every step executes, you could write a module to "clean" the results tree after calling MainSequence in the client and before generating the report. This would require you to traverse the step result tree recursively and deleting any step result that is Done.

[Jervin Justin]

You could also potentially just leave the actual .xml report as is, and then modify the Style Sheet to hide the "Done" steps.

TestStand 4.2 features improved XML Style Sheets that are restructured to reduce the time required to generate HTML output from XML report files and to simplify the task of modifying style sheets so that you can change the appearance and content of XML reports.

For more information about customizing TestStand XML report style sheets and using the included XML schemas, refer to:
NI TestStand Help: XML Report Style Sheets