We had a minor hold up on the release, but I wanted to show you how easy it was to support an existing application with CoexEdit. There are different options which allow you to modify the design of your XPage application easily, but you can also make CoexEdit work with an existing template.
To demonstrate this, let's look at the standard 8.5.3 Discussion template. There are two forms which matter. Not the XPages or Custom Controls, but the forms which hold the data. The two that contain editable rich text fields are the "Main Topic" and "Response", though the "Main Topic" is stored as "MainTopic". Be sure to use the stored name (use the first alias if there is one). On each of these forms, the rich text field is named "Body", as many, many rich text fields are. The template name for the standard 8.5.3 Discussion database is "StdR85Discussion" (copy it from the Design properties tab). So, if we wanted to define the standard discussion explicitly, we would use:
but since the two forms both use the "Body" field, we could shortcut that to:
and honestly, even shorter, since the "Body" field is the default.
Now, let's say we had a different template, possibly with a locked-down design. Let's call it "Masterworks", and it has three forms, "Performance", "Materials" and "Extended Performance". The first two have a standard Body field, but the "Extended Performance" has three rich text fields, "Teaser", "Description" and "AudioFiles". For this, we would use:
With those two lines, we have enabled CoexEdit on all databases with the "Masterworks" XPages template. Tomorrow, we'll see some of the ways the CoexEdit enabling changes the editing experience. But first, one additional tip. If you have a database with no template, you can use the Replica ID of the database instead.
Copyright © 2012 Genii Software Ltd.