<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>v4.9.4 on </title>
    <link>/tags/v4.9.4/</link>
    <description>Recent content in v4.9.4 on </description>
    <generator>Hugo -- gohugo.io</generator><atom:link href="/tags/v4.9.4/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Setup and configuration</title>
      <link>/sicsdocs/technical/server/operational_reporting/setup_and_configuration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/server/operational_reporting/setup_and_configuration/</guid>
      <description>Requirements # Java 21 or later runtime environment. For best performances, the index should be stored on a unit having a low random-access IO latency, like a SSD. SICS Operational Reporting Server # SICS Operational Reporting Server is an analytics and visualization web platform to give real-time visualization of operational data within SICS.
SICS Operational Reporting Server Installation # SICS Operational Reporting Server is a Web Application and can potentially be deployed in any Application Server.</description>
    </item>
    
    <item>
      <title>Configure Mandatory Items</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin/configure_mandatory_items/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin/configure_mandatory_items/</guid>
      <description>To ensure that necessary details are entered on a contract, before it can be regarded as complete, you can define a set of information to be shown in a different color on the contract. If your company also has activated the Registration Complete functionality, the colored items become mandatory.
The following applies to the level of business Assumed Business and Outward Cedent Contract only.
This configuration comes in addition to other configurable settings, (for example, system parameter Business - Conditions - Required Conditions) as well as hardcoded rules in SICS.</description>
    </item>
    
    <item>
      <title>Processing Options</title>
      <link>/sicsdocs/technical/desktop/adh/processing_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/desktop/adh/processing_options/</guid>
      <description>Processing Options # Figure 7 Sys parm processing options
There are several system-wide processing options that apply to ADH, and they are set on the window above.
Rename document file on import # Item Description Selected The name of the file is appended with the date and time that the import took place. Cleared The name of the file is not changed on import. Relevant when This is important if the name of each import document is always the same when delivered to the inbox.</description>
    </item>
    
    <item>
      <title>Output Patterns</title>
      <link>/sicsdocs/technical/desktop/adh/output_patterns/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/desktop/adh/output_patterns/</guid>
      <description>Output patterns # Selecting Output patterns from the menu opens a find window where you can select a single pattern for further processing, create a pattern, or import a pattern from outside SICS.
Figure 8 Output pattern choice
Item Description Name The name given to the output pattern. Active Indicates if the output pattern is active or not. Output type eMessaging Message, External or Tabular. Chosen when the pattern is created.</description>
    </item>
    
    <item>
      <title>Transformation Mappings</title>
      <link>/sicsdocs/technical/desktop/adh/transformation_mappings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/desktop/adh/transformation_mappings/</guid>
      <description>Transformation mappings # The [Overview]({{&amp;quot;/sicsdocs/technical/desktop/adh/overview/#&amp;quot; | relative_url}}) section described the basics about mappings. Here, further details are explained.
Figure 12 Transformation mapping - selection
From this table you can view, edit, copy, create or delete a transformation mapping. Other options include activating or inactivating a mapping, unlinking the mapping from existing documents, and importing/exporting the mapping. Only valid mappings can be activated.
Import and export are important for copying a mapping from one environment (e.</description>
    </item>
    
    <item>
      <title>Transformation Blocks</title>
      <link>/sicsdocs/technical/desktop/adh/transformation_blocks/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/desktop/adh/transformation_blocks/</guid>
      <description>Transformation Blocks # The transformation mapping is at the heart of ADH. This is the part that links the input pattern to the output pattern, via a series of links and functional blocks. These links and blocks are graphical representations of the mapping process. A link directly between the input and output will copy the incoming value without modification to the output. Adding a block provides scope for transforming the incoming value in various ways.</description>
    </item>
    
    <item>
      <title>Automated Document Handling in the SICS Workstation Desktop</title>
      <link>/sicsdocs/technical/desktop/adh/adh_in_workstation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/desktop/adh/adh_in_workstation/</guid>
      <description>Preceding documents relate to the administrative set-up required to create and manage the mapping tools needed to transform an incoming document into a format that can be understood by SICS. For the general user working with incoming documents, there are three main functions.
Import Document # This window allows the user to specify an inbox path and an archive path, and to start the import process.
Figure 31 Import doucment</description>
    </item>
    
    <item>
      <title>SICS Operational Reporting</title>
      <link>/sicsdocs/technical/server/operational_reporting/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/server/operational_reporting/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Tabular data in XML input</title>
      <link>/sicsdocs/technical/desktop/adh/xml_tabular_data_support/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/desktop/adh/xml_tabular_data_support/</guid>
      <description>Tabular input data format # ADH can support the generation of a suitable Input Pattern for handling tabular data in an XML input file/document, but only if the input format is as described here.
Assume the original document contains a table like this:
Q1 Q2 Q3 Q4 Premium 100 100 110 120 Commission 20 25 To be processed as a table in ADH, it must be represented in the XML input file as a &amp;lt;table&amp;gt; element with &amp;ldquo;number&amp;rdquo;, &amp;ldquo;numRows&amp;rdquo; and &amp;ldquo;numCols&amp;rdquo; attributes, and having the following three groups of child elements:</description>
    </item>
    
  </channel>
</rss>
