Web Browser Integration

Web Browser Integration (WBI)

Overview

The OpenForms Application Browser form technology is a form that is based on the Web Browser OpenForms technology. This form can be used as a container for simple, e.g. Web Browser, to complex integrations such as MATIX, a GIS solution from Harris Govern.
An unlimited number of forms can be set up to meet the requirements for displaying spatial, and tabular content of profile users. In addition, an unlimited number of Application Browsers can be configured in a form. Forms can be set up with options that can include the following Key Types, e.g. Parcel ID, Name ID as well as Unformatted Tax Map). Other options include configuration by GIS Server URL, through Synchronization Options, and by Viewing Tabular Data.

Form basic integration, Web Browser Integration (WBI) can be used for adding an interactive website to Govern OpenForms. For example, you could use WBI to add a Geographic Information Services (GIS) web browser interface, such as the Govern GIS Explorer, to a Govern user form and Profile. You could then select records in Govern and view them on the GIS interface. You could also select records on the GIS interface and load them to the Govern Treeview, with the option to set up manual or automatic synchronization between Govern and the website.

The WBI control is added to a custom entity in the Govern OpenForms Designer (OFD). All the configuration is performed in the OFD including any related security settings.

WBI is supported by most websites. It is fully integrated with Govern. It implements predefined commands to add the following functionalities:

  • Loading all records from the Govern treeview to the website
  • Loading the active record in Govern to the website
  • Replacing all records in the Govern treeview with a list provided by the website
  • Replacing the active record in Govern with a list provided by the website

Configuration

Custom entities are used for adding specific predefined controls to a Govern form. In this case, a custom entity is used for adding Web Browser Integration (WBI) functionality. A custom entity cannot stand alone. It needs to be added to an existing form. The form must be added to Profile.
You can add the same custom entity to multiple forms, and add the forms to multiple Profiles, if required.

You need to select a Parent Entity for your new custom entity. Usually, this is the Root Entity.

The following rules apply:

  • The WBI control must be added to a custom entity.
  • The custom entity must be added to an existing form.
  • The form must be added to a Profile.
  • The Dataset Type Code for the Profile must be set to Parcel ID (P_ID) or the Name ID (NA_ID), and must correspond to the value set for the SelectedKeyType.
  • The Dataset Type Code is shown in the following screen shot:

Documentation

Click on the link below to view a .PDF containing details about Web Browser Integration and configuration procedures.
Adding and Configuring WBI

Video Demonstrating Test Tool

A video demonstrating how to test the  integration will be be posted below shortly.

Click here to view the How To demo video

What’s New!

Web Browser Integration (WBI) was introduced in Govern 6.0. As of Govern OpenForms version 6.0.1405, it is used for integrating the Govern GIS Explorer with Govern.

NOTE: The WBI control is used for integrating GIS functionality with Govern as of Govern OpenForms 6.01.1405

Troubleshooting

Any issues that may be related to the Web Browser Integration form will be listed below.

No Access to the Wiki (Log In Error)

Symptom

This error displays a Script Error screen which appears on top of a Wikispaces sign in screen.

Resolution

A solution to resolving this error is to log in to the Wiki prior to launching Govern. When you have successfully logged into the Wiki, start Govern and open the form with the Web Browser Integration form.

Related Topics

 

 

101-std-frm-003-WebBrowserIntegration

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

eGov – Configuration

Configuration of the eGovernment – Public Self Service Portal

Overview

When users arrive at the home page and access the ePortal, or perform a login to access the eProfile, a default starting point is used from the setup. This default refers to a department. The default and other settings are part of a series of steps needed to define the eComponent site. General configuration is carried out through the OpenForms General Settings Editor in GNA. Additional parameters are required to be completed when using the eGovern – Public Self Service Portal module.

General tab

eComponent configuration parameters are located in the Websites Manager form in the Govern New Administration (GNA) Release 6.0 and greater.

eGovern Configuration – SMTP

