General Application Updates

Using File Servers and Logical Folders for File Import and Export

Previously, functions such as external payroll and EDI required users to set parameters that specified UNC pathnames to folders on a shared local server. Those folders were used to store XML or other “flat files” that are imported, exported, or created by the functions. This prevented the use of these functions in the cloud, where users cannot directly add, delete or access files that are stored on local servers.

Now, you define file servers and logical folders to be used for these functions. For example, you could define a logical folder called EDIDemandInboundData to store EDI inbound data files, and a logical folder called EFTImports to store imported EFT files. These could be on the same or different file servers.

The file server and logical folders can be used for either cloud or on-premises applications:

  • For cloud applications, the file servers might already be defined by the Infor Cloud team, or you can use the File Servers form to add AWS S3 buckets or SFTP servers as file servers. Then use the File Server Logical Folders form to define logical folders on those servers.
  • For on-premises applications, you can define the file servers on the File Servers form. The file servers can be either an FTP/SFTP server, a UNC path to a shared local server, or an AWS S3 bucket. (You can also verify the login credentials on this form.) Then define the folders for each file server on the File Server Logical Folders form.

    If the actual physical folders do not yet exist on the server, you must create them separately.

These file server logical folders must be assigned to authorization groups on the Object Authorization for Group form. Only users in those groups can access the logical folders to add or remove files.

File servers and their logical folders are unique to a specific site; however, you can move logical folders from one file server to another.

On these forms, use the logical folder fields to specify which logical folder to use for each import, export or archive function:

  • 1095 Form Printing Report
  • Bank File Format
  • BOM Bulk Import Parameters
  • BOM Import Builder
  • CARaS Commodity Code Extraction
  • CARaS Customer Address Extraction
  • CARaS Parts Extraction
  • CARaS Ship Via Extraction
  • Demand EDI Parameters - Interface Setup
  • EDI Transaction Load Routine
  • EDI Transaction Unload Routine
  • Electronic File Transfer Imports
  • Electronic File Transfer Mappings
  • External Payroll Interface Input
  • External Payroll Interface Parameters
  • Inventory Parameters
  • Magnetic Media Direct Deposit
  • Mexican SAT Parameters
  • Order Entry Parameters
  • Supply EDI Parameters - Interface Setup
  • Tax Parameters
  • W-2 Electronic Filing

The Logical Folder field lists only folders that you have authorization to access.

A Files button sits next to each logical folder field on these forms. Click the button to open the new File Maintenance form, where you can view the files currently in the specified logical folder or upload, download or remove files from the logical folder. You must have the appropriate permissions.

If you upgrade from a previous version, a script attempts to map your existing file folder structures from the various parameter forms to the new file servers and logical folders structure. For more information about upgrades, see the Installation Guide.

More Forms Use the "Get More Rows in the Current Collection" Button

Previously, this button was enabled only on forms where an IDO handled the collection load. Now it is also enabled on forms where a stored procedure handles the collection load.

Renamed Licenses

Licenses with SyteLine as part of the name have been renamed to remove that portion.

Microsoft Office

We now support the downloaded local copy of Microsoft Office 365, and we also now support Microsoft Office 2016. We do not support the web version of Microsoft Office 365.

Employee, Applicant and Contact Names Can Be Longer

The Last Name field for employees, applicants and contacts has been changed to 30 characters. The full name can now be up to 50 characters.

Recommended Patch Analysis

The Recommended Patch Analysis form has been simplified. Tabs have been removed and replaced with a read-only grid. Machine name and utility server name information has been removed because that information is no longer required for this utility form to work.

Reports

Crystal Reports is no longer supported in any way. We have changed several reports so that they no longer require Microsoft SSRS. You can extend dataview and form reports and create your own, even in multi-tenant cloud. Eventually, SSRS will not be used to generate any reports, and the plan for the future is to only use Mongoose forms and DataViews.

General Form Redesign

The layout of these forms has been enhanced:
  • Items
  • Current Operations
  • Current Materials
  • Job Orders
  • Job Operations
  • Job Materials
  • Projects
  • Project Tasks
  • Project Resources
  • Customers
  • Customer Orders
  • Customer Order Lines
  • Estimates
  • Estimate Lines
  • Estimate Job Orders
  • Vendors
  • Purchase Orders
  • Purchase Order Lines
  • Service Orders
  • Service Order Lines
  • Employees

Workbenches

Previously, Workbenches was an optional module with a separate license. It is now part of the base product and does not require a separate license.

Parent topic: What's New in This Version