Std. Feature – View Query Link

Standard Feature – View Query Link

Overview

Query Links are a powerful feature in Govern for OpenForms. This feature allows the addition of a link in a custom control that will open another form or report. In addition, with this feature users are able to set and pass a Govern ID before opening a report or OpenForm. There are a few ways that this feature is implemented in the Govern for OpenForms application.

View Query Link

Why a View Query Link

The main purpose if this implementation is to have an account set up with a principal record, and all satellite offices associated with that record were to then be presented in a grid. When this ACCOUNT that is based on a name ID, is retrieved, if the current ID is set to NA_ID1, then a click on a link could be made to open the name and address of its satellite offices, NA_ID2, NA_ID3, and so on. Previously this link could be performed to another OpenForm, but it was not possible to change the active Name ID (NA_ID) on the linked form. One previous workaround was to take the ID of the current form, go to the configuration of the form and set the NA_ID as an ID setter, as this was not always desirable, often a button was used to control whether the ID would be set. With the View Query Link feature, a more streamlined solution is obtained. When this feature is configured, there are multiple methods of implementing it.

NOTE: The end results are similar, but the methods of implementation differ.

BUSINESS RULES:

If the profile is parcel based, and you search for a P_ID that exists in the profile, a reposition will occur, i.e. the focus will be on the new parcel which will be set as active.
If the P_ID that is being searched for is not in the profile, that record containing the P_ID will be added to the Treeview, i.e. populate the Treeview.
If it’s not the same ID, ex. Only a Name ID, the ID will be set, but nothing will be appended to the Treeview.

View Query Link – Type 1

What are referred to as Type 1 View Query Links are the basic implementation of the View Query Link feature. The link is presented as a hyperlink or a button that will initiate the link. To demonstrate this feature, we will add a link to the Coordinate parameters on the parcel information OpenForms.

Configuration

When a link is placed in the Coordinates group. This link will be set with different properties. As is allowed in the OpenForms Designer (OFD), the link can be initiated as a Hyperlink, or an Action Button.

View Query Link – Type 2

A second implementation is used within the Self Reported Tax Estimate form. A link is created within a View Query. When this link is selected, it will launch the SRT Form on the Tax Filing entity for the specified period.

Configuration

Using the ST Estimate feature as an example, a link to the ST account entity will need to be created. The required configurations are made in the Govern New Administration (GNA) and the OpenForms Designer (OFD). In addition a standard view query will need to be modified through the GNA.

View Query Link – Type 3

The third implementation the View Query Link yields the same link results as the Type 1 and Type 2 implementation, i.e. for SRT, it will launch the Form on the Tax Filing entity for the specified period. Links are created under the Govern Home tab in the Dashboard area.

Configuration

The setup of this View Query Link type is made in the Profile Editor of the Govern New Administration
Examples of the use of the three types of view query links can be observed in the attached documentation.

Importance of Syntax

Modifying the Query

To modify the query, we will use the SQL Query editor in the GNA. The following queries are to be modified for this example:

smPC07 – Current Owner Names & Address
smPC08 – Previous Owner Names & Address

Before we can modify the column we need to change to a link, we need to add another column.

On the GNA Ribbon, go to GNA > Editors (tab) > Select Query Editor.
Look for the smPC07 query; click to select this query for editing.
In the editor we will add another column BEFORE the column that is to be changed to a link.

‘Form=NA01;NA_ID’ + CAST(NA_ID AS VARCHAR) ‘<LINK>’

Proper use of the <LINK> tag

When the ‘<LINK>’ tag is seen before the column, this is an indication that the column is to be hidden and the link information is to be applied to the next column.
DEVNOTE: The Same column can be added twice if single quotes ‘aLink’ are used; there is a restriction if double quotes “” are used.

NEW Select a specific Entity on the form

