Dynamic Search Groups

Dynamic Search Groups

Overview

The Dynamic Search Group management tool is used to group together multiple Dynamic Search Styles. The Dynamic Search Group management tool consists of two parts:

  • Available Groups: The existing groups appear in the Available Groups list box (1). To view the details on a group, highlight it in the list.
  • Search Groups: The Search Groups tab displays details on the selected group (2).

Groups

Creating a Group

To create a group:

Read More...

Click New to reset the form; so that you can enter new data.

  1. In the Code field, enter a string, with a maximum of 15 characters, to identify the style in the database.
  2. In the English Short Description field (or the Short Description field of your first language), enter a description to a maximum of 25 characters.
  3. In the English Long Description field, enter a description to a maximum of 50 characters.
  4. Repeat steps 4 and 5 for the French, Spanish (or second) language fields.
  5. Select the styles to link to the group, using the Add button.
  6. Click Add, under the Available Groups list box to add it to the list.

Modifying a Group

To modify a group:

  1. Highlight the group in the Available Groups list box.
  2. Make your change on the form.
  3. Click Save.

Changing the Style Order

To change the order of the linked styles:

  • Click Up to move the style towards the top of the list; so that it is performed nearer to the beginning of the sequence.
  • Click Down to move the style towards the end of the list; so that it is performed closer to the end of the sequence.
  • Click Add to open a secondary form where you can select styles to add to the group.
  • Highlight the style or styles that you want to add and click Add on the secondary form.
  • To remove a style, highlight it in the Linked Styles list box and click Remove.

Deleting a Group

To delete a group:

  1. Highlight the object in the Available Group list box.
  2. Click Delete.

See Also

Dynamic Search Objects
Dynamic Search Styles
Dynamic Search Groups

 

103-ED-016

 

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...

302-crystal

Crystal Reports

SAP Crystal Reports Run time version for Microsoft Visual Studio | Updated July 5, 2017

Overview

Version – Release [6.0.1411] Crystal Report Runtime 13-0-12

The Crystal Reports run-time package is required to be installed on each client if Crystal Reports are used. Refer to install pack CRforVS_redist_install_32bit_13_0_12 (older pack was 0_7) which is distributed with the binaries. The new package was incorporated to correct known problems with the WPF View tool bar.

Developers

Users that wish to modify existing, and or, develop Govern reports will need to obtain a full developers license for Crystal Reports Designer.

Compatibility

