Requirements export to spreadsheet - include column(s) with parametric constraint(s)

[MartinFijneman]

Prerequisites

• [X] I have written a descriptive issue title
• [X] I have verified that I am running the latest version of the CDP4-IME
• [X] I have searched open and closed issues to ensure it has not already been reported

Description

related to testing of #188

tried out a bit, and would see added value of exporting the parametric constraint(s) as well. Although these can in principle become very complex, in most use cases (and normal circumstances), these will be rather straightforward and simple, and will then add some benefit of including these in the export I think.

To show, I've made an addition as mock-up to see the effect, including a simple one ( a<x) and a more complex (with AND, OR etc.0. In all, it doesn't look too complex to me.

According to the changes of the implementation, and the ongoing work, this would not be needed in multiple columns; a single column for each parametric constraint (based on the combination of relation expressions) is sufficient.

See screenshot:

would become:

Steps to Reproduce

Logs

• [X] There are no logs regarding the issue
• { ] I have attached a log file or included the relevant section in this issue

System Configuration

• CDP4 version:
  • [X] CDP4-IME: 5.0.0 RC 1
  • [ ] Other:
• Web Services:
  • [ ] CDP4 Web Services version:
  • [ ] OCDT WSP version:
• Environment (Operating system, version and so on):
  • [ ] Microsoft Excel (32/64 bit):
  • [ ] Windows OS (32/64 bit):
  • [ ] Additional information:

[MartinFijneman]

issue came up in setting up ROV model, issue request from Niels as well. benefit of having the possibility to use the parametric constraints in e.g. the workbook (and possibly other views as well), to be able to do comparisons etc. in your working space (and not only in the requirements verification itself).