what’s new in insbridge version 5.1 - oracle · 2016. 8. 30. · softdata version 2 is an updated...


Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3

PresenterPresentation Notes


What’s New in Insbridge Version 5.2

Features

SoftData Version 2

SoftData Version 2 Features

Data Sources

Table Data Editing

Table Data Result Sorting

Auto Mapping for Columns of Table Data

Table Data Import

Advanced Copies

Features

Debug Report 2.0

P2P Mappings Copied

Testing: Option for Filter Rules

Output Mapping Refresh

Sequencing Refresh

Project Moves

SRP Reports and Email

Table Loading for Releases


SoftData Version 2

5

PresenterPresentation NotesSoftData Version 2 is an updated version of SoftData with expanded features such as, grouping and default values. The new updated SoftData Version 2 is a feature of Oracle Insurance Insbridge Enterprise Rating SoftRater Server (IBSS) that allows for values to be retrieved dynamically from SoftRater Packages. Soft Data is available from the IBSS Menu Tree.


Changes for SoftData Version 2

• Backend changes to SoftData Version 2 now allow the SoftData request to call the SoftRater engine to make the SoftData call.

• The SoftRater engine now can retrieve the program version that needs to be used by the SoftData request without using global versioning.

• The SoftRater engine can retrieve the table variable revision number that the found program version is packaged to use.

• A SoftData table query can be done using the name of the table. • The SoftRater engine can get the program ID of the table variable used in

the selected program version.

PresenterPresentation NotesNew releases can use either SoftData Version 1 or the updated SoftData Version 2.

SoftData 2 is the preferred method to use for release 5.1.2 but cannot be used by any release prior to 5.1.1.

SoftData Version 2 is for use with IBSS Java instances.


SoftData Version 2 Sample of Format Changes

• SoftData Program Elements (program ID number) – program_id • SoftData Program Elements (program version number) – program_ver • SoftData M node Elements – product_id is not required • SoftData M node Elements – ni (lookup variable name) • SoftData M node Elements – a scope attribute is required for global or

universal tables • SoftData M node Elements – New, g (Grouping) and dv (Default Value) • SoftData M node Elements – New, sv (sort value)

PresenterPresentation NotesInsbridgeData.XML for SoftData Version 2 has a slightly different format than SoftData Version 1. Since this format is run directly through SoftRater, certain attributes are not required such as; the number of qualifiers, the product ID, data types, wildcard indicators, or date mask.

Data can be looked up by various methods; the table variable ID, or the table variable name or both.


SoftData Version 2 Format

• • • • • • •


SoftData Version 2 Features

9

PresenterPresentation NotesNew features have been added to expand the functionality of SoftData Version 2.

SoftData Version 1 can be used in this release, if the new features of grouping, default value or OR condition want to be used, the entire request format must be changed to the format used by SD V2." The formats cannot be mixed.


SoftData Version 2 Grouping and Default Value

• There are three attributes available in SoftData Version 2 that are not available in SoftData Version 1.

• Grouping –

• Default Value –

• OR Condition –

PresenterPresentation NotesGrouping and default value are optional features that can be added to the table variable node.

The OR condition is an optional feature that allows for multiple values to be considered for the qualifier. The OR condition attribute is added to the qualifier node.


SoftData Version 2 Grouping

Criterion1 Criterion2 Criterion3 Criterion4 Criterion5 Result1 Result2

String String String Integer Integer String String A B C 1 2 No Yes

A C B 1 2 No Yes

B A C 1 2 No Yes

B C A 1 2 No Yes

C A B 1 2 No Yes

C B A 1 2 No Yes

X Y Z 8 9 Yes Yes

X Z Y 8 9 Yes Yes

Y X Z 8 9 Yes Yes

Y Z X 8 9 Yes Yes

Z X Y 8 9 Yes Yes

Z Y X 8 9 Yes Yes

Criterion1 Criterion2 Criterion3 Criterion4 Criterion5 Result1 Result2

String String String Integer Integer String String

GROUP

A B C 1 2 No Yes

X Y Z 8 9 Yes Yes

Standard Criteria

Grouped Criteria

PresenterPresentation NotesGrouping indicates that the qualifier fields are related and may be entered in any order. Grouping the qualifiers together reduces redundant table rows and makes tables easier to manage.

For example, in a table with 5 criteria columns, the first three columns may be from the same value type/source, but not in a specific order. That is - the range values may be the same -- A and B and C -- but not in a specific order -- B and A and C, C and A and B, etc. … but the result is always the same, regardless of the order of the first three criteria values.

