Web Site Manager

Web Site Manager

Overview

With the GNA Web Site Manager or Manage Web Site form, you can create a look and feel for each of your Web sites by assigning WebSkins to the eProfile and the eComponents. Each application can be assigned a different skin to provide a different look and feel.
For details about using the Web Site Manager, refer to the eGovern Public Self Service Portal Release 5.1 user guide. See e-Government (Public Web Portal)

 

 

103-ap-004

 

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

Manage Web Skin

Manage Web Skin

Overview

A “skin” is a term used to refer to the appearance of the user interface (UI). Consequently a “WebSkin” refers to the appearance of the UI in a web browser. A WebSkin will present a Web application with a different look and feel, but the behavior of the UI will not change.

With the WebSkin Manager, you are able to customize the look and feel of the eProfile and the eComponents. The WebSkin Manager contains tools for defining the parts of the layout, e.g. title, head, header, footer, left and right margins and body, of a Web site. These parts are defined as a “skin”, assigned a name and ID, and then selected for the eProfile or an eComponent through the Web Site Manager.

Typically the Webskin Manager can be used to replicate the pages of your Web site that will contain restricted access eProfiles and eComponents. For example, the pages that are duplicated can contain eComponents that allow citizens to access information for outstanding tax balances, make payments online, or apply for permits as contractors.

For details about using the Web Skin Manager, refer to the eGovern Public Self Service Portal Release 5.1 user guide. See e-Government (Public Web Portal)

 

103-AP-005

 

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

 

Web Config Editor

Web Config Editor

Overview

The Govern New Administration (GNA) Web Config File Editor is designed to manage Govern’s eComponents. With the Web Configuration File Editor, you are able to define configuration parameters, determine how errors and exceptions are managed by the system, and set auto login parameters.

For details about using the Web Configuration File Editor, refer to the eGovern Public Self Service Portal Release 5.1 user guide. See e-Government (Public Web Portal)

 

103-AP-006

 

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 – SQL Query Editor

SQL Query Editor

Overview

The Govern New Administration (GNA) SQL Query Editor allows you to create both Action and Selection SQL queries. Selection queries are used to search and view data, while Action queries allow you to update, or delete data in the database. As with the SQL Query editor in the Govern for Windows Admin, the queries you design are validated for syntax.

What’s New in 6.1

[6.1.1803] Monitoring Tables for Changes (Section below)
[6.1.1506] You can now override queries by year and jurisdiction and specify the context (the business entity where it will be executed). It is now possible to test the queries.

Command Buttons

New – Click New to clear the screen so you can create a new SQL Query.

  • Save – Click Save to save a new query or modifications to an existing one.
  • Delete – Click Delete to remove the current record.

Read More...

SQL Query Editor Parameters

  • Query Name – Enter a name or code to identify the query.

For the queries that retrieve data and display a value, you can add the following characters to the beginning of the name. These characters format the value in the result:

Character Format Type Example
$ Currency with decimals $2,000.25
@ Currency without decimals $2,000
#! Numeric with decimals 2,000.25
. Numeric without decimals 2,000

For example, the following query retrieves the appraised value of the property and formats it as the Currency without decimals type:

Query Name: @GetApp
Query: SELECT appraised_value FROM MA_MASTER WHERE p_id = parcel id and frozen_id = frozen id and year_id = year id
Result: $288,000
  • English Short Description – Enter a short description to identify the department. This is useful for fast data entry and look-ups if space is limited on the forms.
  • English Long Description – Enter a long description to identify the department. This will be displayed for look-ups on forms and will be normally used for reporting.

Second Language Fields

When there is a 2nd language, or multiple languages, ensure that these description fields are also completed.

  • Is System – This flag / option is reserved for constants that are designated as Govern.NET system data.

About System Reserved Values

Only users with Super-User access will be able to select and deselect the Is System option. In addition Super Users can also create new values and flag them for Govern.NET system use.
NOTE: System constants are reserved for use by the Govern.NET system and as such should not be modified or deleted without a full understanding of the implications. Deletions of system values can damage the Govern.NET system, rendering it inoperable. Modifications that are made to System values should always be noted. When a system wide update is performed, these modifications may be overwritten.

  • Warning – Enter a message to be displayed before the query is executed, in this optional field. For example, if you are linking a query to the Delete button of a function, create a message to notify the user that one or more records will be deleted. The user can confirm or cancel the action.
  • Alternate Connection Key – Database connections are usually set in the General Settings form, they can be overridden if required. An alternate Connection Key can be specified.
  • Query (SQL) – Enter the new SQL Query statement or modify an existing one, in this edit box.

