BP – Import Name to Email

Batch Process – Import Name to Email

Overview

In Development

 

 

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

 

100-ChangesDBStructure

Changes in Database Structure

Version 6.0 and 6.1

Overview

Standard Functions and Features

System and User Validation Tables

Version 6.0 and 6.1

  • Changes to VT_USER and VT_SYSTEM tables. System and User Tables are now validated and compared against the standard structure XML file.

 

Read More...

Userfile

Version 6.0

  • New GLOBAL KEY to allow us to link Workflow and global messages to users.
    • U_ID field added to USR_USERFILE.

User Profiles

Version 6.0.1412

  • Fields removed from USR_PROFILE
    • ORG_NBR
    • GROUP_CODE
    • JURISDICTION_CODE
    • OWNER_MM
    • OWNER_YY
    • NB_REC_WARN
    • NB_MIN_ROLLBACK

Roll Forward Exclusion Tables

Version 6.0

  • New tables added to support the roll forward exclusion of fields.
    • SY_ROLLFORWARD_EXCLUSION
    • SY_ROLLFORWARD_EXCLUSION.TABLE_NAME [PK]
    • SY_ROLLFORWARD_EXCLUSION.COLUMN_NAME [PK]

User Audit Trail New Tables (3)

Version 6.0 – see User Audit for more info [std-fea-017]

  • USR_AUDIT_OPENFORMS
    • AUDIT_ID
    • AUDIT_ACTION
    • ENTITY_ID
    • FORM_CODE
    • USER_ID
    • AUDIT_DATE
    • IP_ADDRESS
    • SOURCE_COMPUTER_NAME
    • REMOTE_COMPUTER_NAME
  • USR_AUDIT_OPENFORMS_CHANGE
    • AUDIT_ID
    • ATTRIBUTE_ID
    • TABLE_NAME
    • COLUMN_NAME
    • OLD_VALUE
    • NEW_VALUE
  • USR_AUDIT_OPENFORMS_KEY
    • AUDIT_ID
    • ATTRIBUTE_ID
    • KEY_NAME
    • KEY_VALUE
    • IS_PRIMARY_KEY
NOTE: The legacy table USR_AUDIT_TRAIL will be kept for modules running in prior releases, but developers should note the new modifications and table structures impact for custom processes.

Property Control (PC)

PC Parcel

Version 6.1

  • NON_PARCEL_FLAG and VIRTUAL_PARCEL cannot be set to null.

PC Sales
Version 6.0

  • PC_SALES is no longer used, only MA SALES

Accounts Receivable & Cash Collection (CC)

Version 6.0

Payer Name

  • PAYER_NAME added to CC_MASTER (name was previously kept in CC_MASTER_NOTES) – 6.0 and 6.1

Mass Appraisal (MA)

For the specification document, click on Appraisal Detail Specification for listing.

Building Changes

Version 6.1

  • Current_P_ID was added to MA_BUILDINGS
  • VT_SY_DRAWCMD is no longer used

Site Changes

Version 6.1
Site changes to support new override methodology

  • These columns were added:
    • LAND_VALUE_OVERRIDE (money)
    • LAND_AG_VALUE_OVERRIDE (money)
    • BLDG_VALUE_OVERRIDE (money)
    • MISC_VALUE_OVERRIDE (money)
    • INCOME_GRM_VALUE_OVERRIDE (money)
    • INCOME_DIR_VALUE_OVERRIDE (money)
    • MRA_VALUE_OVERRIDE (money)
    • PP_VALUE_OVERRIDE (money)
  • These columns were dropped : (No longer used in v6.1)
    • TEMPLATE_CD
    • TEMPLATE_VA
  • A misc. correction script was added to move :
    • LAND_VALUE to LAND_VALUE_OVERRIDE when LAND_OVERRIDE = -1
    • LAND_AG_VALUE to LAND_AG_VALUE_OVERRIDE when LAND_AG_OVERRIDE = -1
    • BLDG_VALUE to BLDG_VALUE_OVERRIDE when BLDG_OVERRIDE = -1
    • MISC_VALUE to MISC_VALUE_OVERRIDE when MISC_OVERRIDE = -1
    • INCOME_GRM to INCOME_GRM_VALUE_OVERRIDE when INC_GRM_OVERRIDE = -1
    • INCOME_DIR_VALUE to INCOME_DIR_VALUE_OVERRIDE when INC_DIR_OVERRIDE
    • MRA_VALUE to MRA_VALUE_OVERRIDE when MRA_OVERRIDE = -1
    • PP_VALUE to PP_VALUE_OVERRIDE when PP_OVERRIDE = -1
  • A misc. correction script was added to move :
    • All XXX_VA values to XXX_OV_VALUE when XXX_OV = -1
    • – XXX_OV_VALUE should be created as well.