To access the specified columns as a group of data, reduce redundancy and more easily manage table data, grouping can be added. Grouping indicates that the fields can be entered in any order. In the example, the table data would effectively be reduced from 12 rows to 2 rows (group "A and B and C" and group "X and Y and Z").

At runtime the engine will sort the criteria and then perform the table lookup.

Grouping must be exclusive of criteria which are defined as "Interpolate" and/or "Wildcard".


SoftData Version 2 Table Grouping

•

•

•

•

•

•

•

•

•

•

•

•

•

•

PresenterPresentation NotesGrouping on table variable is done in SoftData using the attribute.

The attribute is added to the qualifiers that need to be grouped with g=“1”. The “1” means that grouping is required.

The grouped columns must be of the same data type. If the data types do not match, grouping is not done.

At runtime, the rows of grouped columns values are sorted in alpha-numeric order with numbers then alpha characters, ascending from left to right.


SoftData Version 2 Data Sources Grouping

PresenterPresentation NotesGrouping on a data source is assigned in RateManager. To assign grouping, the group checkbox must be checked. The data types must be the same. When the data source is used in a SoftData call, the attribute is not required.

If grouping is not needed, then the attribute can be added to the qualifiers with g=0. This overrides the grouping and turns grouping off.

The row grouped columns values will be sorted in alpha-numeric order' - numbers then alpha characters, ascending from left to right.


SoftData Version 2 Default Value


• The default value is the value that will be selected at runtime if no matching criteria row is found

PresenterPresentation NotesThe default of the table is not stored in the table; it is stored in the runtime object of the program. In the event that a request is sent down and no rows are returned, if default attribute is set to 1, the default value is returned. If the default value of the attribute is set to 0, no rows will contain the default value.


SoftData Version 2 OR Condition


• •

–

• Allows for more than one values to be entered for the qualifier.

PresenterPresentation NotesAn OR condition can be placed on qualifiers. This allows for the qualifier to accept more than one value. For example, if you have a table variable where the value of the 5th criteria could be 1, 2 or 3, you could add an OR condition to the qualifier that would allow any one of the values to pass. The values must be included in the attribute with an end . This shows the value were v is one of the values listed. The operator is for all values.


Data Sources

16

PresenterPresentation NotesData Sources can be created in RateManager for use with SoftData version 2. A data source is a special table type that defines table criteria columns without using existing RateManager variables. Data sources allow grouping to be added directly to the table, eliminating the need to define grouping in the SoftData call. Data Sources can only be used in SoftData version 2.


Data Sources

• Issue No way to use table data in

SoftData calls that does not require RateManager variables

• Solution Provide a means to use table

data that does not require RateManager variables

17

PresenterPresentation NotesThe Issue: Table data used by SoftData required that variables be created in RateManager and used in the table. The data also may have required multiple entries to cover all possible combinations. This creates redundancy and made the table more difficult to manage.

Solution: RateManager Data Sources are a special type of table that is used in SoftData exclusively. The data does not use RateManager variables and the criteria can be grouped together to reduce redundancy and make the table easier to manage.

Data sources are viewed and managed on the table variable tab and are represented by a unique icon.


Data Sources

• Does not use RateManager variables

• Data can be imported and exported like any table

• Are not used in any RateManager variables

• Does not require any special setup

PresenterPresentation NotesData Sources differ from table variables in that the lookup criteria do not come from a static set of existing variable elements (Fields, Calculated Variables, Table Variables, and Result Variables). The criteria columns of a data source can be defined to accept a wide variety of criteria. Data sources also allow for criteria to be grouped on the table. Another difference is that data sources are not used in any calculated variable or algorithm but are used exclusively in SoftData calls.

Data sources are not used in any variables. Data sources can only be added to the output mapping of a program. Since data sources can only be used in SoftData queries, category does not matter. It is recommended that you leave the category at the policy level. Another category can be selected if desired.


Editing a Data Source

• Rows are managed on the first Editing screen

• Data cells are managed on the

second Editing screen

PresenterPresentation NotesData sources data can be edited directly in the table. You select a row where you can edit the data in an individual cell. Data within an individual cell can be added, deleted or updated.

Single rows that are ready for data can be inserted. One or more rows can be deleted.


Editing a Data Source

• Rows are managed on the first Editing screen

• Data cells are managed on the

second Editing screen

