Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Export to Word script to run as a scheduled task on Windows
Topic Summary:
Created On: 16-Sep-2008 18:29
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 16-Sep-2008 18:29
User is offline View Users Profile Print this message


anant mitra

Posts: 50
Joined: 27-Jul-2007

I'd like to export all the modules (including any OLE objects) in a project to separate word documents. I'd like the script to run as a scheduled task. I've looked at doors.dxl provided by Telelogic, that comes with the installation.

I figured that I need to get rid of the GUI to avoid all the clicks, in order to get the script to do what I need. Segregating the parts of the code so that the script does what I need seems to be an involved task in itself.

Please let me know if anyone has a better idea on how to go about this.

Thank You.
Report this to a Moderator Report this to a Moderator
 16-Sep-2008 22:46
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Scheduled Task means running DOORS in batch mode. The Scheduled Task itself will need to invoke DOORS as well as use the Command Line Switches '-batch', '-user' and '-password', meaning your password will be visible in the Scheduled Task. The task may look like this:

"c:\Program Files\Telelogic\DOORS_8.1\bin\doors.exe" -b "c:\MyFolder\MyBatchExport.dxl" -u MyUserName -P MyPassword

all in one line.

The DXL you use must be sensitive to batchMode, meaning it doesn't open up views and it doesn't do things like 'ack' or 'confirm' or display dialogs to the user, since there's no interface and no user. 'print' statements work but are best used for debugging as they will persist in a DOS window even after the batch is finished. The batch file will probably have to set the current folder, perhaps:

current Folder = folder("/MyProject/MyFolder")

First get the script to work interactively, then go for batchmode. Expect difficulties and frustration.

- Louie
Report this to a Moderator Report this to a Moderator
 17-Sep-2008 14:15
User is offline View Users Profile Print this message


Andrew Tagg

Posts: 151
Joined: 26-Oct-2004

Since, as Louie mentions, the username and password are visible in the batch file, it might be an idea to add a new doors user.'Batch' or somesuch. Give this virtual user just enough power to get the job done.

-------------------------
Andrew Tagg
Thales Air Systems, Melbourne
Australia.
andrew.tagg@thalesatm.com
Report this to a Moderator Report this to a Moderator
 25-Sep-2008 01:02
User is offline View Users Profile Print this message


anant mitra

Posts: 50
Joined: 27-Jul-2007

Got it figured out....works fine now.

Edited: 25-Sep-2008 at 01:19 by anant mitra
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.