| Set up Web UI to Connect to an Infor ERP LN Server |  |
| Note For details on how to configure ERP connections based on Federation Services, see Configuring Federation Services for ERP LN with Web UI. Infor ERP administration pages This section describes the administration pages to set up the Web UI to connect to an Infor ERP LN server. Points of attention The Configure an Infor ERP LN Environment section is mandatory. Because of performance reasons, we strongly advice that you run the actions described in the Offline/Online Form Cache Initialization and Stand-alone Form Cache Initialization sections. These sections are only applicable if you use BaanIV, Baan5, or Infor Enterprise Server 8.4.2 or lower. The other sections are optional. Refer to Appendix C, "Prerequisites for the Infor ERP LN Server" to check the requirements of your Infor ERP LN Server. Configure an Infor ERP LN Environment Use the Infor ERP LN Web UI Administration Console to specify configuration settings for one or more Infor ERP LN Environments. For each environment you must specify various settings, such as the host name and BSE directory where the environment resides. The configuration settings are stored on the web server. Therefore, all end users can use this configuration. Start the Web UI Administration Console as follows: http://<hostname>:<port>/<webtop-root>/servlet/admin Enter the administrator password. Use the password specified during deployment of Web UI. If the password was not changed, the password is `webtop`. In the Infor ERP LN Web UI Administration pane, select Infor ERP > Infor ERP Environments. The Manage Infor ERP Environments page is displayed. On this page, you can add, modify, or remove environments. IMPORTANT: Infor ERP BaanIV c4 and Infor ERP Baan5.0c require additional steps to use Web UI 8.7. Specify the required information. For details on the fields, see the online help of the page. Click Save. All values are saved on the web server. Federation Services Settings If you select an environment that uses the Federation Services Protocol and click Generate/Update Keystores, the Federation Services Settings dialog is displayed. Use this dialog to set configuration parameters for user login using Federation Services authentication. By logging on once, users can access multiple applications. Federation Services authentication is handled by Active Directory Federation Services (ADFS). Depending on ADFS configuration settings, users can be logged on automatically based on their Windows credentials. After specifying configuration parameters in the Federation Services Settings dialog, various other settings must be defined. See Configuring Federation Services for ERP LN with Web UI. Diagnostics (test the connection) The second dialog is about Diagnostics. Click the environment you defined in the previous screen. This page can be used to test whether your settings result in a successful connection. Company settings You can give various companies each their own color. Smart links Note The functionality described in this section is not supported in combination with Infor Enterprise Server 8.5 and higher. From Infor Enterprise Server 8.7, you can disable smart links in the Maintain Parameters (ttaad0100m000) session on the ERP LN server. This page deals with smart links. Smart links in Web UI provide a way to quickly zoom to a related session from an overview session. Smart links The following fields are available to make smart links: From session: Specify the session code of the overview session in which the smart link must be available. From field: Specify the field name in the session from which the smart link must be available To session: Specify the session code of the overview session to which the smart link points. To field: Specify the field name in the session to which the smart link points. Reference fields: You must pass a key field to the linked session. Auto Complete Note The functionality described in this section applies only to Web UI 8.4.2 and older versions. From Web UI 8.5, Web UI users can define their own Auto Complete parameters. For details, refer to the Web UI online help. Auto Complete The following parameters can be set for Auto Complete: Auto Complete Enabled: If checked the auto complete database on the web server will be filled and updated and an auto complete list will be shown on fields with zoom functionality. Maximum no of Entries: Tells the maximum number of possibilities which will be shown in the auto complete list. Default interval time: If on a field with zoom functionality the value is changed, auto complete sends at regular intervals a request to the web server. This is the interval time in milliseconds that is used if the web server is responsive. If the web server gets less responsive this interval will be used to automatically adjust the interval time. Print to display If you print a report via the Display option, a browser is started to display the requested report. A company logo and a navigation image are present on every page of this report by default. Use the options on the Print To Display page to remove the company logo and/or navigation images. BaanIV Help Content Installation To install BaanIV Help files, you must start the Infor ERP Admin Pages and choose BaanIV Help Content Installation. Use this function if you want your customized BaanIV help available for Web UI on BaanIV. This function converts all your BaanIV help into Infor ERP LN Web Help format to make it available through Web UI on BaanIV. If you only want the standard BaanIV help, it is recommended that you install the help files as available on the installation media. Please note the following: Getting the help content from the ERP system and installing it as help content can take several hours. Ensure there is at least 100 MB of free disk space on the ERP system and on the web server. Help is retrieved for the packages in the package combination and language of the attached user. If you want help information in another language, in the user’s Web UI user profile, change the language code. Offline/Online Form Cache Initialization Important! This section is only applicable if you use BaanIV, Baan5, or Infor Enterprise Server 8.4.2 or lower. Enterprise Server 8.5 and higher do not use a form cache, because the forms are generated dynamically. Note If you use Enterprise Server 8.5 or higher, the following restrictions apply: You cannot manually configure smart links on the web server anymore. From Infor Enterprise Server 8.7, you can disable smart links in the Maintain Parameters (ttaad0100m000) session on the ERP LN server. Smart links in details sessions are not supported. The Infor ERP form definitions must be converted into a format that Web UI understands. If a user starts a session in Web UI, a process on the Web UI server checks if that converted form definition is already in the form cache. If so, the form definition is returned to Web UI. If not, the conversion process is started. When completed, the converted form definition is stored in the form cache and returned to Web UI. The form cache initialization option allows you to pre-fill the form cache before the system is taken into production. This prevents users experiencing delays when they start a session for the first time. Online Form Cache Initialization The user interface of the Online Form Cache Initialization form is improved. It allows you to select a consecutive range of packages and a non-consecutive range of packages and modules. However, the availability of this feature depends on the version of the Infor ERP system you connect to. Older versions of Infor ERP systems cannot supply the required information to the Online Form Cache Initialization form. When you are connected to such an older version of an Infor ERP back-end, a user interface is displayed that allows you to only enter a consecutive package range. Open the Online Form Cache Initialization form and supply the following information: The location that is the root of the XFE dump directory structure. See the explanation of the Online Form Cache Initialization process later in this section.. The location to store the log files. The location to store the form cache. Important: To confirm the location of the form cache directory, click Submit. The environment for which to initialize the form cache. The username to log onto that environment. The password to log onto that environment. Click Connect. If a connection is established with the selected environment, the Connect button becomes disabled and the Disconnect button becomes enabled. If the Infor ERP system is connected you can supply information about available package combinations, languages, packages, and modules, select the following information: The package combination from the drop-down list. The language from the drop-down list. The package(s) and module(s) from the tree with check boxes. For older Infor ERP systems, the user interface displays fields that allow you to specify a consecutive range of packages only. The Online Form Cache Initialization process uses the package combination and language specified in the User Data (ttaad2500m000) session for the user that connected to the Infor ERP system. Click Start. A modal dialog, which displays the progress of the Online Form Generation process, appears. Note If the cache already contains forms, only those forms older than the associated XFE dump will be regenerated. Also, some optimization takes place to reduce the number of XFE dumps that will be generated and transferred. When the Online Form Cache Initialization process has been started, the following events occur: A connection is established with the Infor ERP system as described in the selected environment, using the given username and password. A comparison, per module, between the creation dates of the forms in the cache and similar runtime objects on the Infor ERP system. If a module is found that contains outdated forms in the cache, a process is started on the Infor ERP system. This converts local session and form data for all sessions and forms in the given module into XML files, also known as XFE dumps. The XFE dumps are collected and compressed in a tar.gz file per package, and each file is transferred to the Web UI server. On the Web UI server, these tar.gz files are unpacked into the XFE Root Directory in a directory structure that reflects the origin of the XFE dumps. When the tar.gz files are unpacked, a process is started on the Web UI server. This converts the XFE dumps into Java form classes that are stored into the Form Cache. Note To move an existing form cache, complete the following steps: Open the Online Form Cache Initialization form. Specify a new form cache directory. Click Submit. Offline Form Cache Initialization If you already have XFE dumps, such as from a previous Online Form Cache Initialization, use the Offline Form Cache Initialization to convert these forms and (re-)initialize the form cache. Before you start an Offline Form Cache Initialization, enter the following information: The location that is the root of the XFE dump directory structure. See the explanation of the Online Form Cache Initialization process. The location to store the log files. The location to store the form cache. Important: To confirm the location of the form cache directory, click Submit. The environment for which to initialize the form cache. The package combination, from the drop-down list. The language, from the drop-down list. The package(s) and module(s), from the tree with check boxes. Click Start. A modal dialog, which displays the progress of the Online Form Generation process, appears. Note The choices you can select in the Offline Cache Initialization Form, such as environments, package combinations, languages, packages, and modules, are determined by the contents of the selected XFE directory. This directory structure is created during Online Form Cache Initialization. For the language part of the structure, only the language code is available. The language name is not available. Therefore, when an Online Form Cache Initialization is performed, a mapping file is created. The name of this file is lcmap.properties, and the file can be found in <xfe directory>/(hostname-part) /(bse-part). If this mapping file is not present, a fallback mechanism is present, that maps code 1 to "Dutch", code 2 to "English", code 3 to "German" and code 4 to "French". Codes that lack mapping will be displayed as they are. To dump the XFE files on the Infor ERP system, transfer the dumps to the Web UI server, and use the Offline Form Cache initialization to convert them, complete the following steps: Check the following conditions: Ensure you are running the correct package combination. If not, do the following: In the Infor ERP user settings, change the package combination. Convert to runtime. Log off from Infor ERP. Re-log onto Infor ERP. Ensure you have enough disk space available to store the form dumps on the Infor ERP system. If you dump all Infor ERP packages in one run, you need approximately 500 MB for each language. Create a dump of the required Infor ERP forms on the Infor ERP server. On the Infor ERP system, start the Run Program command: If you logged on through WorkTop or Web UI, click Tools -> Run Program. If you logged on through BW, click File -> Run Program. Start the Dump Sessions in XML Format (ttadv2280m000) session. This takes some time. In this dump session, you can export the Infor ERP sessions in XML format. Each exported XML file contains general session data and all necessary form information. For details, refer to the session help. By default, only supported Infor ERP sessions are exported. Transfer the session dumps to the Web UI server. After you export the session dumps, use an FTP program to manually transfer the XML files from the Infor ERP server to the Web UI server. Considering the number of files, it is recommended you compress the files into an archive. This reduces the network load and saves time when transferring the files to the Web UI server. The XFE dumps are stored in a directory structure that reflects the origin of the XFE dumps. Therefore, the directory structure to store the XFE dumps in must adhere to some rules. The directory structure has the following format: <XFE root dir of your choice>/[hostname]/[BSE]/[package combination]/[language code] [hostname] - hostname of the Infor ERP system [BSE] - The value of the BSE environment variable on the Infor ERP system. [package combination] - The package combination used while creating the XFE dumps. [language code] - A numeric value that represents the language used while creating the XFE dumps. Note: Not all characters used in the above parameters are always valid as characters in a directory name. The following characters are replaced by an underscore (_): backslash (\), slash (/), colon (:) and space ( ). If these characters occur at the beginning or the end of a parameter, they are removed. For example: XFE root directory of your choice: c:\temp hostname: erpserver $BSE: /usr/erpln/bse package combination: 60sys32 language code: 2 (English) The XFE directory structure must be "c:\temp\erpserver\usr_erpln_bse\60sys32\2". If the Infor ERP LN system runs on Windows, a BSE environment variable usually consists of something similar to "e:\user\erpln". This must be converted into "e__user_erpln". Pay attention to the double underscore at the second and third position, as both the colon and the backslash must be replaced by an underscore. Follow the procedure for Offline Form Cache Initialization to convert XFE dumps. Note: If the cache already contains forms, only those forms that are older than the associated XFE dump will be regenerated. Note To move an existing form cache, complete the following steps: Open the Offline Form Cache Initialization form. Specify a new form cache directory. Click Submit. Stand-alone Form Cache Initialization Important! This section is only applicable if you use BaanIV, Baan5, or Infor Enterprise Server 8.4.2 or lower. Enterprise Server 8.5 and higher do not use a form cache, because the forms are generated dynamically. Form Cache Initialization can affect the performance of the ERP LN system/the Web UI server. Web UI allows you to initialize the form cache from the command-line. To do this, complete one of the following classes in a Java Virtual Machine: OfflineFormCacheGenerator – for Offline Form Cache Initialization. OnlineFormCacheGenerator – for Online Form Cache Initialization . Running these classes in a Java Virtual Machine requires the following settings: Classpath. Location of the Web UI application. Location of the file WebtopProperties.xml. Location of the servlet archive that your application server uses. Options required to perform the actual Form Cache Initialization. Options for Stand-alone Form Cache Initialization
Option | Description
--- | ---
-h/--help | Displays help
-i/--info | Displays available environments (requires the –w option).
-a/--appshome | Path of application directory (required).
-w/--webtopprops | Path of directory that contains "WebtopProperties.xml" (required, except for options -h).
-e/--environment | Environment for which to initialize the form cache (required, except for –h and -i).
-u/--user | Username to login to the specified environment (required for Online Form Cache Initialization, except for options -h and -i).
-p/--password | Password to connect to the specified environment (required for Online Form Cache Initialization, except for options -h and -i).
-c/--packcomb | Package combination for which to initialize the form cache (required, except for options -h and -i).
-l/--language | Language for which to initialize the form cache (required, except for options -h and -i).
-s/--startpack | First package of package range (optional - defaults to " ").
-f/--finalpack | Last package of package range (optional - defaults to "zz").
-x/--xfedir | Root directory of the XFE dump directory structure (required).
-t/--tempdir | Directory to store temporary results generated during form cache initialization (optional - defaults to system temp directory).
-r/--reportdir | Directory to which the report is written (optional - defaults to temporary directory).
-d/--diag | Gives diagnostic output without executing the form cache initialization (optional).
Example The following example shows a Windows batch-file for stand-alone Online Form Cache Initialization. It assumes the environment is created by the Infor Enterprise Server Extensions installer:
    echo ONFCI - Online Form Cache Initialization
    @echo off
    setlocal
    set ARGS=%*
    if not defined ARGS set ARGS=-h
    set PROPSHOME=C:\Infor\ERPLN\ese\Webtop\config
    set SERVLETJAR=C:\Infor\ERPLN\ese\apache-tomcat-6.0.29\common\lib\servlet-api.jar
    set WEBAPP=C:\Infor\ERPLN\ese\Webtop\web
    set WEBINF=%WEBAPP%\WEB-INF
    set CP=%WEBINF%\lib\erp.jar;%WEBINF%\lib\webtop.jar;^
    %WEBINF%\lib\jargs.jar;%WEBINF%\lib\xercesImpl.jar;^
    %WEBINF%\lib\log4j.jar;%WEBINF%\lib\jdom.jar;^
    %WEBINF%\lib\kjc-2.2D.jar;%WEBINF%\lib\tar.jar;^
    %WEBINF%\lib\java-getopt-1.0.12.jar;%WEBINF%\lib;^
    %SERVLETJAR%;%WEBINF%\classes;

    set ARGS=%ARGS% -a %WEBAPP% -w %PROPSHOME%
    java -cp %CP%
    com.ssaglobal.erp.server.fd.pipeline.cache.OnlineFormCacheGenerator %ARGS%
