Create Automated Document Handling Base Data # In the SICS System Administration Utility, open the “Database Updating” function and select “Update Automated Document Handling Data”.
Define Processing Options # Open System Parameters and select the Automated Document Handling / Processing Options section.
The “XML Input Pattern Generation Algorithm” option defines which logic should be used when automatically generating the input pattern from a document. This functionality is triggered when the user creates a mapping from a specific document already present in the database.
...
Enable eMessaging module # In order to enable the eMessaging module, the user must enter the module key.
This setting must be entered using the System Administration function in either SICS Workstation or SICS System Administration Utility.
Once the console has started, click on “System Administration” and select “System Parameter Maintenance” function. A new window will appear. Locate and open the “Module Key” tab, enter in Edit mode and provide the value for"EMessaging Module Unlock Key", as shown in the figure below.
...
This section describes what the SICS System Administrator has to do in order to activate the Access Code features.
Note! It is important that these steps are carefully reviewed and executed before allowing users to enter data into the system.
Main System Parameter (Enable/Disable Access Code Option) # On the System Parameters, Global Defaults window, you decide whether or not to use data segregation, by selecting or de-selecting the Segregate Data by Access Code check box.
...
MS SQL Server # Please see Database Preparation for SQL Server.
Oracle # Please see Database Preparation for Oracle.
PostgreSQL # Please see Database Preparation for PostgreSQL.
Start the SICS System Administration Utility. Log in with a source user and select the source environment. The source user (or the associated 2nd level user if using two level login) must have SELECT, UPDATE, DELETE, INSERT rights on all SICS tables in the source schema.
In the case of Oracle, the source user must also have SELECT rights on various RDBMS system tables / views containing meta data (SYS.ALL_TAB_COLUMNS and SYS.
...
v4.8 Changes to rules # The following rules have been changed and will require action on the part of users to maintain existing (or comparable) functionality.
PreviousMessageMappingRule has replaced PreviousMessageReferenceRule. The old rule is still available and both are optional to allow switch-over.
Example Mapping Sets and XPATH:
NAME FRK_MSG_TYPE IS_NOT_SPECIFIC ORDER_N DESCRIPTION FRK_MATCHING_RULE TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Sender Contract Section Reference EXACT_MATCH TA Receiver Ref CP RCSR ACORD_TECHACC N 110 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Receiver Contract Section Reference EXT_MATCH_POP TA Receiver Ref CP HLR ACORD_TECHACC N 112 TA HighLevelReference EXT_MATCH_POP TA Receiver Ref CP HLR ACORD_TECHACC N 112 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref CP HLR ACORD_TECHACC N 112 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref Risk Code ACORD_TECHACC N 114 TA Lloyds Risk Code EXT_MATCH_POP TA Receiver Ref Risk Code ACORD_TECHACC N 114 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref Risk Code ACORD_TECHACC N 114 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP SCSR ACORD_TECHACC N 120 TA Sender Contract Section Reference EXT_MATCH_POP TA Receiver Ref CP SCSR ACORD_TECHACC N 120 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref CP SCSR ACORD_TECHACC N 120 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP ACORD_TECHACC Y 130 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP ACORD_TECHACC Y 130 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Receiver Contract Section Reference EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Sender ID EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Sender Contract Section Reference EXACT_MATCH TA Sender Ref CP HLR ACORD_TECHACC N 142 TA HighLevelReference EXT_MATCH_POP TA Sender Ref CP HLR ACORD_TECHACC N 142 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP HLR ACORD_TECHACC N 142 TA Sender ID EXT_MATCH_POP TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Lloyds Risk Code EXT_MATCH_POP TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Sender ID EXT_MATCH_POP TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Sender ID EXT_MATCH_POP TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Sender Contract Section Reference EXT_MATCH_POP TA Sender Ref CP ACORD_TECHACC Y 160 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP ACORD_TECHACC Y 160 TA Sender ID EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Section Level Sender Contract Section Reference EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Section Level Receiver Contract Section Reference EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Receiver Contract Reference EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Contract Period EXT_MATCH_POP Receiver Contract Reference `jv-ins-re:Contract[jv-ins-re:InsurerReference[translate(.
...
Sharing tables and data # Please see the System Administrator Guide for details.
Installing a Combined P&C and Life Database # In order to prepare the database to be used by both products, the following procedure MUST be followed:
Install both SICS P&C and SICS Life on the same (or two different) PCs Create tables and base data from the SICS Life System Administration Utility (as described in this document) Start the SICS P&C System Administration Utility and execute the following: Update Security Update Reference Data Update EDI Base Data Note that step 2 will create all tables for both the Life system and the P&C system.
...
Select the desired data provider from the drop down list. Some data providers handle a large number of database rows and there may be a noticeable delay as the data is being read.
Let the mouse rest over the selected data provider in the drop down list in order to display hover help describing details about the selected data provider.
The data container will show matching source and target rows in pairs, matching by the extended key.
...