PresenterPresentation NotesThere are three save options when editing data source data. These options allow you to continue working in the table: Save and Next – Saves the entries and opens the next row on the table for editing. Save and New – Saves the entries and creates a new row on the table directly under the row being edited. Save and Close – Saves the entries and closes the Editing Data screen.

Cells can be tabbed through or the Enter key will move the cursor to the next cell. Mask, wildcard and interpolation along with criteria column information cannot be edited here. If you need to make changes to the criteria, return to the Edit Variable tab.


Working with a Data Source

• Data Sources are used in SoftData Version 2 calls only.

• To use a data source in a SoftData call, you must add the data source to the output mapping for the program.

PresenterPresentation NotesSelect the program you want to use for the SoftData call. Navigate to the Output Mapping screen. On the output mapping screen, select Table Variables for the Variable Filter. Data sources are listed.

Select the data source you need and add it to the Used Variables. Package and Test the Program.


Working with a Data Source

• To verify the data source is in the program, run a test case.

• The data source is returned with the default value

PresenterPresentation NotesData sources are listed on Test Case Editor with the default value displayed.

Like any variable that is selected in output mapping but not used, the data source listed with the default value.


Table Data Editing

23

PresenterPresentation NotesTable data within an individual cell can be added, deleted or updated and single or multiple rows can be added or deleted. New options have been added to the bottom of the Edit Data screen. Insert – Inserts a row either above or below the selected row. Delete – Removes the select row, or selected rows, or all rows on the page. Copy – Copies the selected row, or selected rows. Paste – Pastes copied row(s) either above or below the selected row. If a row is not selected, the rows are pasted at the end of the table.


Table Data Editing

• Issue Inability to copy and paste rows or

delete table rows in bulk • Solution Add the ability to copy and paste rows

and to delete one or more table rows

24

PresenterPresentation NotesThe Issue: Table data that needed to be copied and pasted or bulk or deletions of table data usually required that the data be exported out of RateManager, edited in an outside system and re-imported back in to RateManager. While individual rows can be edited in RateManager, it can be time consuming and cumbersome.

Solution: A single row or multiple rows of table data as well as bulk deletions can now be done in RateManager. The ability to select one or more rows in a table can greatly reduce the time it takes to make a larger number of edits to a table.


New Row Options

New options have been added to the bottom of the Edit Data screen.

• Insert – Inserts a row either above or below the selected row. • Delete – Removes the select row, or selected rows, or all rows on the page. • Copy – Copies the selected row, or selected rows. • Paste – Pastes copied row(s) either above or below the selected row. If a row is not

selected, the rows are pasted at the end of the table. Paste is only displayed when a row has been copied.

PresenterPresentation Notes

These new options expand the functionality of the Edit Data screen.


Deleting One or More Rows

• You can delete a single row, multiple rows or all rows on the page.

• Changes to the table are saved immediately.

PresenterPresentation NotesA single row or multiple rows can be deleted from the table. There is a warning message prior to the row or rows being deleted. Deletions are per page. You cannot select multiple rows across multiple pages and delete. Only the rows on the page you are currently on can be deleted.


Copying One or More Rows

• A single row or multiple rows can be copied.

PresenterPresentation NotesAny row can be copied and pasted anywhere in the table. If no row has been selected, the row will be pasted at the end of the table.

If this is not the action you want to take, click the Esc key on your keyboard, this cancels the copy.


Pasting One or More Rows

• Copied rows can be placed in a specific location or at the end of the table.

PresenterPresentation NotesCopied rows can be pasted any place in the table. If a specific row is not chosen, copied rows are added to the end of the table.



29

PresenterPresentation NotesIn previous releases, SoftData results could not be sorted in ascending or descending order. This meant that when SoftData results populated outside application lists for example, the results may have been presented to users in a way that forced them to scroll for the option they wanted. In addition to being inconvenient, it could slow down application completion time and is counter intuitive to how most users select options.

In release 5.1.1, sorting has been added to SoftData. Sorting allows for SoftData results to be returned in either ascending or descending order by criteria that you select. For example, if you have a table with city, county, and territory code, you can have SoftData results returned by any one of those three options in ascending or descending order.



• Issue Inability to sort table data results • Solution The ability to sort table data results

either in ascending or descending order by the criteria you select

30

PresenterPresentation NotesSoftData provides integration with outside application to allow for data to be dynamically retrieved from SoftRater Packages (SPRs) so that values do not have to be hard coded in to an application while maintaining a high level of operational efficiency for rules and rating applications. SoftData is based on mappings to project/product/program based table variables that were built in RateManager. There are two parts to the SoftData call, the request and the results.

