Branding of Bridge Licensee Sites can now include custom domains. The domain will be shown in the address bar for all users, throughout the system. Any additional portals will inherit the same domain, with the addition of a URL Extension.
For setup instructions, see the detailed section below.
While the default portal is automatically created when a new licensee site is set up, you can add additional portals with different settings, color schemes, and branding. These additional portals will be accessed with a URL Extension assigned to the portal. This feature has been redesigned.
For setup instructions, see the detailed section below.
When creating a new portal for a specific product or distributor, or when modifying the default portal for your company's use, the color scheme can be customized to match company branding or color design preferences. This feature has been redesigned.
For setup instructions, see the detailed section below.
All newly created portals will begin with default content for the logon page, the self-registration page, and the welcome page, as well as the headers and footers of each page in the system. This content can be customized or completely replaced, in order to personalize each portal. Images, text, and links can be inserted for the purpose of branding and providing additional information to users.
For setup instructions, see the detailed section below.
While the new portal customization features allow custom content to be included on several pages, the Home page can now be customized by each individual user. The Welcome Page content can be hidden, and grids can be added to provide quick access to submissions and policies, as well as notes and follow ups.
For setup instructions, see the detailed section below.
In the event that you want to direct your users to other websites, links can be added to individual portals, and will appear in the main menu on the left side of the page. The links will be included in the main menu between the Help and Log Off menu items, and can be set to show individually or in a sub-menu. The links can be restricted to only show to users with specific Security Roles.
For setup instructions, see the detailed section below.
A new option has been introduced to default the effective date of newly created endorsements to the same effective date as the source policy term.
When any new endorsement is created for a policy under a Master Cover with this setting, the effective date will default to the same effective date as the policy or renewal transaction that is being endorsed. The user may then modify the effective date, if necessary.
For setup instructions, see the detailed section below.
In instances where the coverage period panel is not required or should not be available to certain users, conditions can be set to hide the panel. The conditions are based on the type of transaction, the status of the submission or policy, and the security role of the user.
For setup instructions, see the detailed section below.
Previously, any tables included in generated documents would include every row in that table. This feature has been enhanced to allow triggers that define which rows to include in the generated document.
For setup instructions, see the detailed section below.
Field Override Behaviors are sets of rules determining whether or not a field will be displayed for a particular combination of user, transaction type, and submission/policy status.
Triggers can now be included in those rules, using the values of one or more fields to determine if that behavior will be applied.
For setup instructions, see the detailed section below.
A new type of grid has been introduced, allowing rates to be calculated and displayed for each entry.
When viewing the grid, two columns will be automatically added, displaying the premiums for the current transaction and the term.
For setup instructions, see the detailed section below.
To reduce unnecessary data entry, Master Covers can now be copied to produce a new product. If a planned product is similar to an existing product, the Master Cover for the existing product can be copied and modified to suit the new requirements.
For setup instructions, see the detailed section below.
Previously, when pulling premium information into a calculated field, the syntax would call the premium by number (for example [[PremiumInfo[1]/Amount]]). However, it was sometimes difficult to determine the order of the premiums within the system.
The syntax has been updated to allow premium types to be identified by name or ID. The new format allows some premium information to be called by ID, while other information can be called by ID or the name of the premium type.
For additional details, see the 1.6 version of the Calculated Fields Reference Guide, or the detailed section below.