ReqAdmin – Content References Not Updating in Single Pass using ‘Update’ command

Summary

The ReqAdmin update command was not fully updating content references in one pass. After running the update command and updating the authoring web service with the updated repository, when opening an REQ file in the RE3 tool, messaging indicated that content references still needed to be updated.

Technical Notes

  1. For Nested ContentReferences, the existing logic automatically ran the update process twice. If more than two nested levels existed, the update command had to be ran again which then update two additional levels. The command would need to be executed multiple times depending upon the number of nested content references. The logic was modified to update 'all' nested references in one single pass.
  2. Each time the update command was executed, the REQ filesize would grow as a result of updating contentreference elements with new IDs but leaving behind the old as unused rules. The logic was modified to update the parent content reference and any nested content references and update at the same time. This prevents new unused rules from being created but does remove any from existing repositories (development of a function to remove unused rules will be addressed in separate PBI).
  3. To improve performance, caching has been added at org structure level so that a child org that needs to update from a parent/root, won't re-update the parent/root if that was already done. Previously the caching was happening at the org level instead of org Structure level.

Implementation Notes

This feature requires a Requirements Administration Tool (Server Tools) update.