The header and the mapping node(s) in the SoftData request defines where the table variable is located along with version information. Additional attributes can be added to further define the request. The results are the table data that was retrieved based on the request. The results can be used in many ways. For example, on a web-based application where customers or agents can request a quote, SoftData can be used to fill in the values for drop down options.

The Issue: The data returned was listed in the same order as it was entered in the table. There was no way to sort data so that results were presented in an alphabetical or numeric order. Un-ordered data required users to scroll for the option they wanted.

Solution: Sorting has been added to SoftData. A sorting option can be added to the request in the mapping node. The options allow you to select the column where you want the sort to happen and if you want to sort ascending or descending. Adding sorting to the SoftData request returns the results in a way that makes it easier for customers to locate the option they want on a drop down list.


Adding a Sorting Attribute

• To use sorting, there are two attributes that must be added to the Table Variable mapping (m) node. – SC: The sc attribute is where you specify the column that is to be used for sorting. – QC: The qc attribute is where you define the number of qualifiers in the table

variable.

PresenterPresentation NotesResults can be sorted by a specified column either in ascending or descending order.

For SoftData Version 1, a qc attribute and an sc attribute must be added to the m node.

For SoftData Version 2, an sv attribute must be added to the m node.

Sorting is optional.


Adding a Sorting Attribute – SC

• The sc attribute is where you specify the column that is to be used for sorting.

• Format for the sc attribute is: column # | data type | ascending or descending

• Column # can be 1 - 50. • The data type of the column. 0 – Integer, 1 – String, 2 – Decimal, or 3 –

Date. • How the sort is to be done. Ascending = 0 and Descending = 1 • The entries are separated by a vertical bar ( | ).

– For example: sc=”2 | 2 | 0”

PresenterPresentation NotesData types are not required for SoftData Version 2.

SoftData Version 2 is in ascending order by default.


Adding a Sorting Attribute – QC

• The qc attribute defines the numbers of qualifiers. For example qc=”12” • You can verify the number of qualifiers, as well as other information by

going in to RateManager.

PresenterPresentation NotesThe qc attribute must be defined when there are more than 10 qualifiers. For tables with less than 10, the qc attribute can be left off.

The Input XML contains the project ID as well as a listing of field IDs. The Universal tab has field IDs, field names, and data types.

Manage products has the product ID.

Depending on the type of table variable Universal, global, or program details tabs have the table variable ID, variable name, version, and data type.

The QC attribute is not needed for SoftData 2.


Rules for Sorting Attributes

• Sorting by multiple columns can be done. The format for each is separated by a comma ( , ).

• For example: sc=”2 | 2 | 0, 1 | 3 | 0 ” • Sorting attributes cannot be used with other attributes such as

– p ( lookups from a data row position) – fq (list of selected qualifiers in Java only) – c ( total count of data rows to be returned)

• When sorting linked variables, the first value is the one where the sorting is done.

PresenterPresentation NotesYou can sort by multiple columns. The first sorting rule is met, then the second will be met and so on.

The sorting attribute should be used alone. There may be conflicts with other attributes.


Without a Sorting Attribute

Sorting does not have to be done. Simple SoftData calls can still be done.

PresenterPresentation NotesSorting is an optional feature.


With a Sorting Attribute

• Sorting results are returned in the order requested.


Auto Mapping for Columns of Table Data

37


Auto Mapping

• Issue Data imported in to a table variable

required manual column matching • Solution Auto mapping of table variable

column headers

38

PresenterPresentation NotesPreviously auto mapping of column headers when importing table data was only available if you did not preview your data. With this release, auto mapping of columns when importing table data has been added when previewing the data. This allows users to preview data prior to being imported with column headers matched up.

Columns are automatically matched when data is brought in to the table. The matching is done by position. The first column imported is matched to the first column in the table. If the columns are out of order, corrections can be made in the preview window. If auto mapping is not selected, no matching is done.


Table Data Import

39


Imports

• Issue Only tab-delimited data could be

imported in to a table variable • Solution Allow for data from MS Excel to be

imported

40

PresenterPresentation NotesThe issue with importing table data is that only tab-delimited files could be imported and files had to be imported one at a time. This forced users to save their Microsoft Excel (Excel) files in tab-delimited format to import. A more streamlined process of Excel to RateManager was needed.

