Messages

1

Suggestions and Requests / Inheriting Paragraoh and Character Styles

« on: February 03, 2009, 10:23:04 pm »

I have searched the forums and as far as I know it is not possible to do this but it would be very useful for maintaining corporate standards.

It should be possible to set a property on a document template to tell it to inherit the paragraph and character styles from the master document if it is used in a master/model document setup.

This would allow the company standard styles to be defined in the master document rather than having to change all of the templates if a style change is required.

2

General Board / Re: Version control questions

« on: February 03, 2009, 11:57:21 pm »

The File History dialog has a Retrieve command, but it is only available when the package is checked in and the retrieved package is read only- therefore I cannot retrieve an old version from VC and simply replace the latest version in VC because I need to checkout the latest version first, which will effectively remove the old revision I retrieved. If I have the package checked out then the retrieve command in the File History dialog is simply disabled - is this the intended behavior?

This seems to be the intended behaiour, the help file states "The package revision is retrieved in read-only form, enabling you to view the package but not make any changes to the package." I would guess that this is to maintain the consistency of the model.

I am not sure if it possible to roll back a version as I have never had the need to try it -- yet.

The other question is that can a model stored in EAP be concurrently accessed by multiple users, assuming the EAP is on a network drive and version control is used?

As the other posters stated you can share the EAP file but you do have to watch out for accidentally treading on each others toes. You can also have this set up with version control if necessary, it is described in the help file as the "Single Shared Model".  We tend to work with the "Multiple Private Model" setup as it gives us more control and allows for easy offline working.

3

Bugs and Issues / Re: Document Template Corruption

« on: May 06, 2009, 01:47:43 am »

This is easy fixable. Export the template as RTF (from the template editor, choose File->Export from the menu), then open it in your favorite Office program and change the paragraph with the SSBookmark style to something different. Save it again as RTF and then reimport the template into the EA template editor (from the template editor, choose File->Import from the menu).

This should help.

Oliver

Thanks for the tip, I tried it but as I have already managed to remove the spurious protected text by removing and reinserting the Package tag I could not see anything unusual that might now be causing the problem.

I had a very good look at the two Element merge fields that were not being substituted and I couldn't see anything at all wrong with them.

In fact the only thing I could see starnage about the document was that a lot of the other merge fields looked corrupted but when I checked them out they just seemed to have random fonts assigned to them.

4

Bugs and Issues / Document Template Corruption

« on: May 06, 2009, 01:03:53 am »

I have just upgraded from verison 7.1 (830) to 7.5.844.21 and one of my document templates has become corrupted.

When I generated a document with it initially I noticed that it was not outputing images that were embedded in the template and the Element name output was corrupted.

The images (which were gifs) were easily fixed by deleting and reinserting them.

However there seems to be a more serious issue with the corrupted element tag. If I remove and re insert it the corruption is not removed and when I looked closely I noticed that there was a single character piece of yellow highlighted text (a carriage return) that remained when I removed the tag. If I try to delete this I get an error saying that I canot delete because it contains protected text.

If I remove the package tag which contains it and reinsert it then the problem seems to be fixed but when I generate the document the output contains the template data rather than the content, for example:

"element >
1.1. {Element.Name}
{Element.Notes}
< element"