Configuration of the SMTP parameters of the eGovern – Public Self Service Portal is carried out within the Govern New Administration (GNA).
In the GNA ribbon …

  1. Select Application Configurations (tab) > Web Configuration (group) > Manage Web Site.
  2. In the Manage Web Site form, click the General tab.
  3. Locate the Mail group.
  4. Complete the required fields.

The required parameters are as follows:

  • Administrator Mail – This field should contain the email address of the system administrator that has been designated to receive error messages.
  • System Mail – The System Mail parameter is the address that will be used for the from field in the email message. These are system messages that will not require replies, e.g. confirmation of user payments.
  • SMTP Host – Enter the host name of your SMTP server in the SMTP Host parameter. Example: mailhost.domainName.com, or smtp.sparta.com.
  • SMTP Password – In the SMTP Password field enter the password used to access the account. Text entered into this field will appear “cloaked”, i.e. typed letters will appear as asterisks
    ” to hide the typed letters.
  • SMTP Port – Specify the SMTP Port; the typical port is 25.
  • SMTP User – In the SMTP User field enter the username that is used to access the account.
  • Activate email in HTML format – Select this option to send email messages in HTML format. As HTML text additional formatting can be added to the messages. The default format for sending messages is as plain text.

Include Administrator in Email Communication** – Select this option to send a copy of the email message to the administrator.

About Ports

Port information is best obtained from the System Administrator that manages the communications requirements for the organization. By default, the following ports may be used for the SMTP protocol:

For Unencrypted SMTP

Port 25 / 587 / 2525 – This is the default SMTP non-encrypted port but ISPs will deny its use because of spam and malware traffic. Alternate ports are 587, and 2525

SMTP with SSL

Port 465 – This is a deprecated port but may still be used.

Related Topics

What’s New in the eGovern

Upgrading the Web User Interface

eGov Product Map

FAQ

 

 

201-all-egov-config

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

WM Steps Actions Configuration

Workflow Management – Steps Actions Configuration

Overview

When defining the workflow steps, you can specify actions to be executed triggered on INITIALIZATION, on COMPLETION ALL (any status) of the step regardless of the status, or for a specific status (answer).
Click here for the complete Workflow Actions list.

User Interface

The Workflow Management form with Parameters and Definitions is accessed through the Govern New Administration (GNA) under the Application Configurations menu. The menu from the icon has options for the following:

  • Kinds and Categories
  • Departments
  • Link Types

To open the Workflow – Department form in GNA…

  1. On the GNA ribbon, select Application Configurations (tab) > Workflow Management > Departments

The Workflow – Department form is presented in the center pane.

  1. Click to select a department (Table: USR_DEPARTMENT) from the Departments column on the left hand side (LHS) of the interface.
  2. Select the Types tab in the Workflow – Department form. When created, the Type tab will contain the list of currently existing Types.
  3. Click to select a Type from the list.

Activities

Activities are the actions that can be selected by a department when defining workflow processes. A click on Steps in the Type tab will display the Activities screen. It is here that activity steps are created for the selected Type.

Adding Steps to a selected type…

To add action steps to an existing Type, click to select it under the Types tab…

  1. Click Steps.
NOTE: The Steps button will be disabled if there is a type selected or if the selected type is a new type.

About Activity Step Security

If you do not have the security rights to open the STEPS editor, a click on Steps will display an error message indicating that you do not have access rights to view the screen. Access can be obtained from a system administrator through the Govern Security Manager (GSM).

Security Manager (SM) setup

To setup, in Security Manager (SM)…

  1. Expand the Applications node.
  2. Click to expand GNA > Workflow > Workflow Management > Browse Steps.
  3. Right click on Browse Step to display the floating menu.
  4. Select Edit.
  5. The following security options can be enabled:
  • (V) View (view the steps)
  • (I) Insert (create new steps)
  • (U) Update (update existing steps)
  • (D) Delete (delete existing steps)

Refer to the Govern Security Manual user guide for details about security.

Activity Steps Screen Layout

Activity Step – parameters