In release 5.2, table data imports can still be done in tab-delimited format one at a time. But now, table data can be imported directly from an Excel file in batch or one at a time. Various options are presented that allow for rows to be deleted or appended from an existing table and to import table data either immediately or to be saved and the job run at a later time.

To allow for imports from Excel, a few setup procedures must be in place.


Set Up a Shared Workfiles Location

• Table Data Imports requires a shared Workfiles location

• Make note of the Share The share location is required

to be entered in RM

PresenterPresentation NotesA shared Workfiles location allows for multiple instances of RateManager to share the same Workfiles. The Insbridge server and the shared location must be on the same domain. The Insbridge user for each instance of RateManager must be on the domain also. Administrators should be familiar with managing a Windows server and working with Domains. Server permissions are required for: Access to the server where Insbridge has been installed The Insbridge User Account. This is the user used to install Insbridge. Access to the server where Workfiles will be located.


Set Up an RM Environment in IBSS

• IBSS requires an RM environment The RM environment must be the

same as the RM environment entered in IBFA

• Make note of the IBSS URL An IBSS instance is required to be

entered in RM

PresenterPresentation NotesAn RM instance must be entered in the IBSS instance that is being used. The RM instance must be the same as the instance entered in IBFA. You must have IBSS permissions to create an RM environment.


Set Up the Access Right

PresenterPresentation NotesThere are additional setups that need to be entered in RM. You must have admin permissions to perform these tasks.First, set up the group management for access rights. Select the user group(s) where you want to add permissions and allow permissions for RM table job admin.

If table job admin rights are not granted, users can save a job but cannot access the table data management screen to edit, stop or start jobs.


Set Up Preferences

Set up the table management messaging

server and work files share folder location

PresenterPresentation NotesOn the Preferences screen, you need to enter the IBSS instance and the shared workfiles location.

Table Management Import Excel Preview Rows sets the number of rows displayed for preview. Select the number of rows available for preview when importing table data from MS Excel. Available in increments of 5, 10 or 20 rows.


Table Job Management

Table Job Management icon

PresenterPresentation NotesIf your user group has been granted permissions, you will be able to see the table job management icon on the home page and in the tools menu option. Table Management is where users create jobs, select one or more table variables, and then submit the job for processing where the variables are imported in to an Excel workbook. If your group does not have table job management permissions, you can do a single import immediately.


Creating New Job

PresenterPresentation NotesPrior to any users saving a table for import, a job must be created. Jobs are containers that can hold one or more tables for import.

When you create a new job, you enter the name, description, note and email address so that you can get email notification when the job is done. The job is empty and ready for use.


Importing Table Data

Import Table Data to Excel

PresenterPresentation NotesTo import table data, there are two options. You can include it through the program detail table variable or you can include it from the table variable edit screen.

From the program table variable screen. You can select the table variable and right click and choose table management and import data to an Excel workbook.


Importing Table Data Files Specify the workbook

name and the worksheet name

PresenterPresentation NotesThe first step is to specify the workbook name and the worksheet name. The default is the name of the table. Click File to select a different workbook.


Selecting Table Data Files

Select a file saved to the workfiles location or a

file on your local machine or server.

PresenterPresentation NotesYou can choose an existing file saved to the workfiles location. Or you can browse for a file on your local machine or network.


Table Data Workbook and Worksheet

Specify the workbook name and the worksheet

name

PresenterPresentation NotesThe workbook name automatically fills with the selected file. The worksheet name can be adjusted. The default is the name of the table.


Table Data Options

Excel format is either Custom for new tables

or Insbridge.

Auto mapping of columns.

Rows can be deleted and appended on existing

tables.

PresenterPresentation NotesExcel format is either custom for new files or Insbridge for table data that is in Insbridge format. Insbridge format is a file that has been exported from RateManager and contains table information.

For existing tables, you can select to delete all data or to add rows for new data.

Auto mapping is automatically checked. Auto mapping maps the first column of the data to the first column of the table.

Once the options have been selected, click Import.


Previewing Table Data

PresenterPresentation NotesThe data is presented next. The is a view only screen. No edits can be made.

The number of rows displayed is determined by the Import rows setting in Preferences.


Adding to a Job

Choose Save

PresenterPresentation NotesYou have option to save, save and run now, and run now.

Save – saves the import to a job listed on the Job Management tab. If no jobs have been created, the import cannot be saved.Save and Run – saves the import to a job listed on the Job Management tab and then runs the job. If no jobs have been created, the import cannot be saved.Run Now – runs the import job.


