Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - phokanson

Pages: [1]
1
Bugs and Issues / Baseline versions don't seem to show up
« on: December 10, 2014, 01:48:05 am »
We have an extensive tree within a project based on dividing our content up into Catalogs (applications, business processes, data, etc).  The process I'm trying to follow is that each week I need to generate an HTML document from the entire project tree.  To start that process I select the top level tree and create a new baseline.  The trouble is, it finishes (takes a long time ... 4+ hours) without error, but when I go back in to list the baselines, it never created one (or at least it doesn't show up).  Have anyone seen this same thing?  Is there a remedy?



2
Automation Interface, Add-Ins and Tools / Automated document generation
« on: September 03, 2015, 06:28:50 am »
We want to be able to generate HTML versions of our models each Friday.  Right now when I do it, I have to baby sit it as each large slice of the model is generated.  We've divided our models up based on TOGAF structure, so a large slice is defined as "The business domain" which is contained under a single package.  It currently takes me in excess of 6 hours to generate all of what needs to be generated.

Is there any way to have EA automatically generate these documents so I don't need to baby sit it and kick of each slice one by one?

3
Automation Interface, Add-Ins and Tools / Script to convert an element type
« on: December 10, 2014, 12:54:51 am »
Does anyone know of a script to convert all elements of a particular type to another type?

For instance, suppose I have Activity elements through out a project tree and I want to convert those to an element type that I created (derived off of a UML Activity or some other type).  Does something like this exist?

4
Does anyone know of a script that replaces an element with another updated element?

We maintain two trees of project models (all within the same project database).  One tree holds the current (AS-IS) model state that is in production.  The other tree holds the models that are in redesign (TO-BE).  When the redesign models have been approved, we want to replace links with in the AS-IS tree with the updated elements/packages in the TO-BE tree.  If there are just one-zee, two-zee, replacements it's not too bad.  However, we've had several project (an numerous coming up) where many elements/packages will need to have updated links.

Pages: [1]