308-icloud

Integration – Invoice Cloud

Version 6.0

Overview

Governs’ Invoice Cloud integration provides an invoice presentation / payment solution using Invoice Cloud. With Invoice Cloud integration Govern users have 24/7 access to on-line bills and flexible payment options that include all major credit/debit cards and eChecks.
Invoice Cloud consists of 2 major areas. Batch Functions that can be scheduled to send Billing Information reports to Invoice Cloud and the AR & CC Cash Collection Service.

Requirement

Integration needed with invoice cloud. We need to make a new service that:
1. Allows Payments
2. Allows Payment Reversal
3. Update Paperless status for Mailing Index
4. GetArBalances
See AR/CC Web Service

The following actions are also needed:
1. Generate a Summary Account Balance and send it to an FTP
2. Generate a Detail Account Balance (bill) and send it to an FTP

Tax & UB Bill

Tax and Utility Billing PDF Bill

Account Balance Extract

Account Balance Extract is created and push to the FTP.
Work Order for Code: WALGOL1202
Crystal reports that show the balance for each NA_ID

Batch Processes

Consists of 2 batch process that generate reports in CSV format.

1) Batch process – Invoice Cloud Balance :
UI : ComboBox SubSystems (only RE, PP, UB)
Nb. Activity days Add to the report all entries in AR_Master having activities (all activities in AR_DETAIL except payment from InvoiceCloud) in the X last days of activity.

2) Batch Process – Invoice Cloud Invoice :
. UI : ComboBox SubSystems (only RE, PP, UB) ComboBox SubSystems (only RE, PP, UB)

a) subsystems : RE, PP :
UI : Year, Installment
File Name to generate : XXXXXX_RE_TimeStamp.csv or XXXXXX_PP_TimeStamp.csv

b) Subsystem : UB :
UI : ComboBox : Posting ID – Posting Date (From table UB_POST_MASTER)
File Name to generate : XXXXXX_UB_TimeStamp.csv

The Total Billed should be the Sum of Amounts from AR_DETAIL where type = ‘INV’ and having Creation_Date = Posting_Date

Supporting Documents

Click on the links below to view the .PDF document.

Right-click on the links below to down the view the .PDF document.

To download the Excel files below, either right click on the link and select “Save Link As…” from the menu, or click directly and select the option to open in Microsoft Excel.

To download the .CSV files below, right click on the link and select “Save Link As…” from the menu. The file may then be opened in an application like Microsoft Excel.

SQL for the INVOICE

SELECT "AR_MASTER"."SUB_SYSTEM", "AR_MASTER"."YEAR_ID", "AR_SUMMARY"."INSTALLMENT", "AR_SUMMARY"."AR_ID", "NA_MAILING_INDEX"."NA_ID", "NA_NAMES"."FREE_LINE_1", "NA_NAMES"."STREET", "NA_NAMES"."CIVIC", "NA_NAMES"."PRE_DIR", "NA_NAMES"."S_SUFFIX", "NA_NAMES"."POST_DIR", "NA_NAMES"."SEC_ADD_IND", "NA_NAMES"."UNIT", "NA_NAMES"."CITY", "NA_NAMES"."STATE", "NA_NAMES"."ADD_LINE_A", "NA_NAMES"."ZIP_POSTAL", "NA_NAMES"."EMAIL", "NA_NAMES"."NAME_2", "AR_MASTER"."SORT_KEY", "AR_SUMMARY"."PRINCIPAL", "NA_MAILING_INDEX"."SUB_SYSTEM", "NA_MAILING_INDEX"."PRIMARY_INDEX"
FROM (("Waltham"."dbo"."AR_MASTER" "AR_MASTER" INNER JOIN "Waltham"."dbo"."AR_SUMMARY" "AR_SUMMARY" ON "AR_MASTER"."AR_ID"="AR_SUMMARY"."AR_ID") LEFT OUTER JOIN "Waltham"."dbo"."NA_MAILING_INDEX" "NA_MAILING_INDEX" ON ("AR_MASTER"."P_ID"="NA_MAILING_INDEX"."REF_ID") AND ("AR_MASTER"."SUB_SYSTEM"="NA_MAILING_INDEX"."SUB_SYSTEM")) LEFT OUTER JOIN "Waltham"."dbo"."NA_NAMES" "NA_NAMES" ON "NA_MAILING_INDEX"."NA_ID"="NA_NAMES"."NA_ID"
WHERE "NA_MAILING_INDEX"."PRIMARY_INDEX"=-1 AND "NA_MAILING_INDEX"."SUB_SYSTEM"='UB'
ORDER BY "AR_SUMMARY"."AR_ID"