Tutorial

Creating Queries

Create a Simple SQL Query

For this example we will create a basic SQL query that will retrieve lot size information froma Govern table (Table: MA_LAND).
The query will need to get the lot size entry under the LOT_SIZE column in the MA_LAND table. The query should look like the following:

SELECT MA_LAND.LOT_SIZE

This means that we need the LOT_SIZE column…

FROM MA_LAND

…from the MA_LAND table…

WHERE MA_LAND.YEAR_ID = Year ID AND MA_LAND.FROZEN_ID = Frozen ID AND MA_LAND.LAND_ID = Land ID

…the YEAR_ID is the same as the current Year ID, the FROZEN_ID is the same as the current Frozen ID, and the LAND_ID is the same as the current Land ID.

To create a simple query…

1. In the GNA ribbon, click the Editors tab: select SQL Query Editor
2. Click Create a New Item to start a new query.
3. Enter LOTSIZE2 in the Query Name field (2)
4. In the Short Description field enter Lot Size (3)
5. Click into the Long Description field (4), the Short Description will be copied into the Long Description, add any additional information to the name.
6. Click in the Query (Sql) field (5); begin typing in the query created earlier.

SELECT MA_LAND.LOT_SIZE FROM MA_LAND
WHERE MA_LAND.YEAR_ID=Year ID AND
MA_LAND.FROZEN_ID=Frozen ID AND
MA_LAND.LAND_ID=Land ID

NOTE: When entering the query, ensure that there are no spaces before and after the “=” sign. For other syntax rules, see SQL Syntax Rules for GNA.

7. To save the new query, click Save (6); if an error exists within the query, the system will not allow it to be saved. You will be presented with a dialog box like the following; click OK and make any necessary corrections to the syntax of the query.
NOTE: To minimize the chances of errors when composing your queries, refer to SQL Syntax Rules for GNA.
The new query will appear under the SQL Definition List (A) on the left hand side.

The query will appear on the left hand side under the SQL Definition List. When saved this query will be accessible for use in formulas and logical expressions.

Query Types

You can compose and store both Action Queries and Selection Queries in the SQL Query Editor. To retrieve or to use a value from the current record; for example, while running a query from a function or formula, you can include a keyword. See Using Keywords for details.
NOTE: Keywords can be included on the SQL Definition Setup form, only; on this form you must use SQL syntax for Microsoft® Access®.

Selection Queries

Selection Queries are used to retrieve records from one or more specified tables, according to the selection criteria.

The syntax is as follows:

SELECT [column] FROM [table] WHERE [criteria]

For example, the following query, retrieves the City District name from the PC_AREA table for the record matching the current parcel ID, frozen ID and year.

SELECT DIST_CITY FROM PC_AREA WHERE p_id=parcel id and frozen_id=frozen id and year_id=year id

Monitoring Tables for Changes

Available in Rel. 6.1.1803
NEW! Observable user queries are user queries where the result is automatically refreshed whenever one of the parameters or the underlying data changes. This is the case for:

  • View queries
  • Calculated fields
  • Lookup lists
  • Etc.

In order to update itself when the underlying data changes we must listen for the table changed event. As long as the table name is in the query, it will be refreshed.
However, when using a View or an Alias instead of the actual table name, then issues will arise as you will not know that the query must be re-executed. In such instances, the table name can be specified explicitly by using the hint monitortables:

–monitortables(NA_NAMES, PC_PARCEL)SELECT *
FROM v_view1 v1 INNER JOIN v_view2 v2 ON v1.na_id=v2.p_id

In the previous example, v_view1 is actually a view over the table NA_NAMES, while v_view2 is a view over PC_PARCEL. By using the hint monitortables users can explicitly define which tables are monitored for changes.

Action Queries

Action Queries are used to perform actions, such as updating records in one or more tables, adding records to a table, deleting records from a table or creating a new table or index.
This section provides simple examples of Update, Append and Delete Queries. Since the SQL Definition Setup form is used for queries that are run multiple times, it is better to compose and run a Create Query from outside Govern.