An enhancement has added to the View Query Link functionality. It is now possible to open a form and re-position to a specific entity within the form. The ID can then be auto-selected by setting the Govern ID.
To access a specific form and tab item, use the following syntax for the query…
‘Form=FormNum:EntityName;NA_ID=’
…where <FormNum> is the Govern form number, e.g. ST007 immediately followed by a colon “:”, then the <EntityName>, e.g. ST-Filing. There are no spaces between any of the names. Here is an example that will access the Self Reported Tax form (ST007), and specifically target the ST-Filing entity. The Govern ID is then specified, in the following case, an NA_ID
‘Form=ST007:ST_Filing;NA_ID=’

NOTE: If the entity specified in the query is not available, the result will default back to the top level form.

Key Parts of the Modification to the Query

The modifications needed for the query are made up of three (3) parts.

The column must be named as follows: ‘<LINK>’
Indicate what the column is to return NA_ID’ + CAST(NA_ID AS VARCHAR)
The form that is to be opened. ‘Form=NA01;NA_ID’
i.e. the form NA01 is to be set with the NA_ID. Alternatively, the syntax can also be modified to open a report by referencing the report name: ‘Report=NA01;NA_ID’

NOTE: The order of the information is important. The column that will have the link will always be on the next column.

Error Handling Messages:

DEVNOTE: If a code is entered for a non-existent form, an error message is invoked: This form is not accessible, review with your administrator.

If the configuration was performed correctly, the P_ID will be changed. Incorrect configurations can result in errors. Often the error that is encountered is related to syntax. For example an error screen such as the following may be displayed.
In the following, the “=” was missing from the p_id portion of the query.
‘p_id’+ @attrX + ‘;na_id=’ + @attrY (ERROR)
‘p_id=’+ @attrX + ‘;na_id=’ + @attrY (OK)

Documentation

Below is the documentation related to this feature:

101-std-fea-036-View_Query_Link.pdf

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.

The Database Verification file, MSGDatabaseStructMods.xml is read.
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.
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 5)
You need to be a registered member to rate this.

User Key Dynamic

Version 6.0

Overview

This standard technology is a control that is used to generate unique keys in Govern.

Functionalities

Workflow Management

Like user key master, a workflow needs to generate ID’s for Application, Number and Certificates when creating workflows.
Unlike user key Master, though, the fields representing those keys are generated dynamically and are strings, not numerical values.
For the workflow. it creates unique keys for Application, Number and Certificates.

Generates 3 keys in USR_KEY_DYNAMIC table with the following key format: <key type>[<type>:<code>]

<key type> are APPLICATION, NUMBER and CERTIFICATE
<type> are KIND, CATEGORY, etc. Departments and Types will have their own <type> as well.
<code> is the record code like the kind and category code.

Govern eSearches Technical Specifications

Overview

The following is intended for Business Analyst, System Administrators or a technical audience.

Govern IDs

In almost all instances, the navigation from a form to another form relies on the Govern IDs that are displayed in the Govern ID panel.
The list of Govern IDs available can be found in the System Validation Table:
The current Govern ID’s that are available in the system can be identified with a SELECT query of the Govern Database. The result of the following query will be a list of the current Govern ID’s; they are listed under the CODE column.

SELECT * FROM VT_SYSTEM WHERE TABLE_NAME = ‘BRULE’;

