IWS Release Notes - January 2015
We strive to keep our products above the industry standard so that your systems remain current and flexible. For that reason, we make continuous improvements to BriteCore's code base. We've been experimenting with a continuous release process, and we'll be shifting to this to better reflect our daily improvements. Rather than waiting for the all-clear of many items to go out in one weekly release, you'll receive continuous updates for code changes going out in the daily release. Items that require full release notes for this month can be found in this section of the BriteWiki.
January 19, 2015
Enhanced Underwriting - Restrict Business by Zip Code
Funded by State National Fire
BriteCore now provides further control over where you write business. Risks can now be restricted based upon zip code. An override exists so that a risk may still be written, at an authorized staff’s discretion, within a restricted zip code.
When enabled, Agents will be unable to submit applications for a risk located in a restricted zip code unless an override code is entered by an authorized staff. On the Risks tab of the Agent Portal, agents will see the below Approval Required text. Agents can click the information icon to see a custom message (defined by you) that provides direction on the next step(s).
If contacted by an agent, an authorized staff member has the ability to override this restriction by clicking on the Approval Required text and entering a custom code. Once approved, the address is added to a white list and the agent will be able to submit the application for further review. However, if the street address is changed the approval code must be entered again.
Currently this is a database-only setting. If you are interested in using this new functionality, please submit an OOPS! ticket. You will need a list of zip codes you would like to restrict, the text you would like displayed to the agent and the approval code you would like to use.
January 21, 2015
IWS has added new report types to BriteData to expand the usability of reports. The new report types include HTML, TXT, and XML and are selectable on the Define your Report tab. The greatest use case for these new report types will likely be file generation for vendors, however, they can also be used internally if needed. Clicking the ? next to Choose a Report Type will provide additional information for the use case of each report type.
In addition to the new report types, a new tab titled Design the Template has been added. This new tab is available only when the following report types are selected: PDF, HTML, TXT, or XML. On the Design the Template tab, users are able to further define the report using the Jinja templating language (similar to how Custom Deliverables can be designed).
On this new tab, IWS has added a few new elements and enhanced usability.
- Click to Add: Replaces the Drag and Drop functionality for adding data to the report. Users are now able to single click on a Column or Snippet and that item is immediately added to the text editor at the current cursor position.
- NOTE: This functionality will progressively be added to other BriteData tabs in the future.
- Snippets: Pre-defined Jinja functions that can easily be added to the template by clicking on the desired function.
- Text Editor: Center area of the screen where users can edit the report output.
- Help: The Help with Templating link provides additional instruction on using templates with reports.
The Design the Template tab is a powerful tool that greatly enhances the application of BriteData reports, however, it is not required that templating be added to report types that make it available. Reports can be saved and will run with no templating.
January 29, 2015
The existing AutoRun functionality within BriteData has been enhanced to include more options for AutoRun times. In addition to the existing option to run the report monthly, users are now able to select the desired AutoRun setup from a list of several options including: Once a year, Once a week, and Once a day.
All new reports are defaulted to the Manual option. If existing BriteData reports are setup to run monthly, that option will persist with this enhancement.
Enhanced Date Filters
BriteData now allows greater control over report dates. Currently, reports require either a single date or date range. With this release, new date filters allow users to specify precise dates within the single date or date range result set.
For example, a Policy Renewal report in BriteData will look at what will renew X days into the future. Prior to this release, the Policy Renewal report in BriteData would return more than the needed result set. Using the new date filters you will be able to define specific date ranges so the result set contains only the data you need
Setting Up Date Filters The new filters will be added on the Define Rules for your Data tab by using a Computed Column. The name of the column can be anything (for ease of use, IWS suggests using descriptive names such as Start Range or End Range). New keywords have been added to the list of Data Names for building the expression. These include Report Start Date, Report End Date, Days, Weeks, and Months.
These Data Names (which will be auto suggested) must be used in the expression to define the date parameters. The expressions will vary among clients but will be similar to below.
In addition to the Computed Columns, you will also need to add filters to specify which data specific dates will be reported in the defined date range. If your Computed Columns are setup to return data in a date range of 3/1/15 - 6/15/15, the filters will specify which data specific dates (Expiration Date, Effective Date, Inception Date, etc.) the report will pull against for that date range.
Additional Notes: If a report requires a Date Range, users will want to use (Report Start Date + X) and (Report End Date + Y) for the date filters since the report will have two date inputs. If a report requires an As Of Date, users will want to use (Report Start Date + X) and (Report Start Date + (X+Y)) for the date filters because the report will only have one date inputted by the user to calculate off of (there will not be an end date specified).
To assist in understanding these new filters, a sample YAML file can be found here (it must be downloaded...YAML files will not show a preview). This file can be uploaded to a report in BriteData to review the setup described above.