Step Description – Enter an alphanumeric description of the step. This field is will accept a description with a maximum length of 30 characters.
Step Number – Enter a step number from 0 – 999999; this is the numeric designation that will be used for the step. (integer field).
When steps reference this step as a ‘Go To’ step, any modifications to the number will display a warning that will request that the referencing steps are also updated.

Activities group

Activity steps can be added or cancelled from this list.

Activities group – parameters

Add Activities [ + ] – Click to add an activity step.
In the Add Activities modal window, click to select 1 or more activities from the list of activities.
Click Add to add the selected activities, or click Cancel to cancel the action.

Remove Current Activities [ – ] – Click to select an existing Activity step from the Activity group grid.
Click [-] to delete the activity from the list.

NOTE: When steps reference this step as a ‘Go To’ step, any modifications to the number will display a warning that will request that the referencing steps are also updated.

Available Status group

For information regarding the Available Status group, refer to the Workflow Management ACTIONS – Change a Status page on this Knowledge Base.

Initialization Settings group

How the activity is started, i.e. initialized, is specified in the Initialization Settings group.

Create, Update or Remove Actions

For information regarding actions, refer to the Workflow Management Actions page on this Knowledge Base.

Documentation

Click below to view or download the current documentation for this feature.
103-wm-parm-315_Definition_of_Workflow_Types_Steps_Actions.pdf

Related Links

What’s New in Workflow Management
Main Workflow form
Workflow Management Overview
Workflow Management Installation
OpenForms Reference (Configuration) Setup Information
Workflow Management – Workflow Form Controller & Workflow Type Custom Control
Workflow Management – Additional Types
Workflow Management OpenForms Reference
Workflow Management Business Rules
Product Map

 

 

103-wm-parm-315

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

MA – Shared Table and Column Names

 

CAMA Creating Elements with the Same Table and Column Name

Overview

In Govern OpenForms, you can create two or more Mass Appraisal Building Structural Elements or Land Adjustments that have the same table name, but different column names. This can be useful for creating a breakdown by percentage for elements or adjustments.

It is possible to create two or more tables that have both the same table name and the same column name. However, this is not a recommended setup. The following conditions apply:
Building Structural Elements are applied to different models.

  • All Models must be different, not just the combination.
  • Land Adjustments are applied to different land uses or land schedules.
  • All land uses or schedules must be different, not just the combination.

The tables have different sequence numbers.
This is not a recommended configuration. If two or more elements share the same table and column name, they can be overriden with the worng element if a user makes a change in Govern.

For a pdf version of this page, open the following document.
SameColumnDifferentModel.pdf

Configuration for Building Structural Elements

To use this feature, ensure that the Apply Structural Elements to Models option is selected in GNA.
To enable this option.

  1. Launch GNA.
  2. Select Application Configurations > Mass Appraisal > MA General Parameters.
  3. Select Page 2.
  4. Select the Associate SE to Models option.
  5. Click Save.

Configuration for Land Adjustments

Land Adjustments can be associated with either Land Uses or Land Schedules.
To enable one of these options:

  1. Launch GNA.
  2. Select Application Configurations > Mass Appraisal > MA General Parameters.
  3. Select Page 2.
  4. Select one of the following:
    Associate Land Adj. to Land Uses.
    Associate Land Adj. to Land Schedules
  5. Click Save.

 

Creating Mass Appraisal Tables with the Same Table and Column Name

Building Structural Elements

To set up the tables:

  1. Launch GNA.
  2. Select Table Maintenance > Building Structural Elements.
  3. Click New to create a new table.
  4. Select any element type, other than Header, from the Element Category field.
  5. Enter the Table Name and Column Name.
  6. Complete the other parameters as required.
  7. Select one or more models under Apply to Models.
  8. Click Save.
  9. Repeat steps 3 to 8 as many times as required to create additional tables.
    Enter the same table name and the same column name for each table.

Ensure that all models in all tables are different.
If any are repeated, a validation error appears.

Land Adjustments

To set up the tables:

  1. Launch GNA.
  2. Select Table Maintenance > Land Adjustments.
  3. Click New to create a new table.
  4. Select any element type., other than Header, from the Element Category field.
  5. Enter the Table Name and Column Name.
  6. Complete the other parameters as required.
  7. Do one of the following:
    Select one or more land uses under Land Uses.
    Select one or more land schedules under Land Schedules.
  8. Click Save.
  9. Repeat steps 3 to 8 as many times as required to create additional tables. Enter the same table name and the same column name for each table.

Ensure that all land uses or land schedules in all tables are different.
If any are repeated, a validation error appears.

 

 

103-ma-parm-shared-columns

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

103-ma-parm-ComputeEntity

Mass Appraisal (MA) Compute Entity Configuration

Version 6.1 [under construction]

Overview

Expressions are used throughout the Mass Appraisal system in order to compute appraised values.The administrator must setup the different business entities used for computations.

  • Income Economic Compute Entity
  • Income Actual Compute Entity
  • Income Detail Compute Entity
  • Land Compute Entity
  • Master Compute Entity
  • Miscellaneous Structures Compute Entity
  • MRA Compute Entity
  • Site Compute Entity
  • Building Structural Elements Compute Entity
  • Building Areas Compute Entity

 

 

103-ma-parm-ComputeEntity

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

 

AR Lockbox Configuration

Accounts Receivable (A/R) Lockbox Configuration

Configuring the A/R Lockbox

The configuration of the A/R Lockbox comprises the following steps:

  • Verifying the Configuration in the Business Entity Designer (BED)
  • Setting the Default Parameters in GNA
  • Defining the A/R Subsystem Priorities
  • Setting Up Deposit Management
  • Setting Up A/R General Parameters for the Subsystems
  • Defining the Lockbox Batch Process
  • Setting Security for the Lockbox
  • Customizing the Layout

For more information about lockbox user data entry, see the A/R Lockbox user form.

For more information processing an A/R Lockbox file, see A/R Lockbox batch processes.

Verifying the Configuration in the Business Entity Designer (BED)

Read More...

The A/R Lockbox contains one business model with two business entities:

  • Business Model: AR_Lockbox
  • Business Entities. AR_Lockbox_Header and AR_Lockbox_Detail

You can configure the following:

  • On the Model: Allow use in the Govern Query Tool.
  • On the Entities: Set rules for Auditing and Central Notes

Setting the Default User Registry Parameters in GNA

The following defaults are defined in the User Registry Manager in GNA for the Lockbox user form in Govern. They can be configured for the Lockbox user form in Govern. These are defined in the User Registry Manager.

  • Effective Date
  • Entry Date
  • Installment
  • Payment Type
  • Transaction Type

To configure the default settings:

  1. Launch GNA.
  2. Select Parameters > User Registry Editor.
  3. Select Lockbox from the Registry Filter.
  4. Enter a date in the Default Effective Date parameter. This appears on the Lockbox Details tab of the Lockbox form in Govern.
    The Effective Date is the date that the payment becomes effective.
  5. Enter a date in the Default Entry Date parameter. This date appears in the Entry Date field on the Lockbox Details tab of the Lockbox form in Govern, when you click New.
    The Entry Date is the date that the payment is entered.
  6. Select an installment number from the Installment drop-down list. The installment appears on the user form. Installments are used with Real Property Tax. They are defined in the VT_SYSTEM INSTALL table. Setting the installment type for the period in which the payments are entered, speeds up the data entry process.
  7. Select a payment type from the Payment Type drop-down list. Payment types include: ACH, American Express, Collection Agency, Debit, Discover, eCheck Personal, Lockbox, MasterCard, Pinless Debit, and Visa.
  8. Select a transaction type from the Transaction Type drop-down list. Typically, this is Payment.
  9. Click Save.

Users have access to these settings from the Lockbox user form in Govern, if they have the required security permissions. See Setting Security for the Lockbox.

Defining the A/R Subsystem Priorities

Define the order in which payments received through the Lockbox, and by other means, are distributed. This is set on the A/R Subsystem Priorities.
Payments are distributed according to the following rules:

  • Payments are made first to the subsystems with the Ignore Year option selected, according to Priority Number. The subsystem with the highest priority number is paid first.
  • Payments are then made to subsystems with the Ignore Year option deselected, according to Priority Number. The subsystem with the highest priority number is paid first.
  • If two subsystems have the same priority number, and the Ignore Year is the same, payments are made in alphabetical order.

To access the A/R Subsystem Priorities form:

  1. Launch GNA.
  2. Select Application Configurations > Accounts Receivable > A/R Subsystem Priorities.
  3. Enter a number in the Priority field beside each subsystem for which payments are received through the lockbox. This number corresponds to the order in which payments are made on billed items. The highest number represents the highest priority (AR_Master.PRIORITY).
  4. Select Ignore Year to give the subsystem priority. Otherwise, payments are made on all outstanding bills according to year; i.e., all bills from 2015 are paid before the bills from 2016 if this option is deselected.
  5. Click Save.

Click Exit to close the form. A confirmation message appears if there are any unsaved modifications. Click Yes to save your new data or No to close the form without saving.

Setting Up Deposit Management

Deposit Management is required for all A/R transactions including those received through the Lockbox. Deposit numbers can be created manually or automatically. In both cases, they are managed through the Deposit Management entity, which is part of the Lockbox form in Govern.

Full details of setting up Deposit Management are provided in the Accounts Receivable documentation.

Setting Up A/R General Parameters for the Subsystems

Review the Accounts Receivable General Parameters to ensure that the rules for minimum payments are correctly setup.
To review the A/R General Parameters:

  1. Launch GNA.
  2. Select Application Configurations > Accounts Receivable > General Parameters.
  3. Verify the Minimum Balance to Compute Charges parameter.
  4. Scroll through the settings for each subsystem under Related Subsystem Parameters.
  5. Verify the setting for Allow Payments < Late Charges Due for each subsystem.By default, payments that are less than the late charges due cannot be entered on the user forms. A message appears and the payment cannot be saved.
  6. Verify the Minimum Collection Amount for each subsystem for which it appears.

Defining the Lockbox Batch Process

To define the A/R Lockbox batch process:

  1. Launch GNA.
  2. Select Editors > Batch Process Definition Editor.
  3. Click New.
  4. Select A/R Lockbox from the Process drop-down list.
  5. Set up the parameters as defined in the Batch Processing documentation.

Setting Security for the Lockbox

In the Govern Security Manager (GSM), you can define security permissions for the GNA administrative forms used for the Lockbox. However, this security applies to the entire form. For example, the security definitions for the User Registry Manager apply to the entire form, not just the Lockbox options.

The User Registry Lockbox parameters are also available in Govern via an action button. You can provide security for this action button through the OpenForms Designer.

To define this security:

  1. Launch the Govern Security Manager (GSM).
  2. Select Applications > Govern > Profiles.
  3. Select the Profile containing the A/R Lockbox form and Batch Process.
  4. Select Batch Processes > A/R Lockbox.
  5. Right-click on the A/R Lockbox batch process.
  6. Click Edit to set up permissions.
  7. Click Exclusions to define exceptions to the permissions.
  8. Click OpenForms.
  9. Select the A/R Lockbox form.
  10. Repeat steps 5 through 7.
  11. Click Save.

Customizing the Layout

You can make the following changes to the Lockbox user form through the OpenForms Designer (OFD):

  • Customize the form by renaming and repositioning the fields as required by your organization.
  • Customize the Browse screen and the Record Description, if required.
  • Set the security for the Lockbox user form in Govern.