Code	Short Description	Long Description
*date	* Current date	* Current Date
*datetime	* Date/Time	Current Day Date/Time
*time	* Current Time	Current Time
ac_id	Political Unit No	Political Unit No.
ar_detail_id	Acnt Rec. Detail ID	Account Receivable Detail ID
ar_id	Account Receivable ID	Account Receivable ID
bldg_id	Building ID	Building ID
bldg_seq	Building Sequence	Building Sequence
br_id	Bankruptcy ID	Bankruptcy ID
bt_id	Boat id	Boat ID
cc_id	Cash Collection ID	Cash Collection ID
dc_id	Delinquency ID	Delinquency ID
dept	Department	Department
exempt_id	Exemption ID	Exemption ID
folio_id	Project Folio ID	Project Folio ID
frozen_id	frozen ID	Frozen ID
haz_id	Hazard ID	Hazard ID
in_id	Inspection ID	Inspection ID
inc_id	Income ID	Income ID
jurisdic_code	Jurisdiction Code	Jurisdiction Code
key_counter	Activity ID	Activity ID
key_id	PM Key ID	Permit Key ID
key_id_2	Sec Key ID	Permit Key ID 2
keytype	PM Key Type	PM Key Type
land_id	Land ID	Land ID
language	Language	Language
levy_id	Levy ID	Levy ID
link_id	Link ID	Link ID
ma_audit_id	Appraisal Audit ID	Appraisal Audit ID
mb_id	Misc. Billing ID	Miscellaneous Billing ID
misc_id	Miscellaneous ID	Miscellaneous ID
mra_id	MRA ID	MRA ID
mv_id	Motor Vehicle ID	Motor Vehicle ID
na_id	Name ID	Name ID
org_nbr	Organization Number	Organization Number
p_id	Parcel ID	Parcel ID
parmyear_id	Param. Year ID	Parameter Year ID
pp_det_id	PP Detail ID	Personal Property (PP) Detail ID
pp_id	Personal Property ID	Personal Property ID
prj_id	Project ID	Project ID
sa_id	Special Assessment ID	Special Assessment ID
sale_id	Sale ID	Sale ID
st_acct_id	Self Reported Tax Acct ID	Self-Reported Business Tax Account ID
st_id	Self Reported Tax ID	Self-Reported Business Tax ID
tax_id	Real Estate ID	Real Estate ID
tax_map	Tax Map No	Tax Map Number
tx_audit_id	Tax Audit ID	Tax Audit ID
u_id	User Key ID	User Key ID
ub_id	Utility Billing ID	Utility Billing ID
usr_id	User ID	User ID
year_id	Year ID	Year ID
site_no	Site Number	Site Number
d_id	Department id	Department ID
plan_id	Payment Plan ID	Payment Plan ID
batch_id	batch id	Batch ID
mb_inv_id	Misc. Billing Invoice ID	Misc Billing Invoice ID
tif_id	TIF ID	TIF ID
wm_id	Workflow ID	Workflow ID

* Codes are listed in the table but are not Govern ID’s.

Profile Govern IDs

Profiles can be set by parcel (p_id) or by (name_id) but modifications are required.
Although the setup allows for any Govern ID, for Accounts Receivable base profiles, the use of the Name ID (name_id_) is suggested.

Main ID

The search query must return the records where the Govern ID is the first column returned in the list.
For instance, a form in a parcel base profile will expect to have the p_id as the first column in the record.

Other IDs

Profiles that have forms with other Govern IDs, it is mandatory that the ID be returned with the same name as one of the columns of the list, e.g. (P_ID, NAME_ID, AR_ID, and so on…)

Standard Searches (Tree view)

A/R Inquiry

The AR Inquiry Custom Control is used to display, create and maintain all transactions linked to an Account Receivable.

Default Search Group

In the OFD, use the Default Search Group property to select the search group that is used by default in the A/R Inquiry Search.

Default Name Search Group

Use the Default Name Search Group property in the OFD to select the search group that is used by default for selecting the Payor Name in A/R Inquiry transactions.

Default Account Search Group For Payment Transfers

The Default Account Search Group For Payment Transfers property in the OFD is used to select the search group that will be used by default for selecting Accounts in the A/R Inquiry Payment Transfers.

Cash Collection

The cash collection is a stand-alone search (Quick Search) where the Search Group is setup in the form OFD. It does not use the current a/r id or parcel or name from previously loaded entry in the Tree view.
The Cash Collection form is used to create transactions such as payments, deposits, post dated payments and voluntary payments. This form displays only non posted transactions. Prior to creating a transaction users will need to select an existing, or create a new, deposit in under the Deposit Management tab. A search us used to retrieve the A/R Accounts that the transaction will be effected upon.

Validation

Users cannot select a Deposit Transaction Type for a Self Reported Tax Account without providing a Period (ST_ID).

Business Tax

The standard Business Tax ….
The query must return the st_id, the cat_id and the name_id (to be verified)

Corporate Account

The Corporate Account is a “parent” ST account that can be linked to multiple “child” ST accounts. The information set in the Corporate Account is used to create the child ST account(s). The main account is the parent company. The Corporate Account uses the generic link control by Name.
When generating a new record, the name ID is required; the user is required to do the following:

Create a new name
Search for an existing name
Select the current name from the tree view (this option is only available when names are loaded in the tree view)

Workflow Management

The standard searches are available for profiles by PID and NAID.
The query must return the wm_id.

Workflow Fees – Land Management

When not by Year, the A/R goes to the Applicant or Owner.
If by Year, does the A/R go to the Department Year OR the user added Year ???

Workflow Fees – Real Property by Year

(Linked to Name ID) NA_ID = Not Mandatory, P_ID = Yes, Year_ID = Yes, WM_ID = Yes

Workflow Fees – Sub-systems SETUP not by year

Only Name ID needed. (WM_ID = Yes, NA_ID = AR_ID, etc.)

Standard Searches (Stand-alone)

Cash Collection

The cash collection search is a stand-alone search…. and is setup in the form.
The standard Cash Collection search can return anything .. (to be verified)

The controller that loads the search result entries into the Payment Data Entry Grid is as follows:
– to be verified

It does not set the Govern ID’s as current ….

eSearch and Space Characters

The eSearch search parameter will treat space characters in a specific manner. It will apply special rules to the entered strings when space characters are entered by the user. This can be seen when users are entering parcel IDs, telephone numbers, or zip codes. If the system was to parse a blank space character as a search entry, the result may not be predictable. In order to ensure that results are predictable, the wild card ‘LIKE’ operator is used for the search.

After the user enters characters into the eSearch parameter, the system will use specific rules. When a space character is encountered, it is replaced with a Wildcard character ‘%’, i.e. percentage sign.

For Example, the following string is entered with blank spaces.
“1- 1- 1” will be parsed by the system as “% 1-% 1-% 1”

When there are one or more space characters, the system replaces the blanks with ‘%’. Our string of “1- 1- 1” will be replaced to convert our string to “% 1-% 1-% 1”. Effectively our search will be performed with the “LIKE” operator.
There are two (2) ways to represent field masks, as a single box, or as a multi-box. Options are selected in the Govern New Administration (GNA) when creating the masks. Single box masks place all characters in a single text box while a multi-box masks will divide the contents of the mask to build a textbox for mask characters, and labels for non-mask characters. When a user enters Masked Text Boxes in the context of the eSearch, the parameters will be parsed in the same manner described above.

System Architecture (Dataset Treeview)

[In Development]

Overview

The following table describes the rules that the Dataset Treeview is adheres to. For flexibility, Views (queries) are used to define the content to be displayed. To improve the user experience, a Standard Iconology provides visual information to identify the type and status of records listed in the treeview.

Database Views

Naming Standard
	V_TREEVIEW_(name)	Standard system Govern views that are distributed.
	VW_TREEVIEW_(name)	Custom views to include in the list of Treeview that can be selected for a profile
Database
	Security Access	No special security required for the view

SQL View Syntax
	Primary Govern ID	LINE 1 The first field matching a Governs ID name must match the Profile Dataset Type (brule)
	Secondary Govern ID	LINE 1 Sequential, i.e. Line 1, Line 2, and so on…
	Information Displayed	LINE 1 The attributes and their order to be displayed are defined in. Formatting is made in the SQL query view…
	Mouse-Over (Tool Tip)	LINE 1 to Line X (Need to verify) Each line will be displayed on the mouse-over
	Sort Order	Primary Sort Not relevant…
		–
Security
	Database Access	Set up in Profile Editor
Setup
	Profile Editor	For each profile, a treeview is selected that matches the correct dataset type access

Supported Views

Standard Views
	For name dataset profiles (NA_ID)	The following views are supported: V_TREEVIEW_ADDRESS (Name and Address) V_TREEVIEW_BTAX (Name and Business Tax Info) V_TREEVIEW_PP (Name and Personal Property Tax Info) V_TREEVIEW_MB (Name and Misc. Billing Info)
	For parcel dataset profiles (P_ID)	The following views are supported: V_TREEVIEW_LOCATION (Property Location) V_TREEVIEW_PARCEL_INFO (Property General Info)
	For A/R dataset profiles (NA_ID)	For Accounts Receivable Profiles (NA_ID)

