Text Style Editor

Text Style Editor

Version 6.1

Overview

Adding Text and Foreground / Background Styles to User Forms

Use the Text Style Editor in GNA to create styles for the text that appears on your forms as headings or labels, and to create foreground and background colors. These are applied to the elements on the user form in the OpenForms Designer (OFD). The following chart lists the elements and the corresponding styles they support:

TextStyleChart.png

Read More...

Documentation

To read or download this information as a pdf, cick on the following link:
101-std-fea-037-TestStyleEditor.pdf

 

Accessing the Text Style Editor

To access the Text Style Editor:

  1. Launch GNA.
  2. Select Editors > Text Style Editor.

The styles that are already created are listed in the tree view on the left.

Creating a New Text Style

To create a new Text Style:

  1. Click New on the Text Style Editor.
  2. Enter a unique code in the Code field.
    The Code is required in the expression that you use to apply the style.
  3. Enter short and long descriptions in the English and French Short and Long Description fields.
    The descriptions make it easier for users to search through existing styles.
  4. Select a font and font size from the Font drop-down lists.
  5. Select the Bold, Italic, Underline, or Strikethrough buttons to apply character styling.
  6. Select a color from the Foreground drop-down list.
    The foreground color is applied as follows.

    • Labels, Attributes: To the text in the label
    • Groupbox or Tab control: All the text, for example all the labels, within the groupbox, tab, or other item
  7. Select a color from the Background drop-down list.
    The background color is applied as follows.

    • Labels, Attributes: To the area behind the text.
    • Groupbox or Tab Control, Custom Controls: To the area within the item, excluding the attributes
      Note:Background color can be applied to attributes separately.
    • Rows, Columns, Grids, Tab Items, Custom Entities: No background color is applied to these items.
  8. Click Save.

Applying the Text Styles

To apply a Text Style, add an expression to the Text Property in the Open Forms Designer, as described in the following procedure.
To apply a Text Style:

  1. Launch the Govern OpenForms Designer (OFD).
  2. Open the applicable form.
  3. Select the entity.
  4. Select the item to which you want to apply the text style.
  5. Select the Text Style property in the Property Explorer on the right.
  6. Click the ellipsis button to open the Expression Selector.
  7. Enter the expression in the Expression text box.
    The simplest expression is the code for the text style within single quotation marks, such as ‘Header’ to apply the Text Style identified by the Code Header. You can make the expression more complex in order to apply a text style only under a certain condition.
    For example, you could highlight parameters that a user needs to update based on the current data input.
  8. Click OK on the Expression Selector.
  9. Click Save on the OFD form.

Scenario: Applying a Text Style to a Heading

You can apply a Text Style in order to create a Heading that stand out above a groupbox or gird.
To apply a text style to a heading:

  1. Launch the Govern OpenForms Designer (OFD).
  2. Open the form on which you want to add the heading.
  3. Select the entity.
  4. Select the Label in the Controls list box.
  5. Drag it above the groupbox or grid.
  6. Select the label.
  7. Enter a name for the label in the Text property.
  8. Select the Text Style property in the Property Explorer on the right.
  9. Click the ellipsis button to open the Expression Selector.
  10. Enter the code for the heading surrounded by single quotation marks, or apostrophes, as in the following example:
    BoldHeading
  11. Click OK on the Expression Selector.
  12. Click Save on the OFD form.

The same procedure can be used to add a text style to any item on the form.

Scenario: Applying a Text Style Based on a Condition

You can add a Text Style to any expression in order to apply a text style under a condition. For example, you could use a text style to highlight a group box that contains fields that need to be filled only under certain conditions.
In the following example, the Correlated Values group box is highlighted when the Correlated Values method is selected on the CAMA Property Information form.
To apply a text style under a condition:

  1. Launch the Govern OpenForms Designer (OFD).
  2. Open the form on which you want to add the heading.
  3. Select the entity.
  4. Select the Correlated Values groupbox.
  5. Select the Text Style property in the Property Explorer on the right.
  6. Click the ellipsis button to open the Expression Selector.
  7. Enter the following expression:
    If(@attrMETHOD_IN_USE=5, ‘YellowBack’, ‘’)’
  8. This expression is added to a Case statement.
    The code for the text style is enclosed in single quotation marks.
    It is applied if the Correlated Values method, Code 5, is selected.
  9. Click OK on the Expression Selector.
  10. Click Save on the OFD form.

Scenario: Applying Different Text Styles Under Different Conditions

This scenario is the same as the previous one, except that different text styles are applied according to the method selected.
The expression for this is as follows:

Case(True,@attrMETHOD_IN_USE=1,’BlueBackground’,@attrMETHOD_IN_USE=2,’RedBackground’,@attrMETHOD_IN_USE=3,’GreenBackground’)

This expression applies the following backgrounds, or highlights, to items in a groupbox according to the method selected:

  • Appraisal Cost: Blue Background
  • Comparable Sales: Red Background
  • Income DIR: Green Background

What’s New

In the OpenForms Designer (OFD), you can work in Preview Mode to see how styles are applied on the user form, as you work.

 

 

101-std-fea-037

 

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

 

Govern System Dictionary (SY_DICT_DESC)

System Dictionary (SY_DICT_DESC)

Version 6.0

Overview

The system dictionary tables (Table: SY_DICT_XXXX), have historically been used to manage and maintain form descriptions in the Govern database.
There are four SY_DICT_XXXX tables in the Govern database. They are as follows:

  • SY_DICT_DATANAMES – Legacy table from Govern for Windows; this table is still maintained during Verify DB process to keep track of structure and for indexing. (May be dropped in OpenForms Release 6.1)
  • SY_DICT_DESC – Active table that is used to maintain descriptions. Refer to process to generate missing dictionary entries.
  • SY_DICT_TABLES – Legacy table from Govern for Windows; this table is still maintained during Verify DB process to keep track of structure and for indexing. (May be dropped in OpenForms Release 6.1)
  • SY_DICT_VIEW – Legacy table from Govern for Windows; table is still maintained during Verify DB process to keep track of structure and for indexing. (May be dropped in OpenForms Release 6.1)

Of the four (4) databases, there is only one table that is relevant to OpenForms, (Table: SY_DICT_DESC). The three remaining tables are only relevant to Govern for Windows, and may be, at some point eliminated in later version 6.1 releases.

Maintenance Process

As indicated above, in OpenForms, the SY_DICT_DESC table is used to manage and maintain form descriptions through the Verify Database process in the Govern New Administrator (GNA).

Verify Database

The following is a description of the DB Verification actions that directly impact the collection of SY_DICT_XXXX tables. The action is used to generate Missing Dictionary Entries. This is an explanation of the process.
During the Check Column process, Govern manages the description of the fields in the SY_DICT_DESC Table.

  1. The Database Verification file, MSGDatabaseStructMods.xml is read.
  2. The content of the SY_DICT_DESC table is read, the columns of each table are reviewed, and the SY_DICT_DESC.DESCRIPTION (ENG / FRA) is verified as to whether it exists.
  3. If an entry does not exist, it will need to be created, i.e. (ADD), or removed (DROP); in cases when a complete removal of a table is required, any description that is connected to it is also removed.

Only the following columns in (Table: SY_DICT_DESC) are updated:

  • LANGUAGE
  • TABLE_NAME
  • FIELD_NAME
  • DESCRIPTION – There is a 50 character limitation, i.e. all characters after the 50th are truncated.
  • DETAIL – Uses the ‘DESCRIPTION’ property.

Generate Missing Dictionary Entries

Select this option to update the dictionary. This populates (Table: SY_DICT_DESC) with data from the user validation tables; i.e., the tables beginning with VT_USR.

Recommended Use

This process should be run under the following conditions:

  • When configuring the system for the first time
  • After updating the database
  • Anytime that data is missing from user forms.

Modification of process starting from the following release:

  • 6.0.1603.0410 / 6.0.1606.0010 / 6.0.1608.0006
  • 6.1.1603.0481 / 6.1.1606.0021 / 6.1.1608.0016

Custom Entities

Users that create their own custom entities should note that the Verify Database process will not overwrite their descriptions. If there are two entities with the same table/column, the SY_DICT_DESC.DESCRIPTION will be taken from the last label entered. As long as modifications are only made to the custom entities that were created there will be no issues will descriptions being overwritten.

 

 

101-std-fea-038

 

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

101-std-fea-042-ofr

Standard Feature – Form Action Button User Registry
Standard Features Overview, What’s New, wiki Map (Last Update 2016-01-06)

Overview

The following is a standard form action button that can be setup so that users can change USER REGISTRY parameters

Configuration

Action Button = UsrREGISTRYAction

irst you need to add the custom control object by dragging the control to the form (root entity) then click on the custom control object on the form to set the properties.

Element Property Setup
Misc. Action UserRegistry_Action
Name n/a – Maintain by System
Icon Select the icon to be displayed on the form header or leave blank to select the standard icon
Is enabled Standard OpenForms option to enabled the action button only on specific conditions.
Name Maintain by System
Properties
Misc. User Registry Select the User Registry Parameters that should be displayed

  • All
  • Cash Collection
  • Cash Collection Cashier
  • Lockbox
  • mGovern
  • Matix
  • OpenForms
  • Workflow Management
Tooltip Enter the tooltip that will be displayed on Mouse Over of the button
Misc En Enter the name that will be displayed for (to be verified if used)
Internal Element Instructions
Not applicable

101-std-fea-042

101-std-fea-042 #stdfea #std

Standard Feature Form Action Button – User Registry
Standard Features Overview, What’s New, wiki Map … Last Updated February 21st, 2017
Version 6.0 / 6.1

Overview

The following is a standard form action button that can be setup on most forms to allow users to change user registry parameters directly without leaving the form.
Currently applicable to:

  • All
  • Cash Collection
  • Cash Collection Cashiers
  • Lockbox
  • mGovern (Mobile)
  • Matix (GIS)
  • OpenForms
  • Workflow Management

To configure the action button on a form, click here.

See Also

System Registry Parameters
User Registry Parameters
Configuring the Action Button Control

Workload Manager Feature

Workload Manager

Version 6.1

Workload Management Overview

The Workload Manager Standard Module Feature is designed to track activities regarding the Building, Health, Code Enforcement, Planning and Zoning departments’ application as well as the issuance of permits within the organization. This system also allows for an unlimited number of departments to track activities relevant to a parcel of land or the property records. For different Kinds and Categories of workflow, you are able to define all required steps to complete the process. You can define activities that can query other databases in order to apply business rules, and schedule automatic inspections.

Table-driven, user-definable, the system provides for and improves communication and coordination within and between departments. All new construction, variances or zoning changes that have taken place on properties are stored in the system. A flexible database structure allows for the recording and retrieval of various land-related data that can differ for each type of permit or decision. Applications for permits and inspections for buildings, including review of the electrical or the plumbing system can be entered into the system.
Once the information is entered, the system will aid in the investigation or the issuance of a permit or any other activity for a particular property or name.

Documentation

Govern OpenForms v6.1

Click here to read the interim user guide. Note that this document is still in development.

Govern for Windows 10.8

Related Topics

Email Notifications in Govern OpenForms

 

 

101-std-fea-019-Workload Manager

 

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

 

External Command Feature

 External Command Feature

Overview

External commands can be added the Govern Ribbon or to a user form. They are used for opening an external application from Govern to a specific location. Specific information is dent directly from Govern to the external application.
Some examples of how external commands are used include the following:

  • Opening Google Maps to a specific address from the Govern Ribbon in the Property Control Profile.
  • Opening a Real Estate application to a specific address from the Sales Information form in Govern.
  • Sending an e-mail to a property owner directly from the Tax Billing form in Govern.
  • Opening a saved map in Google Drive to a specific location from the Govern Ribbon in the Appraisal Profile.

