Posts

Cannot see AdjustedRate, BaseRate, Basis, TermAmount when creating and editing a rate routine

If you cannot see AdjustedRate, BaseRate, Basis, TermAmount when you edit a rate routine this means your routine is not configured properly to work with costs. A routine may use a cost object, although it is not required. If the routine does not use a cost object it just returns some result. If it does use a cost object then during routine calculation flow it updates such properties of a cost object as AdjustedRate, BaseRate, Basis, TermAmount. In the latter case the routine must be configured to use a cost object. This can be configured in the Parameter Sets section. Find a corresponding parameter set that is in use by the routine. Edit the parameter set and set Include Cost to true. Now you will be able to see predefined AdjustedRate, BaseRate, Basis, TermAmount variables in you rate routine.

Existence Script must be empty if existence is not defined by script

This sounds like a play of words and does not exactly describe what is wrong with your product model. If you start PolicyCenter and see an exception like this: ERROR Configuration COV_PATTERN_CODE [CoveragePattern] : - 1 error(s) in CoveragePattern "COV_PATTERN_CODE "   [1] ERROR COV_PATTERN_CODE  [field : ExistenceScript] : - Existence Script must be empty if existence is not defined by script. ERROR Server.RunLevel ***** PolicyCenter unable to start ***** gw.api.webservice.exception.ServerStateException: Errors detected in Product Model. First correct the errors and then retry startup. at com.guidewire.pc.domain.productmodel.impl.ProductModelImpl.logAndThrowIfErrors(ProductModelImpl.java:1548) at com.guidewire.pc.domain.productmodel.impl.ProductModelImpl.verifyProductModel(ProductModelImpl.java:1540) at com.guidewire.pc.domain.productmodel.impl.ProductModelImpl.verifyProductModel(ProductModelImpl.java:1474) at com.guidewire.pc.domain.productmodel.impl.ProductM

Git cannot unlink a file

Have you ever seen a git error like "cannot unlink a jar file" when trying to stash changes? It may happen if your file is in use by another process. To avoid the error close Guidewire Studio, stop  running servers (like PolicyCenter server) if any. Usually this happens to custom jar library files that you added to your solution. 
Sorry for offtopic, this post is not related to Guidewire product, but may be useful for Spanish people using Cl@ve PIN application. If you try to get PIN from your mobile application and see an error like this: Se excedió el número de reintentos con número de soporte Be aware that now you should enter an additional support number from your DNI. The user interface of Calve PIN application does not provide any hints how to do this, unfortunately. To do this you need to delete you DNI number and add it again. During this process you will be asked for the support number, it's in the top right corner of you DNI card.

How to open Guidewire H2 database file

As you know H2 is the default database used by Guidewire InsuranceSuite products for local development environment. If you see this tag in your PolicyCenter database-config.xml, for example < database name= "PolicyCenterDatabase" dbtype= "h2" > < dbcp-connection-pool jdbc-url= "jdbc:h2:file:/tmp/guidewire/pc;CACHE_SIZE=32000" /> </ database > then you use H2 as well. It's quick and easy to start, but at some point you'll want to take a look at your data tables. How to do this properly? Fortunately, there are great tools for this purpose. You can use DBeaver or DBVisualizer. As an example let's consider DBeaver. To create a new connection try File -> New -> Database Connection, Connection Type = H2 Embedded. Now is the most interesting part. On Generic JDBC Connection Settings in Database/Schema specify the folder where you H2 database files are stored. For example, c:/tmp/guidewire/pc. Warning!  Don&#

Hello World!

Here goes the very first post. In this blog I'm going to highlight Guidewire development questions  and problems that every Guidewire developer may stumble upon. The answers and solutions I suggest come from my practical experience and they may not be the best. If at some point you find a better solution, please don't hesitate to write in comments. Looking forward to hear from you!