Guidewire layer and Customer layer‎

The Guidewire layer and Customer layer are defined to designate clear ownership of files that are contained within the EnterpriseEngage artifact. You must not modify any files in the Guidewire layer.

Note: Edge API updates are not delivered through the standard automated update process as they're a part of the customer layer. Any changes to Edge APIs will be communicated through the EnterpriseEngage release notes.

The Guidewire layer files for EnterpriseEngage are listed below.

DigitalPortals/platform/@gwr/force-resolutions
DigitalPortals/platform/@jutro
DigitalPortals/platform/api-docs
DigitalPortals/platform/bootstrap
DigitalPortals/platform/digital-build-tools
DigitalPortals/platform/digital-build-tools-core
DigitalPortals/platform/digital-modules-js
DigitalPortals/platform/digital-modules-ui

The customer layer files for EnterpriseEngage are listed below.

DigitalPortals/application/account-management
DigitalPortals/application/account-management-claims
DigitalPortals/application/common
DigitalPortals/application/producer-engage
DigitalPortals/application/producer-engage-claims
DigitalPortals/application/quote-and-buy
DigitalPortals/application/service-rep-engage
DigitalPortals/application/vendor-engage
DigitalPortals/.gitattributes
DigitalPortals/.gitignore
DigitalPortals/.nvmrc
DigitalPortals/babel.config.js
DigitalPortals/lerna-debug.log
DigitalPortals/lerna.json
DigitalPortals/manifest.json
DigitalPortals/package-lock.json
DigitalPortals/package.json
DigitalPortals/.eslintrc.js

Note: Some files in the customer layer contain dedicated sections that are only used by Guidewire. Do not edit these sections. Guidewire updates these files based on its own automated procedures (see Automated changes to the customer layer). Eventually these files will resolve to either being in the Guidewire layer or the customer layer.

For more information on how updates are handled from the InsuranceSuite side, see Overview of InsuranceSuite updates.