All Govern for .NET applications use the Crystal Report for Visual Studio runtime engine. Note that this runtime engine is actually version 13.0.XX; the last version of the engine supported by Govern for Windows (VB6) is Crystal Report 2008, i.e. Version 12.0.XX; where XX refers to the version of the service pack
Confirmation of support can be found at the following links:
https://archive.sap.com/discussions/thread/3936896
https://answers.sap.com/questions/78362/is-crystal-runtime-13-for-vs-compatible-with-cryst.html
Reports created with version 2008 are compatible with Govern for .NET. (As of version 2008 which is the last release by Business Object. Since then SAP has released three (3) versions, 2011, 2013, and 2016. These versions are also known as versions 14.0.XX, 14.1.XX, and 14.2.XX.

NOTE: If older versions were installed, a complete uninstall is recommended before installing a new version.

Limitation

Crystal Reports Maximum Report Processing Jobs Limit

Too Many Print Jobs Submitted to the Report Engine
Starting in version 10 of Crystal Reports, the reporting engine was optimized for greatest report throughput. There are specific registry keys that control this optimization. By default, the print job limit is set to 75 print jobs. When a load is placed on the application it can hit the 75 print job limit and cause the error. Note that a print job includes main reports, subreports, and in-session report objects (e.g.; drill down, paging, searching, and more.). Therefore a single report could exceed the 75 print job limit. Consider a report that returns 75 records, with a subreport placed in the detail section and thus running for each record. This report will need to run 75 subreports plus the main report, reaching 76 print jobs and the error will be thrown.
For more information, see SAP Article

Installation

NOTE: Client computers that intend to run Crystal Reports will need to install the Crystal Reports runtime on each client computer. Refer to the Crystal Report Runtime section of the DeployEZ™ Installer Guide for installation details.

This page is periodically updated, please review for the latest updates.

 

302-crystal

 

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...

 

 

GNA – Shared Expression Editor

GNA – Shared Expression Editor

Version 6.1

Overview

The Shared Expression Editor is new in Govern OpenForms 6.1. It is used to facilitate the management of the expressions that are used in multiple forms. Shared Expressions can be created by year and / or jurisdiction.

To view a pdf version of this page with images, see:
Shared Expressions.pdf

Accessing the Shared Expression Editor

To access the Shared Expression Editor:

  1. Launch GNA.
  2. Select Editors > Shared Expression Editor.

Read More...

The Shared Expression Editor contains the following sections:

  • Treeview: The existing expressions are listed in the treeview on the left of the form.
  • General Information: The Code and descriptions of the Shared Expression are listed at the top of the form.
  • Shared Expression text box. The expression is created and displayed in the text box in the center of the form.
    There is an Evaluate section for testing the expression.
    The Context is used for adding the entity in which the expression
  • Used In: When you select an expression, it is displayed in the Expression Editor. The attributes and entities where the expression is used are listed in the Used In section at the bottom of the form.

Shared Expressions can be defined by year. However, the Shared Expression Editor form is not year-based.

 

Creating a New Shared Expression

To create a new Shared Expression:

  1. Launch GNA.
  2. Select Editors > Shared Expression Editor.
  3. Click New.
  4. Enter a code in the Code parameter to identify the Shared Expression.
    This can be any combination of alphanumeric characters and the underscore. It must start with a letter.
    This is a required field.
  5. Enter descriptions in the Short and Long English and French Description parameters.
  6. Enter the expression in the Shared Expression text box.
    This is a required field.
  7. Select an entity for the expression from the Context drop-down list.
    This is an optional field.
  8. Select By Year if the expression is specific to one or more years.
  9. Select By Jurisdiction if the expression is specific to one or more jurisdictions.
  10. Click Save.

Setting Up Expressions By Year / Jurisdiction

To set up expressions by year and / or jurisdiction:

  1. Select the By Year and / or By Jurisdiction option on the Shared Expression Editor.
  2. The Values by Year/Jurisdiction text box opens.
  3. Click the Add icon to add the years and jurisdictions.
  4. Additional Jurisdiction and Year text boxes are enabled.
  5. Select a jurisdiction from the Jurisdiction drop-down list.
  6. Enter a year in Year text box.
  7. Click Save.

Using Attributes in an Expression

If you want to add an attribute to an expression,
You can specify an entity for the expression. If you do this, the entity must be included in the form where the expression is used.
To specify an entity:

  1. Open the required expression in the Shared Expression Editor.
  2. Select the entity from the Context drop-down box.
  3. Click Save.

Expressions are listed by Code and Short Description in the Context text box.

Evaluating the Expression

Like the Expression Selector, the Shared Expression Editor has Evaluation functionality.
To verify your expression:

  1. Enter your expression in the Shared Expression text box.
  2. If any parameters appear on the Editor, enter values in the Parameters text boxes.
  3. Click the Execute button.
  4. One of the following occurs:
  5. If the expression is valid, the results are displayed in the Result text box.
  6. If the expression is not valid, an error message is displayed in the Result text box.
  7. Click Save to save the expression.

Convert Null Parameters to Default Values

Select this option to convert the Null parameters in the database to default values. This option is selected by default. It is used to facilitate the computation. However, for some expressions, it is better to disable this option. You can test the expression using the Evaluate feature and view the difference between enabling and disabling this option.

Adding the Expression to a GNA Form

Prerequisites

  • The expression must be created in the Shared Expression Editor.
    After creating the expression, you need to close GNA.

 

Adding the Shared Expression to an Administration FormYou can add the same shared expression to multiple forms in GNA, as well as user forms.For example, you may want to make multiple Mass Appraisal codes required when the Total Value of the property exceeds $1,000,000.00.
To add a shared expression to an administrative form in GNA.

  1. Launch GNA.
  2. Open the first form to which you want to add the expression.
    For example, open the Mass Appraisal Income Overall Adjustments table.
    Mass Appraisal > Table Maintenance > Single Entry Tables > inc – Income Adjustment
  3. Click the ellipsis button beside the Is Required field.
  4. This opens the Expression Selector.
  5. Select the Shared Expression from the Expression drop-down list.
  6. The expression is not displayed in the Expression Editor and it cannot be evaluated.
  7. Click OK.

Adding a Shared Expression to a Govern Form

You can add a Shared Expression to a Govern user form in the OpenForms Designer. For example, you may want to use the expression that you added to several MA Income tables to enable the Rent Summary group box on the CAMA Income form for buildings with a total value exceeding $1,000,000.00.
To add a Shared Expression to a Govern form:

  1. Launch the Govern OFD.
  2. Open the required form.
    For example, open the CAMA Income Information form.
  3. Select a groupbox or add a label to create an expression.
    For example, select the Rent Summary groupbox.
  4. Click the ellipsis button beside a parameter.
    For example, click the ellipsis button beside the Is Enabled parameter.
    This opens the Expression Selector.
  5. Select the shared expression from the Expression drop-down list.
  6. The expression does not appear in the Expression Editor.
  7. Click OK. on the Expression Selector.
  8. Click Save on the OpenForms Designer.

See Also

Related Information

 

 

103-ED-018

 

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...

 

303-apex

APEX

Overview

303-(uiTN)-ApexMobile.png
Click to enlarge the APEX mobile

Apex Software Licenses

A license is required for installing Apex in an organization.
Please contact your system administrator or Harris Govern sales department for more information.

For Harris Govern Employees, click here to access the Govern R&D Apex Licensing information and download trial version.

 

303-apex

 

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...

 

Quick Search Index Group Editor

Quick Search Index Group Editor

Available in release 6.0.1804 and 6.1.1804

Overview

The Quick Search Index Group Editor will enable users to create groups of indexes that can be used with a Profile, or be made available as a Quick Search Definition in custom controls like generic links. When configuring, i.e. grouping the indexes that are required by users, a “boost” value can be specified for the indexes within a group. The boost value helps to control how the index search results are presented.

Configuration – Quick Search Index Group Editor

In order to create the required table and fields required, users must run the GNA Verify Database process. No additional configuration is required.

Read More...

Provide Access to the Quick Search Index Group Editor

Administrators that need to provide or restrict user access to the Quick Search Index Group Editor, can do so through the Govern Security Manager (GSM). In the GSM, under the left hand pane, locate the Quick Search Index Group Editor node. Refer to the GSM user guide for details about securing nodes.

Using the Quick Search Index Group Editor

In order to access to the Quick Search Index group Editor, in the GNA ribbon…

  1. Select Editors (tab) > Editors (group) > Dynamic Search Configuration > Quick Search Index Group Editor.

Creating a new Quick Search Index Group

When there are no existing search groups, opening the editor will, by default, create a blank form that is ready to be configured. To create a new group, click Create a new item. Parameters for new groups are validated; a code is required and the group must contain at least one index.
All available indexes will be displayed in the Available Indexes pane. Administrators will need to select the checkboxes beside the indexes that they want to include in the group.

Quick Search Index Group – Boost Factor

Upon selecting an index, the user will also be allowed to specify a “boost” value for the index. By default, the index will be assigned a boost factor value of 1. The boost factor influences how results from this index will appear in the Quick Search tab in Govern.
Search results from indexes with higher boost factors will be displayed before search results from indexes with lower boost factors. However, if the searched text string in index is a perfect match, and a partial match in index (B) search results from an index (A) with a lower boost factor may appear above another index (B) with a higher boost factor

Changing the Order of indexes within a group

Selected indexes can be re-positioned with a drag and drop action. The sequence number is displayed at the left of the index. The sequence number corresponds with the order it will appear in the Govern Quick Search pane. Click on the index text, and drag to the space between the indexes.

NOTE: Only selected indexes can be re-ordered.

Documentation

Click to here to the documentation for the Govern Quick Search for details.

Related Topics

Govern Search
Govern Quick Search
Quick Search Index Group Editor
Govern Search Technical Specifications

Saved Datasets
Dynamic Search Objects
Dynamic Search Styles
Dynamic Search Groups
Govern New Administration (GNA)

 

 

103-ED-022

 

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...

304-melissa

Melissa

Overview

Optional System Integration
Instantly Verify and Correct Address Data at Point of Entry! “Industry experts estimate that up to 60 percent of a company’s database is bad; resulting in duplicate records, returned mail, address correction fees, lost opportunities, and dissatisfied customers.” – For more information visit Melissa’s web site www.melissadata.com.

MelissaData MS Govern’s embedded Melissa Data Package enables address verification completely integrated with the Name and Address and Property Location Maintenance functions within the Govern Property Information module. The Melissa Object ensures that a valid address is being recorded, and it will reduce the cost of bulk mailings by generating the ZIP+4 code.

For more information, please contact R&D.

Batch Processes (undocumented)

Documentation

10.8 Melissa Manual in PDF

 

 

304-melissa

 

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...

User Validation Tables Specifications

User Validation Tables Specifications

Version 6.1 | Version 6.0

Overview

Maintain the User Validation Tables in this form. These tables are used to validate the information entered in the various fields. Create and maintain the elements of the tables on the Validation Codes form.

Specifications for Creating Reports

The following lists are useful in report parameters:

Read More...

VT User Table Type

Table Type: The Table Type is system-generated and is used to identify the type of tables as follows:

  • Regular = 0
  • AccountsReceivables = 1
  • MassAppraisal = 2
  • Permits = 3
  • PropertyControl = 4
  • TaxBilling = 5
  • UtilityBilling = 6

Legacy Table Type Codes

  • R: Regular
  • A: Accounts / Receivable
  • C: Property Control
  • B: Property Control (for the Property Area function) – no longer exits?
  • M: Mass Appraisal
  • P: Permits and Inspections
  • S: Super User
  • T: Tax: Aircraft, Boat, Motor Vehicle, Personal Property and Real Property
  • U: Utility Billing

 

 

103-ED-010-spec

 

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...