Update Queries

Update Queries are used to modify records in one or more tables, by changing values in specified tables and fields, according to certain criteria.

The syntax is as follows:

UPDATE table.* SET value WHERE criteria

For example, the following query enters the value abc in the Fire District field of the PC_AREA table, wherever the value for this field is null.

UPDATE pc_area SET dist_fire = ‘abc’ WHERE dist_fire IS NULL

Update Queries are typically used when you need to change multiple records in a table or records in multiple tables.

TIP: You do not obtain a list of results from running this type of query. To verify which records will be changed, you can run a Selection Query
using the same parameters and criteria and view the Results screen.

Insert Queries

Insert Queries are used to add a single record to one or more table. You need to specify the fields to which you are adding values and the value for each field. Otherwise, the default value or Null is entered.

The syntax is as follows:
INSERT INTO table (column list) VALUES (value list)

For example, the following query adds a record to the VT_USR_NAMECODE table, entering the values ENG, LD, ITR and In Trust in the language, department, code, short description fields.

INSERT INTO vt_usr_namecode (language,dept,code,short_desc)
VALUES (‘ENG’,’ ’,’ITR’,’In Trust’)

You can also append multiple records to a table, by first selecting the records in another table. For this, a Selection Query is added to the Append Query.

Delete Queries

Delete Queries are used to remove records from one or more tables.

The syntax is as follows:
DELETE [table.*] WHERE criteria

For example, the following query, add records containing the year 2004 are deleted from the PC_AREA table.

DELETE FROM pc_area WHERE year_id = 2004

TIP: The Delete Query deletes more than the specified fields, it deletes the entire record. To delete data from specific fields only, create an update query that changes the values to Null.

Monitoring Tables

Observable user queries are user queries where the result is automatically refreshed whenever one of the parameters or the underlying data changes. Queries of this sort are used in the following:

  • View Queries
  • Calculated Fields
  • Lookup Lists

and so on…
In the above examples, data changes due to user interaction may occur with the above types of queries. In order to update when the underlying data changes you can “listen” for the table changed event. As long as the table name is in the query, the data will be refreshed. Issues arise when using views
As a view is the result set of a stored query on the data
However, if using a view or an alias instead of the actual table name then we won’t know that the query must be re-executed. In this case you can specify explicitly the table name by using the monitortables hint :

–monitortables(NA_NAMES, PC_PARCEL)SELECT *
FROM v_view1 v1 INNER JOIN v_view2 v2 ON v1.na_id=v2.p_id

In the previous example, v_view1 is actually a view over the table NA_NAMES, while v_view2 is a view over PC_PARCEL. By using the hint monitortables users can explicitly define which tables are monitored for changes.

See Also

Formula Editor

Logical Expression Editor

SQL Syntax Rules for GNA

Query Types

Advanced SQL Queries
Keywords
Best Practices for SQL Queries
Special Cases

100-Queries

 

 

103-ed-004

 

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-ED-007

External Command Editor version 6.1

Version 6.0 | Version 6.1

Overview

The External Commands Editor is used for opening an external application and passing a parameter from Govern directly to that application. Parameters include Govern attributes, Govern IDs, such as the parcel ID, P_ID, and e-mail addresses. External commands can be linked to the Profile Editor, and added to the Govern Ribbon, or added as a link to a Govern form, through the OFD.

Examples include:

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

The syntax for these commands is provided under Examples of Commands .
In Govern OpenForms, 6.1, external commands are added through expressions. In version 6.0, the syntax is different and in version 5.1, both the syntax and the setup are different.

Creating a Command

To create a new external command in 6.1:

  1. Launch GNA.
  2. Select Editors > External Commands Editor.
  3. Enter a code in the Code field to uniquely identify the command.The code must start with a letter.
  4. Enter descriptions in the English and French Short and Long Description fields.
  5. Click the ellipsis button beside the Expression field and enter an expression.This is a required field. See the examples for some expressions that can be added.
  6. An icon is displayed with the command in the Govern Ribbon or on the form.
  7. Do one of the following:
    If you are adding the command to the Ribbon, click the ellipsis button beside the Icon field, navigate to the directory where the icon is stored, and select it.
    The icon is saved in the database; so, you do not need to keep a copy of it.A preview of the icon is displayed beside the field.To delete the icon, click Delete beside the field.If you are adding the command to the form, add the icon in the OFD.
  8. Click Save.
  9. Follow the instructions for adding the command to the ribbon or to a form. When the command is added to a form or to the Ribbon, it is displayed in the Used In text box.

 

