AR – Search to Load Data (101-ar-fea-026)

Accounts Receivable (A/R) Search to Load Feature

Available in Govern Rel. 6.0/6.1

Overview

Selecting a Record Key from the DataSet TreeView will load AR Data, the form also has a feature that allows you to search for keys to load the data. The key is then sent to the TreeView as a Temporary Key to allow the application to recalculate information based on that key.

Demonstration of the Temporary Key

To demonstrate the functioning of a Temporary key in Govern, follow these steps:
Preparatory steps:
  1. Search for a few records to add to the Treeview from the eSearch then open the AR Inquiry form.
  2. Search for a key that contains a field that is of the same type as the profile and is already in the Treeview. It gets selected.
  3. Perform Step 1) but for a key that isn’t in the Treeview already. It gets added, selected, 1st and orange background.
  4. Perform Step 2). the key added by 2) gets replaced by this new one.
  5. Repeat Step 1). notice that the same result and the one added in Step 3) remains.
  6. Perform a search for a key that doesn’t contain a field that matches the Treeview key. The description is based on the Main ID of the key.
  7. Manually remove the temporary key from the Treeview and search for it again. It gets added as Temporary again.

Related Topics

 

 

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

Dataset Treeview Temporary Records

Dataset Treeview Feature – Temporary Records

Overview

The Dataset Treeview Panel contains a list of record keys that, when selected, will send the information to OpenForms which, in turn, will load records accordingly.

Temporary Records

Normally, a user simply searches for record keys and navigates through them to work but some features can load their keys internally without being linked to the Record Keys from the Tree View, for example AR Inquiry and Cash Collection forms. The side effect is that any information normally available outside the form are not refreshed because they are triggered only by a selection in the Tree View, this is the case with Tiles. In order to resolve this issue, these keys are sent to the Tree View but are flagged as “Temporary”. Only one of these keys can appear in the Tree View. The keys are replaced when a new one is introduced; this approach is used so as not to clutter the Tree View with keys that are not part of the user’s workload. In addition these keys can also quickly increase disproportionately. These keys are also not retained when the application is closed.

Business Rules

In order to trigger as many features as possible, the key will be filled with as many ID’s obtained from the database, based on available and missing ID’s from the Temporary Key.

  • First we check to see if we can find IDs from AR_MASTER based on an ordered list of specific ID Types that we get from the Temporary Key. These keys are the same that are needed to add to the Temporary Key afterwards from AR_MASTER.

    From AR_MASTER
    • The ordered ID types are: AR_ID, PP_ID, ST_ACCT_ID, UB_ID, MB_ID,  BR_ID, DC_ID, BT_ID, MV_ID, AC_ID, P_ID, NA_ID 
      • This means that as soon as one key returns records, we stop and take the most recent one.

  • If no AR_MASTER records are found directly, we try to find an AR_MASTER record linked to AR_DETAIL based on specific ordered field types from AR_DETAIL, noting that the IDs taken from AR_MASTER will still be the same as before.

    From AR_DETAIL Expand source
    • the ordered AR_DETAIL Field Types are: ST_ID, INVOICE_NO, PRJ_ID, PM_ID
      • This means that as soon as one key returns records, we stop and take the most recent one.
      • In version 6.1, the content of PM_ID will be a Workflow ID

  • If no NA_ID is found after that for the Real Estate Sub-System, we’ll try to get it from the primary NA_MAILING_INDEX if a P_ID was previously found.

    From NA_MAILING_INDEX

The Temporary Key will be inserted at the top of the Tree View with an Orange background. For example:

  • It is possible that the Temporary Key contains an ID that matches the Profile’s Key Type at this point, but its current Main ID Type is not the same. In that case, we will make this ID Type the main one so as to see the correct description in the Tree View.

Duplicate of an Existing Key

It is possible that after the work is done, the Temporary Key’s main ID exists in the Tree View. If that’s the case, it won’t be added to the Tree View like a Temporary Key, although the ID’s of both will be merged together, it will only be selected.

Context Menu

In the Dataset Treeview, a right click on an item will display and a menu with 3 options:

  1. Remove the current selected item
  2. Remove All items from the Dataset Treeview
  3. Remove All the items except the item where we did a right click on it

If we decide to right click on the panel, only 1 option will show up, allowing the removal of all items from the Dataset Treeview:

Remove

  • The item which we made a right click on will be removed from the Dataset Treeview.
  • If “Dirty”, a confirmation will show up asking you to save the data first.
    • Yes: Save the data and remove the item
      • If there is a validation error on saving, the item will not be removed and the item will remain “dirty”
    • No: Cancels the change and remove the item
    • Cancel: Not remove the item and the item is still “dirty”

Remove All

  • All the items will be removed from the Dataset Treeview.
  • If “Dirty”, a confirmation is displayed asking you to save the data first.
    • Yes: Save the data and remove all the items
      • If validation error on saving, the items will not be removed and the changed item remains “dirty”
    • No: Cancel the change and remove all the items
    • Cancel: Will not remove the items; the item is still “dirty”

DEV NOTE: Currently there is a bug in the techno and the message is displayed twice (2 times).

Remove All But This

  • All items will be removed except the item which we did a right click on in the Dataset Treeview.
  • If “Dirty”, a confirmation will show up asking you to save the data first.
    • Yes: Save the data and remove all the items except the item which we did a right click on it
      • If validation error on saving, the items will not be remove and the changed item is still dirty
    • No: Cancel the change and remove all the items except the item which we did a right click on it
    • Cancel: Will not remove the items and the item remains “dirty”

DEV NOTE: Currently there is a bug in the techno and the message is displayed twice (2 times).

 

Related Topics

Dataset Treeview

Forms Explorer
Reports Explorer

 

 

101-std-fea-049

 

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 – General Connection Parameters

GNA General Connection Parameters

Overview

In the General System Parameters form, you are presented with database details about the currently selected connection key, configuration parameters for controlling how users access the application, and synchronization and refresh parameters for mobile installations.

General Connection Parameters

Database Default Server Type group

In the Database Default Server Type group (A) you will see the database server type of the currently selected connection key.

NOTE: This area is informational and cannot be modified.

Specifying Connection Key Source Folder at Startup

As a time saver users starting up GNA can specify a connection key source folder; i.e. a location for the list of Connection Keys. This feature is useful in multiple database environments where users need to frequently switch between databases. By default GNA will maintain a lock on the location of the last selected Connection Key. The file that the GNA will obtain its list of connection keys from is (File: GovernDABConfig.xml)

Read More...

Database Connection Key parameters

The list of Connection Keys are obtained from the GovernDABConfig.xml file. If an administrator would like to provide an alternate GovernDABConfig.xml file containing Connection Keys, this information can be specified.

Definition File Folder: Type in a new path to the connection keys definition folder, i.e. location of the GovernDABConfig.xml file, or click “…” to browse for a folder.

Organization Parameters

In the Govern New Administration (GNA), it is possible to modify the parameters that were entered at installation. In the Organization Parameters group, you can modify the Organization name.

Organization Name: Enter your organization name. This is the name that appears in the GovernNetConfig.xml document.

User Name Prefix: The User Name Prefix field is used to enter a text string that is added to the beginning of the User ID. This feature allows for backwards compatibility with Govern for Windows. The specified prefix is concatenated with the user name, encrypted, and stored. Since it is appended to the password after a user enters their assigned password, they are not aware of it. The use of this method means that users will never see their real database UserID.

User Name Prefix: If required, enter a prefix into this optional field.

To specify an Organization Name and a User Name prefix…

  1. Select System Parameters > General Installation Parameters…
  2. In the Organization Parameters group, enter an Organization name, and a user name prefix.
  3. Click Save to confirm your changes.

The user must explicitly enable editing for each parcel: When selected the user must click on the Edit icon in the Govern.NET Dataset Treeview before editing a record. By default this option is disabled.

NOTE: This option is designed to minimize errors when selecting a record to edit in Govern. When a record is selected in the Dataset Treeview, a conscious effort must be made to click the Click to Edit icon a second time, and unlock the record for editing.

Mobile Device Parameters

Mobile Device Connection Check Trigger (in ms): After installing a mobile deployment, one of its functions is to continually check the connection to the master database, and compare and update changes to the data.

Connection Check Trigger (in ms): The Connection Check Trigger value determines the length of the interval, in milliseconds, between each check to verify the availability of the connection to the main database. The default value is 1000 milliseconds.

Synchronization Interval (in ms): The value in this field is the interval that will be used to force a synchronization of data between the mobile database and the main system database when Govern.NET’s automatic synchronization option is selected. This option is set on the mobile devices Govern.NET install.

NOTE: For details about Mobile Device configuration, refer to the Govern Mobile user guide.

 

 

103-sy-002

 

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

User Key Dynamic

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.

Related Topics

User Key Dynamics
System Data Dictionary

 

 

101-std-fea-040

 

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