Current status

in version 3.8.3, assuming customers use the indexing v2. Please submit bug reports if you see any unsupported usecase!

Added the ability to nest data macros of Scaffolding inside of the “real Scaffolding macro”.

See also:

Public status will be updated on: https://requirementyogi.atlassian.net/wiki/spaces/RY/pages/2011824146/Scaffolding

Issues

• In version 3.8.3 and Scaffolding 8.29.9, reindexing the page (or editing it) is required after changing the Comala status. After 3.8.6, it works properly.

• In version 3.8.3 and Scaffolding 8.29.9, we have noted cases where Scaffolding renders an old cached version of the contents to Requirement Yogi, which we didn’t know how to solve. We’ve found that nested macros always had to be rendered nested (which removes the need for SUPPORT-174438).

• We’ve rendered most normal cases,

• We don’t extract the macros the same way for the Status and Easy Dropdown Menu (EDM) macros. For those two macros, we index the rendered results instead of indexing the source of the macro. We haven’t seen the difference in our usage, but maybe there is one.

• Recursive macros, Repeat and excerpt macros are not supported, when they contain requirement definitions.

The impact will only ever be that the property, the requirement or the entire page is not indexed for Requirement Yogi. Therefore, it’s worth trying and informing us of usecases that we are not aware of!

Technical difficulties

Scaffolding doesn’t provide a Java API to to access the XHTML/storage format stored in Scaffolding macros. It was requested and rejected on this support ticket, which means we’ve worked around it with the list of limitations above:

Video

Example of supported case

Results: