100-bp-Execution

Standard Batch Process – Execution & Connection

Version 6.0 and Version 6.1 (In Development)

Overview

The following explains the type and mode of batch executions.

Transaction Type

A Govern batch process can run synchronously or asynchronously.

Synch

In synchronous batch processing, transactions are processed one after another in a sequence.
If there are multiple steps in the process, one step is completed before the next begins.

Asynch

In asynchronous processing, multiple operations are started and run at the same time. As soon as one finishes, the next begins.
Multiple steps can run at the same time; for example, steps one, two, three, and four can all begin at the same time.
For long batch processes, using asynchronous batch processing can speed up the transaction time, because multiple computer operations or threads are processed at the same time compared to synchronous batch processing, where one operation has to finish before the next can begin.

IMPORTANT: If a batch process has multiple steps that need to be performed in order; for example, if the results of the first step are required for a calculation in the second step, use synchronous batch processing.

 

Connection Pool

You can define a Maximum Connection Pool Size for asynchronous batch processing in the addition to the general Connection Pool Size. You can also set a Connection time out for batch processes.
These parameters are defined on the Connection Key General Parameters Management form in GNA.

The Connection Pool is the number of connections that can be open on the server at the same time. Connections are required for the asynchronous batch processes. They are used by the threads to perform operations for batch processing. They are also required for all other Govern operations from all deployments in your organization.

The Connection Time Out refers to the length of time that a batch process executes a query before a time out occurs. The default is zero (0). This means that there is no time out.

Transaction Mode

Select one of the following transaction modes for the process.
Break If One Transaction Failed
The process terminates when the transaction fails.

Roll Back If One Transaction Failed
The process terminates when a transaction fails. All the transactions that were completed are cancelled. All the computations are returned to the starting point.

IMPORTANT: The roll back can take a long time to execute if the error occurred at the end of the process.

Continue If One Transaction Failed
The process continues to run even if a transaction fails.

 

 

100-bp-Execution

 

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

Standard Module (Features & Functions)

Govern Standard Module (Features and Functions)

Version 6.1 (Ongoing Development)

Overview

The standard (std) module consists of features, forms, form controls & action buttons, batch programs, etc. that are used throughout the system or that are shared by multiple application modules.
Features (fea) include:

  • (System) UI, Help, Navigation, Treeview, Datasets, External Commands, Cool Bars, Hibernate mode…
  • (Module) Central Notes, User Audit Trail, Global Messaging, Snapshots and Roll Forward of data…
  • (Form Controls) Record Descriptors, Browsing, Generic Links, Special Action Buttons …

Forms (frm) include:

  • Multimedia, Workflow, Activities, Web and Application browsers…

Batch Programs include:

  • Evaluate Expressions…

Click here for the * STANDARD MODULE FEATURE and FUNCTION LIST *

See Also

What’s New

6.1 brings lots of new standard features, see What’s New.

 

 

101-std

 

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

Save and Search Feature

Save and Search

Overview

This feature, when correctly configured, can be used to speed up data entry. By configuring an action button on an existing form. As soon as a Save is performed, the Save and Search feature will display a pop-up Search screen that will be ready to accept the next user entry.

NOTEThis “quick search action” is attached to the save completed event in the code. Whenever the user clicks Save, after the action is performed the Search is displayed again. This function allows the user to immediately begin their search for the next record instead of having to re-open the Dynamic Search panel.

 

NOTEAlthough some users refer to this feature as a “Quick Search”, it should in no way be confused with the Govern Quick Search feature [101-std-fea-004-quicksearch].

Setup

When setting up the action button in OpenForms Designer (OFD), the search style to use is specified.

NOTE: See the following product DEV documentation for configuration instructions.

101-st-fea-018-Self-Reported Tax Quick Search.pdf

 

 

101-std-fea-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...

Govern Advanced Search

Standard Feature – Advanced Search

Overview

The Advanced Search feature is designed to be a time saver when making multiple successive Self-Reported Business Tax filings. When enabled, Advanced Search will operate as follows. After the necessary entries are made, a click on Save will save the filing and launch the Search screen. When opened the screen will have auto-selected the first record found that matches the search criteria specified. If no record is found, the Advanced Search will stay open until a valid criteria is entered, or the screen is closed. Note that the Advanced Search is not to be confused with the Govern Quick Search.

Configuring Advanced Search

Refer to the following document to configure the Self-Reported Business Tax Quick Search.
101-all-SRT Advanced Search(extract)-(6.0).pdf

Viewing the Customization in GNA

In Govern the Advanced Search can be initiated for quick entry when multiple successive entries are required.

Related Topics

Govern Standard features.

 

 

101-std-fea-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...

Std. Feature – View Query

Standard Feature – View Query

Under development

Overview

This is a standard feature.

 

 

101-std-fea-025

 

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

Copy to Next Year Feature

Standard Feature – Copy to Next Year

Overview

The Copy to Next Year batch process is used to copy data from one year to the next. For example in the case of the Utility Billing (UB) module, the system will create the new Utility Billing Services and all related Codes from the current year displayed at the bottom of your screen to the year entered. Recent modifications expand the scope of the data that is copied from a source to a destination year.

Functionality

There are two (2) main modifications that have been made to the Copy to Year batch process. First for each Copy to Year Batch Process, the Govern system now copies the Constants, Shared Expressions, Queries, and the VT_USER from regular Workflows and Property Control. Secondly, in the Real Property Tax module; the Copy to Year functionality has been brought in line to match the same functionality that is found in the Mass Appraisal or Miscellaneous Billing, in order to be able to use the same batch process.
This batch process will duplicate data from the selected year to the target year, for the following tables:

  • All tables that are prefixed by TX_PARM_ and have the “YEAR_ID” column name
  • TX_MODIF_STAMP

In addition the process as of release 6.1.1803.0034 / 6.1.1804.0054, will copy data from the following…

  • (Table: VT_USER) of type Regular, Workflow and Property Control
  • (Table: USR_CONSTANT)
  • (Table: USR_QUERY)
  • (Table: USR_EXPRESSION)

User Interface

Selection Criteria group

From – Select the year that contains the data you want to copy in the From combo-box.
To – Enter the year to which you want to copy the data in the To text box.

NOTE: The To year must be greater than the From year.

Tables Not Related to Subsystems group

Delete destination data before copy – When the Delete destination data before the copy check box is selected, the batch will delete existing records for the target year. If this option is not selected, copied data will be appended to existing ones.

Deleting Data in the Destination Year

When selected, a confirmation window will be displayed, requesting whether you would like to delete the data in the destination year.

NOTE: Selecting Yes will not result in the immediate deletion of the destination year data. The data is only deleted upon initiation of the batch process.

Tax group

Delete destination data before copy – Select Delete destination data before the copy check box to delete existing records for the target year.

NOTE: This is a preexisting option; the functionality has not been modified.

Configuration

Govern New Administration (GNA)

In GNA this batch process is configured through the Batch Process Definition Editor form. Configuration parameters are standard for Govern batch processes.
For parameter details, refer to the Govern Batch Process Definition Editor documentation.

Documentation

103-tx-bp-105_Copy_Constant_to_Next_Year.pdf

 

 

101-std-fea-026

 

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