How to search through structured specifications

[needsomehelp]

Our company has recently switched to structured specifications for our scenarios. Most of it has been good, but I can't search through the scenario's anymore.

Previously we used the extended model search to search through the scenario description. This doesn't seem to work now that we moved our flow from the description to the structured specification. Is there any way to still search through our scenarios?

Some other things we ran into:
- Structured scenarios are missing an option to create alternate alternate and exception exception paths.
- It is impossible to create loops
- It is not possible to show the entry point of the alternate or exception when generating a RTF template.

I've searched through this forum, but couldn't find a solution to any of these issues. Anyone here who could help me out?

[qwerty]

You can search with 'Extended' instead of 'Simple' in the drop down.

To create a loop you need an alternate path which joins back.

AFAIR the alt/alt, ext/ext issue is known. But I can't recall the status. Maybe others.

RTF - don't know that.

q.

P.S. Why do you first switch and then examine whether it works? Guess your hobby it to walk in mine fields.

[KP]

Previously we used the extended model search to search through the scenario description. This doesn't seem to work now that we moved our flow from the description to the structured specification. Is there any way to still search through our scenarios?

The structured specification is saved in the table t_objectscenarios which is presumably not included in the extended model search. Probably worth writing your own custom search and/or submitting a feature request.

[needsomehelp]

Thank you for the quick response, however it seems that t_objectscenarios is included in the extended search. However it contains the scenarios description under the notes attribute. The structured specifications must be stored somewhere else, any idea where that could be?

[Geert Bellekens]

No, they are in fact stored in t_objectscenarios, in the column XMLContent, which does indeed contain what you are fearing  

Geert

[needsomehelp]

Thanks, I see it now, but indeed not what I would have hoped to see.