Examples of Commands

The following example provides the syntax for opening Google Maps to a specific location.
Enter the following expression in the Expression Selector:

cmGglMaps
https://maps.google.com/maps/?q=’+query(‘syMaps‘)
Note: The query must be predefined in the Select Queries Editor in GNA. The query for this expression is:

SELECT ISNULL (PC_ADDRESS.FORMATED_ADDRESS,’aa’) +’ ‘+ ISNULL
(PC_ADDRESS.CITY,”) +’ ‘+ ISNULL
(PC_ADDRESS.ZIP_POSTAL,”), ‘”Map this Location”‘ as Label
FROM PC_ADDRESS INNER JOIN PC_PARCEL ON
PC_PARCEL.P_ID=PC_ADDRESS.P_ID
WHERE PC_PARCEL.P_ID=Parcel ID

Adding an External Command to the Govern Ribbon
External Commands are added to the Govern Ribbon through the Profile Editor in GNA.
To add a command to the Govern Ribbon:

  1. Launch GNA.
  2. Select Editors > Profile Editor.
  3. Select the required Profile.
  4. Select the Links tab.
  5. Click the Add button in the External Commands list box.
  6. Select the command or commands that you want to add from the Select the External Commands window.
  7. Click Save.

The command appears in the Tools menu in the Govern Ribbon for the Profile.

Adding an External Command to a User Form

External commands are added to a Govern user form through the OpenForms Designer, as a link.
To add a command to a Govern form.

  1. Launch the Govern OpenForms Designer (OFD).
  2. Select the Link control from the tree view on the left.
  3. Drag it to the required position on the form. The link is displayed in the selected cell in the OFD Editor.
  4. The Action property is automatically selected and outlined in red. This is a required property.
  5. Configure the properties as described in this section.
  6. Click Save.

Note: The logged-in user must have the required security permissions for the application, form, or batch process. Otherwise, an error message appears.

Defining the Properties for a Link

Select the link on the OFD Editor and modify the properties in the Properties Explorer. When the Link is selected the word Link appears at the top of the Properties Explorer.
Element ID: As with all items, the User Tab Item has an element ID property. This provides reference in the log files.
Layout: Adjust the height and width of the label in the Layout property under Properties.
Display Type: You can display the link in one of the following formats:

  • Hyperlink
  • Button

Action: Select Execute Command from the drop-down list.
Link to: Select the command from the drop-down list.
Icon: Click the ellipsis button and select the icon, you want to add, from a computer or network directory.
The icon is saved to the database. There is no need to retain a copy of it.
Is enabled: Click the ellipsis button to open the Expression Selector. Enter an expression to make the link read-only under certain conditions.
Is visible: Click the ellipsis button to open the Expression Selector. Enter an expression to hide the link under certain conditions.
Expressions evaluate to true or false. You could write False in the Expression Selector to make the link read-only or invisible under all conditions. Alternatively, you could write an expression to do this under certain conditions, such as when another value on the form is equal to a certain amount.
Text: The text entered in this field appears on the form. By default, it reads Link. You can modify this with an expression. Click the ellipsis button to open the Expression Selector.
To display text, you need to enter it inside single quotation marks; for example, ‘Your Text’. You can add other expression syntax to the text in order to make it more specific.
Tooltip: Enter a tooltip, in English, French, or both, to display additional information when the mouse hovers over the link.
The command is launched from a link on the form.

Documentation
For complete details on external commands see:

version 6.1

External Commands, version 6.1

version 6.0

External Commands, version 6.0

version 5.1

External Commands, version 5.1

Information for Govern Users

See also External Command in Govern.

Information for Developers

For Technical Information also refer to govern DEVELOPER’S 101-std-fea-020

Overview | Information for Govern Users | Information for Developers

 

101-std-fea-045

What-If Scenario Feature
Module Overview, Configuration, Installation, OpenForms References, What’s New, wiki MapLast Updated Mar. 20, 2018 …
VERSION 6.1 GA1706

Overview

