PropFlags_IncludeInReport doesn't work?

[10Things_Rob]

I have some properties in a custom step type that I would like to see show up in the report file.

* I set the PropFlags_IncludeInReport to TRUE. They don't appear in the report.

* I set the PropFlags_IsLimit to TRUE. They don't appear in the report.

* If I put my custom Properties in the Limits container, then they show up

* If I rename the Limits container to some other name, then they don't show up

So it seems that my properties must be in a container which MUST be called "Limits" and that's the only way to have them show up in the report.

Is that right?

Why have a "IsLimits" flag if they have to be in the Limits container anyway?

It doesn't seem as flexible as it should be.

I should be able to include any property in the report, without these artificial constraints.

I should be able to call my "Limits" container "Conditions" if I want to.

Is that really the way that it's supposed to work or am I missing something?

[Antonio Lie]

10Things,

Every step will automatically include every subproperty inside of the Step.Result property, a subset of the properties in the Step.TS property, and occasionally other step specific properties such as limits.
For your case I would recommend to add the subproperty under the Step.Result property.
This is the recommended method to use when creating custom step types. While editing the type, you cand add the step property directly.
The advantage of this is that all step instances will automatically have this property created very easily.
Be sure to select the IncludeInReport flag to ensure the property is copied to the ResultList.
If you do not want to put the step properties under the Step.Result property object you can use the 'Execution.AddExtraResult' API method to automatically copy the property to the ResultList based on its name.
This methos usually is called as an ActiveX step inside of the process model or added in a Model callback in a sequence file. By placing this step in the process model all the sequences that use this model will automatically  have the marked properties added to the ResultList. The default TestStand process mdels call this method to automatically add Step.Limits and Step.ComparisonType to the report.

Hope this helps.

Antonio Lie.