The high contrast skin can be activated by users who experience low vision, color-blindness, or similar visual impairments.

If the high contrast skin is active, LN UI is colored so that all controls comply with the WCAG AA norms for accessibility.

Guideline 1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. For level AA, these exceptions apply:

• Large text: large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
• Incidental: the following text or images of text have no contrast requirement:
  • Text or images of text that are part of an inactive user interface component.
  • Text or images of text that are pure decoration.
  • Text or images of text that are not visible to anyone.
  • Text or images of text that are part of a picture that contains significant other visual content.
• Logotypes: text that is part of a logo or brand name has no minimum contrast requirement.
   

This enhancement: 

• Provides an ability for LX to integrate with Infor Federation Services (IFS) to automate provisioning of users.
• Activates LX exit points during maintenance of LX business roles and business units to publish the SyncSecurityRoleMaster BOD which can be received by IFS as LX-specific roles in addition to the three IFS predefined LX-specific roles: LX-SystemAdministrator (corresponding to LX security type S = LX Security Officer); LX-SystemManager (corresponding to LX security type M = LX Security Manager); and LX-User (corresponding to LX security type U = LX User).
• Enables support for LX receiving an inbound SyncSecurityUserMaster BOD (sent from IFS) and creating or revising the associated LX user (or security manager or security officer). This enhancement also supports creating an IBMi user profile which can then be defined as an LX user (or security manager or security officer).
• Activates LX exit points during maintenance of LX users (and security managers and security officers) to send the ProcessSecurityUserMaster BOD to IFS requesting creation or revision of a user on behalf of LX.
• Automates sending revised LX user authorities to corresponding System i Manager (SiM) tasks which can then be uploaded to System i Workspace (SiW).

TECHNOLOGY & FINANCE: Archiving Finalized Transactions

To support correct archiving in a multicompany structure, the following rules apply:

• Each company must have its own archive company. Companies cannot share an archive company.
• The structure of archive companies must be an exact copy of the live environment.
• A company must keep the same archive company until the end of its lifetime. Once data has been archived, you cannot change the archive company.

If extra archiving capacity is required, it is recommended that you set up...

Improve subfile record loading to optimize for WebTop Grid performance.
Improve subfile loading in PUR500-07 to take advantage of WebTop Grid capabilities.

This enhancement allows the WebTop Grids allow users to personalize list-type screens such as PUR500-07 to display as many records as their presentation allows.  With WebTop Grids, the PUR500 user is no longer limited by the number of records that can be displayed in a traditional green screen subfile screen.

You can maintain all the master data, such as items, business partners, central purchase contracts, general ledger and related data in one company and share this data with the other companies. This master data company can be one of the operational companies, but you can also assign a separate company only to be used for the master data.

The advantages of having a separate master data company are:

• Clarity: Having a single company as master data company is clear for all users.
• Authorization: In general, only a few people in an enterprise can maintain the master data and, particularly for this maintenance, the authorization is important. If one dedicated master data company exists, you can use the company authorization to maintain this authorization very easily.

Present PUR500-07 “folded” Purchase Order Line Entry screen as the default Line Entry screen.

Supply Chain Management Enhancements:

WebTop Grid users can personalize the main Purchase Order Line Entry screen to resequencing columns, sort and filter on data values, change column headings, and other features.

In LX 8.4.2, the PUR500-07 “folded” screen is the default Purchase Order Line Entry screen presented to the user. Users can still access the “unfolded” PUR500-06 screen with limited fields displayed, on request.

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

• It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

• For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

• The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.