Income Changes

Version 6.1
Income changes to support new override methodology

  • These columns were added in MA_Income.
    • Building_Value_Override
    • DIR_Rate_Amount_Override
    • GRM_Rate_Amount_Override
    • Gross_Effective_Override
    • Gross_Rent_PCT_Override
    • Gross_Rent_Value_Override
    • Land_Value_Override
    • Misc_Value_Override
    • Net_Dir_Override
    • Net_GRM_Override
    • Net_Value_Override
    • Rent_Units_Override
    • Vacancy_PCT_Override
    • Overall_ADJ_VAL_Override
  • These columns were added in MA_Income.
    • Ma_Income_Group

Income changes to support new calculation method and configuration

  • Income Fields added
    • Ma_Income_Record_Type
  • Income Table added
    • For Added Fields – to be validated

 

Miscellaneous Billing

Available in GA Release 6.1.1606
To offer more flexibility, the misc. billing parameters are now year base.
As such the YEAR_ID was added to the following tables:

  • MB_INVOICE and MB_INVOICE_DET
  • MB_RECURRING and MB_RECURRING_DET

In prior versions, only the AR Class Code was used for the invoice and invoice detail. To simplify data entry and offer more flexibility, the following tables were added.

  • MB_PARM_CATEGORY (contains a category that will be used to link the detail invoice items)
  • MB_PARM_ITEM

New Database Fields

  • LAST_RECUR_DATE was added to the MB_INVOICE_REC table
  • BATCH_ID was added to the MB_INVOICE table

Self Reported Business Tax (ST)

When the fields for ST forms are created, the following USR_FIELDS_XXXXX tables, are no longer used.

  • USR_FIELDS_DEF
  • USR_FIELDS_LABEL
  • USR_FIELDS_MASK
  • USR_FIELDS_NUMERIC_FORMAT (Added for 6.0 and 6.1)
NOTE:The data in the above have been copied to (Table: ST_PARM_CATEG)

New Field added in ST_MASTER

  • NAICS (Varchar 15) MANDATORY when using Estimated Filings.
NOTE: This field is now a Standard System Field and may need to be converted if it was created as an Added Field.

New Tables added for Estimated Filings

  • ST_ESTIMATE_ID

New Table added for Corporate Account

  • ST_CORP_ACCOUNT

Name and Address (NA)

For ACH processing and field encryption, the following changes have been made:

  • NA_ACH_INFO.ACH_DESC (new field)
  • NA_ACH_INFO.BANK_ACCOUNT_NO (new field length = 44)
  • NA_ACH_INFO.TRANSIT_NO (new field length = 32)

OpenForms Tables

Version 6.0

Tables Removed from versions: 6.0.1411.0106 and 6.1.1411.0106
1. OF_SE_APP_TYPE replaced by an object in memory
2. OF_DE_MODELCONTENT was used only for MOD
3. OF_MD_UPDATER was used only for MOD
4. OF_LK_PROFILE_OF1 was used only for MOD to establish the link with a profile.

