1 / 2

First ,I have to make sure the document specification works.

Can you help with this problem? I am trying to use a command line switch to generate a document and there have been difficulties. First ,I have to make sure the document specification works. Starting it from the directory works so I believe the . dsx is set up correctly – true?.

enan
Download Presentation

First ,I have to make sure the document specification works.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Can you help with this problem? I am trying to use a command line switch to generate a document and there have been difficulties. First ,I have to make sure the document specification works. Starting it from the directory works so I believe the .dsx is set up correctly – true? Result - The document is generated and has the correct file name.

  2. …And the dxl is modified for the correct path names (see screen shot on previous page for path names),… When using this script retrieved from the forum the results are different. The module attribute is defined per instructions… // Export module using RPE with named RPE Specification /* SJF 2010/07/20 Created This script reads the value of an RPE specification associated with this module from a module attribute. It then invokes RPE launcher which generates the document For this script to function the module needs to have a module attribute called 'RPE Specification' The value of this attribute should be the name of the DSX file associated with the module (without the .dsx extension) If the DSX file is in a subfolder within the RPE specifications folder (defined by string variable 'RPESpecFolder') then the subfolder should be part of the attribute value and these should be separated with a double backslash e.g. m."RPE Specification" should be equal to "Project 01\\Business Requirements" */ // Set the value of RPESpecFolder to point to the folder where your RPE Specifications are stored // This would normally be a mapped drive on a server // Note: double back slashes must be used to separate nested folder names // Note: value must end with a double back slash string RPESpecFolder = "Z:\\RPE Demonstration\\" Module m = current string RPESpecAttrName = "RPE Specification" if(!exists attribute RPESpecAttrName) { ack "Module attribute '" RPESpecAttrName "' does not exist'" halt } string RPESpecName = m.RPESpecAttrName string RPESpecFullName = RPESpecFolderRPESpecName ".dsx" string RPEHome = getenv "RPE_HOME" string LauncherFullName = RPEHome "launcher\\rpe-launcher.exe" system "\"" LauncherFullName "\" -publish " RPESpecFullName "\"" And the results is a blank document without the correct file name. Can anyone spot the problem?

More Related