To call this sample Windows batch file from the command-line, or another batch file, use the following code:
    onfci -e our_env -c b61abc -l 2 -u jhanson -p secret -x
    c:\our_env\xfel -r c:\log -t c:\temp -s ts -f ts
This command-line executes stand-alone Online Form Cache Initialization for the ts package, in package combination b61abc, and for the English language. The ERP LN definitions of the our_env environment provide the hostname and BSE directory of the ERP system. The logon to the ERP system is performed with user jhanson and password secret. Similarly, you can perform an Offline Form Cache Initialization. However, in the last line of the previous example, enter a different classfile name. You must change the word OnlineFormCacheGenerator to OfflineFormCacheGenerator. Also, on the command-line, omit the options for username and password. Delete Forms Complete the following steps: In the Web UI Administration Console on the Web UI server, select Delete Forms from Form Cache. In the input fields, enter the values that represent the form you want to delete. The values act as a filter on all forms in the form cache. An empty field means "all values". For example: If you leave the Host field blank, forms for all hosts will be deleted from the Form Cache. If you leave all fields blank, all forms will be deleted from the Form Cache. Click Delete. Remove Obsolete Forms This page contains the following options:
Option | Description
--- | ---
Remove Old Version Forms | Removes forms created by older form generator versions.
Remove obsolete activity forms | Removes forms from activity-related VRCs.
For details, refer to the following sections. Remove Old Version Forms To remove forms created by older form generator versions, complete the following steps: Open the Remove Obsolete Forms page. In the Messages section, read the displayed messages. If the form cache contains old version forms, a corresponding message is displayed in the Messages section; for example, `Found forms of previous FormGenerator version(s): v044, v045` If no old version forms are found, the following message is displayed: `No forms of previous FormGenerator versions found` If the form cache contains old version forms, to remove these forms, click Delete. To indicate the progress of the deletion process, messages are displayed in the Messages section. Remove obsolete activity forms Note Use this option only if your company uses Infor ERP LN Application Studio. After an Infor ERP LN Application Studio activity is closed, use this option to recover disk space on the Web UI server. The forms belonging to the closed activity are removed from the form cache. For details, refer to the Application Studio documentation. To remove obsolete activity forms, complete the following steps: Open the Remove Obsolete Forms page. Specify the following information: The environment for which to remove forms from the form cache. The username to log onto that environment. The password to log onto that environment. Click Start. The results of the deletion process are displayed in the Messages section. Report Viewer To specify the settings for the Report Viewer, use this page. You can specify the following parameters:
Parameter | Description
--- | ---
Hostname | The host name of the machine on which the Report Viewer application is installed. Note: If the Report Viewer and Web UI run on the same machine, specify "localhost".
Http port number | The port number used to activate the Report Viewer application. The default port number is 80.
Https port number | The port number used by Web UI to communicate with the Report Viewer. The default port number is 8443.
Virtual directory | The virtual directory of the Report Viewer application. The default directory is "reportviewer". If you selected the default context path ("/reportviewer") during the installation of the Report Viewer, do not change this directory. If you selected a different context path during the installation, you must change the virtual directory accordingly.
Homepage Export On the Homepage Export page, you can export homepages from a user profile. When you export a homepage, the export process generates the following: A homepage archive file which contains the language independent content of the homepage, such as the structure of the homepage and its panes. A homepage property file, also known as a resource file. This file contains language-dependent content in the language the homepage was developed in. The homepages that Infor delivers are developed in English. A homepage property file only contains language-dependent content of the homepage itself, such as the homepage title and the titles of the panes. The file does not contain language dependent ERP LN content used in the homepage, such as label and message descriptions. The homepage archive files and homepage property files are automatically transferred to the ERP LN server, and stored as additional files in the ERP LN data dictionary. You can access the files in the Additional Files (ttadv2570m000) session. Filenames The names of the homepage archive files and the homepage property files have the following structure:
File type | File name structure
--- | ---
Homepage archive file | <homepage-id (max. 28 characters)>.HPA
Homepage property file | <homepage-id (max. 28 characters)>_<ISO 639 language code>_<ISO 3166 country code>.properties Note: The country code is optional, and is only used for a few languages.
For example, when you export the Warehouse Manager homepage, the following files are generated: warehousemanagerhomepage.HPA: Homepage archive file. warehousemanagerhomepage_en.properties: English Property file. To export homepages To export homepages, complete the following steps: Open the Homepage Export page. The homepages you can export are displayed per user and profile. Connect to the ERP LN server: In the Login group box, select an Infor ERP environment, enter a login code and a password, and click Connect. In the Package Combination field, select the package combination which contains the package VRC where you want to store the additional files that will be generated. A list of packages and the corresponding modules is displayed. Select a user and a user profile. Subsequently, select the homepage you want to export from the list. Select the package and module where you want to store the additional files that will be generated. Click Export. Note You can only export homepages from user profiles which have the "homepage creator" role assigned. Use the Homepages Import page to import the contents of a homepage archive file into other user profiles. For more information, refer to "Homepages" in the Web UI online help. ERP LN homepages are not supported in Infor Companion. Translation The homepages that Infor delivers are developed in English. To make these homepages available in other languages, you must translate the content of the homepage property files. For details on the translation procedure, refer to Infor ERP LN Development Tools 8.x Developer's Guide (U8883 US). Homepage Import Infor delivers various predefined ERP LN homepages. During the installation of ERP LN, these homepages are installed as additional files (homepage archive files and homepage property files). Updates will be available in PMC solutions. Before Web UI users can use homepages, you must import the corresponding additional files into their Web UI user profiles. To import homepages, complete the following steps: Open the Homepage Import page. The Web UI user profiles are displayed in the right pane. Connect to the ERP LN server: In the Login group box, select an Infor ERP environment, enter a login code and a password, and click Connect. In the Package Combination field, select a package combination The homepage archives in the selected package combination are displayed per package/module. Select the homepage archives you want to import. Select the user profiles into which you want to import the homepage archives. Click Import. Note Before Web UI users can use the new homepages, they must log off and log on using the updated user profiles. Homepages created in the first release of Web UI 8.4 are delivered in .zip files. To import homepages from a .zip file, use the Homepage Import From File page, which is located under the Infor ERP LN Web UI Administration node. You can export homepages in the Homepage Export page. You cannot export a homepage directly after it was imported. After an import, the Web UI users must first log off and log on using the updated user profiles. ERP LN homepages are not supported in Infor Companion. For more information, refer to "Homepages" in the Web UI online help. Logical Id Mapping This section is only applicable if you use Infor Enterprise Server 8.5 or higher, or Infor ERP BaanIV. Use the Map Logical Ids to Web UI environments page to map logical Ids, which are used in Infor Companion and Infor ERP environments. The mapping between a logical Id and an ERP environment is used to drill back from high-level data, which is displayed in Companion, to detailed data stored in the ERP environment. For details, refer to the documentation on Companion. To map a logical Id to the corresponding ERP environment: On the Web UI server, select Logical Id Mapping in the Web UI Administration Console. The Map Logical Ids to Web UI environments page appears. Click New. In the Logical Id field, enter the logical Id of the ERP environment. To find the logical Id of an environment, log on to Companion and view the ID of the corresponding application. In Companion, a logical ID consists of multiple segments. When you enter the logical ID in the Web UI Administration Console, the different segments must be separated by a period. In the Name field, select the ERP environment from the list. Click Save. Exchange Synchronizer This section describes how to configure and start the Exchange Synchronizer. The Exchange Synchronizer synchronizes contacts and calendar events between Microsoft Exchange and ERP LN CRM. See "Synchronization of CRM contacts and activities to Microsoft Exchange" in the Infor ERP LN Web Help. The Exchange Synchronizer runs on the Web UI web server. Before you can start the Exchange Synchronizer, configuration settings must be specified on the ERP LN server. Prerequisite Java 6 must be installed on the web server. Deployment The certificate of the Exchange Server must be trusted by the Web UI. You must download the certificate from the Exchange Server and import it into the server’s trust store. For details on how to do this, see Appendix A "To Self Sign a Tomcat Web server" in the Infor Enterprise Server Extensions 8.x - Installation Guide (U9484 US). Complete the steps to import a certificate into the trust store. You must update these lines in the `< Web UI installation folder>/WEB-INF/web.xml` file on the web server:
     <!-- Must be enabled for synchronizer (push enabling) to work. Only works with java 1.6 or higher. To enable: Please remove this line and the line after the listener tag --><!--
        <listener>
    	<listener-class>
    		com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    	</listener-class>
        </listener>
        --><!-- Remove this line as well! -->