Tables Removed from versions: 6.0.1411.0017 and 6.1.1411.0021
The tables defined in MSGDatanaseStructMods.xml (so also in OPENFORMS_REFERENCE_60):

  • 1. OF_BE_MAPEXPR
  • 2. OF_BE_MAPTYPE
  • 3. OF_BE_NAVIGATION
  • 4. OF_BE_SERIALIZATION
  • 5. OF_BE_VALRULE_ATTB
  • 6. OF_BE_VALRULE_PARM
  • 7. OF_CTRL_TO_COLUMN
  • 8. OF_LK_ATT_VALRULE
  • 9. OF_MODEL_PERSONALIZATION
  • 10. OF_SE_ACCESSRIGHTS (notion still useful but the table has been replaced by an enumeration in the code)
  • 11. OF_SE_AUDIT
  • 12. OF_SE_LK_ROLE_USER
  • 13. OF_SE_USER_EXCL
  • 14. OF_UI_MAPTABLE (notion still useful but the table has been replaced by CLR objects in the code)

Release 5.x

Version 5.x

  • PC_LK_PARCEL has been replaced with PM_LK_MASTER

See Prior Database Changes (ref. v6.1.1508)

Related Topics

Govern Database DiagramsRefer to the List of Changed Tables section

 

 

100-ChangesDBStructure

 

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

 

100-USR-Registry

User and Machine Registry (USR_REGISTRY) Parameters

Version 6.0 | Version 6.1 (In Development)

User and Machine Registry

The KEY TYPE is used to identify USER and MACHINE registry parameters.

Key Type 1 = User ID registry, – IDENTIFICATION Code = User Id
Key Type 2= Machine registry – IDENTIFICATION Code = Machine Name
Payment Processors not updated

Cash Collection Parameters

By User ID

Registry Type Section Name Key Name Key Type Identification CD Key Value Encrypted Action Notes
Cash Collection Cashier Cash Collection Cashier auto collapse MCR Group and AR Class Distribution 1 user id 0 or 1 0
Cash Collection Cashier Cash Collection Cashier search style 1 userid Style lookup 0 Default lookup group in Cash Collection Form VERIFY conditions
Cash Collection Cashier Cash Collection Cashier real estate up to installment 1 userid 1,2,3,4,t 0
Cash Collection Cashier Cash Collection Cashier self reported tax breakdown by periods 1 userid 0 or 1 0
Cash Collection Cashier Cash Collection Cashier show only accounts by balance 1 userid 0 or 1 0 A/R with a zero balance will not be displayed in the grid
Cash Collection Cashier Cash Collection Cashier year to collect 1 userid YEAR, 0 or null 0 If a year is entered, only A/R for this year will be displayed
default collection type Missing (credit card, cash, etc.)
Cash Collection Parameters Cash Collection credit card type 1 userid Table Lookup will need to use the new table CC TYPE
Cash Collection Parameters Govern allow Misc. Cash Receipts 1
Govern allow xxx Data Entry (Fee, Demand, Discount…) 1 Deprecrated
Govern bill validation verify
Govern cashier Id Text verify
Govern check validation
Govern credit card data entry Automatic/Manual Deprecated?
Govern default access type Table Lookup Property Control, Real Property, SRT, Name … Still in use?
Govern default cycle
Govern default payment data entry year
Govern display cycle code Deprecrated
Govern display fiscal year field Deprecrated
Govern display installment field Deprecrated
Govern print credit card receipt to verify
Govern print receipt log see roadmap
Govern receipt group 3 letter
Govern use cash drawer
Govern slip driver, font, etc. To be reviewed
Cash Collection Parameters Payment Data Entry deposit to be reviewed

 

By Machine

Registry Type Section Name Key Name Key Type Identification CD Key Value Encrypted Action Notes
Cash Collection Cashier Cash Collection Cashier cash drawer name 2 machine name EPSON TM-H6000IV Receipt 0 As shown in Windows Printer names
Cash Collection Cashier open cash drawer sequence 2 machine name 27;105 0
Cash Collection Parameters All the same section names and parameters as by User ID

 

 

100-USR-Registry

 

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

 