The feature of “What If” simulations was integrated in 6.1. The thought behind the simulations is to allow users to make projections on records. These projections will have no impact on any current records. After reviewing their projections, their current record are placed in their scenario.
Govern users will note that the Govern Audit and “What If” features create historical records that use Frozen ID’s. The Mass Appraisal (CAMA) and Tax (TX), PP, and PC modules have the same frozen id, (ID = -32765). Available in release 6.0.1611 and later.

Functionality

What-If simulations are essentially an Audit with a Frozen ID that is used exclusively by the feature. It still uses the audit table and its functionalities; the reserved Frozen ID is (ID =-32764). Refer to the Audit documentation for more details.
NOTE: For Governs versions prior to 6.1.1706, the Frozen ID remains the same for all sub-systems, i.e. (-32765). Versions after 6.1.1706 have their own Frozen ID.

Configuration

The What-If Scenario feature is available for the following Govern sub-systems:

  • Aircraft (AC) Link
  • Business Tax (BT) Link
  • Mass Appraisal (MA) Link
  • Motor Vehicle (MV) Link
  • Personal Property (PP) Link
  • Real Estate (RE) Link

NOTE: Configuration for the What-If Scenario is specific to each subsystem that it is available in.

Documentation

Click below to view the user documentation
101-std-fea-045_Govern_What_If_Scenario.pdf

See Also

101-std-frm-010

101-std-frm-010 #stdfrm #std

Standard Feature – Multimedia Document Queue
Module Overview, Configuration, Installation, OpenForms References, What’s New, wiki Map … Last Updated March 22, 2017

Table of Contents

Overview
Functionalities
Example
Configuration
OpenForms Designer (OFD)
OFD Properties
Extension Selector
Govern New Administration (GNA)
User Interface
Queue group – parameters (center)
Queue grid Columns
Queue grid Columns
How to refresh the Queue grid
Multimedia Type – Name
Details group
Preview
Actions group
Scan Settings subgroup
Adding to the Queue
Documentation
See Also

VERSION 6.1 Under Development

Overview

The purpose of the document queue is to serve as a placeholder for Multimedia documents that are to be added to a record at a later time. For example, a lineup of applicants are waiting to apply for permits or licenses, as the forms are filled out there may not be sufficient time to go through the process of scanning their required support documents for the application. As their record is completed, the scanning or importing attachment process for their multimedia documents are sent to the scanning queue. The will be attached at a later time. When the attachment process is ready to be completed, the Multimedia Scanning Queue presents the list of documents. Each document is selected on the list, and the scanning/import is performed. As each item on the list is processed, it is removed from the queue.

NOTE: The driver for the scanner being used must be Windows Image Acquisition (WIA compliant)

Functionalities

The Multimedia Scanning Queue is a custom control that allows users to “build up”, or “Queue up” a list of required documents for any Govern module. Although the title reads as Workflow Multimedia Scanning Queue, in actuality the feature is not dependent on the Multimedia function and can be used without the Multimedia control.
The Multimedia Scanning Queue action generates a multimedia document for the scanning queue that is related to a workflow. This action is performed according to the parameters defined in the Govern New Administration (GNA).

NOTE: This is not a generic action, and can only be invoked in the context of a workflow. This action is only functional when the category’s entry key type is a P_ID, or an NA_ID. USER_ID or DEPT_ID are not used.

The Multimedia function may be configured to work in together with the Multimedia Scanning Queue in Govern. This function can be used to control individual scans, or to control scanners that perform bulk scanning duties; the condition is that the installed driver for the scanner is WIA compliant.
The Multimedia scanning queue is a grid that displays a list that will require documents to be attached to them.

Example

As an example in a Workflow that results in the generation of a license, users can create a principal form workflow permit type. In addition to the principal form, the form will consist of two custom entities, the Multimedia entity, and the Multimedia Scanning Queue entity.

NOTE: Placing the Multimedia and Multimedia Scanning Queue custom entities together on the same form is not a requirement for functioning. As mentioned earlier, the Multimedia Scanning Queue entity can function independently of the Multimedia custom entity.

Configuration

OpenForms Designer (OFD)

As stated, Multimedia, and Multimedia Scanning Queue are both custom entities. When configuring the Multimedia entity, you would need to choose a parent entity, and set the selected multimedia type, e.g. in OFD configuration, the value of SelectedMultimediaType = Workflow, in the case of the Multimedia Scanning Queue, the configuration of a Parent Entity, or Property is not required.

