LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Requirements Gateway 1.1 terminates docx processing when encountering a symbol

My Word (*.docx) test procedure includes a symbol to denote margin around an expected value such as: "Each motor current reads 45 ±1 degree C"

 

When Requirements Gateway creates the intermediate document, it terminates the creation just before the "±" symbol, so the rest of my document is not included in the file. Obviously this means my remaining covering statements are not included in the coverage analysis. Removing the above symbol is the workaround.

 

Is this known behaviour?

0 Kudos
Message 1 of 7
(3,265 Views)

What is the intermediate document are you talking about?

 

I just made a requirement bsed on the string you provided.....(See the attached image) and i am able to read that requirement.

 

Can you post the same (your req doc and covering doc or something) so that the the same could be seen here

 

Guru

 

1.GIF

Regards
Guru (CLA)
0 Kudos
Message 2 of 7
(3,258 Views)

Bill -

 

I also tested this with both the WordX and Word types in Requirements Gateway 1.1. Perhaps you could provide a simple example project and files that replicates the behavior for me to look at.

Manooch H.
National Instruments
Message 3 of 7
(3,232 Views)
Maybe it makes a difference that it's contained in a table. Here's an example docx file and the intermediate file that was generated. Note the intermediate file stopped at the noted symbol.
Download All
0 Kudos
Message 4 of 7
(3,217 Views)

Bill -

 

I loaded your file in Requirements Gateway 1.1 and am not able to reproduce the behavior you are seeing. I have attached the example that I used to test this behavior below.

 

Could you verify your version of Requirements Gateway by going to Help»About and noting the build number?

 

niRG.png

 

Thanks.

Manooch H.
National Instruments
Message 5 of 7
(3,206 Views)

Apparently this had something to do with my type. I defined my own type based on the built-in WordX as I have unique attributes assigned (and this has worked fine with my requirement documents). Re-assigning my test procedure to the built in "Office" WordX type works. Which is why you couldn't recreate the problem.

 

I will leave the test procedure as the default WordX type.

 

Thanks for your help.

Message Edited by Bill@NGC on 03-02-2010 12:52 PM
0 Kudos
Message 6 of 7
(3,187 Views)
Oh, and yes, I'm using the same version and build of Requirements Gateway as you show above.
Message Edited by Bill@NGC on 03-02-2010 12:59 PM
0 Kudos
Message 7 of 7
(3,184 Views)