Launching an External Command

Launching an External Command from the Govern Ribbon

If an external command is added to the Govern Ribbon.

  1. Launch Govern.
  2. Select the Profile to which the command is added.
  3. Open the form that is associated with the command.
  4. Open the property record that is associated with the command.
  5. Select the Tools menu on the Govern Ribbon.
  6. Select the command in the External Commands section of the Tools menu.

Read More...

For example, if there was a command to open Google Maps to a specific location.

  1. Launch Govern.
  2. Select the property that you want to view in Google Maps, in the required form and Profile.
  3. Click the external command for Google Maps in the Ribbon.
  4. Google Maps open directly to that property.

Launching an External Command from a Govern User Form

If an external command is added to a user form:

  1. Launch Govern.
  2. Select the Profile to which the command is added.
  3. Open the form.
  4. Select the property.
  5. Click the hyperlink or action button for the command.

The external application opens to show the required information about the property. For example, if there was a command to open Google Maps to a specific location.

  1. Launch Govern.
  2. Select the required Profile, form, and property record.
  3. Click the link for the external command on the form.
  4. Google Maps open directly to that property.

 

101-std-fea-020

 

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

 

 

 

101-std-fea-004-ofr

101-std-fea-004-ofr #stdfea #std

Dynamic Searches – STANDARD OpenForms Reference
Govern Standard Module Overview, Configuration, OpenForms Reference, What’s New, wiki Module Map …. Last Modified Feb. 14th 2016

Table of Contents

Overview
Module Specific Dynamic Search Details
General A/R
Aircraft
Boat
Motor Vehicle
Real Property
Personal Property
Miscellaneous Billing
Utility Billing
Special Assessment
Complaints, Grievances, Request for Services …
Permit
AutoSave Treeview

VERSION 6.0 | VERSION 6.1

Overview

(Under construction)
The following dynamic searches are distributed.

  • Module Specific
  • Bar Code
  • Synchronized Treeview

Module Specific Dynamic Search Details

The following search fields are available – See what is available and what is roadmap

General A/R

  • Bar code or A/R ID
  • Bill Number
  • Invoice Number
  • Mortgage Company or Tax Service Orgaization (TSO)
  • Receipt No. (payment)

Aircraft

  • Aircraft Serial Number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Boat

  • Plate Number
  • Boat Serial Number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Motor Vehicle

  • Plate Number
  • Motor Vehicle Serial Number
  • Motor Vehicle ID (MV_ID)
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Real Property

  • Tax Map Number
  • Tax Bill

Personal Property

  • Tax Map Number
  • Account Number
  • Personal Property ID (PP_ID)
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Miscellaneous Billing

  • Account Number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Utility Billing

  • Tax Map Number
  • Account Number
  • Utility Billing ID (UB_ID)
  • Meter Serial Number
  • Route Number and Sequence
  • Name Status (Owner…)
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)

Special Assessment

  • Project Name
  • Project Code

Complaints, Grievances, Request for Services …

  • Enter the reference number
  • Search in application number, permit number, certificate number, alternate permit id and any of the above

Permit

  • Reference number
  • Department
  • Permit Kind
  • Permit Type
  • From and to Date
  • Tax Map number
  • Last or Company / First / Initial
  • Type of Name (Individual, Company or No Format)
  • Include Void Permit
  • Include Historical Permit
  • Include License to Name
  • Search in application number, permit number, certificate number, alternate permit id and any of the above

Note: Backward searches are deprecated

AutoSave Treeview

Synchronized Treeview search

  • Select NAME SEARCH Autosave to access by the content of the Treeview
  • Note: Synchronize must be set to on
  • See Roadmap

Overview | Module Specific Dynamic Search Details | AutoSave Treeview