![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Multiple Modules with WEXP Topic Summary: Created On: 14-Dec-2007 14:57 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Does anybody know of a way to export the contents of multiple modules to a Word document using WEXP? For example, we have a module that contains all of our abbreviations and I would like that included when exporting a requirements module.
|
|
![]() |
|
![]() |
|
Using the WEXP View Name and WEXP Module View attributes the view from another module can be exported at the appropriate point.
------------------------- - Martin |
|
![]() |
|
![]() |
|
Are those attributes created by WEXP automatically? I don't seem to have them. What are examples of values for those attributes?
I'm trying to use the index module creation script in WEXP and nothing seems to happen after I specify an index. Does anybody have any experience with that feature? |
|
![]() |
|
![]() |
|
As for exporting multiple modules: The attributes "WEXP Module View" and "WEXP View Name" are created when WEXP is called for the first time. The correct values are the (full) name of the module to be inserted, and the name of the view to be used during export.
As for the index, I have never tried this feature. Regards, Peter |
|
![]() |
|
![]() |
|
Peter,
Thanks for you response. I set the WEXP View Name attribute to the name of the module both using the full path including the project and then only the module name. I set WEXP View Name to the name of the print view in the module being inserted. I've set those attributes in both headings and object text objects in the main module. None of these combinations seem to work for me. Is there another attribute that I need to set? I've used WEXP to export the module being inserted so all the WEXP attributes exist in that module as well. |
|
![]() |
|
![]() |
|
One of the problems is that there are some WEXP related attributes with quite similar names, so you have to be double careful. I am saying this as you mixed them up in your post already ...
WEXP Module View: Full path to the included module WEXP View Name: View to be used in the included module That's all. The WEXP attributes don't have to exist in the included module. I attached a small script which opens the included module. Run it from the main module, go to the object where the WEXP attributes are set and click on "Open module". If the module to be included does not open with the correct view, you made a mistake when setting the attribute values. Most likely a typo in the view name, e.g. upper case / lower case. Regards, Peter |
|
![]() |
|
![]() |
|
Thanks Peter. You were right, I put the module name in WEXP Module Name instead of WEXP Module View.
Edited: 19-Dec-2007 at 15:52 by Sudip Das |
|
![]() |
Telelogic DOORS
» General Discussion
»
Multiple Modules with WEXP
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.