Module Richtext Contents - Text vs Modules schema method
If you want to publish the richtext contents of a module it seems like there are 2 methods:
|
Accepted answer
Hi Sean,
Sean F selected this answer as the correct answer
|
6 other answers
|
Thanks Kumar.
Comments
Kumaraswamy Gowda
commented Apr 15 '18, 9:46 p.m.
Not anything that I could think of.
Sean F
commented Apr 16 '18, 3:10 a.m.
Thanks Kumar
|
Good points.
|
OK I found another advantage of using the Module schema.
|
The only advantage I have been able to see so far of starting with the Module schema is that you can grab the name of the module itself before changing schema to process the module contents artifacts.
|
^thanks Kumar
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
You are right Sean. To print rich text content, you can use only text schema and set the data source URI as https://server:port/rm/publish/text?moduleURI=module1
However if you also want include module details / bindings / hierarchy, you can start with modules schema. The sample template DNG Module.dta mainly showcases how to configure the data sources for different artifact formats within the module.