Successfully Adding to a Job

Selecting a job

PresenterPresentation NotesIf you opt to Save, you can select the job where you want to save the import to. A success or fail message is displayed.


Viewing the Table Jobs

Jobs show the number of tables and current

status

PresenterPresentation NotesThe Table Job Management tab contains a listing of all jobs. The number of tables in each job is displayed along with the status. Options at the top of the tab allow you to edit job options such as notification email, start a job, delete a job and edit content.

Jobs can be searched using the Views option.


Exclude/ Include Table in a Job You Can Include/

Exclude Tables

PresenterPresentation NotesJobs can be edited to include or exclude an imported file. Certain job options can be edited as well. If you choose to not include a table, you can select to include the table and the job can be re-submitted at a later time. A success or fail message is displayed.


Start the Job

Start the Job

PresenterPresentation NotesJobs can be started at any time. Jobs can only be started from the Table Job Management tab.


Job Status Hyperlink to Check the

Error

PresenterPresentation NotesThere are 5 statuses:

Saved – a new job. This job may or may not have tables included.Submitted – a job that has been submitted for processing.Executing – a job that is currently being processed.Success – a completed job. The Excel file can now be downloaded from the Library tab.Failed – the job failed for some reason. When there is a failed job, there is a hyperlink for you to check on why it is failed and will give you a pop up on why it is failed

For example, if the IBSS instance has not been started, you will receive a failed message.


Adding Table Variable to a Job Through Edit Screen

Import Table Data to Excel

PresenterPresentation NotesThe second way to add table variable to a job is through the edit screen. You have option to import data to MS Excel workbook. The process is the same.


Table Files on The Library Tab

Library to Download the File

PresenterPresentation NotesSuccessful jobs are parked on the Library tab. The Library can be accessed from the library icon or the library menu option.


Table Imports on the Library Choose Table Export

PresenterPresentation NotesOn the library tab select the Table Exports option.


Downloading the File

Choose Save File

PresenterPresentation NotesOn the Library tab, there is a list of Excel files and table variable names along with additional information to identify the file. If more than one table is in a job, each table is listed.

The files can be downloaded only. Select a file and either right click or select the save to file button to download. The file can be saved to your local hard drive or network drive.

The download begins and a success or fail message is displayed.


Debug 2.0

63


Testing Debug Report

• Issue Debug reports could reach very large

sizes • Solution Users can now set page sizes in IBSS

64

PresenterPresentation NotesA debug report is a complete XML that is translated to the screen. The larger the report, the more scrolling the user has to do. This can make viewing the report cumbersome. The debug report was always returned as one complete page.

What’s new for release 5.2 is that the SoftRater engine can monitor how large the final XML is and based on the size, the system will split the results into multiple pages. Users who routinely get large debug reports now can set a page size so that the report can be paged through rather than scrolled through.


Report Size Setting in IBSS

PresenterPresentation NotesTo do that, you must be rating against a java application server. By routing the request to a java engine, a setting can be placed that allows administrators to determine the size of the debug report.

The SoftRater engine has a DEBUG setting where the max page size is set. When producing an XML file larger then the threshold, the page is cut off and a new page is started.

Each page contains the rating summary at the top and has a search feature. The search is per page. View XML is just results, and is not per page.

The setting default is 2MB. Administrators can set the debug size to any size they need. The smaller the setting, the more pages that are returned. If reports of 4mb are typically returned, paging is recommended.

Requirements: The same environment (Rm_java) that is in IBFA must be setup in IBSS.This setting is only for debug reports on the Testing module.This option is only when rating against a Java engine. Windows does not return pages.


Copying P2P Mappings

66


Copying P2P Mappings

• Issue P2P mappings had to be

recreated each time • Solution Allow for P2P mappings to be

copied and searched

67

PresenterPresentation NotesTwo new features have been added to program to program callout mappings; copying and search capabilities. To speed up creation time, copies can be made of callout mappings within an existing program. Searches can be done within an existing program to easily locate a mapping.


Testing: Changes to the Filter Rules Option

68


Testing Filter Rules

• Issue Filter Rules that returned false were

displayed • Solution Users can now turn off false filter

rules being displayed

69

PresenterPresentation NotesFilter rules that returned as false are displayed on the debug report. This can force users to scroll through a lot of unnecessary information and create a large debug report. An option to include or exclude filter rule results has been added. When checked, filter rules that are false are displayed in the debug report. When unchecked, filter rules that return as false are excluded from the debug report. The default is for filter rule results to be displayed in the debug report.


