Published 02/06/2017
Configuration is a web-based application used by financial institutions to collect values that populate entire documents or components of documents necessary to perfect financial transactions. Depending on licensing, it also defines the conditions by which those values are used in any given transaction and may create and maintain custom documents.
These default data values are then used by the partner system in conjunction with the transaction-specific data to render the documents that perfect that transaction.
The demo license key for Configuration that you receive enables functionality for collecting default data values based on the configurability that will be made available to your beta users.
If your beta users will define the selection criteria that controls when that default data is used in transactions, then the demo license key enables functionality for defining the selection criteria: Selection Groups.
Depending on whether the Selection Groups unctionality is enabled, the process for outputting content from Configuration may require that selection groups first be created before content output occurs. For that reason, this document will refer to two processes for outputting content: Selection Groups and No Selection Groups.
This Getting Started guide is intended to provide you with a high-level outline of application functionality that supports the user experience from application launch through the rendering of CSi documents using:
Note that the rendering of CSi documents occurs outside of the Configuration application.
This delivery includes the following.
Configuration functionality is divided into a series of activities. Depending on an institution’s license key and the current user’s permissions, certain activities may not be available.
Activity | Description |
---|---|
Home | Displays the user activity dashboard, along with shortcuts to recent activities. Institution administrators see recent activity for all institution users. Users other than institution administrators see only their own recent activity. |
Data Sets | Creates and maintains default data value collected in licensed data modules. |
Custom Documents | Creates and maintains custom documents that a financial institution may wish to include in a transaction document set. |
Selection Groups | Defines the conditions under which use of data sets and custom documents (if licensed) are permitted in live transactions. Users create selection groups, which are containers for data sets, custom documents, and transaction conditions. |
Publish | Outputs the content of selection groups for live transaction use. The manner in which the content is output is determined by the partner administrator in Preferences prior to the institution’s use of the application. |
Preferences | Configures user permissions and application default settings. This activity is only available to users with administrator permissions. |
The following browsers and versions are supported for use with Configuration.
Before you install:
Verify that .NET 4.5.2 is installed in your Microsoft framework directory.
Verify that SQL Server or SQL Server Express is installed. If you do not already have one of these installed, you may access it here: *http://www.microsoft.com/en-us/download/details.aspx?id=42299
Verify that IIS 7 (or greater) is installed. Check this in the Control Panel > Programs and Features > Turn Windows Features On/Off > Information Services. It is necessary that IIS 6 Management Compatibility be enabled. (Please note that the location of IIS services is unique on Windows Server .)
Verify that Dynamic Content Compression is enabled.
Installing Configuration:
Run the Configuration installer.
Get IIS running Configuration.
After Configuration is installed:
Open a browser window and access your localhost (http://localhost).
Supply the appropriate configuration settings for the database.
Supply the appropriate logon credentials for a partner administrator.
The following steps summarize the steps necessary to configure Configuration for customer use and to test that configuration by creating a sample data set and publishing it from the application. The following sections of this document describe in detail how these steps are performed.
Configure licensing, publish file management, the institution administrator, and selection criteria.
Log into the application using the partner credentials you specified during installation.
Add a financial institution and enter the license key for that institution.
Select a publish method and path.
Add an institution administrator user.
Configure selection criteria (when Selection Groups is licensed).
Test publish file management by publishing a sample data set.
Log into the application as the institution administrator.
Create a simple data set.
Create a selection group with the data set and selection criteria (when Selection Groups is licensed).
Publish the selection group (when Selection Groups is licensed) or the data set (when Selection Groups is not licensed).
Verify content of the published data files.
Your organization may define as many partner administrators as you like in order to manage the application. Each partner administrator can have his or her own user account. The Partner Users tab allows a partner administrator to add or delete other partner administrators.
Please note that unlike the first partner administrator, who is defined during installation, the passwords for additional partner administrators must be set by those users themselves. To manage this, the application sends an email to each additional administrator with a link for setting up the user’s password. This email cannot be generated by the application until you configure email settings. This is described in the next section.
Setting up additional partner administrators:
If necessary, log on as a partner administrator. In Preferences, view the Partner Users tab.
Click the Add Partner button. The Add Partner User dialog box is displayed.
Enter a user name and email address for the additional partner administrator. You have the option of entering a first and last name as well, but this information is not required. Note that an email will be generated by the application and sent to the email address you specify. That email will contain a link for the administrator to set his or her password.
Click Add when done. The additional administrator is added to the list of partner users. You can edit or delete the additional administrator using the Edit and Delete action icons on this list.
Prior to setting up additional partner administrators, email settings must be configured so that the application can generate emails to notify users regarding their account setup and required links to complete the setup process.
*Be sure you are viewing the Email Settings tab for the partner, not for an individual institution in the database. Information on configuring email settings for an individual institution are described later in this document in the Email Settings for Institution section.*
By default, the settings you specify for your organization will be used to configure the email settings for individual institutions. You can modify the settings for individual institutions independently of the settings used for your organization.
Configuring email settings:
If necessary, log on as a partner administrator. In Preferences,
view Email Settings.
Supply your organization’s SMTP settings as appropriate.
Supply a display name and sender’s email address to brand the emails with your organization’s identity.
Click the Test Connection button to confirm the settings create a successful connection. The application will attempt to send a test email from the specified sender’s email address to the same address. If necessary, modify the settings if the test is not successful.
Click Save Changes.
Please note that you can clear all email settings by clicking the Clear Settings button. Clearing settings in this manner automatically updates the database with this change.
After the Configuration application is installed, Configuration launches in an unlicensed state. No application functionality is available until a financial institution is added and a valid license key is supplied by the partner administrator.
Licensing Configuration:
Launch Configuration. You are prompted to supply user credentials.
The partner administrator supplies the credentials specified as part of installation and setup.
Click the Log On button. The application opens in an unlicensed
state. Click the Preferences tab.
Click the Add Institution button.
Paste the demo license key supplied by CSi in the Enter
License Key dialog box. By default, the document library is set
to DocumentLibrary. This is the library of document FXL files
installed with the application. (Other document libraries may be
imported by the partner administrator.) Click OK. The
application validates the license key and enables functionality
appropriate for the license key.
You are prompted to supply information about the database used for
the application. Supply the database server name and database name,
the database user name, and the database user password. You may
specify a database that does not yet exist. It will be created for
you. Click Test Connection to verify the parameters are correct.
When the connection is successful, click Save to save the
database information. You may edit the database parameters later for
the selected financial institution using the Database Management
tab in Preferences.
On the Licensing and Setup tab, specify the financial
institution’s time zone. This time zone will be used to determine
dates and times related to content events such as saving,
modification, certification, and publishing.
The Category field allows the partner administrator to group financial institutions together based on a category label that the administrator enters. The label allows financial institutions to be more easily sorted on the financial institution drop-down list.
The partner administrator can specify a category for institutions. The category can then be used to filter institutions.
Selection Groups only. The default values collected in Configuration are combined with selection criteria that determine the conditions under which those values are used in transactions. The combination of data values and selection criteria are output from the application using its Publish function.
The manner in which Publish outputs content depends on the partner’s configuration of Publish File Management in Preferences. An Apply Changes to Category check box is included so that the administrator may elect to make publish file management changes to all institutions in a category simultaneously. The application prompts the administrator to confirm this action.
Option | Function |
---|---|
Web Services | Allows web services to be specified where the application will notify the partner that published content is ready for processing. When web services is used, additional features related to custom publish data become available that allow you to specify additional data to be included when the application sends information to your platform. To use the feature, click the Custom Publish Data link, then add or remove key value pairs as necessary. |
File Path | Allows a file path to be specified where published content will be posted by the application. In order to use a file path, Configuration must have write-access to the specified file path. Please note that a document library can be referenced as {DocumentLibrary} and appear in the publish file path as C:\inetpub\wwwroot\Temp\Publish\{DocumentLibrary}\Production. At the time of publication, the name of the active document library for that institution will replace {DocumentLibrary}. |
Store published content in ZIP file | Publishes content in a single ZIP file. The contents of this ZIP file are updated each time a new publish event occurs. This is applicable when publishing to a file path. |
URI Path | Allows specification of either the web services URI or the file path URI. When web services are specified, this path is where notifications from the application are stored regarding output files. When a file path is specified, this path is where the output files themselves are stored. |
Collected Data Configuration Path | Allows you to use the same default configuration file path for each financial institution, or to specify a unique configuration file path for a financial institution. The configuration file allows a partner to control which data elements will be presented as transactional in Configuration. Values for such data elements are collected in Configuration, but suppressed from publishing so that they can be collected at transaction time with the partner's system. The partner may also use the configuration file to supply default values or lock values in specific data elements. |
Selection Groups only. The published content from the application includes:
A TXL file for each published group. The TXL includes the default values supplied to all data sets included in the group.
A supplemental FXL file that contains the selection criteria that dictates the transaction conditions for use of the TXL data.
An XML file manifest that lists the output content to aid in partner automation of content consumption.
When custom documents are published, an FXL file is output for each custom document in a selection group.
Without Selection Groups. The published content from the application includes:
Configuring publish file management:
If necessary, log on as a partner administrator. In Preferences,
select the financial institution for which you are configuring
parameters from the institution list at the top of the screen, then
click Load.
In Preferences > Licensing and Setup, select the publish file management options that support your implementation.
If you want to apply those file management options to all institutions in the current institution’s category, activate the Apply Changes to Category check box.
Click the Save Changes button. If you are applying the changes to all institutions in the current category, you are prompted to confirm this action.
The data collection workflows available in the Data Sets activity are each controlled by an FXL file supplied by CSi. Among other things, the FXL files determine which data elements will be presented on the workflow tabs, and in what order they will be presented. Collections of these FXL files are referred to as document libraries.
When the application is installed, there is no initial default document library. It is necessary to specify a document library as part of the application setup process in order for institutions to access the data collection workflows included in their license key.
For information on importing and updating document libraries, please refer to the Managing Document Libraries section in this document.
Prior to a financial institution’s use of Configuration and your setup of institution administrators, email settings must be configured so that the application can generate emails to notify users regarding their account setup and links to complete the setup process.
By default, the values used to configure email settings for institutions will be those used to configure email settings for your own organization. You can modify the settings for each institution separately.
Configuring email settings:
If necessary, log on as a partner administrator. In Preferences,
select the financial institution for which you are configuring
parameters from the institution list at the top of the screen, then
click Load.
Click Preferences > Email Settings.
Supply your organization’s SMTP settings as appropriate.
Supply a display name and sender’s email address to brand the emails with your organization’s identity.
Click the Test Connection button to confirm the settings create a successful connection. The application will attempt to send a test email from the specified sender’s email address to the same address. If necessary, modify the settings if the test is not successful.
Click Save Changes.
Please note that you can clear all email settings by clicking the Clear Settings button. Clearing settings in this manner automatically updates the database with this change.
As the partner administrator, you may elect to set specific rules regarding the complexity of passwords selected by users of all institutions you add to the database. These rules will be enforced for all new users added to the database as well as existing users whose passwords may no longer meet the criteria that you define.
Setting password rules:
If necessary, log on as a partner administrator. In Preferences, click the Password Rules tab.
Select the password configuration options that are appropriate for your organization’s password standards. When you select a configuration option, additional controls are displayed for determining related password rules. For example, selecting Minimum Password Length displays controls for specifying the minimum length and the error message that users will see if they attempt to set a password that does not satisfy the minimum length requirement.
It is recommended that you customize your error messages so that your password rules are apparent to your users.
You can test your password rules. Enter a sample password and click
the Test Password button.
When you are finished, click the Save Password Configuration button.
A partner administrator is the business partner representative given responsibility for designating the initial institution administrator and configuring license key, selection criteria categories (when Selection Groups is licensed), and branding defaults for the financial institution using Configuration.
An institution administrator is the financial institution representative given responsibility for maintaining user permissions for Configuration. The institution administrator may also be responsible for maintaining the lists of values associated with selection logic criteria (when Selection Groups is licensed). There may be multiple institution administrators, all of whom can access all licensed functionality in the application.
The initial institution administrator is set up by the partner administrator. In order to test the application’s publish file management, CSi recommends that you create a test institution administrator for the purposes of exercising application functionality prior to setting up actual institution administrators.
Setting up a test institution administrator:
If necessary, log on as the partner administrator. In Preferences, select the financial institution for which you are configuring parameters from the institution list at the top of the screen, then click Load.
In Preferences > Permissions, click the Add Administrator button. The Add Administrator dialog box opens.
Create institution administrator credentials for yourself.
Click the Add button. A confirmation message appears. An email is sent to the email address you specified that includes a link for completing the user account setup. This link expires in 24 hours.
Access the setup link in the email notification. Your browser will open the Configuration screen for setting your password.
Enter your password and confirm that password, then click the Submit button.
If the password meets any password complexity that may have been put in place, a confirmation message appears with a link to log into Configuration. Click the link, then provide your user name and password.
To set up actual institution administrators, follow the same procedure noted above in accordance with your organization’s conventions for user names.
Prior to a financial institution’s use of Configuration, selection criteria must be defined by the partner organization. Selection criteria are the condition or conditions that must be satisfied in order for data values to be used in transactions. Selection criteria differ by financial institution, but may include categories representing product types, business regions, loan status, or any other data relevant to the logic of selection.
Selection criteria are composed of categories and lists.
Selection categories are always defined by the partner administrator. They include a screen label that is visible to institution users of the application and a datapoint value that is output as part of the supplemental FXL file when a publish event occurs.
Criteria lists may be defined by either the partner administrator or the institution administrator. These are the individual list values available within any given selection category. For example, when the selection category is Products, an institution administrator may need access to the list to maintain the current list of institution products. When the selection category is Collateral Type, the partner administrator may prefer to lock the list so that accidental changes to collateral type are not made by the institution administrator.
Creating selection criteria:
If necessary, log on as a partner administrator. In Preferences,
select the financial institution for which you are configuring
parameters from the institution list at the top of the screen, then
click Load.
View the Selection Criteria tab.
Click the Add Criteria button. The Add Selection Criteria
dialog box opens.
Specify the Criteria Name and corresponding Datapoint Name for the selection category.
Specify a list entry Label and corresponding Datapoint Value. There is no limit to the number of entries that can be included on the criteria list. You must create one initial entry in the dialog box in order for a valid entry of selection criteria to be made in the database. You can create additional list entries in Preferences after you submit the category to the database.
Click the Add button.
Adding list entries:
If necessary, log on as a partner administrator. In Preferences,
select the financial institution for which you are configuring
parameters from the institution list at the top of the screen, then
click Load.
Click Preferences > Selection Criteria.
Click the Add List Item for the selection criteria category where additional list entries are required.
Specify a Screen Label and Datapoint Value, then click Add.
Locking lists:
If necessary, log on as a partner administrator. In Preferences,
select the financial institution for which you are configuring
parameters from the institution list at the top of the screen, then
click Load.
Click Preferences > Selection Criteria.
Click the Lock icon for the selection criteria category whose list entries are to be restricted to partner administrator modification. You can unlock the list by clicking the Lock icon again.
Either the partner administrator or institution administrator may add, remove, or modify the list of valid values within a selection criteria category.
If the selection criteria have been locked by the partner administrator, then criteria lists are read-only and can be edited only by the partner administrator. A locked list is displayed with a lock icon. Institution administrators can only edit unlocked criteria lists. An unlocked list is displayed with an unlock icon.
Tool | Function |
---|---|
Edit. Opens the Edit Criteria Item dialog box so that you can modify the screen label and datapoint value for the list entry. |
|
Delete. Deletes the list entry. You are prompted to confirm this action. |
When Custom Documents are licensed with Configuration, users may access data dictionaries so that they can incorporate data elements, like borrower address or account number, into the text of a custom document.
CSi supplies a standard dictionary to its partners that includes those data elements appearing on the CSi documents received by the partner. That standard dictionary may be used as is, or it may be modified by the partner. For example, a partner may want to remove data elements to which they have not mapped.
The partner may also create and distribute its own data dictionary, and institutions may elect to use their own dictionaries that are available only to their own users. The process by which modifications of an institution dictionary are communicated to the partner for mapping is managed by the partner.
Standard and partner dictionaries are read-only for institution users. Institution dictionaries are read-write and are imported by either the partner administrator or the institution administrator in Preferences.
Specifying data dictionaries:
If necessary, log on as a partner administrator and select the financial institution for which you are configuring parameters from the institution list at the top of the screen, then click Load.
Click Preferences > Dictionaries.
To import content of a standard dictionary supplied by CSi, click the Import Standard Dictionary button.
To import content of a partner dictionary supplied by you, click the Import Partner Dictionary button.
Partners may elect to replace the default Configuration logo that appears in the upper left corner of the application window with a logo they specify. The logo will not appear on the Logon screen.
Default Configuration logo
Specifying a logo image:
If necessary, log on as a partner administrator. In Preferences,
select the financial institution for which you are configuring
parameters from the institution list at the top of the screen, then
click Load.
Click Preferences > Branding.
Click the Select a file button and select the image file you want to use. It must not be larger than 90 pixels high and 215 pixels wide. The file format must be .GIF, .PNG, or .JPG.
Click the Save Changes button. When the screen is refreshed, the selected logo will appear on every Configuration screen except the logon screen.
To revert to the original Configuration logo, click the Use default logo button, then click Save Changes and refresh the screen.
In order to test publish file management configuration, CSi recommends that the partner administrator use a test institution administrator user account to:
Create and certify a sample data set with default values.
Create a selection logic group containing the test data set.
Publish the group.
Verify the published content.
Steps 1-3 are performed within Configuration. In order to publish a group, the group must satisfy the following conditions.
Includes content. To be published, a group must include at least one associated data set.
Includes selection criteria. To be published, a group must include at least one piece of selection criteria.
Certified content. To be published, all data sets associated with a group must be certified.
Passes value check. To be published, all content associated with a group must be evaluated to determine if there is a conflict among the default data values included in the content.
When a group has satisfied a condition, the condition is displayed with in the application.
When a group has not yet satisfied a condition, the condition is displayed with in the application.
For the purposes of this beta release, create a data set associated with Policies > Privacy. If your demo license does not include Privacy, create a data set corresponding to the Policies, Products, or Provisions categories that are available to you. For the purposes of these instructions, Privacy is provided as an example.
Creating a test data set:
If necessary, make sure you are logged in as an institution administrator. (The partner administrator cannot access data set, selection group, or publish functionality.)
Click the Data Sets tab in the top right portion of the application window.
Expand branches in the Navigation pane to locate the data set category that correlates to the document or document component that you want to configure. Select Policies > Privacy for this test.
Click the Create Data Set button. Enter a name for the data set and click Create.
By default, new data sets are opened so that the first workflow tab is active. For a Privacy data set, this tab is the General tab. Supply values to all required data elements denoted with a red asterisk. You may optionally supply values to those data elements that do not have a red asterisk.
Click on the Facts tab. Supply values to all required fields denoted with a red asterisk. You may optionally supply values to those data elements that do not have a red asterisk.
Continue supplying required values to the remaining workflow tabs. The application automatically updates the saved data set as you move among the tabs.
Click the Save tool to save your custom content when you have completed the last tab.
The Data Collection window opens when you create a new data set or open an existing data set. The window is divided into a series of workflow tabs that generally represent the main sections of content that must be completed for the data set in question.
Each workflow tab presents a set of related data elements from which users make selections or enter text to reflect their institution’s default content for transactions that use the data set.
The General tab contains data elements that determine which additional tabs must be added to the workflow in order to collect content for the data set.
Before you can move forward with data collection, you must provide values to all required data elements on the General tab.
Workflow tabs are styled so that you can easily identify tabs that are complete, incomplete, active, and inactive.
1 | Light blue tabs are completed tabs. These tabs are not missing any required values. You may click on them at any time to review or modify their values. |
---|---|
2 | The gold tab is the active tab. Only one workflow tab may be active at a time. |
3 | Light blue tabs with red labels are incomplete tabs. You may click on them at any time to supply any missing required values. |
4 | Gray tabs are inactive. No values have yet been supplied to them, but you must complete all preceding tabs in the sequence in order to access them. |
Document Settings is a set of modules used to define the information and institutional standard practices required for loan or deposit documentation. The default data collected in these modules may be used in documents across the CSi Deposit and Lending libraries.
Note that the only modules in this category which can be previewed in Configuration are those associated with Global > Document Header and Global > Document Footer.
The Privacy workflow allows you to configure and customize the language that comprises the disclosure required by Title 12: Banks and Banking, Part 216- Privacy Of Consumer Financial Information (Regulation P). The workflow allows a financial institution to: 1) provide notice to customers about its privacy policies and practices; 2) describe the conditions under which the financial institution may disclose nonpublic personal information about consumers to nonaffiliated third parties; and 3) provide a method for consumers to prevent the financial institution from disclosing that information to most nonaffiliated third parties by opting out of that disclosure, subject to the allowed exceptions.
Provisions are sections of documents that CSi allows financial institutions to configure to better fit their unique compliance or product requirements. Depending on the provision in question, users may configure them by:
including the provision if it is not included by default
excluding the provision if it is included by default
appending language to the default provision text
replacing the default provision text
A data set is deemed complete when the user has supplied all of its required values. Data sets that have been completed are eligible for certification. Certification represents the institution’s approval of the data set for transaction use.
When the user certifies a data set, the application evaluates all workflow tabs to ensure that no required values are missing and that there are no conflicting values supplied to the same data elements.
Certifying a test data set:
If necessary, make sure you are logged in as an institution administrator.
Click the Data Sets tab and open the data set you want to certify.
On the Properties tab, click the Add Certification button.
The application evaluates all workflow tabs to ensure that all
required values are supplied and that there are no conflicts between
the values.
Click Certify to confirm the certification. The data set is made read-only and it becomes eligible for publication.
A selection group is a user-defined collection of data sets (and custom documents, if licensed) for which selection criteria is defined. When a group is published, the values in the data sets are used in transactions that satisfy the group’s selection criteria.
The Selection Groups activity is used to create and maintain these groups by:
Managing content. This includes adding and removing data sets or custom documents from a group.
Managing selection criteria. This includes defining the transaction conditions that must be satisfied in order for content to be used in transactions.
Analyzing groups. This includes identifying content that may have conflicting values within a group.
Creating a test selection group:
1.If necessary, make sure you are logged in as an institution administrator.
Click the Selection Groups tab in the top right portion of the application window.
Click the Create Selection Group button. The Selection Groups workflow is displayed with the Properties tab made active.
Enter a name for the new selection group in the Name edit box.
Click on the Manage Content tab. Add the test data set you created to the group by clicking the Add tool corresponding to that data set.
The group now includes content that has been certified. There can be
no value conflict in the group because only a single data set is
associated with it. Three of the four publish-ready criteria should
be satisfied:
Click on the Manage Selection Criteria tab. Specify selection criteria from the categories and lists defined in Preferences. All publish-ready criteria should be satisfied.
Click the Save tool to save the group.
Publishing refers to functionality that packages group content—default data values from data sets and selection criteria—for transaction use by the platform system or LOS.
Configuration outputs a TXL file with default data values, a supplemental FXL that defines the selection criteria associated with that data, and an XML file manifest. The files are output according to the publish file management method specified by the partner administrator in Preferences.
All files output by the application use the financial institution’s name as a prefix. For example, Group 1 published by CSi Bank is output as CSi Bank Group 1.TXL. This is intended to facilitate the use of a single directory by the business partner for multiple financial institution output from the application.
Publishing a test group:
If necessary, make sure you are logged in as an institution administrator.
Click the Publish tab in the top right portion of the application window.
Open the test group you created. Its content and selection criteria are listed for review and confirmation that the correct group has been opened. To publish the group, click the Publish button.
Retracting refers to the removal of selection group content from live transaction use by the partner system. Depending on the published file method specified in Preferences by the artner administrator, the application either removes the published content itself or contacts the partner system to complete the retraction process.
Note that retracting a selection group does not remove the group from the Configuration database, nor does it remove content that is associated with the group. Only published groups may be retracted.
Access the published file location specified in Preferences > Licensing and Setup by the partner administrator. This location should contain the published output for the selection group you published. If you published to a ZIP file, the ZIP file should contain a supplemental FXL file, a TXL file containing the values specified in the test data set, and an XML file manifest.
In order to test publish file management configuration, CSi recommends that the partner administrator use a test institution administrator user account to:
Create and certify a sample data set with default values.
Publish the data set.
Verify the published content.
Steps 1-2 are performed within Configuration.
For the purposes of this beta release, create a data set associated with Policies > Privacy.
Creating a test data set:
If necessary, make sure you are logged in as an institution administrator. (The partner administrator cannot access data set or publish functionality.)
Click the Data Sets tab in the top right portion of the application window.
Expand branches in the Navigation pane to locate the data set category that correlates to the document or document component that you want to configure. Select Policies > Privacy for this test.
Click the Create Data Set button. Enter a name for the data set and click Create.
By default, new data sets are opened so that the first workflow tab is active. For a Privacy data set, this tab is the General tab. Supply values to all required data elements denoted with a red asterisk. You may optionally supply values to those data elements that do not have a red asterisk.
Click on the Facts tab. Supply values to all required fields denoted with a red asterisk. You may optionally supply values to those data elements that do not have a red asterisk.
Continue supplying required values to the remaining workflow tabs. The application automatically updates the saved data set as you move among the tabs.
Click the Save tool to save your custom content when you have completed the last tab.
The Data Collection window opens when you create a new data set or open an existing data set. The window is divided into a series of workflow tabs that generally represent the main sections of content that must be completed for the data set in question.
Each workflow tab presents a set of related data elements from which users make selections or enter text to reflect their institution’s default content for transactions that use the data set.
The General tab contains data elements that determine which additional tabs must be added to the workflow in order to collect content for the data set.
Before you can move forward with data collection, you must provide values to all required data elements on the General tab.
Workflow tabs are styled so that you can easily identify tabs that are complete, incomplete, active, and inactive.
1 | Light blue tabs are completed tabs. These tabs are not missing any required values. You may click on them at any time to review or modify their values. |
---|---|
2 | The gold tab is the active tab. Only one workflow tab may be active at a time. |
3 | Light blue tabs with red labels are incomplete tabs. You may click on them at any time to supply any missing required values. |
4 | Gray tabs are inactive. No values have yet been supplied to them, but you must complete all preceding tabs in the sequence in order to access them. |
Document Settings is a set of modules used to define the information and institutional standard practices required for loan or deposit documentation. The default data collected in these modules may be used in documents across the CSi Deposit and Lending libraries.
Note that the only modules in this category which can be previewed in Configuration are those associated with Global > Document Header and Global > Document Footer.
The Privacy workflow allows you to configure and customize the language that comprises the disclosure required by Title 12: Banks and Banking, Part 216- Privacy Of Consumer Financial Information (Regulation P). The workflow allows a financial institution to: 1) provide notice to customers about its privacy policies and practices; 2) describe the conditions under which the financial institution may disclose nonpublic personal information about consumers to nonaffiliated third parties; and 3) provide a method for consumers to prevent the financial institution from disclosing that information to most nonaffiliated third parties by opting out of that disclosure, subject to the allowed exceptions.
A data set is deemed complete when the user has supplied all of its required values. Data sets that have been completed are eligible for certification. Certification represents the institution’s approval of the data set for transaction use.
When the user certifies a data set, the application evaluates all workflow tabs to ensure that no required values are missing and that there are no conflicting values supplied to the same data elements.
Certifying a test data set:
If necessary, make sure you are logged in as an institution administrator.
Click the Data Sets tab and open the data set you want to certify.
On the Properties tab, click the Add Certification button. The application evaluates all workflow tabs to ensure that all required values are supplied and that there are no conflicts between the values.
Click Certify to confirm the certification. The data set is made read-only and it becomes eligible for publication.
Publishing refers to functionality that outputs default data values from data sets for transaction use by the LOS.
Configuration outputs a TXL file with default data values for each data set. The files are output according to the publish file management method specified by the partner administrator in Preferences.
All files output by the application use the financial institution’s name as a prefix. For example, Privacy Disclosure published by CSi Bank is output as CSi Bank Privacy Disclosure.TXL. This is intended to facilitate the use of a single directory by the business partner for multiple financial institution output from the application.
Publishing a test group:
If necessary, make sure you are logged in as an institution administrator.
Click the Publish tab in the top right portion of the application window.
Open the test data set you created. To publish the data set, click the Publish Data Set button.
Retracting refers to the removal of data set content from live transaction use by the partner system. Depending on the published file method specified in Preferences by the partner administrator, the application either removes the published content itself or contacts the partner system to complete the retraction process.
Note that retracting a data set does not remove it from the Configuration database. Only published data sets may be retracted.
Access the published file location specified in Preferences > Licensing and Setup by the partner administrator. It should contain the published output for the data set you published. If you published to a ZIP file, the ZIP file should contain a TXL file containing the values specified in the test data set.
The data collection workflows available in the Data Sets activity are each controlled by an FXL file supplied by CSi. Among other things, the FXL files determine which data elements will be presented on the workflow tabs, and in what order they will be presented.
These FXL files may be updated periodically by CSi to create changes in the data collection workflows. For example, if regulations change so that more data must be collected for a particular document or document component, the FXL file must be updated to present those new data elements.
When the application is installed, there is no initial default document library. It is necessary to specify a document library as part of the application setup process in order for institutions to access the data collection workflows included in their license key.
The Document Management tab in the Preferences activity allows the partner administrator to import updated libraries of FXL files when new FXL files are available from CSi.
Institution administrators may access the Document Library tab in Preferences to select an alternative document library when their financial institution is ready to use an updated library to drive their data collection workflows. Changing document libraries may result in certified data sets becoming uncertified if they are missing values that are required in the updated libraries.
Institution administrators may access the Document Library tab in Preferences to select an alternate document library when their financial institution is ready to use an updated library to drive their data collection workflows. They are only able to select document libraries that have been made available by the partner administrator.
Updating the document library requires action from both the partner administrator and the institution administrator.
This document provides information specific to the partner administrator’s activities. Please refer to the Configuration Document Library Maintenance Guide for information on activities performed by the institution administrator.
The first step in this process is performed by the partner administrator. You must import the new Configuration document library and place it in C:\inetpub\wwwroot\Documents.
The CSi document library server is updated as new document libraries become available. To check the CSi document library server for updates, click the Check for Updates button.
You can then upload available document libraries to make them available to financial institutions. Once a library is uploaded, it continues to appear on the Available Document Libraries list. If an available library has been imported, it appears with a green check mark on the Available Document Libraries list.
Importing document libraries:
If necessary, log on as a partner administrator. In Preferences, click the Document Management tab.
Click the Check for Updates button. To import an updated document library, locate its name on the Available Document Libraries list and click its Download icon. The application begins downloading the new document library.
The Import Document Library dialog box appears. Enter a display
name and description for the library. The Display Name should
clearly communicate to the financial institution the version of your
software with which the Document Library is compatible. The
description should provide financial institutions with any
additional information relevant to them. Specify the library file
path where the library resides. This is the directory path on the
Simplicity server where you placed the document library, for
example, C:\inetpub\wwwroot\Documents\2015D1.1. Then click
Add.
Multiple document libraries may be imported, and the partner administrator has the discretion to use any of the imported libraries as the library for new institutions that are added. The application allows a library to be designated as the primary library. The primary library is selected by default when the partner administrator creates new institutions.
Once this step is complete, the financial institution administrator can access the Preferences tab to complete the document library update.
Configuration includes several levels of user help.
Provides general reference information about application functionality. The user guide is viewed online and opens in a new browser tab.
This content is presented as the first tab of Data Sets workflows. The Help tab presents a brief overview of the workflow in question and notes transactional data that may impact the standard language ultimately used at the time of transaction.
This is a short description of each tab in a data collection workflow. It provides context for the data elements presented on the tab and how the values you supply will be used in transactions.
This is a short description of data elements in the Data Sets workflows. Tooltips appear when you position the mouse pointer over a data element and are removed from display when the mouse pointer is repositioned on the screen.
Detailed help is displayed when you click on the help icon associated with a data element. This help offers additional details about the data element, typically beyond what is stated in the tooltip.