Distribution Methods (Govern Techno)

Views are created, updated, included in …

SYSTEM	AREA	ITEM	DESCRIPTION
Database Verification
	Create	The standard views are created automatically on a Database Verification execution when the view does not exists
	Update	The standard views are replaced when there is a deletion. They are recreated;
	Verify	The standard views are executed for errors … errors are thrown
EMT (Import / Export)
	Exported	When a profile is exported Views are also transferred
	Imported	No Views are imported
Database Extraction
	Extracted with	The standard/custom views in use for all Views and Functions and are extracted and copied.	>00b050

Mobile
	Copied	Standard and Custom views are copied.

Standard Iconography

SYSTEM	AREA	ITEM	DESCRIPTION
Standard Icons
	Govern IDs	Profile Dataset Govern ID Icons that are displayed in front of each record when by: Parcels = HOUSE icon (p_id) Names = PERSON icon (na_id)ALL OTHER ITEMS Accounts = FOLDER icon (ST_ID, PP_ID, MB_ID, UB_ID, RE_ID…) None or Undefined = Govern ID only Edit mode turned on = Padlock icon
	Record Selected	Regular – These use the same icons as the selected identifier
		When Edit Mode The Lock icon is displayed when Edit Mode is Activated. On selecting a record, the EDIT icon is displayed and must be pressed to access record in modification mode
	Inactive Records	Same Govern ID icon but greyed out

Dynamic Search (eSearch), Saved Datasets and Treeview

The Dynamic Search (AKA e-search) and saved dataset search is highly integrated with the treeview. Users can use the results of searches to append to, or remove records from the treeview.

Dynamic Queries

ACTION	CONDITION	EXPECTED RESULTS
Send to the Treeview	From Dynamic Queries	The result of a search 101-std-fea-004


On Append		Records are added to the treeview


On Deselect and Load		Not Applicable (N/A)



On Add and reposition		Custom Control action – Determine Custom Control

Saved Datasets

ACTION	CONDITION	EXPECTED RESULTS
Get Records
	From Saved Dataset	The content of a saved dataset101-std-fea-006
	From Action Button Send to Treeview	If the action button sent to the treeview is used (available in the following standard forms: Split Merge, Parcel Linking, Name Linking

Other Treeview Integration

The treeview can be populated from the Dynamic Search Queries (e-search), from the Query Tool, from a Saved Dataset or from special Action Button Controllers (Send to Treeview). Optionally, if they are setup to this effect, the treeview can be populated by the results of the Matix GIS search, the Web Browser and the Application Browser forms.

ACTION	CONDITION	EXPECTED RESULTS
Get Records
	From Action Button Send to Treeview	If the action button send to treeview is used (available in the following standard forms: Split Merge, Parcel Linking, Name Linking
	From GIS Matix Search	101-std-frm-008 Manual Mode Automatic Mode
	From Web Browser Form	101-std-frm-003 Manual Mode Automatic Mode
	From Application Browser From	101-std-frm-005 Manual Mode Automatic Mode
	From Query Tool	Manual refresh to be performed by user. ()
Selected Record
	Default	First record is selected
	User clicks on a record	Record is selected
On Select
	Refresh Govern IDs	Main Govern IDs Secondary Govern IDS First Record is Selected
	Refresh Forms

Treeview User Interaction

The users can perform the following Treeview Actions

ACTION	CONDITION	EXPECTED RESULTS
On Mouse Over
	Tool Tip	Line 2 to x is displayed as a Tool Tip
On Select
	User clicks on a record	The Govern IDs are refreshed The icon changes The forms are refreshed with the selected record Govern ID
On Remove
	X	The user can remove records from the Treeview
On Move
	Previous F6	Go Up
	Next F7	Go Down
On Expand
	Form Expand Icon	The Forms are displayed below the treeview entry. The same forms as the Forms Explorer are displayed. Displays the forms that the user/role has access to in GSM
	Double Click
On Collapse
	Form Expand Icon	The Forms are no longer displayed
	Double Click

Inactive Business Rules

The users can perform the following Treeview Actions

ACTION	CONDITION	EXPECTED RESULTS
Parcel
	Inactive and Effective year
	Effective date
Name

Buildings
	Effective and Inactive date
Links
	Effective and Inactive date
Accounts

Jurisdictions
	TFS13225
Mobile
	Checkout	Bypass Checkout

Special Features

The users can perform the following actions:

NOTE: The following actions are the same as on load.

ACTION	CONDITION	EXPECTED RESULTS
Auto Synch


Form Refresh
	Govern F5	Used to update the treeview If profile view is changed If form is added If date is changed
Hibernate

101-std-fea-005-Treeview_Architecture

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

Standard Feature – Saved Datasets

Saved Datasets

Overview

Govern Saved DatasetsThe Govern Saved Dataset pane is standard in release 6.0 and higher. This pane will allow users to load, save, and delete saved datasets. All saved datasets for the current user, excluding datasets that are present prior to the hibernate process.
In addition, users are able to create new datasets from a search result, append to an existing dataset, load, edit, or delete one or multiple datasets.

What’s New

When applicable, new features, or new ways of performing an old function in Govern will be listed below. Version Numbers and sections will be indicated in the list.

Saved Datasets Interface

The interface is an auto-hide pane. This pane appears with a click on the Saved Datasets icon on the Ribbon, or by hovering the mouse pointer over the tab.

Saved Dataset Grid Behavior

The Saved Dataset grid allows for creation and maintenance of user saved datasets.

Select all saved datasets in the list…

Click on the check box of the first header column to select all items in the grid.

Sort Grid by Headers…

As is standard with Govern grids, a click on a column header will sort the list in ascending or descending order. Ascending or Descending order is determined by the direction of the triangle that appears in the column heading. Typically the list is sorted by the name or the date.

Restoring the default Sort Order

Click the header until the arrowhead indicating the direction of the sort disappears.

Quickly Load a Saved Dataset to the Treeview…

When you want to quickly load a dataset to the treeview pane, double click on a row to clear the Dataset Treeview and load all selected dataset to the tree view.

Grouping by Columns…

The Governs interface drag and drop features allow for additional possibilities in the grid. The space above the columns is referred to as the Grouping Area. When possible, this space expands to accommodate column names when they can be added.
To group according to a column…

Click and drag the column head to the space marked “Drag a column header here to group by that column“.
Release the Column header in the area.
Repeat the drag and drop action for additional required columns.

Removing Column Groupings…

To remove column groupings…

With the mouse pointer, click and drag the column heading from the grouping area.
When your cursor is outside the grouping area, the cursor will change to a large “X”.
Release the cursor; the grouping will be removed.

Command Buttons

The Saved Datasets pane can be displayed by hovering over the auto-hide tab. When you want the pane to display permanently without sliding back, click the Auto-Hide pin icon. The pane will remained fixed in the interface until the Auto-Hide button is re-selected.

Load to Treeview

Click Load to Treeview to load a dataset to the Treeview. The feature is enabled only if at least one item is checked. When clicked, the action will clear the dataset treeview and load all selected datasets to the treeview.

Append to TreeView

To append to the records that are in the treeview, click Append to Treeview. This button will only be active when one or more datasets have been selected in the Saved Datasets grid. When the append action is performed, all records from the selected datasets will be appended to the treeview.

Add / Replace Dataset

Toggle button between add and replace dataset. If at least one item is selected, replace the items in the selected dataset, otherwise create new dataset by showing the Save dataset window.
This button is always visible. When the user selects the Add a New Dataset button, they will be prompted with the Create New Dataset screen. Enter a name and click Save.

Append Dataset

Append Dataset will append all items from the tree view to any selected datasets in the list of saved datasets. This button is only active when one or more saved datasets has been selected in the list.

Delete Dataset

This button is used to delete saved datasets. To delete one or more dataset from the list, select the datasets that are to be deleted, and click Delete Dataset.

Share Dataset

Users that are members of other roles may share their Saved Datasets. This is done through Share Dataset feature.
To share saved datasets…

Select the check box for the dataset that you would like to share.
Click Share Dataset.
In the Share Dataset window, enter a name for the shared dataset.
Select the Roles and or Users that you are a member of, and would like to share the dataset with.
Save the change with a click on the Share button.

NOTES: Saved Dataset names can be up to 50 characters including spaces. The datasets that are displayed are only for current ID’s, as an example if the open profile is based upon a P_ID, then only saved datasets that have a Reference Type of P_ID are displayed.

Video

NOTE: There are no Training Videos available

101-std-fea-006

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

BP – Generate SSRS Reports by Groups

Batch Process – Generate SSRS Reports by Groups

Overview

Processing time is a factor where batch processes are concerned. In instances where a batch process is to be run on queries that result in an extremely large record set, processing time can be an issue. In order to manage long processing times for a single large record set, an SSRS report can be run that will break down the record set into multiple smaller, manageable groups. Each individual group will require less time to process. The Generate SSRS Reports by Group batch process will scan for any existing groups generated by the SSRS report, and print or save in the .PDF file format.

SSRS Report name: co_genssrsgprpt

Batch Process Name: Generate SSRS Report by Groups

Read More...Read Less...

Functionality

Report

The report will provide the records of groups for the .PDF file. For example, a query generates 1000 records. In our report we will specify that the resulting record set of 1000 parcels be divided into N groups; where N = 10. The resulting record set is broken up into 10 groups consisting of 100 parcels per group. Both the number of groups to print (N), and the Year will be hard coded in the report as a parameter. During processing, the SSRS report will create a temporary table, (Table: PID_GROUP), to manage the breaking up of the parcels into groups.

NOTE: The temporary table name is selected at the users discretion.

The SSRS report will use the following SQL functions:

NTILE()
ROW_NUMBER()
RANK()
DENSE_RANK()

Batch Process

This batch process will print or save .PDF files of all groups it finds in a defined folder. For our example, the Batch Process will scan and locate the 10 groups, and will process 10 times, in order to generate the 10 .PDF files that will contain the record details.
To process, the groups, the user will need to set a path to the location where the .PDF files will be generated to.

NOTE: This is a standard batch process and definition that is designed exclusively for SQL Server Reporting Services (SSRS) reporting.

For more information see General OpenForms Batch Processing

101-std-bp-012

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

Standard Feature – View Query Link

Overview

View Query Link

Why a View Query Link

View Query Link – Type 1

Configuration

View Query Link – Type 2

Configuration

View Query Link – Type 3

Configuration

Importance of Syntax

Modifying the Query

Proper use of the <LINK> tag

NEW Select a specific Entity on the form

Key Parts of the Modification to the Query

Error Handling Messages:

Documentation

Related Topics

System Dictionary (SY_DICT_DESC)

Overview

Maintenance Process

Verify Database

Generate Missing Dictionary Entries

Recommended Use

Custom Entities

User Key Dynamic

Overview

Functionalities

Workflow Management

Related Topics

Govern eSearches Technical Specifications

Overview

Govern IDs

Profile Govern IDs

Main ID

Other IDs

Standard Searches (Tree view)

A/R Inquiry

Default Search Group

Default Name Search Group

Default Account Search Group For Payment Transfers

Cash Collection

Validation

Business Tax

Corporate Account

Workflow Management

Workflow Fees – Land Management

Standard Searches (Stand-alone)

Cash Collection

eSearch and Space Characters

Related Topics

System Architecture (Dataset Treeview)

Overview

Database Views

Supported Views

Distribution Methods (Govern Techno)

Standard Iconography

Dynamic Search (eSearch), Saved Datasets and Treeview

Dynamic Queries

Saved Datasets

Other Treeview Integration

Treeview User Interaction

Inactive Business Rules

Special Features

Saved Datasets

Overview

What’s New

Saved Datasets Interface

Saved Dataset Grid Behavior

Select all saved datasets in the list…

Sort Grid by Headers…

Restoring the default Sort Order

Quickly Load a Saved Dataset to the Treeview…

Grouping by Columns…

Removing Column Groupings…

Command Buttons

Load to Treeview

Append to TreeView

Add / Replace Dataset

Append Dataset