Sequencing and Output Mapping Refresh

70


Sequencing Refresh

• Issue The search and select options

were combined • Solution Separate the search and select

options in to Available and Used

71

PresenterPresentation NotesThe Sequencing screen added filter options that allow for definitions to be set for available variables, used variables, or both for the available algorithms and the used algorithms.


Sequencing

PresenterPresentation NotesThe sequencing tab contains a listing of algorithms and driver assignment scenarios. As in previous releases, you can filter the view to show all available, or only selected algorithm types. In release 5.2 you can now enter a search parameter and filter only the available algorithms by the selected view. At the same time, you can enter a search parameter for the used algorithms and search on that as well. You do not have to search separately. This reduces the number of steps to be taken when you wanted to search both available or used algorithms.

The elements that are included in the available search are determined by the entry in the search field and the filter selection. For example, if only normal rating algorithms are listed, then only normal rating algorithms will be searched. No Underwriting or Driver Assignments will be included in the search. All used algorithms are searched.


Output Mapping Refresh

• Issue The search and select options

were combined • Solution Separate the search and select

options in to Available and Used

73

PresenterPresentation NotesThe Output mapping screen added filter options that allow for definitions to be set for available variables, used variables, or both.


Output Mapping

PresenterPresentation NotesThe output mapping tab contains a listing of the variables found in the program. As in previous releases, you can filter the view to the available results variables or field variables or whatever variable type you want to view. In release 5.2 you can now enter a search parameter and filter only the available variables the selected view. At the same time, you can enter a search parameter for the used variables and search on that as well. You do not have to search separately. This reduces the number of steps to be taken when you wanted to search both available or used variables.

The elements that are included in the available search are determined by the entry in the search field and the filter selection. For example, if only result variables are listed, then only results will be searched. No other variable type will be included in the search. For used variables, all variables are searched.


Project Moves

75


Project Moves

• Issue Projects could not be moved from one

domain to another. • Solution Allow projects to be moved

76

PresenterPresentation NotesMoving a project moves the entire project, including products, folders and universal elements, to another domain within the same domain type. The available domains listed are in the same domain type as the project being moved.


Project Moves

PresenterPresentation NotesThe available domains listed are in the same domain type as the project being moved. You cannot create a new domain type and move a project in to it. At the time of the move, the project name can be changed. The products selected in the project and the P2P abbreviation will remain the same but can be edited after the move. You must have project management permissions to move a project. If the move project option is grayed out or unresponsive, you do not have permissions.


Advanced Copies

78


Variable Copying

• Issue On the universal level, elements could not be copied to the local level.

On the local level, dependent elements were not always being copied and copied elements had to have name changes.

• Solution Universal elements now can be copied to the local level. A check for

dependencies had been added. Element names are locked and no longer require changing.

79

PresenterPresentation NotesFunctionality in Universals has been expanded to allow for copies to be made to the local level of any program in the project. The process of copying variables has been enhanced to make sure the copied variable includes any dependencies, reducing the amount of editing that was required. Updates have been made to the way local copies are done include keeping the same name when copying to the local level of another program and creating versions of existing variables.


Universal Copies

PresenterPresentation NotesIn previous releases, universals could not be copied to a local level. In release 5.2, universal elements can be copied to any program in the project. When copying a universal table variable to a local level: Universal copies to a local level are project wide. More information has been added to help select the Destination Program where the element should be copied. The Destination Program name is listed first, the folder name is in parenthesis and the product name is last, also in parenthesis. In the example above, the highlighted program is CA Auto 2, in the California folder, under the Auto product. Duplicate naming is not allowed. The New Name must be different from the Old Name. Universal permissions are required to make copies at the universal level.


Local Copies

PresenterPresentation NotesIn previous releases, local to local copies may not have included all dependencies. For example, if a local algorithm used a local table variable, when the algorithm was copied, the table variable may not have been copied also. This meant that users had to also copy the table variable and then edit the algorithm. In release 5.2, local to local elements have dependencies checked.


Local Copies

PresenterPresentation NotesWhen performing a local to local copy, dependencies such as the usage of other local elements are checked. If there are local elements used in the element being copied that are not in the Destination Program, then those elements are copied also.

For example, the Option AB Fee algorithm, a local variable, uses table variables Option A and Option B, also local variables. When Option AB Fee is copied from program Maine to program Kansas, the algorithm is copied and so is the table variables that are being used.

