Develop a Consumer Sales Portal
Developers can use the v5 API to develop and configure a Consumer Sales Portal that issues a policy or submits a quote to an agent. In the build-out, attribute metadata is defined for the data objects associated with each product. When developing portal pages, you can refer to the product's attribute metadata to build each page with various fields and then use the API to process the data entered in those fields. For more information on attribute metadata, see Product Attribute Reference.
This section includes information about the Consumer Sales Portal API flows and related functionality. However, the interactive API includes all the parameters available for each API. For information on how to view and test the API and its parameters, see "Try out" the API V5.
Consumer Sales Portal API flows
Consumer sales portal setup requirements
- Register the Consumer Sales Portal with Guidewire Identity Federation Hub
- Contact the Guidewire Cloud team to register the portal with the Guidewire Identity Federation Hub (Guidewire Hub). The Guidewire Hub enables the Consumer Sales Portal to be issued a JWT from Okta.
- Configure the Consumer Sales Portal to authenticate with InsuranceNow
- InsuranceNow must be configured to request and decode JWTs from Okta.
- Configure the Consumer Sales Portal to use Google Places for address completion
- Specify the Google API key in the GOOGLE_API parameter of the webpack.prod.js and webpack.dev.js files. It is recommended that the Sales Portal does not use the same Google API key as InsuranceNow core.
- Configure the
directportal
user with the authority attributes required to issue a policy for the products available in the Consumer Sales Portal - If the
directportal
user does not have the authority to perform the steps required to issue a policy, policy issuance will not succeed in the Consumer Sales Portal.