New and changed in PolicyCenter 9.0.4
See also
- For resolved and known issues in 9.0.4, see the Release Notes.
Personal data destruction
PolicyCenter supports destruction of some kinds of data. Destruction can mean either purging the data completely from the database or it can mean obfuscating data, making the original contents permanently unreadable.
Guidewire recognizes the need for insurers to be able to destroy personal information both on an on-demand basis or on a time-based basis. Destruction can be mandated by regulation or business practices, within the requirements of regulation, codes of conduct, or other business practices.
See also
Distributed MessageReply plugins
By default, MessageReply
plugin code runs on the server assigned to the message destination. If
the plugin class is defined with the @Distributed
annotation, the plugin code can run on any server in the cluster.
@Distributed
public class MyMsgReplyPlugin implements MessageReply { ... }Retrieving a document
Several changes are introduced to the operation of retrieving a document.
See also
- The “Retrieve Documents” section of Implementing a document content source for external DMS
New URL_DIRECT response type
The IDocumentContentSource
plugin methods that retrieve a document support the new response type
of URL_DIRECT. A response
of URL_DIRECT is the same
as the existing URL response
type, except the plugin caller will read the returned URL address and
redirect the client browser to it. The client browser is then responsible
for retrieving the document contents.
Referencing values of the ResponseType property
The supported values for the DocumentContentsInfo class ResponseType property are DOCUMENT_CONTENTS, URL, and URL_DIRECT. The syntax used when
referencing these values has changed.
Original reference syntax: gw.document.DocumentContentsInfo.VALUE
New reference syntax: gw.document.DocumentContentsInfo.ContentResponseType.VALUE
For example, the URL value is referenced as gw.document.DocumentContentsInfo.ContentResponseType.URL.
Replace the TargetHiddenFrame property
The DocumentContentsInfo
class TargetHiddenFrame
property is replaced with the ContentDispositionType
property. Supported values for the ContentDispositionType
property are DEFAULT,
INLINE, and ATTACHMENT.
Replaced |
Equivalent |
|---|---|
|
|
|
|
The syntax used when referencing a ContentDispositionType value is
shown below.
Reference syntax: gw.document.ContentDispositionType.VALUE
For example, the INLINE value is referenced as
gw.document.ContentDispositionType.INLINE.
With the removal of the TargetHiddenFrame property, the
IDocumentContentSource
plugin target parameter
is deprecated. The replacement parameter is contentDisposition. The target and contentDisposition parameters
are defined in the Studio plugin registry for the IDocumentContentSource plugin.
DocumentContentsInfo Methods
Changes occurred to some of the DocumentContentsInfo class methods.
The setTargetHiddenFrame method is deprecated. The replacement method is the new setContentDispositionType method.
setContentDispositionType(contentDispositionType : ContentDispositionType)The data types changed for two arguments of the getDocumentContents method. The new method signature is shown below with the changed argument types in bold.
getDocumentContents(strDocUID : String,
contentResponseType : gw.document.DocumentContentsInfo.ContentResponseType,
contentURL : String,
documentURL : String,
documentsDir : String,
demoDocumentDir : String,
contentDispositionType : gw.document.ContentDispositionType,
includeContents : boolean)In the original signature, the ContentResponseType argument was
a String and the ContentDispositionType argument
was of type boolean.
New DocumentsUtilBase method
The DocumentsUtilBase
class includes the new method getContentDispositionForDocument
to retrieve the ContentDisposition
value for a document.
Support for Bing Maps V8 REST interface
Features that require geocoding use Bing Maps in the base configuration. As described at https://blogs.bing.com/maps/June-2016/Bing-Maps-V8-Web-Control-Released, Microsoft is retiring the SOAP service Bing Maps V7 on June 30, 2017. Its replacement, Bing Maps V8, requires that existing code that uses the Bing Maps SOAP web services be implemented as REST.
There is a new plugin implementation class, BingMapsPluginRest, that supports Bing Maps V8. This class is registered by default in GeocodePlugin.gwp. There are also new support classes for making requests and handling the returned information.
See also
Database attribute autoupgrade
<database> element in
database-config.xml and added attribute
autoupgrade to the element. This attribute takes one of the
following values:fullmanual
Histogram statistics database element modification
<histogramstatistics> element in
database-config.xml to remove the following attributes:databasedegreesamplingpercentage
This change has no meaning or effect at the column (histogram) level.
Table statistics database element modification
Guidewire modified the action attribute on the <tablestatistics> element
in database-config.xml
to add a force option.
<tablestatistics name="string" ... action="update|delete|keep|force"/>This option updates statistics for the table while running incremental statistics, regardless of the percentage threshold.