CC – Cash Collection Receipt Report

Cash Collection (CC) Receipt Report

Version 6.0 | Version 6.1

Overview

This is the standard receipt printed when using Cash Collection module.

Available in GA 1606.

Purpose of Receipt

– Undefined –

Process Name

cc-rpt-058

Sample Report

A sample report will be provided when available.

 

 

101-cc-rpt-058-Receipt

 

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-cc-rpt-060-CheckValidation

Cash Collection (CC) Check Validation Report

Version 6.0 | Version 6.1

Overview

This is the standard report used to print the check endorsement when using Cash Collection.
Available in GA 1609.

Process Name

cc-rpt-060

Sample Report

– To be provided when available –

 

 

 

101-cc-rpt-060-CheckValidation

 

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

 

Dataset Treeview

Dataset Treeview

Overview

Datasets that appear in the Dataset Treeview are populated with the results of searches made through the Search form. Records that are loaded into the Dataset Treeview may be appended to through the Saved Dataset pane, or deleted directly in the Treeview pane.

Populating the Dataset Treeview

To populate the Dataset Treeview with search results…

  1. When the Predefined Searches pane is in its default position, place your mouse pointer over the tab to display the search form (A).
  2. In the form perform a search type; for this example we will perform a property search by P_ID.
  3. Click Search for Result.
  4. Search results will be displayed in the lower portion of the search form.
  5. Click Load to the search result to transfer the search result records to the Dataset Treeview pane.
  6. If the Dataset Treeview pane is not displayed, click its tab at the bottom of the pane.

 

The Treeview Explorer

The Treeview Explorer displays record information in a hierarchical arrangement. In the Treeview panel, you are able to expand or contract a record by clicking on the arrowhead icons.
For example, on a search that retrieves tax map records, when you double-click on the tax map, it lists name information at the next level. Each item can be expanded to show specific data on the property, such as owner and occupant names, parcel information and location, permits, utility billing and accounts receivable records.
As you select each level of information, the data is displayed in the appropriate OpenForm when it is displayed on the right hand side.

Record Edit Confirmation

When a dataset has been loaded, it is easy to select and begin to edit a record. This ease of selection may at times be a detriment as at times the wrong record may be selected, and the user immediately begins to edit in error. It has been determined that if a secondary confirmation is introduced during the record selection process, there is less chance of erroneously editing the wrong record.

Through the Govern New Administration (GNA), the Record Edit Confirmation option can be enabled to add a secondary confirmation. When Record Edit Confirmation is enabled, after the user selects a record, they are obliged to click on a secondary icon (A), to fully unlock the record for editing.

To enable Record Edit Confirmation…

  1. In GNA, select System Parameters (tab) > General Connection Parameters.
  2. In the General Connection Parameters form, locate the Organization Parameters group and select The user must explicitly enable editing for each parcel option.
  3. Click Save to save the option.
  4. To close the form, click Exit.

When this option is enabled, after loading a dataset, users may still select a record for editing, but the selected record will have an icon beside it. The user must click the icon in order to fully unlock the record for editing.

System Architecture

For all details regarding the Govern Treeview Architecture, refer to 101-std-fea-005-Treeview_Architecture.

What’s New

Context Menu in Dataset Treeview

NEW! Users of the Dataset Treeview will note that when it is populated with one or more records, there is a description for each record. This description can be a Parcel ID, an Account Number, and so on. A quick method of deleting individual records is to hover the mouse pointer over a record. When the width of the Dataset Treeview pane is wide enough, placing the mouse cursor over the description will display an “x” that can be used to remove the record. Unfortunately when there is insufficient space, i.e. the space is not wide enough to display the full description, the “x” is not visible. To address this situation a context based menu has been added to the interface.
TreeviewContextMenu00.png
To display this menu…

  1. Right click on the record of interest in the Dataset Treeview.
  2. In the floating menu, you now have option for additional functions that appear beside the record when the entire line is visible.

