Updates for Mongoose System Administrators

This topic describes general updates to the Mongoose framework.

Support for Windows authentication

You can now use Windows credentials for SQL Server authentication, for use during Mongoose installation and configuration. The IDO runtime service must be set to allow a Windows user with SQL permissions.

Express configuration option

We simplified configuration for basic installations, ones where only the base features are needed and the default values are acceptable. This new option allows you to configure Mongoose without needing to decide what components to select.

Single database option for configurations

Driven chiefly by the need to simplify cloud installations, we now offer the option to configure Mongoose using a single database for all metadata. This option includes all form, form templates, objects, and application metadata in a single database.

This option must be selected during initial configuration, using the Configuration Wizard. Once installation is complete, you can then use the same database to configure all database access in the Confguration Manager.

CLI option for system health checks

We added the ability to perform system health checks on a number of Infor Framework services. These health checks can be performed using a Command Line Interface (CLI) option with the Configuration Manager executable file (ConfigManager.exe). See the Configuration Manager help topic "CLI options with Configuration Manager."

List of "widget" forms

We created a Widget Forms form to display a list of the forms that developers and customers have created to be used as "widgets". Such widget forms are typically small and suitable for use in Ming.le pages or as context applications within Ming.le or in other similar scenarios.

Sites column added to license consumption form

We added a Sites column to the grid display on the License Modules per User Connection form. This column is most useful in multi-site setups, where the system administrator wants to monitor which site users are connecting from.

Fully configurable help URL

Previously, the help URL included a hard-coded folder named language, followed by a subfolder name that was configurable based on the currently selected culture (for example, language/en-US). That is still the default setting, and the subfolder name is defined in the Help Sub Dir field on the Language IDs form. You can use the new Override Middle Help URL field on the Language IDs form to specify an alternate folder name that replaces both the hard-coded language folder and the subfolder. For example, you can specify the culture part of the help URL for American English as just en instead of language/en-US. The rest of the help URL is already configurable through the Configuration Manager utility.

Prevention of potential BOD sequencing error

We added a new stored procedure to prevent a potential problem where incoming BODs might arrive out-of-sequence. The new process makes sure that only the latest version of an incoming BOD is processed.

To do this, we added a BOD Information table that collects certain data from every incoming BOD. We also created a new core form (Purge BOD Information) to allow administrators to purge the information in this table either automatically or manually.

Form for identifying license or module required to run forms

When you run a form that is not licensed to you, a warning message appears.

We created a new form, Modules For Form, to help in identifying what license or module is required to run a certain form.

Using existing group authorizations for a new or another existing user

You can copy sets of group authorizations and apply them to new and existing user profiles.

Enhancements to the XML to IDO Wizard

We made a number of enhancements to the XML to IDO Wizard. We added:

  • An option to create Replication Document Outbound metadata.
  • An option to create an Application Event System (AES) OnBODReceive event instead of Replication Document Inbound.
  • New functionality to save an XmlToIdo project template.

Group security for Critical Numbers

To reduce the need to configure each user's access to Critical Number categories or specific Critical Numbers, you can now apply group security permissions.

Changes to Replication Document-associated forms

We merged the Replication Document Attributes form with the Replication Document Elements form, thus putting replication document elements and attributes on the same form. The functionality previously controlled by the Replication Document Attributes form is now contained in the Attributes tab of the Replication Document Elements form.

In addition, we made other changes to the resulting form. The primary change was the addition of a user control version of the XML parser to the form. This enhancement allows a user to click any visible node from the BOD on view in the XML parser display and send the relevant data to the form itself.

Purging Replication Document Inbox and Replication Document Outbox

You can now delete all records marked as processed in Replication Document Inbox and Replication Document Outfox using the new Replication Document Inbox/Outbox Purge Utility form.

XPAB and RSDAO options removed

The smart-client-via-browser (or XBAP) client is now considered obsolete and all related options have been removed.

In addition, all projects related to RSDAO have also been removed.

Assigning a license for an Infor Ming.le administrative user

A mechanism for assigning a predefined license module to an Infor Ming.le administrative user using an AES event is created for this release. A new core AES event, AssignUserToAdminLicenseModule is added, and requires the user name as the parameter. A new process default, AdminLicenseModuleName is also added. The purpose of this process is to set the default license module.