OFD Properties

Properties Value
Custom Entity
ID
Element ID Generated by system
Misc
Action MsGovern.OpenForms.CustomControls.dll
MultimediaScanningQueue_Control
Name
Parent Entity – Not Required –
Properties
Tab sequence number – Not Required –
Text Multimedia Scanning Queue
(User defined name)

Extension Selector

This is displayed when the ellipsis button [ … ] at the end of the Action parameter is selected

Assembly Class
MsGovern.OpenForms.CustomControls.dll MultimediaScanningQueue_Control

Govern New Administration (GNA)

In the Department Maintenance form when defining Multimedia codes, note that one of two data types can be used for scanned requests. The data types that can be scanned are as follows:

  • I (Image) – Image files that are stored within the database.
  • P (Picture Link in the database) – Links to files that are external to the database.
NOTE: Picture (P) data types are associated with the External Document (Permanent Path) option.

external image image2017-2-27_13-53-14.png?version=1&modificationDate=1488221594276&api=v2

User Interface

When correctly configured, the Multimedia Scanning Queue form is presented with three (3) main groups. On the tab is a Refresh button

Queue group – parameters (center)

Queue grid Columns

Multimedia Type – Select one of two options Name, or Parcel. The initial default value is dependent upon whether the profile is based on a NA_ID, i.e. Name, or a P_ID, i.e. Parcel. This value can be changed to view the items in the queue.

Queue grid Columns

This grid is populated as a result of a query and will display a list of the multimedia documents that are to be scanned in the queue. There are two (2) queries that are used to populate the Queue grid. Which query used is determined by the value selected in the Multimedia Type parameter located above the grid. Consequently the columns displayed will be dependent on a selection of the Parcel (P_ID) or Name (NA_ID).

How to refresh the Queue grid

Users may refresh the grid containing queued items at any time. This can be done with a click on the refresh button that is displayed on the immediate right of the tab label.

Multimedia Type – Parcel
Entry Date – This column will display the entry date of the record
Document Type – The Document Type is the multimedia code that was assigned to the record when it is being queued. These codes are created in the Department Maintenance form under the Multimedia Codes tab.
Parcel Info – A certificate number is displayed in this column. If a certificate number is not present, then the application number is displayed.
Workflow # – When appropriate, this column will display the Workflow number associated with the record.

Multimedia Type – Name

Entry Date – This column will display the entry date specified for the queued record
Document Type – The Document Type is the multimedia code that was assigned to the record when it is being queued. These codes are created in the Department Maintenance form under the Multimedia Codes tab.
Name – This parameter displays the content of free_line_1 from the NA_NAMES table name (NA_ID) associated with the record.
Workflow # – When appropriate, this column will display the Workflow number associated with the record.

Details group

Info Type – This is the document type assigned to the requested file.
Details – Displays parcel or name information
Request Date – If available, this is the set date requested for the document
Document Type – The requested document type is indicated in this field. This is description of the document.
Image Type – This is the classification of the image.

Preview

Document Type – Description of the document.
File Type – This is the type of file, e.g. .jpg, .png, .bmp, .doc, .pdf, and so on.

Actions group

Import – Click to display the file selection window; navigate to and select the file that is to be imported.
Scan – To scan directly from Govern click this button. When the scan is complete the image will be displayed in the Preview group. No interim UI is displayed.
Save – A click on Save will save the file with the record. When the save is complete, the record will be removed from the scan queue.

Scan Settings subgroup

There is a combo-box that displays the WIA compliant scanner that is configured on the system.
Scan with the integrated UI – When this option is selected, the interface will default to the scanner manufacturers interface. When selected, all options in this form will be disabled.

Adding to the Queue

Items are added to the queue either directly through the Multimedia form, or as a result of actions that are associated with an activity. When the item has been added to the queue as a request, they can then be selected one at a time from the list. The required multimedia file is then acquired to be added to the request through a file import, or an import as a result of a scanner acquisition. When the imported document as been saved, i.e. associated with the queue request, the file is removed from the queue.

Documentation

101-std-frm-010 Workflow Multimedia Scanning Queue.pdf

See Also

Workflow Management ACTION – Generate Multimedia Image Queue
Multimedia
Workflow Management Wiki Map