You must remove the comment lines to be able to use the push synchronization of the Exchange Synchronizer. After these steps have been completed, you must restart the server instance. To configure and start the Exchange Synchronizer Step 1. Configure the Exchange Synchronizer Complete these steps: Log on to the ERP LN server. Start the MS Exchange Synchronization Settings (ttaad2140m000) session and define a configuration. In the MS Exchange Synchronization Settings (ttaad2140m000) session, click Users. The MS Exchange Synchronization Users (ttaad2141m000) session starts. Specify the users that require synchronization of their contacts and calendars. See the session help. Step 2. Start the Exchange Synchronizer Complete these steps: In the Web UI Administration Console, expand the Infor ERP node and select Exchange Synchronizer. The Synchronizer Control page appears. Specify the required information, such as the CRM environment for which the Synchronizer must be started. See the online help of the Synchronizer Control page. Click Start. The Synchronizer is now running for the specified environment. Repeat this step for each CRM environment for which the Synchronizer must be started. Note To stop the Synchronizer for an environment, select the environment in the Synchronizer Control page and click Stop. Configuration settings on the Infor ERP server This section describes Web UI configuration settings, which must be defined on the Infor ERP server. Personalization settings Through the Web UI interface, the end-user can easily personalize ERP LN sessions. See "Personalize ERP sessions" in the Web UI online help. To control whether an end-user is allowed to personalize ERP LN sessions, use the Application Personalization check box in the User Data Template (ttams1110m000) session. Easy Filtering In overview sessions, Web UI users can enter filter criteria in the input fields above the grid. See "Easy Filtering" in the Web UI online help. To configure easy filtering for ERP LN: Select an appropriate value in the Allow Easy Filter field in the Maintain Parameters (ttaad0100m000) session. This field determines if, and for which fields, easy filtering will be available. Convert the changes to the Runtime Data Dictionary. See the online help of the Maintain Parameters (ttaad0100m000) session. Decimal/Thousand Symbol You can specify which decimal sign and thousand sign will be used in amounts in ERP LN sessions in Web UI. Complete these steps: Start the Maintain Parameters (ttaad0100m000) session. Complete one of these steps: Select the Use Decimal/Thousand Symbol Client check box. The amounts are displayed using the decimal sign and thousand sign as defined in the Windows settings on your client PC. All amounts are displayed using the same decimal sign and thousand sign. Clear the Use Decimal/Thousand Symbol Client check box. The amounts are displayed using the decimal sign and thousand sign as defined in ERP LN. In ERP LN, decimal signs and thousand signs are defined per software language and per currency. Therefore, different decimal signs and thousand signs can be displayed in fields in the same session. To convert the changes to the Runtime Data Dictionary, click Convert to .... All user files will be (re)built. To make the changes active at runtime, all users must log off and log on again. See the online help of the Maintain Parameters (ttaad0100m000) session. Icons in grid In Web UI, icons can be displayed in enumerated fields in overview sessions. The icons are linked to enum constants and are displayed instead of the corresponding enum descriptions. This saves space in the grid. If a user hovers over an icon in a grid, the corresponding enum description is displayed as a tooltip. To ensure icons can be displayed in the grid: Select the Allow Icons In Grid check box in the Maintain Parameters (ttaad0100m000) session. Use the Domains to be Displayed as Icon (ttgfd4525m000) session to link icons to enum constants. See the online help of the sessions mentioned. Note In Web UI, users can choose whether they want to view icons or the corresponding enum descriptions. See "Personalize ERP sessions" in the Web UI online help. Pictures In some ERP LN sessions, such as the Contact (tccom1640m000) session, Web UI users can add pictures. See "Pictures" in the Web UI online help. When a user adds a picture in a session, the picture is stored in an image repository on the ERP LN server. To ensure users can add images in sessions, complete these steps on the ERP LN server: Optionally, change the location of the image folder. Assign authorizations for the image folder and its contents. See "Image parameters" in the Infor Enterprise Server 8.x Administrator's Guide (U8854 US). Password aging To benefit from this feature, the Enterprise Server 8.3 or higher is required for ERP LN. For older Infor ERP versions a Tools solution is required, and there is a minimum requirement for the porting set. All of this is described in Solution 209841. Related topics The Infor ERP LN Web UI Administration Console Configure Infor Workflow |