SQL for the BALANCE

SELECT "AR_MASTER"."SUB_SYSTEM", "AR_MASTER"."YEAR_ID", "AR_SUMMARY"."INSTALLMENT", "AR_MASTER"."AR_ID", "AR_SUMMARY"."AR_ID", "NA_MAILING_INDEX"."NA_ID", "NA_MAILING_INDEX_1"."NA_ID", "AR_SUMMARY"."BALANCE", "NA_MAILING_INDEX"."SUB_SYSTEM"
FROM (("Waltham"."dbo"."AR_MASTER" "AR_MASTER" INNER JOIN "Waltham"."dbo"."AR_SUMMARY" "AR_SUMMARY" ON "AR_MASTER"."AR_ID"="AR_SUMMARY"."AR_ID") LEFT OUTER JOIN "Waltham"."dbo"."NA_MAILING_INDEX" "NA_MAILING_INDEX" ON ("AR_MASTER"."P_ID"="NA_MAILING_INDEX"."REF_ID") AND ("AR_MASTER"."SUB_SYSTEM"="NA_MAILING_INDEX"."SUB_SYSTEM")) LEFT OUTER JOIN "Waltham"."dbo"."NA_MAILING_INDEX" "NA_MAILING_INDEX_1" ON ("AR_MASTER"."UB_ID"="NA_MAILING_INDEX_1"."REF_ID") AND ("AR_MASTER"."SUB_SYSTEM"="NA_MAILING_INDEX_1"."SUB_SYSTEM")
WHERE "NA_MAILING_INDEX"."SUB_SYSTEM"='RE' AND "AR_MASTER"."YEAR_ID"=2012 ORDER BY "AR_MASTER"."AR_ID", "AR_SUMMARY"."INSTALLMENT"

Installation of Web Services

Invoice Cloud Web Service (Release 5.1)