By default, there will be an option to “[x] Remove”. When there are other options, e.g. Edit, they will also be presented in the menu.
This feature is available in the following releases: 6.0.1611.0067 / 6.0.1702.0080 / 6.1.1611.0060 / 6.1.1702.0121

Reposition

Previously, when performing a search of records with the same NA_ID but multiple ST Account numbers, when you copy the record to the Treeview, the system would only select the first account. Now the selected record will be sent to the Treeview. (Available in release 6.0.1503)

Hibernate Mode

This behavior of selecting only the first account also applies to the Hibernate process. As Govern is restored from a hibernation if a second or third account is selected before hibernation, when the application is restored, although the NA_ID is correct, only the first account will be displayed.

Load to Treeview and Add (Append)

As data is loaded or appended to the Treeview from the Search, or the Saved Datasets form, the following rules apply:

  • When a record is selected for append, only new files will be loaded. If previously loaded, the file will not be reloaded into the Treeview.
  • If no search result is selected, the Add to Search Results button will be disabled.

Hibernate

Previously the Hibernate would store the NA_ID of the records displayed in the various panes that are opened in the interface. Now to maintain the fidelity of the hibernated user environment, all Govern ID’s are used; i.e. NA_ID, P_ID, ST_ID, and so on.

NOTE: User Hibernate information is stored by user in (Table: USR_HIBERNATE). The following query will display the hibernation information for “userName”

SELECT *
FROM USR_HIBERNATE
WHERE USR_ID = ‘userName’;

Treeview Synch
In Govern for VB6, external tables (PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL), were used by external applications and reports to automatically know the current recordset and currently viewed parcel. In Govern release 6.0 and upwards, these external tables are being phased out and the functionality provided by them will need to be reproduced.

NEW! The Treeview sync. feature saves the contents of the current profile in (Table: USR_SAVED_DATASETS) with a “Saved Dataset” name of “AUTOSAVE” under (Column: USR_SAVED_DATASETS.SAVED_SET_NAME). Should a profile be changed, the dataset loaded in the Treeview will be automatically synchronized to (Table: USR_SAVED_DATASETS).
This feature recreates the functionality provided by the three (3) external tables that were used in Govern for Windows, (Tables: PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL). For example users could run a batch process on a saved external dataset as opposed to a set range.

NOTE: In release 6.0 a simultaneous save will be made to (Table: PC_EXTERNAL) and (Table: USR_SAVED_DATASETS), Tables NA_EXTERNAL and PM_EXTERNAL are no longer supported.
In release 6.1, all three (3) tables PC_EXTERNAL, NA_EXTERNAL, and PM_EXTERNAL will not be supported.

  • PC_EXTERNAL (Supported in release 6.0; not supported in release 6.1)
  • NA_EXTERNAL (Not not supported in release 6.0 and 6.1)
  • PM_EXTERNAL (Not not supported in release 6.0 and 6.1)

Enabling “Synchronize Dataset Treeview”

This feature is enabled in the User Registry through the User Registry Manager. The Options button is located below the Govern suite button in the Govern User Interface.

  1. Click the Options button; click Options.
  2. In the Registry Manager form, verify that the Registry Filter is set to User ID.
  3. Under the Section Name column, locate Synchronize Dataset Treeview; click to select the option under the Key Value column.
  4. Click Save to save your changes.

When you return to the Govern interface, the Treeview Sync. icon will be enabled. This is a toggle, i.e. ON/OFF button that will enable or disable the feature.

Location of Data

As indicated above, all data will saved in (Table: USR_SAVED_DATASET). Associated columns are as follows:

COLUMN DESCRIPTION
USR_ID User ID
SAVED_SET_NAME By default will be AUTOSAVE
REF_TYPE “P_ID”, “NA_ID”, etc. Based on the profile Key Type
SORT_SEQ Order in the Treeview
IS_CURRENT TRUE if the current item in the Treeview

NOTE: All data will be saved based on the Key Type of the profile. This is done so as to support multiple Key Types at the same time.

  • The data is not saved by profile, so the synchronization for a Key Type will be done on the last active profile using that key type.

