Topics

1

Suggestions and Requests / Model Document , Master Document into Linked Doc

« on: June 11, 2009, 01:52:23 am »

An option to have the Model Document and Master Document generate into their own self-contained Linked Document would facilitate usage of these elements as central documentation stores in the HTML Report.

As a Linked Document, the user would be able to view the documentation without the process of downloading and loading into an external viewer, and the model author would not need to worry about URL or file path references.

2

General Board / Connecting TFS 2010

« on: November 25, 2010, 06:54:21 am »

Hello, we've recently moved to TFS 2010, and I'd like to use it from EA.  Is there any specific instructions to do this?  I believe I need to use the Team Foundation Server MSSCCI Provider 2010 here: http://visualstudiogallery.msdn.microsoft.com/en-us/bce06506-be38-47a1-9f29-d3937d3d88d6

And then configure EA to use SCC.
When I do this, I am able to set the Local Project Path, and am able to select the Provider (it is the only one listed for me).  However, the Current User and SCC Project Path are not populated.  
When I attempt to save this configuration, I get an SCC_E_UNKNOWNPROJECT error dialog.

Am I doing this correctly?  What am I missing?

Thank you!

3

General Board / File references in HTML Report

« on: November 13, 2009, 09:51:18 am »

How can I maintain the proper reference to a file when working with the file locally and maintaining the reference when published as an HTML report?

For example, in a Document Artifact, I may add Files on my local computer.  When I publish to HTML Report, EA copies those files over to the destination in a \Files subfolder, but the references are not updated.
I have tried replacing the file path manually to what would be the relative web server path to the file, but this doesn't work either.

4

General Board / Linked document from Model Document in HTML Report

« on: June 10, 2009, 07:27:33 am »

I'm new to EA, and just getting my feet wet understanding all the capabilities of the report generation.
Here's what I'd LIKE to do:

• In diagrams in various packages, add a Document element with a linked document describing the vision driving what is being described in the diagram
• In a parent package, combine all the documents into one.  I've got a Model Document setup to query on all Document artifacts which works well and produces an .RTF with all documents concatenated

Linked documents work very well in an HTML Report - a simple click gets you to your formatted document.  And it's easy - there's no worry or management about URL versus file path, and how those must change when authored on a local computer and then deployed to a server.

So I want the final result to be a linked document as well.  But I can only figure out how to produce an .rtf file.  I was hoping the Model Document would behave like a linked document, or if a linked document was setup its content would be automatically updated when the Model Document was.

Is this possible?  Or a different strategy?  If the .rtf file is the only way, I can't figure out how to reference it so that the reference survives both locally and when the HTML report is deployed, so advice on that would be appreciated.

Thank you!