Configuring notes and note templates
The Notes feature requires little configuration.
You cannot add and delete search filters in the search-config.xml file, as you can for other types of searches.
Note plugin interfaces
There are two plugin interfaces associated with notes. They do not affect the primary use of notes, which are stored in the database and do not require an external system, such as a document management system. They are related to note templates, which can be a customized method of creating notes. The plugin interfaces are:
INoteTemplateSource– Retrieves note templates—INoteTemplateDescriptor objects—that are used to help create notes. The default implementation isgw.plugin.note.impl.LocalNoteTemplateSource. This Gosu class retrieves templates from the server file system, but can also be customized to get them from a document management system.INoteTemplateSerializer– Customizes reading and writing of INoteTemplateDescriptor objects.
Note fields
Notes and note templates have a set of fields, also called properties. PolicyCenter uses these fields to attach the notes to various policy entities and to search for notes and note templates.
The following table describes the fields
of a Note that are visible
in PolicyCenter screens.
Attribute Name |
Definition of Attribute |
How Set |
Search for Note? |
Editable? |
|---|---|---|---|---|
|
Logged-in user who wrote the note |
By PolicyCenter |
yes |
no |
|
Contents, the text of the note |
By author in editor |
yes - any string |
yes |
|
Date the note was originally written |
By PolicyCenter |
yes - and by range |
no |
|
Must exist and be unique |
By author in editor |
yes |
yes |
|
Value from the |
By author in editor |
no |
yes |
|
Value from the |
By author in editor or by template |
yes |
yes |
|
Defined in the template and given to its notes |
By author in editor or by template |
no |
yes |
The author, body, date, related to, confidential, and security type are fields unique to notes and are not a part of note templates.
Security type is the Security Level in the user interface.
The following fields are used in note templates. The first two are applied by the note template to a note created from it.
Field Name |
Definition of Field |
Search for Template? |
Search for Note? |
Editable in Note? |
|---|---|---|---|---|
|
The subject of the template and of notes created from it. |
no |
no |
yes |
|
The topic of the template
and of notes created from it. A typecode of the |
yes |
yes |
yes |
|
A typecode of the
|
yes |
no |
no |
Creating a note template
A note template is a pair of Gosu files, a .gosu file and a .gosu.descriptor
file. To access the files, open Guidewire Studio and navigate in the Project window to .
The easiest way to create a new template is to modify copies of two existing files for one of these templates. Then save the two files with new, matching names in the same location as the other note template files.
Note template files
A note template consists of two separate files:
- A descriptor file with a name ending in
.gosu.descriptor. The file contains metadata about the template.For example,
ActivityActionPlan.gosu.descriptor. - A template file with a name ending in
.gosu. This file contains the text for the body of the note.For example,
ActivityActionPlan.gosu.
In the base configuration, a note descriptor file has the following fields.
Field |
Description |
|---|---|
|
A |
|
A Base configuration values include
|
|
The product that the note is associated with. For example, Commercial Package or Workers’ Compensation. Can be used in template search. |
|
A |
|
The topic of the note, a Can be used in template search. |
|
The subject of the notes created with this template, a |
|
A |
See also
- An external system can retrieve and validate note templates. For information, see Document management
- Template web service
