Where are Resource Documents stored?

[Nick Webb]

Hi all,
Just wondered if anyone knows where Resource Document information is stored?  I'm not doing too well looking through the database...
Cheers
Nick

[Geert Bellekens]

Nick,

I haven't heard of "Resource Document" information before. Care to elaborate?

Geert

[RoyC]

Geert

From the Help:

The Resource Document feature enables a particular documentation configuration to be 'remembered', linking the loaded template within the Generate RTF Documentation dialog to the current highlighted package. If a particular template is always used with a specific package, and multiple cases of documentation exist to be propagated, saving these as Resource Documents can ease document generation later. They save the package, output file destination and template name of the document.

You identify and store Resource Documents using the Resource Document button on the Generate RTF Documentation dialog.

... and they are accessed through the Documents > RTF Documents folder in the Resources window.

[Nick Webb]

Roy,

Thanks for the definition.

To be more specific, what I am interested in is whether the file paths are stored in the database?  I was exploring the idea of automating the creation of Resource Documents for an Add-In which uses the RTF Generator.  It appears that absolute file paths are used and perhaps that Artifacts/Linked Documents might be more flexible for relative path names, other file types etc.  ISound sensible?

Cheers
Nick

[Geert Bellekens]

Ah, RTF document generation stuff.  
Explains why I never heard of it.

Geert

[Aaron B]

if you are trying to find this information in the database, try looking in t_trxtypes where Description = "SSDocProfile"

[KP]

Nick, have a look in t_trxtypes.Notes where t_trxtypes.Description='SSDocProfile'. And try not to break anything!

EDIT: Rats! Aaron beat me to it...

[Nick Webb]

Having spent a lot of time playing with virtual documents I can produce pretty much what I need (sometimes with a bit of help from my add-in).  Main concern is that I don't want to clutter my model with multiple Model Document elements, which at first glance Resource Documents seem to address...   Perhaps dynamically building  the models and updating filters is a better approach?   it seems a shame to ignore the RTF features entirely as I think they are pretty flexible.  I might stop wasting time thinking about Resource Documents however!

Nick

[Nick Webb]

KP and Aaaron - many thanks!

I'll tread carefully and will persevere just for a little longer  

[Nick Webb]

One more question!  what does the "UID" in the Notes field reference?!

EDIT: found it - UID=package ID of package selected for RTF generation...  

LET'S GO!  8-)