This eliminates the need to do multiple copies and edits.


Local Copies

PresenterPresentation NotesIn previous releases, local to local copies required name changes. This may have complicated the creation of some local elements and programs where similar elements were used.

In release 5.2, local to other program local elements do not require name changes. The New Name field is grayed out. This creates an identical element in the other program and reduces the need for editing. If a change is made to the original element and then copied a second time, a second version of the element is created in the Destination Program.

When copying at the local level in the same program, the name must be changed.

Local copies are done at the product level. The Destination Program name is listed first, then the folder name. In the example above, the selected program is IL_AU_Prog_FEILAU, in the Illinois folder.


SRP Updates

84


SRP Updates

• Issue SRP emails need to convey more

information • Solution Create a more detailed email from

IBFA and allow for Global Versioning Report to be included

85

PresenterPresentation NotesIn this release, a Global Versioning Report can be added to an SRP during the packaging process on the product level or on the program version level. This allows users in IBFA to view the global versioning data used by the program.

A more detailed output email from IBFA for package loading has been created. Environment, server, and server time is now included on all emails from package management for IBFA.


Loading Table Data from a Release

86


Release Table Loading

• Issue Table Data loading takes a long time • Solution Allow for changes to table loading

87

PresenterPresentation NotesThe current load time when loading SRPs and table data from a release can be lengthy if duplicate SRPs or table are involved. Now, when loading packages from a release, the time stamp of the SRP is checked against the already loaded SRPs. If there’s a duplicate, the SRP is not loaded. For table data, the time stamp is also verified. If the time stamp of the currently loaded table is newer, the table is loaded. If the time stamp is older, the table in not loaded.

This change removes the loading and unloading of duplicate data and assures that the latest table is what’s used.


Announcements for Release 5.2

• Release 5.3 will be the last supported release for Oracle WebLogic 11g (release 10.3.6.0). After release 5.3, support for Oracle WebLogic 11g will no longer be available.

• SoftData version 1 is being retired. No new features will be added. Bug fixes will continue to be done.


Slide Number 1What’s New in Insbridge Version 5.1.1Slide Number 3What’s New in Insbridge Version 5.2SoftData Version 2Changes for SoftData Version 2 �SoftData Version 2 Sample of Format Changes�SoftData Version 2 Format �SoftData Version 2 FeaturesSoftData Version 2 Grouping and Default Value�SoftData Version 2 Grouping�SoftData Version 2 Table Grouping�SoftData Version 2 Data Sources Grouping�SoftData Version 2 Default Value�SoftData Version 2 OR Condition�Data SourcesData SourcesData SourcesEditing a Data SourceEditing a Data SourceWorking with a Data SourceWorking with a Data SourceTable Data EditingTable Data EditingNew Row Options�Deleting One or More Rows�Copying One or More Rows�Pasting One or More Rows�Table Data Result SortingTable Data Result SortingAdding a Sorting Attribute�Adding a Sorting Attribute – SC �Adding a Sorting Attribute – QC �Rules for Sorting Attributes�Without a Sorting Attribute�With a Sorting Attribute�Auto Mapping for Columns of Table DataAuto MappingTable Data ImportImportsSet Up a Shared Workfiles LocationSet Up an RM Environment in IBSSSet Up the Access RightSet Up PreferencesTable Job ManagementCreating New JobImporting Table DataImporting Table Data FilesSelecting Table Data FilesTable Data Workbook and WorksheetTable Data OptionsPreviewing Table DataAdding to a JobSuccessfully Adding to a JobViewing the Table JobsExclude/ Include Table in a JobStart the JobJob StatusAdding Table Variable to a Job Through Edit ScreenTable Files on The Library TabTable Imports on the LibraryDownloading the FileDebug 2.0Testing Debug ReportReport Size Setting in IBSS�Copying P2P MappingsCopying P2P MappingsTesting: Changes to the Filter Rules Option Testing Filter RulesSequencing and Output Mapping RefreshSequencing RefreshSequencing�Output Mapping RefreshOutput Mapping�Project MovesProject MovesProject Moves�Advanced CopiesVariable CopyingUniversal Copies�Local Copies�Local Copies�Local Copies�SRP UpdatesSRP UpdatesLoading Table Data from a ReleaseRelease Table LoadingAnnouncements for Release 5.2�Slide Number 89

what’s new in insbridge version 5.1 - oracle · 2016. 8. 30. · softdata version 2 is an updated...

Documents