To install the following are the installation steps for the Invoice Cloud Web Service:

  1. Deploy the Release 5.0.9 of the Resources Files.
  2. Install and configure the WCF Accounts Receivable API [Filename: WCFAccountsReceivableAPI.zip].
  3. Modify the web.config file to use the GoverNetConfig.xml of the deployment [Location: In the root of the specific deployment folder]
  4. When installing Release 5.1 of the web service, administrators will need to manually create the following table in (Table: NA_NAMES: WEBPROFILEACCESSRT (Smallint, Allows Null). This field was added to provide support for the eGov and is used in the business rules of the Names.

Verification of the Service

The WcfTestClient.exe application is used to test the web service. This application can be obtained on the Govern FTP site or from Govern Technical Support: WCF Test Application.zip. For additional details regarding testing Govern Web Services

What’s New!

Release 6.0
The two (2) Govern batch processes that are associated with the Invoice Cloud process for Real Property and Personal Property modules have been modified to allow them to identify required InvoiceTypeID’s that match with AR Cycle codes for Real Property (RE) and Personal Property (PP). – Release 1703.06

Prior to release 6.0 of the Govern Web service, manual changes were required to be made during the installation of the Invoice Cloud Web Service:

  • Modify the web.config to use the GovernNetConfig.xml file located in the deployment root directory.
  • Create (Table: NA_NAMES.WEBPROFILEACCESSRT), with properties set to (smallint, allow NULLS).

The above steps are no longer required, they are automatically created when the Database Verification process is run in the Govern New Administration (GNA).

Related Topic(s)

Govern API and Service

 

 

308-icloud

 

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

 

DeployEZ Pre-release Versions

DeployEZ Pre-release Versions

Overview

New implementations and upgrades that are installed by Govern Professional Services (PS) and upgrade teams will often install pre-release versions of Govern. Pre-release versions of the Govern application can contain features that are in the current branch for early testing in our clients’ production environments. Although still in active development, they are supported. Users of pre-release versions will note that some features encountered may be subject to change while they are designated as prerelease.

Accessing Govern Pre-release versions

Pre-release versions can be accessed in through a setting in the DeployEZ parameters screen.

To view pre-release versions of Govern…

  1. Open DeployEZ.
  2. If you have the Always ask before opening this file option selected, click Run to allow the update.
  3. DeployEZ will open to the Main Menu.
  4. In the DeployEZ Main Menu, double click on the large green DeployEZ icon on left hand side of the window.
  5. The DeployEZ Parameters screen will be displayed.
  6. Under the General tab, you will see the option for Include pre-releases.
  7. Click to select this checkbox.
  8. To save your setting, click Save.
  9. Click Exit to close the Parameters screen and return to the Main Menu

Viewing Pre-release Versions for Deployment

Once this Include pre-releases option has been enabled, you will be able to view and download pre-release versions of Govern for your deployment packages. Follow the steps required to download binaries from Azure DevOps.

To view the pre-release versions…

  1. In the Main Menu screen, click to select one of the download options.
  2. Click Next.
  3. In the List of Found Applications screen, you will note Govern build versions with a -pr suffix; these are pre-release versions.
  4. Click to select the required build version(s).
  5. To download the selected version(s), click Next.

When the selected versions have been downloaded, you will be returned to the Main Menu screen. You can then proceed to creating your deployment using the standard steps.

 

Related Topics

DeployEZ

 

 

deployez_prerelease_versions

 

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

DeployEZ Pre-release Versions

DeployEZ Pre-release Versions

Overview

New implementations and upgrades that are installed by Govern Professional Services (PS) and upgrade teams will often install pre-release versions of Govern. Pre-release versions of the Govern application can contain features that are in the current branch for early testing in our clients’ production environments. Although still in active development, they are supported. Users of pre-release versions will note that some features encountered may be subject to change while they are designated as prerelease.

Accessing Govern Pre-release versions

Pre-release versions can be accessed in through a setting in the DeployEZ parameters screen.

To view pre-release versions of Govern…

  1. Open DeployEZ.
  2. If you have the Always ask before opening this file option selected, click Run to allow the update.
  3. DeployEZ will open to the Main Menu.
  4. In the DeployEZ Main Menu, double click on the large green DeployEZ icon on left hand side of the window.
  5. The DeployEZ Parameters screen will be displayed.
  6. Under the General tab, you will see the option for Include pre-releases.
  7. Click to select this checkbox.
  8. To save your setting, click Save.
  9. Click Exit to close the Parameters screen and return to the Main Menu

Viewing Pre-release Versions for Deployment

Once this Include pre-releases option has been enabled, you will be able to view and download pre-release versions of Govern for your deployment packages. Follow the steps required to download binaries from Azure DevOps.

To view the pre-release versions…

  1. In the Main Menu screen, click to select one of the download options.
  2. Click Next.
  3. In the List of Found Applications screen, you will note Govern build versions with a -pr suffix; these are pre-release versions.
  4. Click to select the required build version(s).
  5. To download the selected version(s), click Next.

When the selected versions have been downloaded, you will be returned to the Main Menu screen. You can then proceed to creating your deployment using the standard steps.

 

Related Topics

DeployEZ

 

 

deployez_prerelease_versions

 

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

Govern Release Notes

Govern Release Notes

Overview

The Govern for OpenForms Release Notes are reports that are generated by the system that is responsible for OpenForms builds. Release Notes reports are a listing of product enhancements and bug corrections for an indicated release. In the past the reports were a MIME Encapsulation of Aggregate HTML or MHTML format.

UPDATE Presently, Govern Release Notes can be found through the DeployEZ application. As an administrator, when you are downloading Govern binaries, links to view associated release notes will be displayed. It will be necessary to ensure that you are updated to the latest version of DeployEZ.

Configuration

There is no configuration required for viewing Release Notes, only ensure that you are using the latest version of the DeployEZ application.

Viewing Govern Release Notes

In order to view the release notes you may need to update to the latest version of DeployEZ.

NOTE: The following steps are intended for users with administrator level access.

Updating to the latest version of DeployEZ

To update to the latest version of DeployeEZ…

 

Read More...
  1. Go to the DeployEZ URL at deployez.msgovern.com.
  2. On the page, click Install; this will display the Save As
  3. Select a location to save the DeployEZ.application file to. Note the location for later retrieval.
  4. In the folder that the file was saved into, double click on the DeployEZ.application file.
  5. If you encounter the Open File – Security Warning, click Run.

After running the application, the updated DeployEZ interface will be displayed.

User Interface

Viewing Govern Release Notes

As release notes are released, when applicable, with an update to the application, they are viewed in the screen that follows the selection of either of the two (2) options to download binaries:

  • Download binaries from Azure DevOps
  • Download binaries from a directory

To view the links to Release Notes…

  1. In the Main Menu, select one of the download options for binaries.
  2. Click Next.
  3. In the list of Found Applications screen, you will see the option to import the Latest Version.
  4. Hover your pointer over the list of versions to display a What’s new
  5. When your pointer is over the version, slide it to the What’s new link; click the link.
  6. The Release Notes screen will be displayed.
NOTE: You may encounter a 3-Letter Customer Code warning screen. This screen is an indication that Customer Code field in the DeployEZ settings is empty. To learn more about this warning and resolve it, follow the steps in the Completing 3-Letter Customer Code Settings section below.
  1. Click OK to proceed
  2. The Release Notes window is displayed.

Release Notes Window

The window that displays the release notes is presented with options for viewing the notes and or printing them. In the release notes window, there are buttons and parameters that allow you to view the information, reformat the on-screen presentation, search the content, zoom in or out, or print.

Release Notes Window Features

Along the top of the Release Notes window is the ribbon area containing the following:

What’s new in <Release Version> – This is the current build number of the application.

…since version <Last Version> – In this field is the last version of the application that these notes will refer to. This field serves as a filter and the content can be changed.

For example:

The latest downloaded version is 6.1.1811.1893. You want to see what has been introduced or corrected since the last version that you’re using which might be v6.1.1802. You would enter 6.1.1802 into the …since version field and click Show.

 

[ ] Group by version – Click this check box to view the notes by build numbers rather than by the default module.

[ Show ] – After making a modification to the …since version field, click show to refresh the content.

[ Print ] – Click print to display the content of the Release Notes window. This will display the print dialog window for the Windows printer that you have access to.

Along the bottom of the Release Notes window are the following options:

Find – Click the magnifying glass icon to display a text find field. Enter a text string to search for in the notes.

[v]  – Click the down arrow to display additional search functions

Match whole word only – Select this ,option match the whole word and not variations.

Match case – When you want to make a search that the case of the letter is relevant, click to select this option.

Display Modes

The information within the Release Notes window can be display in three (3) different modes:

Page Mode – The content is displayed in a “spread”, i.e., information is presented in 2 columns

Two Page Mode – This mode is similar to the Page Mode, but a frame is placed around each of the pages.

Scroll Mode – The Scroll Mode is the default mode; the content is presented as one scrollable column.

Zoom Options

[ – ] Decrease Zoom – To decrease the size of the text, i.e., zoom out, click the [–].

[ + ] Increase Zoom – Click [+]. to increase the size of the text, i.e., zoom in.

Zoom Slider – You can also use the scroll slider to manually zoom in or out.

Customer Code Warning

When the 3-letter customer code setting has been completed, the release notes will be filtered, and you will see the notes that are relevant to you as a client. This warning does not stop you from viewing all release notes, only the ones that are filtered for your customer code.

This will not stop you from viewing all Release Notes., rather the notes will not be filtered, and release notes will be displayed.

Completing 3-Letter Customer Code Settings

To avoid encountering the Customer Code warning when viewing release notes, you will need to complete the Customer 3-Letter Code field in the DeployEZ settings. The 3-Letter Code is available in all client databases, but because DeployEZ can handle multiple databases situations may arise where the code has not been entered in a secondary or tertiary database.

NOTE: To complete this section, you will need to know what your three (3) letter customer code is. If you do not know this code, contact customer support for assistance.

To complete the Customer Code setting…

  1. In the DeployEZ interface, double click on the large DeployEZ logo
  2. In the DeployEZ Parameter screen, locate the Customer Code field.
  3. Click in the field and enter your 3-letter customer code; note that the field is not case sensitive.
  4. Click Save.
  5. Click Exit to return to the main screen.

Once the above steps have been completed, you will no longer be presented with the Customer Code Warning.

 

 

 

Older Notes

Read More...

The following Release Notes reports are a listing of product enhancements and bug corrections for the indicated release. The reports are in MIME Encapsulation of Aggregate HTML or MHTML format. This means that the content of the MHTML file is encoded as if it were an HTML e-mail message.

These release notes are available for the following releases. Click on the link to download the report that corresponds with the release that you are interested in.

NOTE: When you click on any of the links below, you will be presented with the option to either open the file with an application that support MHTML documents, typically Internet Explorer, the Microsoft MHT Viewer, or you can save the file away for viewing at your convenience. Internal access to TFS is required to access Release Notes reports with embedded links. If you do not have internal access to TFS, you will need to contact Govern Customer Support and open a ticket stating the TFS # that you require additional information about.

 

Download MHT Viewer

Click here to download an MHT Viewer that allows you to read .mht files.

 

Related Topics

DeployEZ

 

 

release_notes

 

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

Govern Release Notes

Govern Release Notes

Overview

The Govern for OpenForms Release Notes are reports that are generated by the system that is responsible for OpenForms builds. Release Notes reports are a listing of product enhancements and bug corrections for an indicated release. In the past the reports were a MIME Encapsulation of Aggregate HTML or MHTML format.

NEW Presently, Govern Release Notes can be found through the DeployEZ application. As an administrator, when you are downloading Govern binaries, links to view associated release notes will be displayed. It will be necessary to ensure that you are updated to the latest version of DeployEZ.

Configuration

There is no configuration required for viewing Release Notes, only ensure that you are using the latest version of the DeployEZ application.

Viewing Govern Release Notes

In order to view the release notes you may need to update to the latest version of DeployEZ.

NOTE: The following steps are intended for users with administrator level access.

Updating to the latest version of DeployEZ

To update to the latest version of DeployeEZ…

 

Read More...

  1. Go to the DeployEZ URL at msgovern.com.
  2. On the page, click Install; this will display the Save As
  3. Select a location to save the DeployEZ.application file to. Note the location for later retrieval.
  4. In the folder that the file was saved into, double click on the DeployEZ.application file.
  5. If you encounter the Open File – Security Warning, click Run.

After running the application, the updated DeployEZ interface will be displayed.

User Interface

Viewing Govern Release Notes

As release notes are released, when applicable, with an update to the application, they are viewed in the screen that follows the selection of either of the two (2) options to download binaries:

  • Download binaries from Azure DevOps
  • Download binaries from a directory

To view the links to Release Notes…

  1. In the Main Menu, select one of the download options for binaries.
  2. Click Next.
  3. In the list of Found Applications screen, you will see the option to import the Latest Version.
  4. Hover your pointer over the list of versions to display a What’s new
  5. When your pointer is over the version, slide it to the What’s new link; click the link.
  6. The Release Notes screen will be displayed.
NOTE: You may encounter a 3-Letter Customer Code warning screen. This screen is an indication that Customer Code field in the DeployEZ settings is empty. To learn more about this warning and resolve it, follow the steps in the Completing 3-Letter Customer Code Settings section below.
  1. Click OK to proceed
  2. The Release Notes window is displayed.

Release Notes Window

The window that displays the release notes is presented with options for viewing the notes and or printing them. In the release notes window, there are buttons and parameters that allow you to view the information, reformat the on-screen presentation, search the content, zoom in or out, or print.

Release Notes Window Features

Along the top of the Release Notes window is the ribbon area containing the following:

What’s new in <Release Version> – This is the current build number of the application.

…since version <Last Version> – In this field is the last version of the application that these notes will refer to. This field serves as a filter and the content can be changed.

For example:

The latest downloaded version is 6.1.1811.1893. You want to see what has been introduced or corrected since the last version that you’re using which might be v6.1.1802. You would enter 6.1.1802 into the …since version field and click Show.

 

[] Group by version – Click this check box to view the notes by build numbers rather than by the default module.

[ Show ] – After making a modification to the …since version field, click show to refresh the content.

[ Print ] – Click print to display the content of the Release Notes window. This will display the print dialog window for the Windows printer that you have access to.

Along the bottom of the Release Notes window are the following options:

Find – Click the magnifying glass icon to display a text find field. Enter a text string to search for in the notes.

[6]  – Click the down arrow to display additional search functions

Match whole word only – Select this ,option match the whole word and not variations.

Match case – When you want to make a search that the case of the letter is relevant, click to select this option.

Display Modes

The information within the Release Notes window can be display in three (3) different modes:

Page Mode – The content is displayed in a “spread”, i.e., information is presented in 2 columns

Two Page Mode – This mode is similar to the Page Mode, but a frame is placed around each of the pages.

Scroll Mode – The Scroll Mode is the default mode; the content is presented as one scrollable column.

Zoom Options

[ – ] Decrease Zoom – To decrease the size of the text, i.e., zoom out, click the [–].

[ + ] Increase Zoom – Click [+]. to increase the size of the text, i.e., zoom in.

Zoom Slider – You can also use the scroll slider to manually zoom in or out.

Customer Code Warning

When the 3-letter customer code setting has been completed, the release notes will be filtered, and you will see the notes that are relevant to you as a client. This warning does not stop you from viewing all release notes, only the ones that are filtered for your customer code.

This will not stop you from viewing all Release Notes., rather the notes will not be filtered, and release notes will be displayed.

Completing 3-Letter Customer Code Settings

To avoid encountering the Customer Code warning when viewing release notes, you will need to complete the Customer 3-Letter Code field in the DeployEZ settings. The 3-Letter Code is available in all client databases, but because DeployEZ can handle multiple databases situations may arise where the code has not been entered in a secondary or tertiary database.

NOTE: To complete this section, you will need to know what your three (3) letter customer code is. If you do not know this code, contact customer support for assistance.

To complete the Customer Code setting…

  1. In the DeployEZ interface, double click on the large DeployEZ logo
  2. In the DeployEZ Parameter screen, locate the Customer Code field.
  3. Click in the field and enter your 3-letter customer code; note that the field is not case sensitive.
  4. Click Save.
  5. Click Exit to return to the main screen.

 

 

Older Notes

Read More...

The following Release Notes reports are a listing of product enhancements and bug corrections for the indicated release. The reports are in MIME Encapsulation of Aggregate HTML or MHTML format. This means that the content of the MHTML file is encoded as if it were an HTML e-mail message.

These release notes are available for the following releases. Click on the link to download the report that corresponds with the release that you are interested in.

NOTE: When you click on any of the links below, you will be presented with the option to either open the file with an application that support MHTML documents, typically Internet Explorer, the Microsoft MHT Viewer, or you can save the file away for viewing at your convenience. Internal access to TFS is required to access Release Notes reports with embedded links. If you do not have internal access to TFS, you will need to contact Govern Customer Support and open a ticket stating the TFS # that you require additional information about.

 

Download MHT Viewer

Click here to download an MHT Viewer that allows you to read .mht files.

 

release_notes

 

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 – Batch Process Definition Editor

Batch Process Definition Editor

Version 6.x | Version 5 and less

Overview

The GNA Batch Process Definitions editor is used to define how you want your batch processes to appear and run in Govern. This includes setting up your batch processes, configuring each process, associating one or multiple reports, and synchronizing the batch process definitions and adding permissions. When complete, the batch processes are displayed in Govern.
This procedure has two major steps:

  • Configuring Batch Process Definitions
  • Adding Batch Processes Definition to Govern.
  • Configuring Sequential Batch Processes (101-std-fea-046)
  • Configuring Sequential Batch Processes (101-std-fea-046)

 

Read More...

Configuration

Configuring Batch Process Definitions

Configuring Batch Process Definitions describes the following topics; locate the appropriate sections on this page:

  • User Interface
  • Defining a Batch Process
  • Defining the Transaction Type
  • Defining the Transaction Mode
  • Adding a Report
  • Deleting a Batch Process Definition

Batch Process Definition – User Interface

This section provides a tour of the Batch Process Definitions UI. The interface is comprised of a treeview (left hand side), the definition form (main central area), and a secondary window for creating the menus and submenus or categories.
To access the Batch Process Definitions form:

  1. Launch Govern New Administration (GNA).
  2. Select Batch Process > Definitions.

Once you create menus and define batch processes, the selected items are listed in a treeview on the left of the form. You can display or hide the treeview according to your preference.

About Batch Process Definitions

You can view, add, or modify a batch process definition, as described later in this section.
To display or hide the English and French long and short descriptions, click on the arrow beside the text box at the top of the form.

About the Menu Manager

The Menu Manager form is used for creating the menus and submenus for organizing your batch process definitions in Govern.NET.
To access the Menu Manager

  1. Launch Govern New Administration (GNA).
  2. Select Batch Process > Definitions.
  3. Click the ellipsis button beside the Category text box.

If categories are already created, they are listed on the left. You can expand a category to view secondary levels if they exist. The name of selected menu is displayed on the right. You can expand the name to view the English and French short and long descriptions.

Defining a Batch Process

Use the following process to name the definition and to associate it with a Govern Batch process.

NOTE: You need to define the processes under the category to which they are assigned and will appear in Govern.

To define a Batch Process:

  1. Select the category where you are defining the process as described under Selecting a Category for the Batch Process. The batch processes already defined for the category are displayed in the treeview on the left.
  2. Click the New button.
  3. Enter a code for the new batch process definition. This is a required field.
  4. Select a Govern batch process from the Process drop-down list. This is a required field.
  5. Enter a name for the record in the text box at the top right. This is automatically added to the English Long Description field.
  6. Click the button to the left of the text box where you entered the name. This expands a menu with additional descriptions.
  7. Add an English Short Description and French Short and Long Description as required. These fields are optional.
  8. Click the Save button to add the category to the menu.
    If you click the New button without saving your modifications, a confirmation message appears:

Defining the Transaction Type
The Govern batch processes can be run synchronously or asynchronously. If they are run synchronously, they are run on the same server. If run asynchronously they are run on multiple servers at the same time.
Select Synch or Asynch as required. For processes with multiple transactions, it is recommended to use asynchronous processing as this spreads the load over multiple servers and makes for faster processing time.
Pool #: For Asynchronous processes only, enter the maximum number of transactions to be handled by the client servers at any one time.
This works as follows: If you are running asynchronous batch processing, there is one master server that manages all the transactions and is responsible for sending them to the client servers. The value In the Pool # field indicates the maximum number of transactions to send out by the master server at any one time.
Scenario: Running a Batch Process Asynchronously
The following scenario illustrates how asynchronous batch processing works.
The parameters are as follows:

  • Master server: one
  • Client servers: five
  • Transactions: 50,000
  • Pool #: 50

The master server sends out the first 50 transactions to the client servers. Each server is responsible for ten transactions. As soon as a server completes one transaction, the master server sends it another. This continues until all transactions have been processed. However, there are never more than 50 transactions being handled by the client servers at any given time.

Defining the Transaction Mode

Select one of the following transaction modes for the process.

  • Break If One Transaction Failed: the process terminates when the transaction fails.
  • Roll Back If One Transaction Failed: the process terminates when a transaction fails and all the transactions that were completed are cancelled. Computations are returned to the starting point.
  • Continue If One Transaction Failed: Continue to run the process even if a transaction fails.

Adding a Report

Use the following procedure to associate one or more reports with the selected batch process.
To add a report: to the batch process:

  1. Launch the Batch Process Definitions form.
  2. Select the category for the process as described under Selecting a Category for the Batch Process.
  3. Select the batch process from the treeview on the left.
  4. Click Add Reports.
  5. Select one or more reports from the Choose the Reports menu.
    TIP: You can select multiple reports using the left mouse button.
  6. Click Select Reports.

The selected reports are displayed in the List of Reports text box. The parameters for the report are displayed in the Report Parameters list box.
The List of Parameters text box displays the parameters that can be included in the report and that can be used to build an external report; for example, these could include Date To and Date From fields. The purpose is to give you the exact reference and wording of these fields.

Deleting a Batch Process Definition

To delete a batch process:

  1. Launch the Batch Process Definitions form.
  2. Select the category for the process as described under Selecting a Category for the Batch Process.
  3. Select the batch process from the treeview on the left.
  4. Click the Delete button.

Adding Batch Processes Definition to Govern

When you have defined your batch processes, you need to add them to Govern.NET. In order to do this, you need to launch the Govern Security Manager and synchronize your new processes between GNA and Govern. Then, you need to assign access permissions.

Synchronizing Batch Process Definitions

When you have synchronized your new batch process definitions, they appear on the Govern.NET menu.
To synchronize the new batch processes:

  1. Launch the MSGovern Security Manager (GSM).
  2. Select your database connection key.
  3. Right-click on Applications and select Synchronize menu from the dropdown list. A confirmation message appears.
  4. Click Yes on the confirmation message.

Permissions and Batch Processes

Use the following procedure to assign access permissions to the new batch process definitions. You can grant permissions by profiles and grant permissions to the Batch Process Editor application in Govern Administrator.

  1. Launch the MSGovern Security Manager (GSM).
  2. Select your database.
  3. Expand Applications > MSGovern.NET > Batch Process > Batch Process.
  4. Continue to expand the menus until you are the level where you want to grant permission.
  5. Right-click on the item that you want to secure.
  6. Define the permissions and exclusions as required and as described in the Govern Security Manager.

What’s New

 

Related Topics

Govern New Administration (GNA)
Batch Processing in OpenForms

 

 

103-ed-013

 

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

 

Govern DeployEZ

111-(ico)-DEZ-[v6.0].png  Govern DeployEZ

Overview

Govern DeployEZ is used for installing the applications, resource files, custom controls, and Help files required for the Govern OpenForms Product Suite, in other words for installing everything that you need for your deployment.

With Govern DeployEZ, you can:

  • Maintain all the deployments required by your organization from one central location on a Web server.
  • Install all administrative and user applications, in the Govern OpenForms Product Suite from this location.
  • Create customized deployment packages to meet the requirements of all your end-users and system administrators.
  • Maintain multiple versions of the same applications to meet the different needs of your organization, such as testing and production.
  • Roll back to an earlier version easily and seamlessly.
  • Ensure that only one version of a deployment is created at a time with the automatic lock.
  • For the overview document see 111-Install-DeployEZ

 

Read More...

 

Documentation

Documents related to the Govern DeployEZ application include the following:

Govern DeployEZ
This document describes how to install, uninstall, and configure Deploy EZ. It provides the step-by-step procedures for Creating a new deployment and updating an existing one.
See 111-all-deployez -GovernDeployEZ-(man)-[v6.0].

Steps to Follow When the Update is Complete

Perform the following steps when the new deployment is complete, but before making the applications available to the users.

  1. Run a Database Verification.
    This step verifies that the stored procedures are valid, it verifies the database tables and ensures that there are no errors in the database structure. It rebuilds the user and system validation table and verifies the table indexes. Refer to the Govern New Administrator (GNA) documentation for further details.
  2. Launch the Govern Scheduler and restart the Scheduler Service. Ensure that no one is running a scheduled batch process when you perform this step. The Scheduler Service automatically checks for new batch process and updates the existing ones at startup. It automatically updates the Govern Scheduler application. Refer to the Govern Scheduler guide for further details.
  3. Define the Report Configuration parameters in GNA. See the following section.

Downloading Reports

To download the Govern standard reports for your deployment:

  1. Launch DeployEZ.
  2. Create a new deployment or update an existing one.
  3. For this deployment ensure that the Govern Standard Reports option is selected.
  4. When the deployment is complete you can verify the following folders in the Deployments folder:
    Reports: The latest reports are extracted from a zip file and loaded to this folder.
    Binaries > REPORT: This folder contains a sub-folder for each release and version that you have downloaded. The reports that downloaded with each version are found in the sub-folder
  5. Launch GNA.
  6. Select Parameters > General Settings Editor.
  7. Select Report from the Registry Filter drop-down list.
  8. Ensure that the patch is correctly set in the Standard Report Path for Crystal Reports or SRSS accordingly.

Videos (Restricted – Internal Access Only)

This video provides an overview of Govern DeployEZ.– Short tutorial for first time users.
The video will open in a separate tab.

  • Getting Started with DeployEZ – For first time users.
  • Installing DeployEZ – Learn how to install the Govern Deploy EZ application.
  • Configuring DeployEZ – Learn how to configure Govern Deploy EZ for your deployments.
  • Creating a Deployment – Learn how to create a Govern OpenForms deployment with DeployEZ
  • Updating Deployments – Learn how to update an existing deployment
  • Uninstalling – Learn how to uninstall, reinstall, or roll back a Govern OpenForms deployment.
NOTE: If you are changing your deployment server or uninstalling your current deployment, ensure that you remove the configuration file. Verify the configuration path in the Govern DeployEZ 6.0 guide.

Installation Notes

System Requirements Release 6.0
Installing DeployEZ
Uninstalling DeployEZ

Troubleshooting

Reinstalling DeployEZ

You may want to reinstall Deploy EZ if you are changing the Deployment Server or the deployment path. In order to do this, you must completely uninstall Deploy EZ.

Uninstalling DeployEZ

Instructions for completely uninstalling Deploy EZ are provided in the following link.
Uninstalling Deploy EZ

NOTE: The paths for uninstalling certain files are different depending on whether you installed Deploy EZ release 6 or release 5.1 or 4.7.I

 

See Also

Download Govern Pre-release Versions

Release Notes

Govern

 

What’s New

Download Govern Pre-release Versions

Pre-release versions of the Govern application can contain features that are in the current branch for early testing in our clients’ production environments. Although still in active development, they are supported. These versions can be downloaded for creating deployments. Click here for details.

Govern Release Notes

Govern Release Notes can now be found through the DeployEZ application. As an administrator, when you are downloading Govern binaries, links to view associated release notes will be displayed. It will be necessary to ensure that you are updated to the latest version of DeployEZ. Click here for details.

Govern DeployEZ has a whole new look and feel compared to version 5.1 and prior. It is now a ClickOnce application. It is maintained on a Web server and installed from a Web link. Whenever you launch the application from your computer, a verification is made, and if a more recent version exists, it is used. This ensures that all users have the latest version and all the latest features of DeployEZ.

DeployEZ is not tied to any one Govern OpenForms release. You can use it to install any version of any application. When creating a deployment directory for Govern DeployEZ, you are required to use the UNC format. If you try to enter a drive name in a mapped drive, an error occurs and you are unable to continue:
[Version 6.0.0.58] Prior to this version a folder called MS Govern was created in the deployment server root directory. This folder is no longer needed and can be deleted.

 

 

111-all-deployez

 

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