Generating LOB endpoints for multi-line products

Products that started development prior to Hakuba (2023.06.0)

The manner in which LOB-specific endpoints are generated changed in the Hakuba (2023.06.0) release. If you developed or installed any products on a release prior to Hakuba, there are additional considerations for the pre-Hakuba products. For more information, see Products whose line prefix is not identical to the product prefix..

LOB-endpoint generation is initiated at the product level, but it is executed at the line level

When you generate LOB-specific endpoints, you initiate the generation at the product level.

However, by default, PolicyCenter generates LOB-specific endpoints at the line level. When the endpoints are generated, the endpoints are prefixed using the line code. If you generate LOB-specific endpoints for a multi-line product, the endpoints for each line will have their own prefix.

Lines shared across products

Lines that are used by multiple products must have the same line code, such as ba for a business auto line. This ensures that the same set of endpoints are used by products that share a given line.

If a given line is used by multiple products and you make a change to that line, you only need to regenerate the endpoints for any one of the products using this line. For example, suppose you have an Inland Marine line that is used by an Inland Marine product and a Commercial Package product. After generating endpoints for both products, you make a change to the Inland Marine line. You then regenerate the endpoints for the Inland Marine product. You do not also need to regenerate the endpoints for the Commercial Package product. The Commercial Package product will automatically have access to the regenerated Inland Marine line endpoints.

If a single line of business is used by multiple products, then either all of those products must be in visualized mode or all of them must be in installed mode. You cannot have a single line of business used by two or more products where some are in visualized mode and some are in installed mode.

Cloud API does not require a mono-line product for every LOB

Cloud API supports the ability to generate LOB-specific endpoints for a line of business, even when that line is used only by multi-line products. For example, suppose you have a Commercial Property Line that is used only by a multi-line Commercial Package product. When you generate LOB-specific endpoints for the Commercial Package product, Cloud API generates endpoints for the Commercial Property Line, even though this line is used only by multi-line products.

Other services or environments may require that you create a mono-line product for every line. For example, Guidewire APD Service may require you to create a mono-line Commercial Property package for the Commercial Property Line before you can add that line to a multi-line Commercial Package product. But this requirement is not enforced by Cloud API. Cloud API can generate endpoints for the Commercial Property Line using only the Commercial Property package.

The RestAPIsGeneratingByPolicyLine config parameter

There is an application configuration parameter named RestAPIsGeneratingByPolicyLine. It is a Boolean parameter that controls the level at which endpoints are generated.

• true - PolicyCenter generates endpoints at the line level.
  • Endpoints are prefixed by the line code.
  • This is the default.
• false - PolicyCenter generates endpoints at the product level.
  • Endpoints are prefixed at the product code.

Guidewire recommends against setting this parameter to true unless you are working with one or more products whose LOB-specific endpoints were generated in an instance of PolicyCenter prior to the Hakuba release (2023.06.0). For more information, see Products whose line prefix is not identical to the product prefix.