To set up the security:

  1. Launch the Govern OpenForms Designer (OFD).
  2. Open the A/R Lockbox form.
  3. Select the Security icon to shift to Security Mode.
  4. Select a Security Type, Profile, and Role or user.
  5. Select the User Registry action button.
  6. Define the security permissions.
  7. Click Save.
  8. Repeat steps 4 to 7 for all required combinations of Security Type, Profile, and Role or user.
  9. Repeat steps 4 to 7 for all required combinations of Security Type, Profile, and Role or user, but select the Quick Save and Insert action button.

 

 

101-frm-036-config

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

 

 

 

 

322-forte

ForteTM Payment Processor

Overview

Available in General Availability Release (GA) 6.0.1606
The ForteTM Payment Processor allows Govern users to accept credit card payments at their Point of Sale (POS) using the Forte POS credit card terminal. Forte is a 3rd party integration option consisting of both a hardware, i.e. POS terminal with customized firmware, and a software component. The Forte POS terminal along with payment processing gateways, make up the Govern Forte Payment Integration.
The following Govern modules are required for the integration:

Configuration

In order to implement this solution, configuration is required at two levels:

322-ui-forte.png
Test Credit Card & eCheck RT Information – Click to Access

 

  1. Hardware and software configuration of the Forte POS credit card terminal.
  2. Configuration in the Govern system registry with the Govern New Administration (GNA).

Hardware & Software Configuration of Forte Terminal

Installation and connection instructions for the Forte terminal are bundled with the shipping package. This terminal is to be connected with the workstation that is configured with the Govern application.
Connection options are Ethernet, or USB. Software with instructions, intended for use with the Terminal is also included. This hardware and software pre-configuration must be completed prior to any Administrator configuration in Govern.

Configuration in GNA

The following system registry settings need to be configured.
To begin the configuration in GNA:

  1. Launch GNA.
  2. On the GNA ribbon click Parameters (tab) > General Settings Editor.
  3. Select Cash Collection from the Registry Filter combo box.
  4. Configure the required key values in the related Key Name columns

Key Name Columns

There are four (4) parameters that are required to be configured in the SY Registry in GNA.
Forte Merchant ID – This value will be provided by Forte.
Forte Password – Enter the password that was provided by Forte.
Forte Response Time-out (Seconds) – Enter a value of 70.
Point of Sale Provider – Select Forte from the combo box.

Setting up the Forte Payment Processor

Installation of the Forte Hardware

It is recommended by the Verifone Device supplier that the driver installation should occur before connecting the device. Typically users will connect a device prior to installation of the drivers.

NOTE: If you have already connected the device, and Windows detected new hardware, simply cancel any dialog screens indicating that new hardware has been found. Disconnect the Verifone Device, and proceed with the software installation.
– Installation MUST be performed by a user with administrative privileges.

Documentation

Click below to download or view the documentation.

Forte Pos Integration

322-FORTE_POS_Integration.pdf

Forte Web eGovern Integration

322-Forte_eGovern_Processor_Payment.pdf

Forte Web eGovern Payment Process (UPDATED)

322-Forte_eGovern_Processor_Payment.pdf

Forte Test Credit Card and eCheck RT Information

322-Forte-(Test Credit Card and eCheck Information).pdf

Troubleshooting

The section is reserved for any troubleshooting information related to installing and configuring the FORTE payment processor.
The following should be verified prior to connecting the payment device:

  • All installations MUST be performed by users with administrator rights.
  • When performing the driver installation, running the silent.bat file is the preferred option.
  • The software driver installation must be performed prior to connecting any hardware devices.

Issues with Freezing of the Forte Application

When there are issues with the Forte Application freezing, e.g. the terminal will stay frozen on the WELCOME screen. If the terminal “hangs”, it typically means that it is having a problem with one of its connections.
RESOLUTION – One possible resolution involves users trying the following steps:

  1. Enter the Forte application without anything but the power connected to the terminal.
  2. If successful, then connect either the miniUSB or the Ethernet cable and reboot the terminal.
  3. Now enter the Forte application again. If the terminal “hangs”, it typically means that it is having a problem with one of it’s connections.

Related Topics

Point of Sale (POS) Processing

 

 

322-forte

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...