Add a new entry in Reports > Generate a Document-Style Report in DNG
I have derived several variants of the printModuleBook.doc file with specific styles.
When starting the Reports > Generate a Document-Style Report command in DNG, I would like to specify additional entries in the first dialog "Select the Document-Style Report Type".
I do not have an RPE Studio license.
When starting the Reports > Generate a Document-Style Report command in DNG, I would like to specify additional entries in the first dialog "Select the Document-Style Report Type".
I do not have an RPE Studio license.
3 answers
Hi Philippe,
You should only need RPE if you are making modifications to the report itself. If you are just changing the style sheet, you can replace the existing one in the /server/conf/rm/reporting/initialization/templates/word directory and re-initialize the publish service (https://<server>:<port>/rm/publish/initialize). Hope it helps,
You should only need RPE if you are making modifications to the report itself. If you are just changing the style sheet, you can replace the existing one in the /server/conf/rm/reporting/initialization/templates/word directory and re-initialize the publish service (https://<server>:<port>/rm/publish/initialize). Hope it helps,
Comments
I have been able to change the printModuleBook.doc file and re-publish the report. It works.
But I would like to have several "Print Module Book" entries, each pointing to a specific .doc.
I understand I have to add new entries in the MANIFEST.MF file but I do not know which .dta files need to be specified for these new entries. .dta files are binary files, I cannot change the printModuleBook.dta.
For each variant of printModuleBook.doc, you can have a corresponding .dta file in RRDG template folder (ex. C:\Program Files\IBM\JazzTeamServer\server\conf\rm\reporting\initialization\templates\rrdg). You can just copy paste the .dta file and rename it to match the file name of .doc. You do not need RPE Studio for this.
After this, register the new templates with DNG and reinitialize the publish service. You should see the new entries.
You can refer http://rpeactual.com/2014/07/17/deploying-templates-in-rrcdng/
After this, register the new templates with DNG and reinitialize the publish service. You should see the new entries.
You can refer http://rpeactual.com/2014/07/17/deploying-templates-in-rrcdng/
I followed the steps:
- add a new entry printModuleBook in the MANIFEST.MF (in META-INF directory) file with reference to printModuleBook2.dta
- copy and paste printModuleBook.dta into printModuleBook2.dta in rrdg directory
- create a printModuleBook2.doc (based on printModuleBook.doc) in word directory
- republish the templates in the server
Result: I manage to get the new entry in the Print dialog but when starting it on a module I get an internal server error 500 >>>>
hide details
Requirements Management/6.0.1
- add a new entry printModuleBook in the MANIFEST.MF (in META-INF directory) file with reference to printModuleBook2.dta
- copy and paste printModuleBook.dta into printModuleBook2.dta in rrdg directory
- create a printModuleBook2.doc (based on printModuleBook.doc) in word directory
- republish the templates in the server
Result: I manage to get the new entry in the Print dialog but when starting it on a module I get an internal server error 500 >>>>
hide details
URL: https://phil.clm.net:9443/rm/publish/report
token is expected to be in 'name/value' format (More info found at entry [69b66378d294af2b] in the RM application server log)
Requirements Management/6.0.1