The desired behavior when there is more than one Treeview dataset for the same ID Type is to perform a reload when the user switches from one instance to another.

Business Rules

Programmers should note the following Business Rules.

When Parameters Change:

  • From TRUE to FALSE – Delete all SAVED_SET_NAME that have a status of “AUTOSAVE” and replace the value with the current USR_ID
  • From FALSE to TRUE – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with the current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
    – Starts monitoring Dataset tree view changes

When Opening Govern (Before opening Profiles):

  • Starts monitoring Dataset tree view changes if Flag is on

When monitoring Dataset tree view changes:

  • If Active profile changes – Delete All SAVED_SET_NAME equal to “AUTOSAVE” and replace with current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the tree view data
  • If Treeview is replaced (By eSearch / QueryTool / Matix/…); i.e. a Load
    – Delete All SAVED_SET_NAME equal to “AUTOSAVE” for current USR_ID and current REF_TYPE
    – Insert Into USR_SAVED_DATASET based on the Treeview datazzz
  • If an item is added into the Treeview (By eSearch / QueryTool / Matix /…); i.e. Add Or AddAndReposition
    – Insert the new item into USR_SAVED_DATASET
  • If an item is removed from the Treeview (using the X button); i.e. Remove
    – Delete the new item into USR_SAVED_DATASET
  • If the active item changes in the Treeview; i.e. Reposition()
    – Update IS_CURRENT in USR_SAVED_DATASET
NOTE: This is done by setting the current id to -1 and setting the prior id to 0

 

NOTE: Always hide AutoSave SAVED_SET_NAME from saved dataset functions

  • V6.0 (only) – PC_EXTERNAL will need to be maintained at the same time
  • V6.1 – All three (3) tables, PC_EXTERNAL, PM_EXTERNAL, and NA_EXTERNAL are to be removed.

Related Topics

Dataset Treeview Temporary Records

Forms Explorer
Reports Explorer

 

 

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

 

Multimedia

Multimedia

Version 6.1 (In Development)

Overview

The Multimedia OpenForm is used for linking multimedia files to property, name, permit and sales records; for example, building drawings can be linked to a property record, photographs or video files to a complaint, building plans can be scanned and linked to a permit or the property deed to a sales record. PDF documents and unlimited text lines can used as annotations to the file. Each property control OpenForm can create and maintain customized multimedia links. The Multimedia tab can be configured with any number of different OpenForms in order to create a link to the following:

  • Parcel
  • Name
  • Inspection
  • Hearing
  • Permit
  • Workflow
  • Offense
  • License
  • Sale
  • Activity

Multimedia can be recorded by property, name or by a multitude of reference ID’s (Account Number, Sale, Building, Inspection, Split Merge Transaction, Permit, Complaint, and so on.)

For setup information, see Standard Feature Installation of the Multimedia control.

 

NOTE: The Multimedia tab can be found in numerous profiles as it is a general usage form that allows users to attach multimedia files to records as needed.

 

Multimedia Document Types

Govern can support a variety of Multimedia documents. These documents can range from image formats such as .BMP, .TIF, .JPG, to Adobe Acrobat .PDF, or Microsoft Word .DOC files, etc.

Displaying the Image

When a multimedia image document has been linked to the current record, the document will be displayed in the right hand pane when you open the form. Otherwise, click Open Document or doubleclick on the image the Preview pane to display the document. The document will be displayed with the application that is set as the default for viewing the file type that is selected. For example if you have
Microsoft Word installed and you preview a .doc file, Microsoft Word will be launched. Use the controls of the previewing application to close the window and return to the Multimedia tab.

Setup Options
Depending upon the business requirements, through the parameters, the same form controller can be configured with different keys and for different multimedia types.

Technical information

Below is the technical setup and configuration document for the Govern Multimedia Documents custom entity.
See – 101-std-frm-001 Govern 6.0 Multimedia Documents

 

 

101-std-frm-001

 

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