EpicorUserExpCust UserGuide 905700 Part1of3

Epicor ICE 2.
5 User Experience and Customization Guide
Epicor ICE 2.5 User Experience and Customization Guide User
About Epicor Software Corporation

Epicor Software Corporation is a global leader delivering business software solutions to the manufacturing, distribution, retail and services industries. With nearly 40 years of experience serving midmarket organizations and divisions of Global 1000 companies, Epicor has more than 20,000 customers in over 150 countries. Epicor enterprise resource planning (ERP), point of sale (POS), supply chain management (SCM), and human capital management (HCM) enable companies to drive increased efficiency and improve profitability. With a history of innovation, industry expertise and passion for excellence, Epicor inspires customers to build lasting competitive advantage. Epicor provides the single point of accountability that local, regional and global businesses demand. The Companys headquarters are located in California, with offices and affiliates worldwide. For more information, visit www.epicor.com.
Disclaimer
Copyright 2012 by Epicor Software Corporation. All rights reserved. Printed in the United States of America. No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation. Epicor is a trademark or registered trademark of Epicor Software Corporation in the United States and other countries. All other trademarks are property of their respective owners. Microsoft product screen shots reprinted with permission from Microsoft Corporation. Epicor Software Corporation makes no representations or warranties with respect to the contents of this document and specifically disclaims any implied warranties of merchantability, satisfactory quality or fitness for any particular purpose. The contents of this document are believed to be current and accurate as of its date of publication, April 2012. Changes to this document between reprintings and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time without notice. The usage of any Epicor Software shall be pursuant to an Epicor end user license agreement and the performance of any consulting services by Epicor personnel shall be pursuant to Epicors standard services terms and conditions
Epicor Worldwide Headquarters 4120 Dublin Boulevard Dublin, CA 94568 Phone 949.585.4000 FAX 949.585.4091 http://www.epicor.com
Release 9.05.700 Distribution April 2012
Table of Contents
Chapter 1: Startup Configurations...............................................................................................................................1 Configuration Settings File...................................................................................................................2 Configuration File Location ...................................................................................................2 Make a Copy of Default........................................................................................................2 Multiple Configuration Files ..................................................................................................2 The Configuration Editor.......................................................................................................2 Settings - The Complete List..................................................................................................6 Run Time Arguments.........................................................................................................................15 Run Time Arguments List ....................................................................................................16 Chapter 2: Styling and Themes ..................................................................................................................................19 User Maintenance .............................................................................................................................20 Style Theme Loading .........................................................................................................................20 Runtime Stylist...................................................................................................................................22 Runtime Stylist Primary Controls .......................................................................................23 Resources............................................................................................................................25 Roles ...................................................................................................................................27 Components in the Used By Section....................................................................................37 Role Selection......................................................................................................................37 Style Filter Management ....................................................................................................................39 Style Tracking ....................................................................................................................................45 Theme Maintenance ..........................................................................................................................46 Default Theme Retrieval.....................................................................................................................54 Case Study New Button Theme ......................................................................................................55 Chapter 3: Personalization..........................................................................................................................................69 Personalize the Main Menu Interface.................................................................................................70 The View Menu .................................................................................................................................70 The Options Menu.............................................................................................................................72 Save Settings on Exit .........................................................................................................................74 The Favorites Bar ...............................................................................................................................75 Personalize the Program Interface......................................................................................................79 Personalization Options Window.........................................................................................79 Personalize Sheet Layouts ..................................................................................................................86 Personalize Toolbars ............................................................................................................91 Personalize Grids .................................................................................................................91 Advanced Personalization Options .....................................................................................................99 Personalize Sheet Properties ..............................................................................................102 Modify Grid Properties.....................................................................................................................108 Import, Export, and Delete Personalizations .....................................................................................110 Chapter 4: Basic Customization................................................................................................................................115 Customization Rights.......................................................................................................................116 Developer Mode ..............................................................................................................................116 Select Customization.........................................................................................................117 Launch Developer Mode..................................................................................................................119 Disable Memory Caching ..................................................................................................119 Developer Mode................................................................................................................120 Customization Tools Dialog ...............................................................................................121 Custom Session Options ..................................................................................................................123 Top Most Mode.................................................................................................................123 Grid Settings .....................................................................................................................123
Hide, Move, and Add Elements .......................................................................................................125 Hide Elements ...................................................................................................................125 Move Elements..................................................................................................................126 Add Elements....................................................................................................................128 Save Options ...................................................................................................................................141 Export Customizations .....................................................................................................................143 Chapter 5: Advanced Customization .......................................................................................................................145 Customizing Alternate Interfaces .....................................................................................................146 Styling Specific Controls ..................................................................................................................149 Define the Control Style ....................................................................................................150 Create the Control Style....................................................................................................151 Disable the Control Style ...................................................................................................154 Non-Customizable Forms.................................................................................................................155 Customization Form Wizards ...........................................................................................................156 Rule Wizard ......................................................................................................................156 Image Column Wizard ......................................................................................................169 Form Event Wizard............................................................................................................176 Sheet Wizard ....................................................................................................................180 Event Wizard.....................................................................................................................185 Foreign Key Views ...........................................................................................................................189 Script Editor.....................................................................................................................................195 Script Editor Options .........................................................................................................198 Script Editor Event Handlers ..............................................................................................201 Event Sequence for Startup ...............................................................................................205 Event Sequence for Shutdown ..........................................................................................205 Script Editor Examples .......................................................................................................205 Custom Object Explorer ...................................................................................................................209 UI Objects .........................................................................................................................210 Data Objects .....................................................................................................................216 Adapters ...........................................................................................................................219 Assembly Reference Manager ..........................................................................................................220 The String Manager.........................................................................................................................221 Customization Code Wizards...........................................................................................................225 Custom XML Editor .........................................................................................................................242 Debug Customizations ....................................................................................................................244 Chapter 6: Customization Utilities ...........................................................................................................................253 Database Viewing Tools ...................................................................................................................254 Data Dictionary Viewer......................................................................................................254 Field Help ..........................................................................................................................257 Dataset Relationships Tracker ............................................................................................258 Tracing Log .......................................................................................................................259 Global Customization Tools .............................................................................................................261 Context Menu Maintenance..............................................................................................261 Custom Fields....................................................................................................................267 Extended Property Maintenance ........................................................................................269 Extended User Defined Table Maintenance........................................................................272 User Defined Codes Maintenance .....................................................................................274 Resource Editor .................................................................................................................276 BAQ Zones ......................................................................................................................................280 The BAQ Zone Process ......................................................................................................280 Use Case: Customer Website BAQ Zone............................................................................285 Use Case: Part Image BAQ Zone........................................................................................291 Use Case: Customer Part BAQ Zone ..................................................................................298
ii
Deployment.....................................................................................................................................306 Main Menu Deployment ...................................................................................................306 Sub Program Deployment .................................................................................................309 Customization Management............................................................................................................313 Personalization Purge ........................................................................................................313 Customization/Personalization Maintenance......................................................................314 Verify Customizations/Personalizations ..............................................................................318 Run and Modify a Customization/Personalization ..............................................................320 Show Custom Data ...........................................................................................................323 Force Validation.................................................................................................................326 Generate Web Forms ........................................................................................................326 Customization Maintenance Log .......................................................................................328 Clear Application Cache....................................................................................................329 Chapter 7: User-Defined Tables ................................................................................................................................331 Standalone User-Defined Tables .......................................................................................................332 Parent/Child User-Defined Tables .....................................................................................................344 Parent and Child EpiRetrieverCombos ...............................................................................344 Chapter 8: Localization .............................................................................................................................................371 Country Group and Country Codes .................................................................................................372 Install Languages .............................................................................................................................372 Language Maintenance ...................................................................................................................376 Change Languages ..........................................................................................................................386 Localization Layer ............................................................................................................................388 Translation Utility .............................................................................................................................394 User Account Maintenance..............................................................................................................400 Chapter 9: Solution Management............................................................................................................................405 User Maintenance ...........................................................................................................................406 Define the .CAB File ........................................................................................................................406 Build the Solution ............................................................................................................................407 Create the Solution .........................................................................................................................412 Export the Solution Definition..........................................................................................................413 Import the Solution Definition .........................................................................................................414 Install the Solution...........................................................................................................................415
iii
iv
Introduction
The Epicor ICE 2.5 User Experience and Customization Guide explores the interface tools available within the Epicor ICE framework. This guide is intended for managers responsible for fine-tuning their departmental use of the Epicor 9 application and advanced users looking to modify the application interface for their specific needs. This guide begins by exploring the various startup methods available within the configuration settings file. It then examines the functionality for both styling the look of the interface and personalizing specific programs by user. Then the customization tools are thoroughly documented through a series of chapters beginning with the basic customization tools and then progressing on to managing customizations and modifying user-defined tables. This guide concludes with chapters on localizing the application for different languages/cultures and building a customized solution. You need both sets of tools fully leverage the Epicor application throughout your domestic and international organization. Use this guide as a starting point to learn about the available interface tools and as a reference for later use of these same tools. This guide is a crucial resource for anyone who needs to leverage these tools for both managing and enhancing their organizations unique business practices.
vi
STARTUP CONFIGURATIONS | CHAPTER 1
Chapter 1 Startup Configurations
The application contains functionality you can use to modify the settings it uses to launch both throughout your system and on specific workstations. To do this, you leverage Configuration Settings Files and Run Time Arguments. By using different startup configurations and run time arguments, you can define specifically how the application runs on each workstation. For example, if you want the application help hosted on a separate server from the deployment server, you would modify the configuration settings file by entering the servers URL in the helpServerURL attribute. You would then update this parameter on all configuration settings files throughout the company. You can also modify a specific workstation with these tools. You can set up the configuration settings file to have the application use custom images or define a run time argument that launches the application using the MES interface. By changing just a few parameters within the configuration settings files and run time arguments, you define how the application runs on each workstation and interacts with the server.
EPICOR SOFTWARE CORPORATION | 1
CHAPTER 1 | STARTUP CONFIGURATIONS
Configuration Settings File

For the application to launch, it must find a configuration settings file. This file defines the main settings for your server installation as well as each client installation. If the .exe file can see the default.mfgsys file (or a different .mfgsys file specified through a run time argument), the application launches on the workstation. The configuration settings file is an .xml formatted file that uses syntax understood by the application. This section explains how you modify the configuration settings file. It also describes one of the most common changes, giving a user the ability to automatically log into the application. A complete list of all the settings and their functionality is also found later in this chapter.
Configuration File Location

Your configuration files are all located in the Config folder within your client installation folder. Locate the Files You use Microsoft Windows Explorer to find and select these files. 1. Open your client installation folder (in this example, Epicor 905), the client folder, and the config folder. 2. The configuration files available for your client installation display in this folder. Notice multiple configuration files are available within this folder. You can create several configuration files in order to launch the application using different settings. 2 1
Make a Copy of Default

Before you modify a configuration settings file, you must make a copy of the original default.mfgsys file. This ensures that you always have the original settings available for reference. This also creates a backup file that can restore the original configuration settings, if needed. You make a copy of this file by using the copy and paste functions within Windows Explorer.
Multiple Configuration Files

A key method for modifying the configuration settings file is to create alternate versions of it and then have a workstation launch with a selected alternate file. You can then keep the original file while you experiment with different configurations. You do this by first creating the alternate configuration file and then defining the /CONFIG run time argument on a workstation. To learn how to use this feature, read the Run Time Arguments section later in this chapter.
The Configuration Editor

When you finish making copies of the default.mfgsys file, you are ready to modify these files. You do this by using the Configuration Editor. This tool is automatically installed with your client application. To modify this file, you need to understand your computer network. If you are not sure about customizing this file, work with your Epicor consultant before you enter any changes.
2 | EPICOR SOFTWARE CORPORATION
Launch the Configuration Editor You use Windows Explorer to launch this program. 1. Open your Client Installation folder. In this example, you open the Epicor\Epicor905 directory on your C: drive. 2. Open the client folder. 3. Select the ConfigEditor.exe icon. 1 2
Configuration Editor What to Do When the Configuration Editor launches, it prompts you to select a file you want to edit. After you select the configuration file, you can then edit the file parameters as you need. Here is what you do: 1. The Please select a configuration file window displays. 1
2. Notice this window automatically displays all the files contained within your Config folder. Select the file you want to edit. In this example, you select the default.mfgsys file. 3. Click Open. 2
4. The Configuration Editor displays.
10
5. The configuration file settings are divided into several sheets. The Application sheet displays all the settings that apply to the overall application. You define settings like AppServerURL, ResourceFile, and Version here. 6. The User sheet contains the settings you can adjust for the specific user on this client workstation. 7. The Deployment sheet contains the settings for moving, or deploying, files from your server to the client installation. 8. The Help sheet contains the settings that define the directory paths for the application help, online support, and the Feature Summary. Use these options to define where this configuration file looks for documentation and support resources.
11
12
13
9. Use the Sort sheet to define the method used globally to sort strings within the application. Your options are stringSort and wordSort. You can also create exceptions to the default sort method on this sheet. 10. The Tools sheet contains the default settings that are needed to use the Software Developer Kit (SDK). Sold separately from the application, this toolset enables developers and advanced users to extend the application to create new tables, business objects, and UI forms. If you use the SDK, these default values are automatically added to your configuration file. If you need, however, you can edit them on this sheet. 11. To change a setting, enter an expected value in its field. An expected value is a parameter that is compatible with the setting. For example, you can use the Culture Code to define the default language displayed on the Login window for this client installation. You can enter any ISO language code in this field. 12. When you have modified all the settings you need, click Save. 13. To exit the Configuration Editor, click Close. The selected configuration file now has your revised settings. The next time the application is launched using this configuration file, your new settings become active. For details on all the settings contained on these sheets, read the Settings The Complete List section later in this chapter.
2 Example - Automatic Login A common reason you modify this file is so the user can automatically log into the application. When this user double-clicks the program icon on the desktop, both the user name and password populate the Log On window and the application launches immediately.
To set up the automatic login, modify several settings within the default.mfgsys file (or another configuration file). 1. Launch the Configuration Editor and select the default.mfgsys file. 2. Click Open.
3. The Config file:default.mfgsys window displays. Click the User tab. 4. Enter a UserID. This value is the identifier for the user who is logging into the application from this workstation. Enter the identifier defined for this account within User Account Maintenance. In this example, you enter Jane Smith. 5. Enter a Password. This value is the password for the user who is logging into the application from this workstation. Enter the password defined for this account. 6. Click Save. 7. Click Close. This configuration file is saved with the new settings. The next time this user clicks the desktop icon, the Log On window does not display. On this client machine, the application automatically launches using this user account.
3 4 5
STARTUP 6 7 EPICOR SOFTWARE CORPORATION | 5
Settings - The Complete List

This series of tables list all the settings available within the default.mfgsys file. Each setting has its own row; Purpose and Expected Values are displayed in the right column. Each section displays its settings in alphabetical order. New settings may have been added to the configuration file since the publication of this user guide. For the most up-to-date information, review the Configuration Settings File topic within application help.
Application Settings The Application settings contain general connection settings and configuration settings. You change these settings to apply custom (OEM) style themes to the application. You can also define custom images and text through these settings. Typically, system administrators define these settings and then distribute the updated configuration files to all workstations within the network for which they apply. SETTING PURPOSE AND EXPECTED VALUES Defines whether business object logic or File-Copy logic is used to transfer files (attachments, reports, and so on) from the client to the AppServer in a smart client installation. Available values: BusinessObject When you specify this option, a standard client to server communication method is used while the application transfers information from the client to the AppServer file system. You then have increased security, as the AppServer file system does not need to be accessed by the client Windows user. Direct When you specify this option, the Windows File-Copy logic is used to transfer information from the client to the AppServer file system. You need to expose the AppServer file system for Read/Write access by the client Windows user. The address of the appserver where the client connects protocol://server:port; it uses the form value AppServerDC://servername:port. Protocol AppServerDC by default, or else AppServer for load balancing. AppServerURL Server Host name of the machine that runs AppServer. Port The port of the broker that runs the software. Default is 9001. Also note, the AppServer accepts strings and numbers, but the port value only accepts numbers. The location of the local disk cache folder. This folder is used to hold cached .xml files. If none is specified, the default is: C:\Documents and Settings\All Users\Application Data\Epicor (Windows XP) or C:\ProgramData\Epicor (Windows 7) This folder accommodates some environment variables which can be substituted during startup. %UserName% The Windows ID of the user. Example: jsmith AlternateCacheFolder %UserDomain% The Windows user domain. Example: USEAST %AppData% The application data folder. Example: C:\Documents and Settings\ jsmith\Application Data (Windows XP) or C:\Users\jsmith\AppData (Windows 7) %Homepath% The home path folder. This location is specified in Local Users and Groups. Example: C:\Documents and Settings\jsmith (Windows XP) or C:\Users\jsmith (Windows 7) %AllUsersProfile% The location of the All Users profile. Example: C:\Documents and Settings\All Users (Windows XP) or C:\Users\Public (Windows 7) The ISO language/culture code that defines the specific language and format which displays on the Log On window. For example, sch (Simplified Chinese). CultureCode This value only affects the Log On window. After the user enters a user name and password and clicks past this window, the language and culture code settings defined on the user account display within the Epicor application.
AppServerFileTransfer
SETTING
PURPOSE AND EXPECTED VALUES A path name to a resource file that contains custom images. You can add images to this file by using the Resource Editor; this utility is available for download from EPICweb. Any images contained within this custom file will override images within the base resource file. Typically, the value you enter for this setting is: .res\MfgCustomImages.resource. The behavior when a duplicate attachment ID exists. Two values can be used:
CustomResourceFile
DuplicateAttachmentMode Prompt A new attachment ID must be entered. AutoDateStamp A date stamp automatically appends to the record. The Uniform Resource Identifier address the client uses by default to launch the Enterprise Search functionality. When the Enterprise search is launched, it uses the URL you define in this setting value. You can, however, override this default URL address within each company record; use the Company Configuration > System > General Settings sheet to enter a different Search URL for the specific company. EnterpriseSearchURL Likewise, you can override the URL value defined on the company on a specific user record. Launch the User Account Maintenance > Options sheet and enter the alternate Search URL you want for the current user. The order of precedence for URL addresses: 1. User record (User Account Maintenance) 2. Company record (Company Configuration) 3. Configuration Settings File HelpAboutCopyrightText HelpAboutCopyrightURL HelpAboutImage HelpAboutProductText HelpAboutTitleText HHCustomMenuID The copyright text for the About dialog box. The copyright URL for the About dialog box. The bitmap file for the Help About window. The product text for the About dialog box. The title text for the About dialog box. The menu ID for the sub process that causes customized Handheld menus to load onto your screen. The number of most frequently used business objects whose security settings should be cached when a user logs in. Logic then tracks this number of business objects in the following XML file: C:\Documents and Settings\All Users\Application Data\Epicor\<appserver_and_port>\<version>\<company>\BOSecMRUList\ BOMRUList_<userID>.xml (Windows XP) or C:\ProgramData\Epicor\<appserver_and_port>\<version>\ <company>\ BOSecMRUList\BOMRUList_<userID>.xml (Windows 7) This cached information helps minimize the number of calls between client and server, improving performance. This path is the default location of the cache folder, but it can change based on the AlternateCacheFolder setting. The number of most frequently used datasets. The information on the tracked datasets is used at login to both fetch (get) and memory cache the extended properties for frequently used datasets. The logic tracks this number of datasets in the following XML file: C:\Documents and Settings\All Users\Application Data\Epicor\<appserver_and_port>\<version>\<company>ClsAttrMRUList\ ClsAttrMRUList_<userID>.xml (Windows XP) or C:\ProgramData\Epicor\<appserver_and_port>\ <version>\<company>ClsAttrMRUList\ ClsAttrMRUList_<userID>.xml (Windows 7) This cached information helps minimize the number of calls between client and server, improving performance. This path is the default location of the cache folder, but it can change based on the AlternateCacheFolder setting. EPICOR SOFTWARE CORPORATION | 7
MaxBOMRU
MaxClssAttrMRU
SETTING MESCustomMenuID MESImage ProductBrandIcon ProductBrandText ProductID ProductLogonImage ResourceFile
PURPOSE AND EXPECTED VALUES The menu ID for the sub process that allows customized MES menus to be loaded. The default image that is used by the MES menu. The default is blank. Use this setting to define an optional icon that displays on the far left of the application title bar. Optional text that displays on the left side of the application title bar. If you specify a ProductBrandIcon, this text displays to the left of this icon. The product identifier; for example "Epicor". This setting defines an alternate bitmap image that displays in the upper half of the Log On window. A path name to the resource file. This file contains images and other resources that can be changed by partners for branding purposes; for example: C:\Epicor\Epicor905\client\res\MfgBaseImages.resources The Session Manager tracks all of the instances of the application running on this computer, so that users can launch several instances without logging in and consuming an additional license. Typically this will just monitor one user, but it can monitor several instances if Terminal Services are enabled. Here are the expected values for this setting: ActiveHidden The default value. This value causes the Session Manager to run, but its icon is not displayed within the System Tray.
SessionManager
ActiveInTray Causes the Session Manager to run; there is an icon displayed in the Windows system tray. Disabled Causes the Session Manager to be turned off. Whenever a shortcut or Information Worker attempts to launch the application, a login window will display. Any Information Worker processes or MFGSYS shortcuts you launch do not consume an additional license if the Session Manager is running and an instance of the client application is already logged on to the appropriate AppServer.
SessionManagerUri SplashImage SysmonPort ToolbarSettings Version
The Uniform Resource Identifier address the client should use to communicate with the manager service. The splash screen image when you first log into the application. The port used for the Session Manager. Enter the port that this computer will use. For example: 7777 The path and XML file that defines the users default settings for the toolbar functionality. For example, .\res\ToolbarSettings.xml. The current release and patch number for the application; for example "9.05.700". Defines whether business object logic or File-Copy logic is used to transfer files (attachments, reports, and so on) from the client to the WebServer when Epicor Web Access (EWA) forms are generated from customizations and dashboards. Available values: BusinessObject When you specify this option, a standard client to server communication method is used while the application transfers information from the client to the EWA WebServer file system. You then have increased security, as the EWA WebServer file system does not need to be accessed by the client Windows user. Direct When you specify this option, the Windows File-Copy logic is used to transfer information from the client to the EWA WebServer file system. You need to expose the EWA WebServer file system for Read/Write access by the client Windows user.
WebServerFileTransfer
User Settings The User settings contain parameters that only apply to a specific user. Use these parameters to activate the Single Sign On feature, System Monitor settings, login settings, or search settings. Typically system administrators define these settings for a specific user; this configuration settings file is then used to launch the application on the specific workstation. SETTING PURPOSE AND EXPECTED VALUES The concentration of pixels on the window, this setting accommodates different geometries of forms in different versions of Windows. None The default. No adjustment of forms is done. AutoScaleMode Dpi An adjustment (dots per inch) of concentration for pixels is done on forms. The forms are adjusted to adhere to the DPI field on the Display Properties > Settings > Advanced General form in Windows XP and Control Panel > Display > Custom DPI Settings form in Windows 7. Common settings are 96 DPI and 120 DPI. ComboAutoCompleteMode Defines how automatic completion works in the combo control when the user types in the text field of the combo. Only two values can be used - AutoCompleteOnly and DropDownList. Indicates whether network compression can be run through this .mfgsys configuration file. This setting uses the following syntax: <CompressionEnabled value=true/>
CompressionEnabled
Although these network compression settings are defined within the .mfgsys configuration file, you must activate them on each user account. With this feature, you can indicate which high traffic users require network compression. To do this, launch User Account Maintenance, navigate to the Options sheet, and select the Enable Network Compression check box. Controls the levels the compression library uses to compress network traffic. The available values for this setting are 1-9; consider the values 9 (Maximum, Slowest), 7 (Normal), and 1 (Very Fast). This value represents the level at which you will dedicate CPU time for compression to determine how compressed the resulting data will become. The higher the value, the less data will go over the network, but note more time is then required on the server to run the compression routine. Depending on the network, a higher value can actually lead to slower performance than a lower value. The value you define for this setting depends on your network resources. Run tests or work with your network consultant to find the optimal value. This setting uses the following syntax: <CompressionLevel value=7/>
CompressionLevel
CompressionThreshold
Indicates how big the transmission must be, in bytes, before the compression is activated. Messages smaller than this size are not compressed. Allowable values for this setting are 256 32,768. A value of 512 is the default and the suggested size for WAN users. Overall system performance can increase if the compression threshold is increased for LAN users. Run tests to determine the optimal compression threshold for your network. Use this setting to adjust the size of the context menus. Depending on the value you enter, context menus can become taller or shorter. The expected values are: 0 All Open With items display within the More sub-menu.
ContextMenuNestingLevel
-1 All Open With items display directly on the context menu. X Substitute an integer value (2, 3, 4, and so on) to indicate how many items to display in the context menu; the remaining items will display in the More sub-menu.
For example: <ContextMenuNestingLevel value =0/> DataCollectionUser
Defines whether or not this user is a data collection user; these users only have access to Data Collection functionality. Two values can be used - true or false. EPICOR SOFTWARE CORPORATION | 9
SETTING
PURPOSE AND EXPECTED VALUES This value controls the default location of search forms as they open. Available options: Top Search forms open at the top of the window from where you launched the search. This value generally provides more real estate for displaying the search results. Center Search forms open in the middle of the window from where you launched the Search. This setting is best for Multi-Monitor configured client systems, as the search window opens centered on the user interface form regardless of which monitor is displaying the Epicor application.
DefaultSearchFormLocation
DefaultSearchPageSize
Use this value to control the maximum number of records returned by a search for display within the search results. Lower values generally make more efficient use of server and network resources. Common settings range from 100 to 1000. Use this setting to determine the initial behavior of a user interface (UI) form as it opens. When no value is specified for this setting, a UI form opens with no special processing. Available options:
FormOpenMode
AutoSearch The primary search for each UI form automatically displays as the form launches. AutoPopulate The primary search for each UI form is automatically run, and all selected records automatically populate the form as it displays on your screen. This setting is used with the LoginDefault setting. When LoginDefault is set to Last, the value of LastLoginID is the last user ID entered during the logon process.
LastLoginID When LoginDefault is set to List, the value of LastLoginID is a series of previously entered user IDs that have accessed the application. For the other LoginDefault setting values, LastLoginID is not used and is typically set to have no value. The login default setting that defines what displays in the User Name field. Possible values: Last Displays the last user ID that was used. LoginDefault List Displays a list of all the recently entered user identifiers. Windows Displays the same user ID used to log onto Windows on this client machine. None No default value; the User Name field will be blank. Password The password for auto-login; for example, BobS. This setting controls if a ribbon view or a standard toolbar is used on forms. Possible values: RibbonView True The commands from the standard toolbar will be dispersed in several ribbon tabs on the top of forms. False A standard toolbar will display on forms. SelectTextOnEnter This setting determines whether an entire word or number is selected when you click a field with a value. Only two expected values can be used - true or false. The choices are true or false (the default). A value of true means the application should use single sign-on logic, and not prompt for user ID and password but instead use the user ID of the current Windows user. The location of the smtp server; the smtp server is required for email. Defines whether or not the System Monitor will start when the application is launched. Only two values can be used - true or false.
SingleSignOn
SmtpServer StartSystemMonitor
SETTING
PURPOSE AND EXPECTED VALUES Use this setting to launch the application with a default theme and option. You can then display the application using a look and feel you prefer. The attributes you define are the style and the options for that specific theme. If you want to use the default Epicor appearance without running the styling features, enter None in these parameters. Enter Default to use the theme defined as the default on the server. If you would like to use another server distributed theme (other than default), specify its name and file extension. To use a theme from any location on a local computer, enter the complete path and filename. For example:
Style
<Style value=C:\epicor\MyThemes\BlueMain.isl options=SpecifyName|None|Default/>
<Style value=BlueMain.isl options= SpecifyName|None|Default/>
<Style value=Default options=SpecifyName|None|Default/>
<Style value=None options=SpecifyName|None|Default/>
For more information, review the Styling and Themes chapter within the Epicor ICE User Experience and Customization Guide.
The frequency that determines how often the client System Monitor checks the server when non-priority print jobs are scanned and processed. This non-priority value is used for Scheduled reports. SystemMonitorNonPriorityPoll This value is measured in milliseconds; the minimum value is 3000 - the higher the number, the more network traffic is avoided. This value is used with SystemMonitorPriorityPoll and SystemMonitorPriorityPollDuration to determine how the System Monitor interacts with the tasks sent to it. The frequency that determines how often the client System Monitor checks the server when priority print jobs are scanned and processed. This non-priority value is used for reports sent immediately to the System Monitor. SystemMonitorPriorityPoll This value is measured in milliseconds; the minimum value is 3000 - the higher the number, the more network traffic is avoided. This value is used with SystemMonitorNonPriorityPoll and SystemMonitorPriorityPollDuration to determine how the System Monitor interacts with the tasks sent to it. The value of this setting determines how long the System Monitor will remain in Priority Polling Mode. By default, the System Monitor regularly polls the AppServer using the milliseconds defined for the SystemMonitorNonPriorityPoll value. This Non-Priority Mode is used by the application to process scheduled reports through the System Monitor. When a report is submitted directly (not scheduled) for processing, the System Monitor is then switched to Priority Polling Mode. SystemMonitorPriorityPollDuration While in Priority Polling Mode, the System Monitor polls the AppServer using the milliseconds defined for the SystemMonitorPriorityPoll value. The Priority Polling Mode lasts for the milliseconds value you define for this SystemMonitorPriorityPollDuration setting. Once the process goes past this duration value, the System Monitor returns to Non-Priority Polling Mode. This value is used with SystemMonitorNonPriorityPoll and SystemMonitorPriorityPoll to determine how the System Monitor interacts with the tasks sent to it.
SETTING
PURPOSE AND EXPECTED VALUES Use this setting to enable the Text Expansion Test item within the Tools menu on each form. Since the translations sometimes result in longer strings than the original, it is important that developers allocate sufficient space for language expansion. This item helps developers achieve this task and check which forms do not have sufficient space allocated. Only two expected values can be used - "true" or "false".
TextExpansionTest
You can fine tune the text expansion behavior in the Client\Res\EpiResourceLibConfig.xml. For example: <Options> <option <option <option <option name="TextExpansionFillChar" value="^" /> name="TextExpansionEndChar" value="|" /> name="TextExpansionMinChars" value="8" /> name="TextExpansionPercentRatio" value="30" />
The value of this setting determines whether tree nodes should be checked to see if they have children when they are created. When there are large numbers of nodes being created (over 1,000), this can take a long time. If the number of rows available for the child view is greater than the value TreeExpandIndicatorTreshold set, child node processing will be deferred until the indicator is selected for expansion. Zero value implies to always check for children. 200 is a good value if you enable this feature. For example: <TreeExpandIndicatorThreshold value="200" /> UserID The user ID for auto-login; for example, "BobSmith".
</Options>
Deployment Settings The Deployment settings contain general client distribution parameters. Modify these parameters to configure how files are moved from the server to the client. These settings define the directory path that the client uses to locate the server files and the method used to receive these files either Xcopy or zip. Typically system administrators define these settings and then distribute the updated configuration files to all workstations within the network for which they apply. SETTING clearClientDir PURPOSE AND EXPECTED VALUES This setting determines whether to clear the local client directory before a client update. Available options are Never, Always, and Prompt. This setting determines whether the local client cache will be cleared as part of a client update. Either the default cache location of C:\Documents and Settings\All Users\Application Data\Epicor\<appserver_ and_port> (Windows XP), C:\ProgramData\Epicor\<appserver_and_port> (Windows 7), or the directory specified by alternateCacheFolder is conditionally cleared based on the value you enter for this setting. Available options are Never, Always, and Prompt. If the setting of deploymentType is defined as zip, the value of this setting is the name of the zip file retrieved from the Deployment Server during a client update. The default value is: ReleaseClient.zip The URI of the deployment directory on the deployment server. The method the deployment system uses to do actual deployment of client assemblies. deploymentType The choices are xcopy and zip (which copies a named zip file locally and then unzips).
clearDNS
deploymentPackage deploymentServer
SETTING
PURPOSE AND EXPECTED VALUES If deploymentType is set to xcopy, this setting determines whether the xcopy runs and does a date comparison with the /D switch, or downloads all files regardless of date.
doDateComparison The choices are true or false. If it is set to false, then xcopy copies all files regardless of modification date. optimizeAssemblies A setting that determines whether you can optimize assemblies within the Epicor application. The choices are true or false. A setting of true requires that you have administrator rights on the client installation.
Help Settings The Help settings configure how the help system is hosted. You can host the help files locally on a client or centrally through a server. You can also define how the client installation accesses Epicor ePortal and Internet-based online technical updates. Typically system administrators define these settings and then distribute the updated configuration files to all workstations within the network for which they apply. For additional information about how to use these settings, review the Help System topics within application help. SETTING AnnotationsOverrideXSL PURPOSE AND EXPECTED VALUES The path or filename of the .xslt file; this file lets the user print help annotations. If you want to give users the ability to print their annotations, enter a path or filename within this property. For example: \\myServer\Epicor\MfgSys905\Help\enu\Standard\myXSLT.xslt/> The path name for the embedded courses licensed to your Epicor application. After you install the education courses, enter the path to the courses within this parameter; for example: http://EpicorEducation/EpicorEducation9001/ . Note that Epicor recommends you create a separate configuration settings file for your training environment and then link this settings file to a unique desktop icon. In this way, the embedded courses are not available within your working environment. The product and URL used when the user accesses the Customer Center; for example Epicor followed by the URL href = https://epicweb.epicor.com/support/epicor9/ If the URL changes for the Education Courses License server, this setting indicates the new server location which holds these licenses. Typically this value remains blank. If a new server is required, however, enter the URL path for this setting.
courseServer
CustomerCenter product
E9EducationKeysServer
featureSummaryHomePage The home page for the Feature Summary, for example fs.htm. helpServer The path name that is used to point the client machine to the help files. If you want to link the help files to a central server instead of individually on each client, enter the path to the help files location on the server. The product and URL used when the user accesses online (ePortal) support; for example Epicor followed by the URL href = https://epicweb.epicor.com/support/myepicweb
OnlineSupport product
Sort Settings The following settings define how strings sort within the application. If you update a Client installation, the Sort settings are overwritten to match the values defined on the server level configuration file.
SETTING
PURPOSE AND EXPECTED VALUES This value indicates the method used globally to sort strings within the application. The available values are: stringSort The default value, this sort method does not use any special sort weighting. This causes non-alphanumeric symbols, like hyphens, to be displayed together. This is useful, for example, if your company uses the hyphen in part numbers. Under this logic, the hyphen character has a weight like any other character, so records using this character are sorted together, based on the hyphens Unicode sequence value.
Sort Method Default
wordSort This sort method gives non-alphanumeric Unicode characters (like the hyphen) a reduced sort weight, causing these characters to be sorted among the alphanumeric characters. This reduced sort weight is not based on its Unicode sequence value. Under this logic, co-op and coop are listed together. To set the global default value for the application, use one of the following syntaxes: <wordSort value="default" /> <stringSort value="default" />
You can also create exceptions to the default sort method by adding additional lines after the default value. You do this by defining the table and column (TableName.ColumnName) that sort using the different method. For example, if your application globally uses the wordSort method, you can enter a new line under the default line (<wordSort value=default />) that indicates the stringSort method will be used on part numbers. This exception value uses the following syntax: <stringSort value="Part.PartNum" />
Sort Method Exceptions
Each exception line only supports one table/column combination. To apply this logic to multiple table/columns, enter multiple lines: <stringSort value="Part.ParNum"/> <stringSort value="Customer.CustNum"/>
Continue to enter all the exception lines that you need. If a column has a LIKE value, and the LIKE is one of the columns specified here, the other column uses the same sort method logic as well. Tools Settings Use the Tools settings to review and update the default values required for localization and the Software Developer Kit (SDK). These values must be added manually to the config file. Localizations modify the interface to display using the language and culture format required by a country or region. The SDK toolset enables developers and advanced users to extend the application in order to create new tables, business objects, and UI forms. SETTING PURPOSE AND EXPECTED VALUES Indicates whether the Country/Group Code drop-down list displays on the user interface. This list defines country group and country localizations. If you are localizing the Epicor application, you can select the country/group code on various programs and items (like business activity queries and userdefined codes) to structure how you want the localizations to display throughout the companies within your organization. localizationDeveloper This value is primarily for Epicor Partners developing localization solutions for the application. By default, this setting is set to false to hide the Country/Group Code drop-down list from most users. If you are a localization developer, however, enter true for this value. The Country/Group Code drop-down list will display on various programs throughout the Epicor application, where you can select country/group values from it as you need. For more information, review the Country Group and Country Codes section in Chapter 8: Localization. 14 | EPICOR SOFTWARE CORPORATION The Software Developer Kit is a set of tools sold separately from the application. If you need to extend functionality beyond the tools provided within the application, contact your Epicor Account Manager to purchase the SDK toolset.
SETTING
PURPOSE AND EXPECTED VALUES The files used to link your SDK project to the code for the server (.ini) and your database (pf). The .ini file links the SDK project to the server source code. The .pf file links the SDK project to your database.
OpenEdgeParameters For example: -pf C:/_Projects/MfgSys803/Deployment/Server/Config/MfgSys.pf -ininame and C:/_Projects/MfgSys803/Deployment/Server/Config/MfgSys.ini The password that you use to log into the application. For example: W325 Password If you do not enter a Password and then attempt to generate SDK business objects, an error message displays that stops this process. The client directory that contains your new and customized SDK applications. For example: C:\_Projects\MfgSys905\Source\Client\ The name that is used to link your SDK projects to their .xsd files. When the .xsd file is created, this target name value is automatically added as an attribute to the .xsd file. For example: www.epicor.com/Mfg/100 The user identifier that you use to log into the application. For example: ChrisK UserID If you do not enter a User ID and then attempt to generate SDK business objects, an error message displays that stops this process.
TargetLocation
TargetNameSpace
Run Time Arguments

Each workstation can be set up to launch the application in a specific mode. These modes, or run time arguments, activate immediately when a user double-clicks on the program icon. Several run time arguments are available. You can, for example, indicate the application launches either the Dashboard or the MES interface - instead of the default Main Menu. You can also have the application launch using a different configuration file. Run time arguments are also useful, for example, when you are customizing programs. Normally during Run Time, you have several favorites groups that autoload their programs into memory. You cannot, however, customize autoloaded programs. To disable this feature while you are customizing, you use the /AUTOLOADSUPPRESS run time argument; this prevents the application from autoloading any programs. You can also use multiple run time arguments at the same time to further define how the application launches on the workstation. For example, you want a workstation to only use the MES interface and you also want it to update to the latest version. Because of this, you use both the /MES and /UPDATE run time arguments. Activate Run Time Arguments You add run time arguments to the properties of the application icon. Heres what you do: 1. On the desktop for the workstation, right-click the applications icon. 2. A Context Menu displays. Select the Properties command. 1
3. The applications Properties window appears, displaying the Shortcut tab. 4. In the Target field, enter a [Space] after the target directory path. 3 5. Enter a right slash ( / ) or en dash ( - ), followed by the run time argument. For example, C:\epicor\905client\client\MfgSys.exe /UPDATE or C:\epicor\905client\client\MfgSys.exe -UPDATE 6. To add another run time argument, repeat the steps. For example: C:\epicor\905client\client\MfgSys.exe /UPDATE /CONFIG=mydefault.mfgsys or C:\epicor\905client\client\MfgSys.exe -UPDATE -CONFIG =mydefault.mfgsys 7. Click Apply. 8. Click OK. The next time the application is launched on this workstation, it uses the run time argument or arguments you entered. 4 5 6
Run Time Arguments List

This table lists all the run time arguments available for the application. They display in alphabetical order. New run time arguments may have You can enter these arguments in two ways. You can enter the entire argument; for example, /AUTOLOADSUPPRESS. The application also accepts, however, a shorthand version that only uses been added since the publication of this user guide. Use the /HELP the first three characters of the argument; for example, AUT. or -HELP run time argument to You can use either the right slash ( / ) or the en dash ( - ) to activate run time arguments. display the current list. ARGUMENT ? or HELP PURPOSE This mode causes a window to appear that displays all the available run time arguments. Use this mode to get a quick list of the current options. The autoloading feature causes selected favorite groups to load all their programs into memory; it improves the performance of these programs. If you customize the application, however, you need to suppress autoloading. By running this argument, you disable autoloading on this workstation. To learn more about the autoload feature, read the AutoLoad Favorite Groups section in the Personalization chapter within the Epicor ICE User Experience and Customization Guide. BASE Use this argument to prevent the loading of any verticalizations (industry-specific user interface features), customizations, or personalizations. This option is useful for testing the user interface.
AUTOLOADSUPPRESS
ARGUMENT
PURPOSE This argument causes the application to use a different configuration file saved in the same folder as the default.mfgsys file. Enter the name of the file after the equals sign. The next time the application is launched on this workstation, it uses this configuration file. For example: C:\epicor\905client\MfgSys.exe /CONFIG=mydefault.mfgsys This argument causes the application to launch using the CRM User Interface. Use this mode to display the application for a user with a CRM user license. This interface displays modules which include: Customer Relationship Management Case Management Quote Management Configurator Management ShopVision Trackers Status Dashboards
CONFIG=<filename>
CRM
DB
Use this argument to cause the Dashboard interface to launch - instead of the Main Interface. Use this mode if you only want this user to access a dashboard interface. To learn more about dashboards, review the Epicor ICE Tools User Guide.
HH
This argument causes the application to launch using the Handheld MES Interface. Use this mode to display the application within a handheld device. This interface displays the tools needed to report labor, inventory, and material transactions against jobs. Use this argument to launch the Handheld MES Interface in Customization mode. You can then customize this interface as you need. For more information, review the Sub Program Deployment section in the Customization Utilities chapter within the Epicor ICE User Experience and Customization Guide. This argument causes the application to launch the MES Interface - instead of the Main Interface. Use this mode for workstations being used by the shop floor. This interface displays the tools needed to report labor, inventory, and material transactions against jobs. Use this argument to launch the MES Interface in Customization mode. You can then customize this interface as you need. For more information, review the Sub Program Deployment section in the Customization Utilities chapter within the Epicor ICE User Experience and Customization Guide. You can limit the programs available on the Menu Menu by including a menu identifier with the config run time argument. To do this, add a run time argument (a right slash or en dash), followed by the specific menu identifier. You can find the specific menu identifier you need in Menu Maintenance; for example: C:\_epicor\905client\MfgSys.exe /menuid=CRMN0000 Use this argument to give the application multiple printer options. When active, the application first checks to see if a default printer is selected on a Crystal Report definition. If it is, this printer and its settings are automatically used to print the report. If a printer is not defined on the report definition, however, the default printer selected on the workstation is used instead. Use this runtime argument when you need a specific printer, like a label printer, to print a specific report. Use this argument to prevent updates from being automatically installed on this workstation. It stops the client application from checking its version number against the current version on the server.
HHC
MES
MESC
MENUID=<Menu ID>
RPT
SKIPCHECK Run this argument to streamline how quickly the application launches on this workstation. By disabling these routines, the application no longer automatically updates each time it is accessed. This argument causes the application to skip checking its version number, but then updates the workstation to the current version available on the server. This forces the client to update even when the version on the client and the server are the same. Use this argument when you install a patch on the server; this patch then automatically updates on your client installations. You can also use this argument when a problem occurs on a client installation. Adding this argument makes sure the client installation is using the current version. EPICOR SOFTWARE CORPORATION | 17
UPDATE
STYLING AND THEMES | CHAPTER 2
Chapter 2 Styling and Themes
Complete control over the look and feel of the entire interface is available through the styling functionality. You can use this toolset to display a pre-built design, or theme, from the options installed with the application. You can also use these tools to edit an existing theme and create a new theme. Through the styling functionality, you manipulate the look of each item, or component, within the interface buttons, check boxes, fields, borders, and other items. You have complete control over the look of each component, as you can update the different states in which they display. For example, you can create multiple button states normal, selected, pressed in a graphics program and then add these various states as the default look for all buttons within the application. Because you are updating one user interface definition, or UI role, the changes you make display globally throughout the interface. Your updated or new theme can then be made available to everyone within your entire organization. This toolset contains export and import functions, which you can then pass along your revised or new theme to whomever you want. Use the styling functionality to create a user interface unique for your company, departments, and users. By refining the look of existing themes or creating new ones, you can transform the application to display an entirely different look and feel.
CHAPTER 2 | STYLING AND THEMES
User Maintenance
Only specific users can access the styling functionality. You give users styling rights through User Account Maintenance. Main Menu Path: System Management > Company Maintenance > User Assign Styling Rights in User Maintenance To assign styling rights to a user account: 1. Use the Detail sheet to find and select the user record you need. 2. Click the Security sheet. 4 3. Select the Can Maintain Themes check box. 4. Click Save on the Standard toolbar. This user can now access the Styling features. The next time this user logs into the application, the styling features are available on the Options menu from the Main Menu. 1 2
Style Theme Loading

You can load any pre-built, new, or updated Theme to quickly preview and edit the look of the interface. You do this in the Load Style Theme program. Some alternate themes were automatically installed with the application. If any new or revised themes become available on your system, you can also select them to preview and edit through this functionality. Load Style Theme To preview the interface theme: 1. On the Main Menu, from the Options menu, select Styling > Load Style Theme. 1
| STYLING AND THEMES3 4 20 | EPICOR SOFTWARE CORPORATION
2. The Open window displays. 3. This window defaults to the Styles folder. This folder contains all default themes available for your application. 4. Select the theme you want to use. Notice that all themes use the .isl file extension. In this example, you select the ArcticBlue.isl theme. Epicor recommends you to save all your themes within this folder; this makes it easy for your users to find and select them. This folder is located within the C:\epicor\<Client Installation Name>\Client\Styles. 5. Click Open.
3 4
6. The interface now displays using the selected theme.
You can now use this theme for the rest of the current session. You can also use the Runtime Stylist to edit the theme. Note that if you exit the application, however, the theme reverts back to the default theme. If you want a different theme to become the default, run the Theme Maintenance program. Use this tool to indicate that a different, selected theme becomes the default look when you launch this client application. For more information about this tool, read the Theme Maintenance section later in this chapter.
Another way to define a default theme is to change a setting within the Configuration Settings File.This file controls several global sessions for your client installation. To define a default theme in this file, you change the Styles setting. You can learn more by reviewing the Configuration Settings File section within Chapter 1: Startup Configurations. Customized controls can also be set up to display a specific style; review this functionality within Chapter 5: Advanced Customization. EPICOR SOFTWARE CORPORATION | 21
Runtime Stylist
The primary tool of the Styling functionality is the Runtime Stylist. Use this tool to change the appearance of every component within the user interface. You can then see this change immediately, as the interface is updated while the application runs. This helps you decide if you like, or do not like, the change to the interface. You use this tool to modify an existing theme or create an entirely new theme. You can then use this theme for your client installation and make it available to other users within your company. The application runs in two modes Run Mode (or Runtime) and Developer Mode. Typically you use the application in Run Mode, which means that the application sheets are used for normal activities like data entry and processing. The Runtime Stylist operates in Run Mode, so you can see the application in action while you edit the styling. In Developer Mode you suspend the normal operation of the program in order to customize it. The styling features are never used in Developer Mode. For more information about the two modes, read Chapter 4: Basic Customization. Runtime Stylist divides the user interface items into three main categories UI Roles, Component Role Settings, and Shared Object Role Settings. Each of these categories has various properties and options that you can manipulate as you need. The differences between these categories are explored later in this section. The Runtime Stylist is a third party application published by Infragistics, Inc. The tool is based on this companys NetAdvantage AppStylist application. This section of the chapter gives you a tour of the primary features of this tool.For complete information on this company and its products, please visit their website at: www.infragistics.com.
Launch the Runtime Stylist To launch the Runtime Stylist: 1. On the Main Menu, from the Options menu, select Styling > Runtime Styler. 1
2. The Runtime Stylist displays next to the Main Menu. You can now use this program to update or create new themes. 2
Runtime Stylist Primary Controls

This section defines all the main controls within the Runtime Stylist. Use these controls to create a new theme, load an existing theme, and manage the default styling on specific components. Use Style Library The Style Library displays on the top section of the Runtime Stylist. This section contains the primary controls for this program. Available options: 1. The Style Library: section indicates which theme is currently loaded. 1 In this example, the Office2007Calibri.isl theme displays. Note that the files for themes all use the .isl extension. 2. Click the New button to create a new theme. 3. To update an existing theme, click the Load button. 4. To create a copy of the current theme, click the Save As button. 5. Click Save to record your changes to a current theme. 6. If you want to constantly display the Property Panel, click the Show/Hide Property Panel button. The Property Panel always stays on your screen; it displays different items based on the selected setting, component, or UI role. 7. The Update Mode tab defines how the interface refreshes after you make changes to the current theme. The Runtime Stylist is set to immediately update the interface; you cannot change this value. 2 5 6 7 3 4
Manage StyleSets The base look and feel of each interface component is defined through a StyleSet. Much like a cascading style sheet determines the look and feel of an .html page, a StyleSet determines the original overall look contained within the selected theme. You can then change the baseline look of each component through the Runtime Stylist. Use the middle section of the Runtime Stylist to control the StyleSet used on the current theme. Available options: 1. Click the Add New, Remove, or Manage StyleSets buttons. 1
3 3. Click the Add New button to 5 create a new StyleSet to add to the current Style Library (theme). It is called New StyleSet followed by an incremented number. 4. To delete the current StyleSet from the library, click the Remove button. To the confirmation message, click Yes. 5. If you wish to change the default StyleSet used by the current theme, highlight the StyleSet option you want from the Existing StyleSets list. For example, the EpiStyle_Invisible style set is used to hide a specific field. However, you could change this style to use a gradient, image, or other style. You can then apply this style to a field using the Rule Wizard. For more information, review the Rule Wizard sections in Chapter 5: Advanced Customization. 6. Select the Make Default option. The StyleSet now displays in bold text followed by this word: (Default)
2. The StyleSet Manager window displays.
8 9
10
7. The StyleSet Name field displays the selected StyleSet. If you need, you can change the name of the StyleSet. 8. To use one StyleSet as the foundation for a new StyleSet, select this StyleSet from the Based On drop-down list. In this example, StyleSet 2 is based on StyleSet 1.This means that StyleSet 2 now uses all of StyleSet 1s component styles unless this styling is changed within StyleSet 2. 9. Use the Control Defaults list to select a style for a specific component. To do this, select the check box next to the component. This style is now the default for this component within the current theme. Only one default style is defined for each component, so if you select a component that already has one, you are asked if you want to change it. 10. When you finish working on the StyleSets for this theme, click OK.
Resources
Resources are containers of style information that you can then use within themes. A resource can be any item you create or add to a theme, like a gradient or a graphic file. Each resource can then be applied to a UI Role. You can use the Runtime Styler to import and export various resources (graphics, colors, and other settings) that you use with your themes. You can then incorporate these resources into any role on the user interface that you need. UI Roles are styling records that create a uniform look for the various interface components like buttons, fields, borders, check boxes, and other items. To learn more about UI Roles, read the UI Roles section later in this chapter. Manage Resources Use the Resources tab to manage all the resources stored within the current Style Library (theme). To use this tab: 1. Click the Resources tab. 1
2. Click the Add New button to create a new resource. This displays the 2 Properties Panel; use this window to create the resource. To learn more about this key styling window, read the UI Roles section later in this chapter. 3. After you add a resource to the current Style Library, it is labeled as Resource 1, Resource 2 and so on. To change the label text, right-click the resource; its context menu displays. Select the Rename command to change the label. 4. Notice that you also Add New and Remove resources through this context menu. 5. If you want to duplicate the selected resource, select the Create Copy command from the context menu. 6. To create a new resource from another resource, use the commands under the Copy From submenu. 7. To delete a resource from the Style Library, highlight it and click the Remove button. 4 3 5 6
8. You can also pull in the resources from another style library (theme). To do this, click the Import button. This launches the Open Style Library window from which you select an .isl file to load. For more information, read the next section, Resources Tab Importing Resources, to learn about the import functionality. 9. If you click the More Buttons icon, you display the Export button. Click this button to save this resource list as a separate file. This causes the Save Style Library button to display, where you can select a folder and enter a filename for the new library. Import Resources While you import resources, you can indicate which specific resources you want imported from a selected style library (theme). To select the resources: 1. On the Resources tab, click Import.
2. The Open Style Library window displays.
3. By default, this window opens the Styles folder. If you need, you can navigate to another folder that contains the .isl file (theme) you need. 4. Select the .isl file that contains the resources you want to import. 5. Click Open.
6. The Select Resources window displays.
7. You can now indicate which resources you want to import from the style into the current theme. If you want to import a single resource, highlight it from the list. To select a range of resources, hold down the <Shift> button on your key board and select two different resources; all the resources within this range are selected. To select specific, multiple resources, hold down the <Ctrl> button on your keyboard while you select the specific resources you want to import. Notice that in this example, the <Ctrl> button was used to select the highlighted resources. 8. To select all the resources in this library, click the Select All button. 9. To remove your selections, click the Deselect All button. 10. When you finish, click OK. 9 10
10
If an imported resource has the same name as a resource currently used in your theme, the Resource Name Conflict window displays. Use this window to rename the resource and resolve the name conflict.
11 11. The resources you selected display within the Resources tab.
Roles
Use the Runtime Stylist to update the styles of specific components through the Roles tab. To do this, you use the Roles Tree View to navigate through all the components on the user interface. You can also use the Tree View to launch the Properties Panel for each UI Role, so you can make detailed appearance changes on each role. Roles use an inheritance feature to help you make global changes to a theme. When you make a change to a base role, this change is then passed along to all the components that use this base role. For example, each base role contains a default background resource; you can change the color on this resource. This causes all the components which use this base role to display using the same background color. You can, however, override this inherited styling on specific components. Leverage this functionality to create an overall style for your theme, but then add variations to it as you need. This section describes the three main role categories UI Roles, Component Role Settings, and Shared Object Role Settings. It also describes the specific options you can change for each role type. Change the Look of UI Roles A UI Role is a category that defines the overall look for buttons, labels, radio options, or any other component on the user interface. You change the look of each UI Role through the Runtime Stylist. These changes then display on any component that uses the UI Role. To do this, UI Roles have a parent-child relationship organized through a Tree View. Any property changes you make to a UI Role that has a higher node within the tree causes other UI Roles beneath it to display the same changes. If you make a change on a child UI Role, however, this change does not override the settings defined on the parent UI Role. As a result, you can create unique styles for specific components. To navigate and select a specific UI Role: 1. Click the Roles tab. 2. To reduce the number of UI Roles that display, click the Filter by Control drop-down list. Select the specific component that you want to change. In this example, you select the UltraButton option; now the Tree View only displays the UltraButtonBase role and its child roles. 3. In the Tree View, expand the UI Roles node. 4. Click the Base parent node and continue to expand the child nodes until the UI Role you want displays. 5. In this example, you want to change the properties for the UltraButtonDefault role. Select this role. H 1 2 3 4 If you need to override styling from a base role, you must set the components UseOSThemes property to False. The example at the end of this chapter shows you how to change this setting.
6. The Properties Panel 6 window displays. Use this panel to change the 9 style settings for the role. For this example, the panel is labeled: Settings for UltraButtonDefault
7 10
7. Each role contains various states through which it displays. Depending on the users actions on the interface, a different state for the component appears. In this example, the UltraButtonDefault role has a Normal state, a HotTracked (highlighted) state, and a Pressed state. You can edit the settings of each state as you need. 8. Notice you can always restore all the states of the current UI role to their original values. To do this, click the Reset States button. 9. Select the tab of the state you wish to edit. In this example, you select the Normal tab. 10. Notice that the bottom toolbar divides the states settings into Background, Border, Font, Image, and Other groups. The next sections detail the style settings available within each group.
Set Background Image for UI Role The Background options define what the current states background looks like including fill color, image (if used), disabled color, and alpha level. Available options: 1. Click the Background Fill drop-down list to define whether the background for the role is a solid color, gradient, or a hatch pattern. 2. Use the Fill button to indicate the main color displayed for the background of the state. When you select either a gradient or a hatch 1 pattern, two Fill buttons then display. You can then define the two colors used for the background gradient or pattern. 3. Click the Type button to define the gradient or hatch pattern type that displays. When you click this button, a list appears; select the gradient or hatch pattern type you want. 4. To substitute an image for the states background, click the Image button and select File from the drop-down list. An Open File window displays. Find and select the image file that you want to display. 5. If the main image is not available, you can indicate that a second image can be displayed instead. To define this image, click the Disabled Image button to find and select this backup image from the Open File window. 6. Click the Layout Mode drop-down list to indicate how this image displays within the state. Available options: Center The image is placed in the middle of any component that uses this state. Stretch The image is pulled across any component that uses this state. The image size is not modified, so it may or may not fill the entire component. Tile The image size is not modified. Instead, multiple versions of the image display through a series of tiles. 4 5 6 2 3
7. If you select the Stretched layout mode, the Margins button displays. Click this button to display the Stretch Margins Editor. 8. Use the Top, Right, Bottom and Left values to define the margins, in pixels, for the image. 9. When you finish, click OK.
10. You return to the Properties Panel.
10
11. Click the Image Alpha drop-down list to select how the image displays. Available options: UseAlphaLevel Select this option to use the Alpha Level defined on the Other section of the Properties Panel. For more information, review the UI Roles Other section later in this chapter. Opaque Users see this image exactly as it normally appears. Transparent Users can see through the image. 11 12 13
12. Use the Disabled Fill button to select what color is used when the main selected color is not available. If the Background Fill is for a gradient or a hatch pattern, a second Disabled Fill button becomes available. Use this button to select a second color to use when the second gradient or hatch pattern color is not available. 13. Click the Alpha drop-down list to select how the background fill colors display. Available options:
UseAlphaLevel Select this option to use the Alpha Level defined on the Other section of the Properties Panel. For more information, review the UI Roles Other section later in this chapter. Opaque Users see this color exactly as it normally appears. Transparent Users can see through this color.
Set Border for UI Role The Border options define what the border of the state looks like. Available options: 1. Click the Border button. 2. The Color Picker window displays. Use this window to define what color the current state of the UI Role uses along its edge. 3. If you want, you can also make the border appear transparent by clicking the Transparent button (the button with the red line through it) within the Color Picker. 4. After you select the color, you return to the Properties Panel. 5. Click the Border 2 button to launch the Color Picker; use this window to define a second color that this UI Role displays along its edge. 6. You can use the Border 3D button to select the color (from the Color Picker) of the three dimensional border. If you want, you can also make the border appear transparent by clicking the Transparent button (the button with the red line through it) within the Color Picker. 7. Click the Alpha drop-down list to select how the border color appears to the user. Available options: UseAlphaLevel Select this option to use the Alpha Level defined on the Other section of the Properties Panel. For more information, review the UI Roles Other section later in this chapter. Opaque Users see this color exactly as it normally appears. Transparent Users can see through this color. 4 2 3 1
6 7
Set Font Attributes for UI Role Use the Font setting to change the font type, size, color, style, and other font attributes for the selected state. Available options: 1. Click the Font Type drop-down list to select the specific font you use for this state of the UI Role. 2. Click the Font Size drop-down list to define how large the font displays. You can also use a size not available on this list. To do this, click the Font Size field and enter the number you need. 3. Click the Font Color button to display the Color Picker. Use this window to define the color this font uses. 1 2 3
4. Use the Font Style buttons to indicate whether any additional styling, like bold or italics, is used with this font. Available style buttons: Bold Italics Underline Strikethrough 7 6 5 4
5. Click the Vertical Alignment button to indicate the alignment that this text has in vertical relationship within the borders of the component. Available options: Top Middle Bottom
6. Click the Horizontal Alignment button to indicate the alignment that this text has in horizontal relationship within the borders of the component. Available options: Top Middle Bottom
7. If the text does not fit within the component borders, you can specify how to display this text by using the Text Trimming dropdown list. In this example, EllipseWord is selected, indicating that ellipses display on the component to indicate that additional words cannot be displayed. 8. Use the Disabled button to select what color is used when the main font color is disabled. Click this button to display the Color Picker; use this window to select the backup color that you need. 9. Use the Alpha drop-down list to select how the font displays on the component. Available options: UseAlphaLevel Select this option to use the Alpha Level defined on the Other section of the Properties Panel. For more information, review the UI Roles Other section later in this chapter. Opaque Users see this font exactly as it normally displays. Transparent Users can see through this font.
Set Foreground Image for UI Role Use the Image options to define how a foreground image displays within a component that uses this state. This image displays in front of any background image, color, gradient, or hatch pattern. Available options: 1. Click the Image button to find and select the foreground image you want to display. When you select the File option, an Open window displays that you use to search for the image file you want. 2. Click the Vertical Alignment button to indicate the alignment that this foreground image has in vertical relationship within the borders of the component. Available options: Top Middle Bottom 3 2
3. Click the Horizontal Alignment button to indicate the alignment that this foreground image has in horizontal relationship within the borders of the component. Available options: Top Middle Bottom
4. Click the Alpha drop-down list to select how the image displays on the component. Available options: UseAlphaLevel Select this option to use the Alpha Level defined on the Other section of the Properties Panel. For more information, review the UI Roles Other section later in this chapter. Opaque Users see this image exactly as it normally displays. Transparent Users can see through this image.
Define Additional Options for UI Role The Other section contains additional options that do not fit in any of the previous sections of the Properties Panel. Available options: 1. Click the Cursor drop-down list to define how the mouse pointer displays when it hovers over a component that uses this state. 2. The Alpha Level defines how visible the selected color level is for this UI role. The Background, Border, Font, and Image sections all have an option that can use this Alpha Level value; review these previous sections for more information. If the value is set to 0, the current state of the UI role does not appear. As the level increases, the state becomes more and more visible. It is fully visible at Alpha level 255. 1
2 3
3. The Themed Element Alpha button is similar to the Alpha buttons found on the Background, Border, Font, and Image sections. The value you select here, however, only applies to themed elements when the UseOsThemes property is set to TRUE. This property is a Component Role Setting that you can apply to all the UI roles within your theme; a later section in this chapter, Component Role Setting, explains how you change these settings. If you set this value to Transparent, you turn off the styling for this state of the UI role. Preview UI Role Use the Resources and Preview sections to both apply resources to the current state and preview how they display. You can also convert a state into a resource that you can then use in another state. To use this section of the Properties Panel: 1. To display the Resources options, click the Down Arrow within the Resources section. 2. To add a resource to this state, click the + (Plus) button. 3. To delete a resource from this role, click the - (Minus) button. 4. When a resource is higher in the list than another resource, its settings take precedence over any resource that is below it. 4 For example, the first EpiShape resource has a Green gradient on its background. The second EpiShape resource has a Yellow gradient applied to its background. The first EpiShape resource is higher on this list than the second EpiShape resource. Because of this, the state displays the Green gradient. 6 2 3 5 1
5. To change the order of precedence, select the resource and click either the Up button or the Down button. Continuing the previous example, if you move the second EpiShape resource higher than the first EpiShape resource, the Yellow gradient now displays instead of the Green gradient. The current state of the role updates with the resources you define. 6. Click the Convert to Resource button to capture the appearance properties of the current state. A resource is then created for these properties that you can then use in other UI role states. 7. Click the Down Arrow next to the Preview button to review how these resources display. 8. The Preview section displays how the selected resource looks using the current settings. 9. The 3D Preview section displays what the selected resource looks like in three dimensions.
Define Overall Styles for UI Role Use the Properties tab to define some overall values for the current UI role. Depending on the UI Role you select, you can define a Border Style, a Button Style, both styles, or neither styles. To define overall styles for the UI role: 1. Click the Properties tab. 1
2. To select a style for this UI role's border, click the Border 2 Style drop-down list and select a style. In this example, the list is grayed out, so only the default border style can be used. 3 3. Click the Button Style drop-down list to select a style for this UI roles buttons. Because this example is a role for UltraButtonDefault, this drop-down list is available. STY
Manage Component Role Settings Use the Component Role Settings features to style both Inbox Components and Infragistics Components. Inbox Components are interface items not included within the Infragistics component set. Both component types have settings that they share with other component role settings (Common Component Properties); they also have settings available only within individual components (Component Specific Properties). To navigate and select a specific component role setting, do the following: 1. Click the Roles tab. 2. Open the Component Role Settings folder. 3. You can select All Components, Inbox Components, and Infragistics Components. In this example, you select the Inbox Components node. 4. Select the component you want to modify. In this example, you select the Inbox CheckBox component. 1 Whether or not you change the common or component specific properties, you are only changing the style of the currently selected component role.
2 3
5 5. The Properties Panel displays. In this example, it is the Settings for Inbox CheckBox window. You can now modify these settings as you need.
Set Common Component Properties Use the first section of this window to modify any properties shared across all components. Available options: 1. Click the Categorized button to display the different categories available for the selected setting. In this example, only one 1 behavior is available: the Resolution Order. 2. Notice that a Description of the selected property displays at the bottom of this section. 3. To display these properties in alphabetical order, click the Alphabetical button. 4. Click the Property Pages button to view any page information. 2 4 3 5
5. To manipulate a specific property, click the propertys row. All the options available for this property typically display in a drop-down list. If a drop-down list does not appear, however, you may enter a value within the text field.
ResolutionOrder is a property unique to the Common Component Properties section. Use this property to define the order through which styling and component properties are resolved. For example, if you select ControlThenApplication, the style overrides any property settings defined on the control component with any settings defined within the application itself.
Set Specific Component Properties Component Specific Properties are items available only for the selected component role. To use this section of the window: 1. Click the Categorized button to display the different categories available for the specific setting. 2. Notice that a Description of the selected property displays at the bottom of this section. In this example, the BackColor description displays. 3. To display these properties in alphabetical order, click the Alphabetical button. 4. To view any page information, click the Property Pages button. 5. To manipulate a specific property, click the propertys row. All options available for this property typically display in a drop-down list. If a drop-down list does not display, however, you may enter a value within the text field. 2
3 1 5 4
Manage Shared Object Role Settings The Shared Object Role Settings node displays the objects used between multiple components. For example, the Embeddable Editors display under this node; these editors pull from base UI classes like EditorWithCombo, EditorWithMask, and EditorWithText. Any changes you make to these shared object roles are then passed along to all the components which use these object roles. The rule to remember is that when you change a Component Role Setting, you only change the component. When you change a Shared Object Role, you affect all the components that use the shared object.
To navigate and select a shared object role setting: 1. Click the Roles tab. 2. Open the Shared Object Role Settings folder. 3. All the shared object roles display. Select the setting you want to modify. In this example, you select the DragDropIndicatorManager setting. 1
4 4. The Properties Panel displays. You can now make the changes you need to this component.
Set Specific Properties for Shared Object Role Settings This section displays properties shared between several components. To use this section of the window: 1. Click the Categorized button to display the different categories available for the specific shared object setting. 2. Notice that a Description of the selected shared object property displays at the bottom of this section. In this example, BottomArrowImage displays. 3. To display these shared object properties in alphabetical order, click the Alphabetical button. 4. To view any page information, click the Property Pages button. 2 5. To manipulate a specific property, click the propertys row. All the options available for this property typically display in a dropdown list. If a drop-down list does not display, however, you may enter a value within the text field. 1 3 5 4
Components in the Used By Section

The Used By section of the Runtime Stylist displays all the components that appear using the selected UI role. When you select an item from this list, you display the Component Role Settings window, where you can make additional changes to this component. Modify Components in the Used By Section To leverage this functionality: 1. Use the Tree View to navigate to the role you want. 2. Select the UI Role you want to view. In this example, you select the Button role. 3. All the components that use this role display in the Used By section. 4. Select one of these components. In this example, you select the top UltraButton item. 1
5 5. The Component Role Settings window displays. Make the changes you need. For more information about the options on this window, review the previous Manage Component Role Settings section.
Role Selection
As you make changes to the current theme, you can navigate through the user interface to see how the changes look. Because the Runtime Stylist is active, however, you can also launch a component Property Panel to immediately make the changes you need. Use this tool to further refine your style. You can then make specific runtime changes to selected components as you see them on the interface.
Use Role Selection Tool To use the Role Selection tool: 1. Launch a program that you want to review. In this example, you launch the Analysis Code Maintenance program. 2. Hover your mouse over a component you wish to update. In this example, you hold it over a cell in the grid. 3. The Role Selection call out window displays. This window displays all the UI Roles and Component Filters that define the selected component in this example the grid cell. 4. To launch the Properties Panel for one of these roles or filters, press the specific key on your keyboard. In this example, you want to change the look of each grid cell, so press 1 on your keyboard. 2 3 1
5. The Property Panel, Settings for 5 GridCell, displays. 6 6. Make the changes you need to this UI Role. In this example, you create a gradient that displays within the cells of every grid.
7. The change immediately displays within the interface. In this example, the red gradient displays within each cell. Continue to use the Role Selection tool to make all the changes you want on the interface. When you finish your changes, save your theme.
Style Filter Management

Use Style Filter Management to create filters to use within a specific theme. You can create child style filters based on the original, or parent, theme. These filters limit these child styles so that their styling is only used within a specific company, plant, language, or program. The style filter functionality supports many styling combinations for the same theme, as you can create a child style filter that is then the child of another child style filter. This section also describes how you can create style filter combinations. Launch Style Filter Manager To launch this program: 1. From the Options menu, select Styling. 2. Select the Style Filter Manager. 1 2
Create a Child Style Filter To use Style Filter Management: 1. The filters available for the current theme display in the Tree View. 4 2. If you want to create a new style filter for a different theme, click the Load button to find and select the .isl file you want. 3. To create a child style filter, first highlight the parent style you want on the Tree View. In this example, the Default style is selected. 4. Right-click your mouse to display the context menu. Select the Create Child Style command. 3 1
5. A (New) style filter displays on the Tree View. Enter a StyleSetName for this child style filter. In this example, you enter Epicor Mfg - Chicago. The new Name displays on the Tree View. 6. Select a FilterType. Available options: Company Plant Language Application None
In this example, you select Company; you can now create a child style filter for a specific company within the default theme.
7. Define what item is affected by this filter. To do this, click the FilterTypeSelect drop-down list. Depending on the filter, different items display. In this example, all the companies within the application are listed, so you select the Epicor Mfg Chicago option. When users switch to this company, the interface displays using this child style. 8. The FilterValue displays the name that the application uses to identify the selected item. In this example, the company ID, VN30C, displays. 9. You can also define the EpiResources that use this child style filter. If you need, you could enter values in these properties to limit this child style to specific interface items, like panels, the OK shape, and so on. In this example, you leave these properties blank. 10. The EpiStyles section defines the additional interface components that use this style filter like the Message Box and the Navigation Control. If you need, you can enter additional style values in these fields.
7 8 9
10
11 12 13
11. The Description area displays an explanation for the currently selected property. This text changes as different items are selected. 12. You next must select the Create resources if missing check box. This indicates that you can create the main EpiResource for this style filter. 13. Click Save. 11 40 | EPICOR SOFTWARE CORPORATION
14 14. The Save Style Library window displays. 15. Select the parent theme inside which you want to save your child style filter. In this example, you select Office2007Calibri.isl. 16. Click Save. Your child style filter is now saved within the parent theme. Right now, however, this filter does not change anything. You next must launch the Runtime Stylist to define the styling you want for this child style filter.
15
16
Modify Child Style Filter To complete the child style filter: 1. Launch the Runtime Stylist (or Infragistics App Styler). 2. Click the Load button. 3. The Open Style Library window displays. 4. Select the theme that contains your child style filter. In this example, you select the Office2007Calibri.isl file. 4 5. Click Open. 2 3 1
6. When the Runtime Stylist displays, click the Active StyleSet drop-down list and select Epicor Mfg - Chicago. 7. Create your child style. Highlight an area of the interface, and press the corresponding key.
8 8. The Settings window displays. 9
9. Make the changes to this item that you want. For this example, you are changing the interface to shades of gray.
76 42 | EPICOR SOFTWARE CORPORATION
10. To see how this styling choice looks, on the Main Menu, launch a program within the Epicor Mfg - Chicago company.
10
11. All the programs within this company display using this child style. STYLING
11
12. Access another company, and in this example, you navigate to Epicor Corporation and launch Sales Order Entry.
12
13 13. Notice that the default styling displays within this program. This happens because the child style filter applies only to the Epicor Mfg - Chicago company. You can continue to create child styles for all the other companies within your organization. By leveraging this functionality, you make it easier for users to identify different companies when they switch between them.
Filter Inheritance Priorities Much like the roles use an inheritance hierarchy, the child style filters use a similar system. The styling defined on a filter that has a higher priority is passed down to a filter that has lesser priority. You can then override the inherited styling within a filter, however, by modifying a lesser priority. Here is the filtering hierarchy: 1. Default 2. Company 3. Plant 4. Language 5. Application Use this hierarchy to create many filtering combinations within a selected theme. For example, you first create a style filter for Company VN00C. You next create a second Language style filter, which you call Spanish. Lastly, you create an Application filter for Supplier, and this filter is a child style filter derived from the Spanish filter. Now when you launch the application and use VN00C for the company, you see the company filter styling. If you change the session to display the Spanish language, however, most of the forms now display using the Spanish filter styling. The only form that does not is Supplier Maintenance, which displays the specific styling you created through this application style filter. Next, you open the Supplier style filter again and modify it to be based on the Default filter. This child style filter is now applied throughout your application because it is directly related to the Default filter. Notice that this order of inheritance prevents certain parent-child relationships from occurring. You cannot, for example, pass along styling from a Language style filter to a Company style filter.
Style Tracking
Another styling tool that helps you create your theme is Style Tracking. You activate this tracking mode to find out the details for a specific interface component. Style Tracking is useful, for example, when you are trying to apply a style to a specific component. It helps you find the details about a specific component that you can then modify within the Runtime Stylist. Activate Style Tracking To turn on Style Tracking: 1. On the Main Menu, from the Options menu, select Styling > Style Tracking On/Off. This turns Style Tracking on. 2. If Style Tracking is active, the icon is highlighted. 1
View Style Tracking Information Now styling information displays for all selected components on the interface. To view the style tracking information: 1. Hover your mouse pointer over an interface component you want to review. In this example, you hold it over the Material check box. 2. The Style Tracking list displays. 3. The StyleSetName indicates which StyleSet is currently used for this component. 4. The Control Name displays the specific application name for the current component. In this example, chkMaterial is displayed. 5. The Control Type field indicates the application name for the interface component. For this example, the EpiCheckBox control type is displayed. 6. The Top Level Control field defines the main component that contains the selected component. In this example, AnalysisCodeForm is displayed. 7. The Read Only value indicates whether users can manipulate this control. If this value is set to True, users can only view, and not change, this control. You can then use this information to locate the UI role for this component within the Runtime Stylist. 1 2 4 3 5 7 6
Theme Maintenance
Use Theme Maintenance to manage all the themes you want available throughout your system. Use this tool to add, export, and delete themes. You can also select a default theme for all the client installations linked to your application server. To launch Theme Maintenance: 1. From the Options menu, select Styling. 2. Select the Theme Maintenance option. The Theme Maintenance program displays. The next sections describe how you use this tool. 1
Import Theme in Theme Maintenance To begin using this program, you first import the themes you want to manage into Theme Maintenance. They can then be loaded into this program. 1. From the Actions menu, select Import Theme.
2 2. The Open window displays. 3. Notice that this window automatically defaults to the Styles folder. 4. If you need, click the Look in: drop-down list or the Navigation Shortcut icons to navigate to a different folder. 5. Select the file you want to import. In this example, you select ArcticBlue.isl. 6. Click Open. 3
8. If the theme was successfully imported, this confirmation message displays. Click OK.
9. You return to Theme Maintenance. Click the Name button.
10. The Theme Search program displays. 11. Click Search. 12. Within the Search Results grid, select the theme or themes you want to import. 13. If you want to import all the available themes, click the Select All button. 14. Click OK. 10 11
12
14
13
15. The selected themes display within Theme Maintenance.
15
Manage Themes in Theme Maintenance To manage all the imported themes: 1. In the Tree View, select the theme you want. 2. The Name field displays the filename for the selected .isl file. If you need, you can change the styles name. 3. The Description field displays the brief explanation of the selected theme. If you want, you can enter a different description in this field. 4. To make this theme available to all your client installations, select the Distributable check box. This theme is automatically downloaded to all client machines within your system.
1 2 3 4
5 6 7
If users set up their Configuration Files to use specific server themes, the corresponding theme is automatically loaded when the user logs into the client application. They do this by defining the Style parameter within the Configuration File. Any changes made on the server to these themes (through the Runtime Stylist) are automatically updated on all client applications.
Likewise, if any customized program is set up to use a specific server theme, the corresponding theme is automatically loaded when a user launches the customization. As previously described, any changes made on the server to these themes (through the Runtime Stylist) are automatically updated on all client applications. 1 5. The Version field displays the theme version number. The application uses this number to identify the style.
For more information about the Style parameter within the Configuration File, review Chapter 1: Startup Configurations. For more information about the styling override options on a customized control, review Chapter 5: Advanced Customization.
6. The Last Updated By field displays the identifier of the user who previously updated the theme. 7. The Last Updated field displays the date on which the theme was last modified. 8. To record your changes to the theme, click Save on the Standard toolbar. Set up Default Theme in Theme Maintenance To indicate that the current theme is the Default Theme for the application: 1. Verify that the Distributable check box is selected. 2. From the Actions menu, select Make Theme Default. 2
3. A window displays indicating that this theme is selected as the default. Click OK.
2 50 | EPICOR SOFTWARE CORPORATION
4. The Default Theme icon now displays on the Detail sheet. Any client installations set up to display the default automatically uses this theme. Only one theme can be selected as the default for your application. If you select another theme as the default, the previous theme is no longer defined as the default.
5. You can also remove the Default status from a theme. To do this, from the Actions menu, select Clear Theme Default. STYLING AND THEMES |
6. The Default Theme icon is no longer displayed next to the Name field. 7. To record your changes to the theme, click Save on the Standard toolbar. 7 6
Export Theme in Theme Maintenance If you have created a theme that you want to make available throughout your organization, you can export it into a folder you select. To export a theme into a folder: 1. In the Tree View, select the theme you want to export. 2. From the Actions menu, select Export Theme. 8 2
3. The Save As window displays.
4. Navigate to the folder to which you want to export the theme. You can do this by using the Save in: drop-down list or the Navigation Icons on the left. 5. Enter a File name for the exported theme. 6. When you finish, click Save. The theme .isl file is exported into the new folder. Another user can now import it into their application using Theme Maintenance.
Delete Theme in Theme Maintenance You can also use Theme Maintenance to remove themes from your application. A deleted theme is no longer available to the client installations linked to your server. To delete a theme: 1. In the Tree View, select the theme you want to remove. 2. Click the Delete button on the Standard toolbar.2 1 2 1
3. A message appears asking if you want to delete the record. Click Yes.
4. The theme no longer displays on the Tree View.
Default Theme Retrieval

You can restore the original default theme by using the Unload Style Theme command. All areas within the interface then automatically return to the default styling defined for the application. To use this feature: 1. From Options menu, select Styling. 2. Select Unload Style Theme. The interface changes back to display the default theme. 2 1
Case Study New Button Theme

This section now guides you through a case study of a detailed example of styling. Use this example to better understand how you can create your own themes to use throughout your organization. To begin this case study, you have created a series of graphic files (within a graphics editing application) that you would like to use for button states throughout the application. You leverage the styling functionality to create a new theme that uses these button graphics. You then indicate that this theme becomes the default for all of your client installations. To create button graphics that work well with this example, make graphics that are 22 width x 18 height pixels in size. You should make three graphic files a Button_Normal.png, a Button_HotTracked.png, and a Button_Pressed.png. Be sure to place these graphic files within a folder that you can then access through the Runtime Stylist.
1 Create the Style Library You first must create the style library for your new theme: 1. On the Main Menu, from the Options menu, select Styling > Runtime Styler.
2. The Runtime Stylist window displays. 3. Click the New button. The new Style Library is created.
2 3
Define Component Role Settings Now change some component role settings for the UltraButton component. These settings are then applied to nearly all the buttons within the application. To define the Component Role Settings: 1. Click the Roles tab. 2. Expand the Component Role Settings node. 3. Expand the Infragistics Components node. 4. Select the UltraButton component.
2 3 4
5 5. The Property Panel, Settings for UltraButton, displays. 6. Change some Common Component Properties on this window. 7. Set the UseFlatMode property to True.
7 8. Set the UseOsThemes property to False. This indicates that you override the styling from a base role. 9. Close Settings for 'UltraButton'.
Define UI Role Settings To change the settings for the UltraButton UI Role: 1. Within the Roles tab, expand the UI Roles node. 2. Expand the Base node. 3. Select the Button UI Role.
1 2 3
4 4. The Property Panel, Settings for Button, displays. 5 6 5. Verify that the Normal tab is selected. This indicates that you are modifying the Normal state for the Button UI role. 6. Click the Background Fill Color button.
7. The Color Picker window displays. 8. Select the Transparent button (the button with the red line through it). 8
9. You return to the Settings for Button window. Notice that the Transparent icon now displays within the Background Fill Color button. 10. Within the Border section, click the Border Fill Color button. 9
10
11. The Color Picker window displays. Click the Transparent button again.
11
12. Now the Border Fill Color button displays the Transparent icon. H APTER 2 | STYLING AND THE
12
MES 58 | EPICOR SOFTWARE CORPORATION
Select and Size the Image To select the specific button graphic file to use for the Normal state of this UI role: 1. Within the Background section, click the Background Image button and select the File option. PTER 1
2 2. The Open window displays. Navigate to where you previously saved the three button states graphics you created. APTER 3. Select the first button state. In this example, you select the Button_Normal.png file. 4. Click Open.
5 5. You return to the Settings for Button window. APTER 6. Select the Layout Mode button. 7. Click the drop-down list, select the Stretched option. STYLING AND THEMES | 6 7
8. A Margins button step displays. Click this button. 8
9. The Stretch Margins 9 Editor window displays. 10. In the Left Margin field, enter 5. 11. In the Top Margin field, enter 4. 12. In the Right Margin field, enter 5. 13. In the Bottom Margin field, enter 4. 14. Click OK. 13 10 11 12
14
Globally Save the Styling Because you only selected the UseFlatMode option on the UltraButton component setting, some buttons do not use your new normal state. To make sure all the buttons throughout the application use this same state, you need to modify a Component Role Setting. To modify the Component Role Setting: 1. Return to the Roles tab. 2. Expand the Component Role Settings node. 3. Select All Components. 2 3 1
4. The Settings for All Components window displays. 5. Set the UseFlatMode property to True.
6. Set the UseOsThemes property to False. This indicates that you override the styling from a base role. Now all the buttons throughout the application use your new Normal state. 5 6
Modify Hot-Tracked State Repeat these steps for the button components HotTracked state. During these steps, you indicate that your HotTracked graphic is used for this button state. Heres how: 1. Return to the Roles tab and navigate to the Button component.
2 2. If you need, launch the Property Panel, Settings for Button, again. Be sure 4 to select the Hot Tracked tab. 3. Set both the Background Fill Color and the Border Fill Color buttons to Transparent.
3 5 6
4. Click the Image button and select your HotTracked.png file. 5. Select the Layout Mode to Stretched.
6. Click the Margins button and use these values for the margins: Left 5 Top 4 Right 5 Bottom 4
You now have updated the HotTracked state for buttons throughout the application. Modify Pressed State To modify pressed state: 1. In the Property Panel, Settings for Button, click the Pressed tab. 1
2. Set both the Background Fill Color and the Border Fill Color buttons 3 to Transparent. 3. Click the Image button and select your Pressed.png file. 4. Select the Layout Mode to Stretched.
2 4 5
5. Click the Margins button and use these values for the margins: Left 5 Top 4 Right 5 Bottom 4
You now have updated the Pressed state for buttons throughout the application.
Save the Style Library You have finished creating the button styling, so you must save this style library. It then becomes a theme you can select for the application. To save a style library: 1 1. Click the Style Library tab. 2. Click the Save As button. 3 3. The Save Style Library window displays. 4. Enter a File Name for this theme. For this example, you enter GrayButtons.isl. 5. Click Save. 2
Set New Theme as Default The new theme is now ready to become the default look for all of your client installations. To set a new theme as default using Theme Maintenance: 1. On the Main Menu, from the Options menu, select Styling > Theme Maintenance.
2 1 22. The Theme Maintenance window displays. 3. You first need to import the GrayButtons theme into Theme Maintenance. To do this, from the Actions menu, select Import Theme.
4. The Open window displays. 5. Select the GrayButtons.isl file.
5 6. Click Open.
7. To the confirmation message, click OK. 7
8. You return to Theme Maintenance. Click the Name button.
9. The Theme Search window displays. 10. Click Search.
11. From the Search Results grid, select the GrayButtons option. 12. Click OK.
10
11
12
13. The GrayButtons theme now displays within Theme Maintenance. 15 14. Select this themes Distributable check box. This indicates that all the client installations on your system can use this theme. 15. To make this theme the default for the application, from the Actions menu, select Make Theme Default.
13
14
16. To the confirmation message, click OK.
16
17. The Default Theme icon displays. The GrayButtons theme is now the default for the application. 18. Click the Exit button to close Theme Maintenance. When a client is first installed, it is set up to use the default theme. If a client installation no longer uses the default theme, however, you can change this back within the Configuration Settings File. To do this, you update the Styles setting. To learn more, review the Configuration Settings File section within Chapter 1: Startup Configurations. 17
18
View the Theme The button theme is now the default look for the client installations throughout your system. Any client installations set up to display the default style automatically use this theme. To see your new theme in action, close the application and then launch it again. When the Main Menu appears, you can see how this new theme is incorporated into the interface. 1. Some changes are on the Main Menu. Notice that the bottom and left side sliders now contain thumb buttons that use your new button style. 2. The Arrow buttons use the button style. 3. The Navigation buttons at the bottom of the Main Menu display using this style.
2 3
4. Launch a program. You will see that all buttons in the application use the gray button styling. The button graphics display for all the various sized buttons because you selected the Stretched Layout Mode. When you hover your mouse over a button, the HotTracked.png graphic displays. When you click a button, the Pressed.png graphic displays. This happens because you defined these different states within the Runtime Stylist. As this case study demonstrates, the Styling functionality is a dynamic tool that you can use to create interface themes unique for both you and various areas within your organization.
PERSONALIZATION | CHAPTER 3
Chapter 3 Personalization
Personalization is defined as any change made to the application that only affects a specific users interface. Every user has different needs. Some users may want to change the order of columns on a grid. Others may want to add more options to a programs status bar. Epicors application can be set up to reflect these individual needs. Use the Personalization tools to modify any programs interface to maximize your workspace to better match the tasks you perform every day. Personalizations are stored by individual user and do not affect any other users on the system. Once a personalization is created, it can be exported from the software, and imported back in to the application for another user. It is important to understand that personalizations are stored on the server and not on each individual users machine. Because of this, if a user logs in to another workstation, their personalizations are automatically downloaded and cached to that computer. The flexibility of the software enables every user to tailor the interface to suit their business needs and maximize their efficiency. In this chapter, you explore the personalization tools you can use to refine the interface and make your daily routine more efficient. This chapter ends with a discussion on advanced personalization. Advanced personalization options are only available to those users with user account personalization privileges.
CHAPTER 3 | PERSONALIZATION
Personalize the Main Menu Interface

Several personalization options are available at the system level or main interface. You can change the organization of the main interface to quickly access the programs you frequently use, thus making you more efficient. When you first log in to the application, you are presented with the main interface. 1. The Menu Bar is located on the 1 top of the interface and 2 contains four menus; the File menu, View menu, Options menu and the Help menu. 2. The Standard Toolbar contains buttons you use to change your current session. These icons are also accessible from the Options menu, which is described later in this chapter. 3. The History Toolbar contains a dropdown list that displays recent programs you have launched. To use this feature, select a program from this list and click the Go button. The selected program displays. 4. The Menu Items Pane is located on 6 the left side of the main interface and contains access to Menu Groups and Favorites. The Menu Groups sheet contains a series of folders by which you navigate through the application. The Favorites tab is where you can create personal favorites menus for your frequently accessed programs. 5. The Contents Pane is located on the right side of the main interface. This displays the contents of each folder as you navigate through the main menu. 6. The Status Bar displays along the bottom of the interface. 3 5
The View Menu

You can personalize the main interface in several ways. The View menu can be used to select interface functionality that displays by default when the application is first launched. You can choose to display large or small icons, and you can decide to display or hide certain elements of the main menu including the Favorites Bar, the Full Tree, Menu Items, the History Toolbar, and the Status Bar. 1. When you select the View menu from the main menu, options that change the default view of your main menu are available.
2. When the Full Tree option is selected, the application displays all the modules through a series of folders and program icons in both the Main Menu pane and in the Menu Items pane. 2
4 3. The Main Menu pane is found on the left side of the main interface. 4. The Icon Level pane is found on the right side of the main interface.
5. When you select the Large Icons option from the View menu, the application displays folder contents as large icons in the Menu Items pane.
6. If you do not want to display the contents of the main menu folders in the Menu Items pane, you can deselect the Menu Items view. When you do this, you use the Full Tree to navigate to all folders and programs in the application. Throughout this user guide the Full Tree and Menu Items views are used in all the menu displays. 7. When the History Toolbar is selected, a drop-down list displays on the main menu that contains programs that you have recently accessed.
8. When you select the Status Bar option from the View menu, the Status Bar displays at the bottom of the main interface. This bar contains information such as current company, location, language and other details about your current session.
The Options Menu

The Options menu contains settings you use to change your current company, plant, language, and so on. It also contains user preferences you leverage to personalize the Status Bar on your main interface. You can also save personalized settings automatically when exiting the application. The Options menu also contains access to the applications Styling functionality which gives you complete control over the look and feel of the entire interface. You can use this toolset to display a pre-built design, or theme, from the options installed with the application. The Preferences command controls specific elements that display on the Status Bar of the main interface. You can also add a tab to the Main Menu for displaying dashboards and web sites. Additional options are available at the program level to modify the status bar for a particular program. Program Options are discussed later in this chapter.
Modify the Status Bar on the Main Interface The Preferences command on the Options menu controls specific elements that display on your status bar of the main interface. To modify the status bar on the main menu: 1. From the Options menu, select Preferences.
2. In the Preferences window, select the elements to display on the status bar. Notice you can place the current User ID, Language, Company, Plant, Server, and Workstation on the status bar. 3. You can click the Clear History button to remove the history from the History Toolbar.
4. Select the Tabs sheet to add a new tab to the main interface. 5. Click the New button to create a new tab that displays a Web Browser. 6. Enter the text you want to display on the tab in the Tab Caption field. In this example you enter Epicor.com. 7. Select Web Browser in the Type field. You can also select the Dashboard Type to display a system dashboard on the main menu. 9 8. Enter the web address you want to display in the Content field. If you have chosen Dashboard in the Type field, the Content field contains a list of Dashboards in the application for you to select. 9. Click OK. 4 5 7 6 8
10. Review the changes on the Main Menu to verify it displays the items you need.
10
Save Settings on Exit

The Save Settings on Exit option automatically saves any settings you have changed on your View menu when you exit the application. By default, this option is enabled for every user. It causes the application to track which folders were expanded in the Folder List when the user closed the application. Folders still expanded on exit are then expanded again at login. Once you have set a default folder, disable the Save Settings on Exit option. If you do not, the interface always opens to the last folder you had open before you quit the application. 10 For example, if you regularly use Opportunity / Quote Entry and would like this programs folder to be expanded at login, open the main interface to the Quote modules General Operations folder. Verify the Save Settings on Exit option is selected, and exit the application. The next time you login, the main interface opens directly to this folder. Now disable this option, and the Main Menu always opens to the Quote Module folder. Any recent change made to the Folder List interface are saved only when you enable this option. Notice that you can automatically restore the Main Menu interface to its default view by selecting the Reset Layouts to Base option. You can also restore the Main Menu to the version you previously saved by selecting the Reset Layouts to Last Saved option.
The Favorites Bar

You can quickly access an internal program without having to navigate through the Folder List. The Favorites Bar is a place on the main interface where you can store the programs you use regularly. The Favorites Bar can also link to external programs and files, such as Microsoft Word and Excel. Favorites Bar User Privileges To modify the Favorites Bar, you must select the Can Allow Favorites Programs check box on the Options sheet in User Maintenance. Main Menu Path: System Management > Company Maintenance > User To give a specific user rights to modify the Favorites Bar: 1. Enter the User ID of the User you want to grant the Personalization Privileges. 1
2. Click the Options sheet. 3. Select the Can Maintain Favorites Programs check box. 4 2
4. Click Save on the Standard toolbar and exit the program.
Add Internal Shortcuts to the Favorites Bar You can add internal shortcuts to the Favorites Bar that open any program in the Epicor application. To add an internal shortcut to the Favorites Bar: 1. Right-click the program name from the menu. 2. Select Add to Favorites Bar from the content menu. 3. The icon for the shortcut now displays on the Favorites Bar. 3 1 2
Add External Shortcuts to the Favorites Bar You can also add external shortcuts to the Favorites Bar that open any applications or files that are stored on your network. To add an external shortcut that opens Internet Explorer to the Favorites Bar: 1. Right-click the Favorites Bar and select Add New Shortcut from the context menu. 2. In the Properties dialog window, browse to the program or file you want to add to the Favorites Bar. 2 3. Click OK.
4. The Internet Explorer shortcut icon now displays on the Favorites Bar.
Create Favorites Groups Shortcuts on the Favorites Bar can be organized into Favorite Groups. For example, you can group programs by modules or create a group for a workflow that contains specific tasks. Later if you want to make changes, any favorite groups and shortcuts you add can be removed or renamed. To add a new favorite group to the Favorites Bar: 1. Right-click the Favorites Bar and select Add New Group from the context menu. 2. Click New Group to rename it in the Favorites Bar. 1
3. Enter the New Group name. In this example, the group is called Reports. You can change the name of this group by using the Rename Group option.
AutoLoad Favorites Groups You can improve the performance of Favorites Bar programs you use the most by using the AutoLoad feature. This program automatically loads selected programs in your workstation's memory. When you select an autoload option for a favorites group, all the programs contained within the favorite group are temporarily selected for memory caching. Each program can then be pre-loaded into memory during the current session so when you launch one of these selected programs, it displays faster. To access the AutoLoad options, right-click a Favorites Group. Two AutoLoad options are available on the Favorites Bar. 1. AutoLoad this Group - Automatically loads favorites group programs into your workstations memory when you log into the application. 2. AutoLoad on Session Changes - This option causes memory cached programs to re-load into memory when the User, Plant, Company, or Language are changed during the current session. The AutoLoad feature uses some of your system memory. You should not select every program for AutoLoad, as this feature uses some of your system memory. When the AutoLoad option is enabled, the application takes longer for the login process. While programs autoload, you can continue to do other things like answer email or web browsing. While the programs within the Favorites Group are loading in the background, an icon appears on your workstations system tray. Memory Caching When you select an Autoload option for a favorites group, all the programs contained within the favorite group automatically are selected for Memory Caching. Each program can then be pre-loaded into memory. This improves the programs performance in Run Mode, as it displays faster when you launch it again during the current session. The Memory Cache option is located in the programs Options window. The Memory Cache check box appears on the General tab. Additional information on this option is reviewed in the Options section of this chapter. 1 2
Before you personalize or customize a memory cached program, be sure you disable this feature. To do this, press the [Shift] key on the keyboard and then launch the program. You can do this from either the Main Menu or a context menu.
1. After any program is launched (in this example the Part Maintenance form has been launched), click the Tools menu. 2. Select Options. 1
3. The Options window displays. 4. On the General tab, clear the Memory Cache check box. 5. Click OK.
6. Exit the program. You can have the same program open multiple times. For example, one session of the program can have memory caching active, while another session of the program can turn off this function. You can then customize the program while its cached version is still in use. To learn more about Customization, review Chapter 4: Basic Customization, Chapter 5: Advanced Customization, and Chapter 6: Customization Utilities. 6
Personalize the Program Interface

The program interface has many personalization features available. You can personalize each programs interface so it displays the configuration that works best for you.
Personalization Options Window

Many of the program level personalization features are found in the Options window from the Tools menu in a specific program. Once the options are selected from this window, they become the default standards that are used each time the program is run. In addition, this window has several global settings that affect every program. In the following example, Customer Maintenance is used to demonstrate the personalization options. Main Menu Path: Sales Management > Quote Management > Setup > Customer 1. Click the Tools menu. 2. Select Options. 2 1
General Options The General tab contains options that affect the entire program. These options determine whether your sheet, toolbar, grid, and tree view personalizations save when you close the program. Special actions are also available, such as automatically launching the Search window when you activate the program. 1. As The Form Opens - The options in this group cause specific actions to occur as the program (form) launches. 2. No Action - When selected, this option causes the program (form) 1 to launch normally. All the programs fields are blank and you 4 must search for an existing record or create a new record. 3. Auto Populate Data - When 5 Auto Populate Data is selected, the program executes a search (the search form does not display) and 6 selects all records to return them to the program. 4. Auto Load Search - When a program is launched with this option enabled, the search form displays automatically without having to click a button to manually launch the search. If you specify a named search (from the drop-down list) in conjunction with this Auto Load Search setting, the Named Search field in the search form populates with that search. When Auto Load Search is selected without specifying a Named Search, the search form loads and waits for entry. If you want to auto populate a program with many records, consider using a Named Search to retrieve a filtered list of records instead of the whole table. A Named Search is search criteria previously defined and saved. This can be automatically launched with the Auto Load Search option, or selected manually from the search window. Named Searches are discussed in greater detail within the Searches chapter in the Epicor ICE Tools User Guide. 5. Memory Cache - Select this option to cause the current program to stay in your computers memory after it closes. The next time you launch this program, it appears faster, improving this programs performance. This program only stays in memory during the current application session. When you exit the application, the program is also removed from memory. 2 3 7
8 9 10
11
The form takes longer to open when the auto populate option is selected since the program is also executing a search and loading every record found in the data table. For example, using the Auto Populate option in Job Entry or Part Maintenance is not recommended. The files in these programs tend to be very large with many records. This can take a very long time to launch the program.
You need to disable memory caching before you can customize or personalize a program. To disable memory caching, hold down the [Shift] key on the keyboard and then launch the program. This can be done from either the main interface or a context menu.
Only select this option for programs program you use most frequently. If this option is selected on several programs, your computer may run low on memory, impacting its performance. 6. Show Ribbon Override Indicates whether the program toolbar displays as a ribbon instead of a series of drop-down menus. Select True to display the ribbon on the current program. The next section, Ribbon Interface, provides more detail about this feature. 7. On Save Layouts - The interface layouts of a programs grids and sheets can be changed during a session. To save these changes for the next session, you would select the Save Layouts command from the Options menu of the main interface. The two Save Layouts options found in a programs Options dialog box control whether or not these changes are saved for a specific program. By default, these options are enabled in every program. Available options: Save Dock Layouts: This option saves all the position changes you make to a programs sheets. Personalizing sheet layouts is discussed later in this chapter. Save Grid Layouts: This option saves changes you make to a programs grid layout. You can change the order in which columns are displayed within each grid and also resize the grids column. Personalizing grid layouts is discussed later in the chapter. 80 | EPICOR SOFTWARE CORPORATION
8. Context Menu - When selected, the Context Indicator check box causes the interface to show which fields have Context Menus. If the field has a context menu, a triangle displays in the upper right corner of the field. You can also personalize the color of the Context Indicator triangle by selecting a color from the drop-down list. 9. Select the Zone Indicator check box to define the color used for displaying any BAQ zone indicators on a program. Users hold their mouse over the BAQ zone indicator to display a tooltip of the BAQ results for the current value of the field (if any). Depending on the columns the BAQ returns, the BAQ zone can display different results. For example, you could have a BAQ zone display the current customers web site. For more information on creating business activity query zones, review Chapter 6: Customization Utilities. The BAQ Zones section describes how to create and display BAQ zones. 10. If you want to indicate which fields need data before a new record is saved, select the Required Field check box. 11. Click OK. After you exit the Options window, notice all required fields become highlighted on the interface. Any sheet tabs that contain required fields are also highlighted. 12. When a field displays a Context Indicator, a context menu can be accessed by right-clicking on the field. The fields context menu displays; you can use it to cut, copy, and paste text as well as open related programs. 12
Ribbon Interface You can cause the top of each program window to display a ribbon interface instead of a series of menus. The ribbon interface groups together related functions and links for easy access. This feature is available from the Options window of the Tools menu for any program. In the following example, Customer Maintenance is changed to display the ribbon interface. 1. Navigate to Customer Maintenance. Main Menu Path: Sales Management > Quote Management > Setup > Customer 2. From the Tools menu, select Options. 1
3. Click the Show Ribbon Override drop-down list and select True. 4. Click OK to close the Options window.
5. The ribbon displays on your program. The Main tab contains buttons that launch Action programs specific to your program, navigation arrows, and file editing tools.
6. The Links tab contains buttons that launch programs related to the current program, like search and entry programs. It also contains the methods by which you can send the files created within the current program.
7. The Support tab contains buttons you use to launch customization, personalization, and translation tools. You can also use this tab to access the application help and support resources available from Epicor.
8. To display the Save, Undo, and Exit buttons below the ribbon, select the Show Below the Ribbon option from the Quick Access toolbar. To place these buttons above the ribbon again, select the Show Above the Ribbon option from this toolbar.
9. To hide the ribbon from constantly displaying, select the Minimize the Ribbon option. The tabs still display, but the options do not appear unless you click the specific tab. To maximize the ribbon again, clear the Minimize the Ribbon option. Hot Keys Options Use Hot Keys (shortcut keys) to quickly navigate through the interface with keyboard options. The Hot Keys sheet is where all shortcut key combinations are defined for the current program. This sheet also contains controls you use to globally define specific functions. Global Options are discussed later in this chapter. To define a Form Hot Key: 1. Select a Command from the dropdown list. Available options include New, Edit, Delete, and so on. 2. Click the Short Cut drop-down list and select the keyboard combination you want to use for the command. Available options include <F4>, <Shift><F2>, <Alt> 5, and so on. These shortcut key combinations are then used on the current form. 1 2
Dialogs Options The Dialogs sheet contains a series of tabs that indicate when data can be verified for specific actions that occur within the program. When a selected action activates, a confirmation window automatically displays. You must acknowledge the message before you can continue to use the program. These actions (or tabs) indicate the type of action which can trigger a dialog window: 1. Update - When a current record is edited and one of the selected conditions occurs, a confirmation window displays.
1 3 4
2. Add New - A confirmation window displays when you create a new 2 record. 3. Delete - A confirmation window displays when you delete a record. 4. Undo - A confirmation window displays when you remove the results of a previous action on the program.
Tree View Options Use the Tree View sheet in a programs Options window to change the text that displays within a programs Tree View. You can also change the Image (icon) and the Display Column (field) that displays in the Tree View as well.
Global Options - Status Bar Use the Global Options sheet to personalize global Hot Keys and modify the Status Bars that display in every program. 1. Select the Status Bar Panel options you want to display on programs. These options can be different from the status bar options that display on the Main Menu. 2. Click the Border Style and Panel Border Style drop-down lists to personalize these items on the interface. 1 2
Global Options - Hot Keys You can define shortcut keys used throughout the application on the Hot Keys tab. In addition to defining shortcuts, several additional global options are also available: 1. Select a Command from the dropdown list. Available options include New, Edit, Delete, and other program commands. 2. Click the Short Cut drop-down list and select the keyboard combination you want to use for the command. Available options include <F4>, <Shift><F2>, <Alt> 5, and so on. This short cut key combination is then used to launch this program function throughout the Epicor application. 3. Handle [Enter] as Tab - Select this check box to indicate you want to use the Enter key to move through each program's fields. You can then use both the Tab and Enter keys to move through the fields. 4. Launch Search with - Define the global shortcut you want to use to launch a search from a selected field. 5. Launch Enterprise Search with Use this shortcut combination to launch the Enterprise Search functionality. This search application retrieves indexed content from your Epicor application. You can search on any record within the Epicor database like a part, customer, purchase order, AR invoice, and so on. For more information on Enterprise Search, review the Searches chapter in the Epicor ICE Tools User Guide. 6. Launch Maintenance with Use this drop-down list to define the shortcut used to launch the maintenance program for a selected field. EPICOR SOFTWARE CORPORATION | 85 5 6 7
1 2 3 4
7. Launch Info Zone with A shortcut combination you use to activate a BAQ zone. Pressing this keyboard combination causes a tooltip to display BAQ results for the current value of the field (if any). Depending on the columns the BAQ returns, the BAQ zone can display different results. For example, you could have a BAQ zone display the current customers web site. For more information on creating business activity query zones, review Chapter 6: Customization Utilities. The BAQ Zones section describes how to create and display BAQ zones. 8. Use the Designer Grid tab to specify the grid characteristics used when you are in personalization mode. Grid settings include activating the Snap To Grid functionality, and determining the grid size. 9. The Snap to Grid option helps position elements when you are creating personalizations on a grid. When this option is selected, the shapes pull, or snap, towards the grid dots. For example, if Snap To Grid is selected and you add a check box to the form, the box snaps towards the nearest grid dots, instead of floating between the dots. 10. Use the Grid Width and Grid Height values to specify the space, in pixels, that displays between the grid dots in Personalization mode. 11. Click OK to save your changes and exit the Options dialog window. 9
10
11
Personalize Sheet Layouts

A sheet is a layer of a programs interface that contains related functionality. Every program contains at least two or more sheets (the Detail and the List sheet). You can use the personalization tools to change the position of any sheet within a program. By clicking and dragging each sheets tab, you can also change the order in which the sheets are displayed. A sheet can even be completely moved out of the program so that it displays as a floating sheet. Modify Sheet Tab Order Each sheet displays with a tab. The order of the tabs within a sheet can be changed by clicking and dragging the tab to a new position. For example, in Part Class Maintenance displayed below, the Detail sheet displays to the left of the List sheet by default. By clicking and dragging the List tab, you can move it to the left side of the Detail sheet: 1. Before the List sheet is moved.
2. After the List sheet is moved.
3. To save the current settings, click the Tools menu. 4. Select Save Layouts. 5. To reset the sheet layouts to their default position, from the Tools menu, select Reset Layouts to Base. 3
4 5
Docking Sheets In addition to changing the tab order within a program, tabs can be moved out of their default position by dragging them and docking them to a new position on the same sheet. A sheet can be docked to any one of four quadrants of a window (top, bottom, left, and right). As a sheet is dragged out of position, an outline displays on the window indicating where the sheet will be placed when it is released. The outline snaps into position when the mouse is moved into one of the four quadrants of the window. Once the outline snaps into position, release the mouse to dock the sheet. 1. Click the List sheet tab and drag it down to the bottom of the sheet. 2. The outline snaps into position in the lower portion of the window. 1
3. Notice the List Sheet is now docked to the lower section of the window.
4. If you drag the List sheet to the right side of the window, the outline again snaps into position.
5. When you release the mouse button, the sheet docks to its new position in the window. 5
6. To reset the sheets to their default position, click the Tools menu. 7. Select Reset Layouts to Base. 6
Floating Sheets A Floating sheet is a sheet moved from its original position and released in a non-docked position. Use this feature to display many sheets at the same time. To create a Floating sheet: 1. Click a sheets tab and drag the sheet away so that the outline does not snap into any of the quadrants of the window. In this example, click and drag the List sheet.
2. Release the sheet into the nondocked position.
3. When a sheet is floating, the thumb tack icon does not display in the upper right pane of the sheet title bar. When you exit the program, any floating sheets close automatically.
If you save the sheet layouts, the floating sheet reopens in the same position when the program is launched. To return the sheet layout to its default position, select the Reset Layouts to Base command from the Tools menu. You can also return a floating sheet to its previous position on the docking sheet by double-clicking on the title bar of the floating sheet.
Auto Hide Sheets The Auto Hide thumb tack icon displays on the right side of every sheets title bar that is docked into position. The default view of the thumb tack icon is in a pinned position. When the icon is selected, the thumb tack changes to an unpinned position and auto hides the contents from view. 1. Once a sheet is unpinned, it slides out of view and is replaced with a tab. In this example, the Tree View of Part Class Maintenance is unpinned and is hidden on the left side of the program. 1
2. If you hover the mouse over the tab, the Tree View pane slides back into focus. Leverage the Auto Hide feature to temporarily hide sheets you use less often. All the information is readily available, but pulled out of the way. Notice all docked sheets contain the Auto Hide thumb tack icon, allowing sheets to be hidden when not in use.
Personalize Toolbars
Every program contains default toolbars you can move to any location in a programs window. They can be docked to either side of the interface or placed in a floating position. Default toolbars you can personalize: 1 1. Main Menu Toolbar - This toolbar displays all the programs menus. It typically displays the File, Edit, Tools, Actions, and Help menus. 2. Standard Toolbar - All the main controls are displayed on this toolbar. Options like New, Cut, Paste, Refresh and so on display on this toolbar. 3. Navigation Toolbar - Use this toolbar to search through all the records created through this program. It displays the Search button and the Navigation tool. Moving Toolbars Each Toolbar has a dotted line along its left side. This is called the Move Control. Use this control to click and drag the toolbar into the position you want. To move a toolbar to one of four sides of any window: 1. Hold your mouse pointer over the toolbars Move Control. 2 3
2. A four way arrow pointer displays. 3. Click and hold down your mouse button and drag the toolbar to one of four sides of the window. When it is placed next to the edge, it automatically flattens itself to the side. Release the mouse button. 2 3
4. To adjust its position along the side, click and drag the Move Control along 4 the horizontal or vertical edge of the window. You can also position each toolbar as a floating toolbar. This toolbar is always visible on top of the program, regardless of the sheet selected within the program. Use this feature to place the toolbar wherever you need it on the window. After you close the window, the toolbar reverts back to its default position.
Personalize Grids
Grids display information through a series of columns and rows. Each column displays a category of information, like Part Number or Part Class, while each row displays data for individual records. The List sheet in each program displays information in a grid format. The standard Personalization tools provide you with the ability to change grid layouts in several different ways.
Additional personalization options are available to users who have the Personalization privilege enabled in their User ID. These options are reviewed in the Personalization Mode section of this chapter.
Change Column Order Every grids columns can be moved around into any order that you want. 1. To move a column within a grid, click and drag the column to the desired position. 2. When the red arrows display, release the mouse button and the column docks in its new position. 2 1
3. In the example below, the Buyer ID column is moved to the far left.
Adjust Column Width You can also adjust the column width so the maximum amount of information displays in each column. To automatically adjust the width of a column to fit the data it contains: 1. Place the mouse pointer over the right edge of a column header. The mouse pointer turns into a double arrow icon. 1 2. Double-click the mouse to adjust the width of the column to auto-fit its contents.
To manually adjust the width of a column, place the mouse pointer over the edge of a column. The mouse pointer turns into a double arrow icon. Click and drag the arrow to the left or the right to widen or shrink the column manually.
Grid Split Option 1. Available on the left of horizontal scrollbars and on the top of vertical scrollbars of each grid is a small bar that can be dragged to split a grid either vertically or horizontally. 2. Similar to the freeze panes option in a spreadsheet, when you place the mouse over the bar it changes to a double arrow icon. 3. You can drag this bar towards the center of the grid to split it. 3
Sort Columns You can sort the grid records in ascending or descending order using the data in a selected column (field). To sort columns: 1. Click the column header by which you would like to sort. The grid automatically sorts the contents in ascending order based on the selected column. 2 1
2. When you sort by a particular column, an arrow icon displays in the column header indicating an ascending sort. In this example, the Part Class records that contain a blank Buyer ID sorts at the top of the list. You can then identify records you need to update. 3. You can change the sort on a column to be descending by clicking the column header again. 4. Notice the arrow icon now displays upside down. This 3 indicates the grid is sorted in descending order by the data in this column. 4
Grid Filters Use the Show Grid Filters option to work with a subset of data in a grid. You specify the column data you want to see; when you apply the filter, data that does not meet the criteria you specified does not display within the grid. You can further limit the filter results by creating another child filter that runs against the results of a parent filter. You can create as many child filters as you want to get the results you want. To use the Show Grid Filters option: 1. Right-click anywhere on the grid and select Show Grid Filters.
2. Notice the Filter icon displays in each column. 3. Click the Filter icon in the column you want to filter and select the data you want to see. 2
4. The grid now displays only rows that contain the column data you filtered. Notice the Filter icon changes to indicate a grid filter has been applied to the data in the grid.
Show Group By Many grids offer Show Group By functionality that groups all of the records in a grid by a specific column. This option is available in any grid, and especially useful in the Dashboard programs. The Sales Order Backlog Status dashboard is used to illustrate this functionality. 1. Navigate to the Sales 1 Order Backlog Status dashboard. Main Menu Path: Executive Analysis > Status Dashboards > Sales Order Backlog Status 2. Click the Refresh All button to retrieve all the part records to the dashboard.
3. Drag and drop the Part column header onto the Group By area above the grid.
4. All sales order records are now organized by Part. You can see the sales orders placed against each part by clicking on the plus (+) sign. This expands the rows under each part to display the sales orders.
Show Group By - Secondary Once you have grouped by one column, you can add a secondary Group By. For example, you can group parts by Part and then by Unit Price. To Group a grid by multiple columns: 1. Drag the second column header (Unit Price) next to the Part group by option. 2. Release when the red arrows display. 2 1
The column headers now display in the Group By header. Notice each of the Groupings displays a count of records. This example shows two groups of parts organized by their Unit Price Values. Two methods are available to turn off the Show Group By functionality: Right-click the title of the grid, and click Show Group By to remove the check mark and disable it. Drag the column headers back down to the grid area and release. This returns the columns to their default position.
Enable Show Summaries Many grid fields can be set up to display summarized data. Five options are available for any number field in a grid: Average, Count, Minimum, Maximum and Sum. The Customer Tracker is used in the example below to demonstrate this functionality. 1. Navigate to the Customer Tracker. Main Menu Path: Sales 1 Management > Order Management > General Operations > Customer Tracker 2 2. In the Customer ID field, enter a unique customer identifier.
3. Select the Orders sheet and click the Retrieve button to display all the open orders for the customer. 4. Right-click the Open Orders title of the grid.
5. Select Show Summaries.
6 6. Once the option is enabled, the column header for every number field in the grid will display a Sigma icon. To access the Summary options for a specific field, click the Sigma icon next to the column header. 7. Select any or all of the options that display in the Select Summaries window. 7
8. When selected, the Sum option totals the column and adds Grand Summary information along the bottom of the grid. 8
9. In addition to displaying the Sum along the bottom of the grid, this feature also displays the Sums when using the Group By functionality. 10. To save the changes you have made to the grid, right-click the grid again and select Save Layout from the content menu. In this example, the Open Orders grid is grouped by Part, and summarized by Selling Quantity. 9
10
Advanced Personalization Options

Advanced personalization refers to specific features of personalization available only to users with Personalization security privileges. All the personalization options discussed so far in this chapter are available to every user. However in this section, you explore the additional personalization options available only to users with Allow Personalization rights. Use the Advanced Personalization features to create additional changes to the user interface, such as changing fonts, font sizes, colors, and tab stops. You can also hide or display columns in grids. Once a personalization is made for one user, it can be exported from one machine and imported to any other user who would also like the same personalized program. Assign Personalization Privileges The advanced Personalization Privileges are assigned by User ID in User Account Maintenance. Main Menu Path: System Management > Company Maintenance > User 1. In the User ID field, enter the user identifier for the User you want to grant the Personalization Privileges. 1
2. Click the Options sheet. 3. Select the Allow Personalization check box. 4. Click Save and exit the program. 4
3 Activate Personalization Mode To access the Advanced Personalization features, select Personalization from the Tools menu in any program. In this example, you are personalizing the interface for Sales Order Entry. After you launch the program, you must activate personalization mode to begin personalizing this program. 1. Navigate to Sales Order Entry. Main Menu Path: Sales Management > Order Management > General Operations > Order Entry 1 2. From the Tools menu, select Personalization.
3. This opens the Control Properties window for that program. The Control Properties window contains all the advanced personalization features. This window displays in the forefront of your window until it is closed by selecting the Delete, OK, or Cancel buttons. 4. A grid also displays over the sheet currently in focus. Use this grid to help you move elements to the areas where you want them. 3
Begin Personalization 1. To begin personalizing the form, click the field (or element) on the sheet in focus. This updates the Control Properties window with the selected element name and its properties. In this example, the Ship To fields on the Sales Order Entry Summary sheet are personalized.
7 6
2. When an element is selected to Personalize, it is surrounded with white boxes. In this example, the Ship To group box is selected. 3. The Element Name field displays grpShipTo, this is the name of the element in focus. 4. The Path Code name displays the form or sheet name programmatically. This value is the specific path name used by the programs in the application to execute or display the sheet in focus. In this example, the Path Code name is Epicor.Mfg.UI.FrameWork.EpiGroupBox. 5. The Properties are items in the Control Properties window that may be modified for each element (on a sheet). As you click different fields (elements), the Control Properties window displays the set of properties that may be modified for those elements. The dialog window changes to reflect the type of control you select. You may also rearrange the position of controls on the form by dragging and dropping them.
This Control Properties window is a sub-set of all the properties available. Use the Customization tools to access many other properties. To learn more about Customization and the additional tools available, review Chapter 4: Basic Customization.
6. The buttons located at the bottom of the Control Properties window are used to Import and Export personalizations, as well as Delete, Save (OK) and Cancel an existing personalization. 7. Click the Select Top Level Form button to reset the Control Properties window to the top most level of the selected form.
Personalize Sheet Properties

A sheets font type, font size, background color, foreground color, and tab stops can also be personalized. Personalize the Colors of Elements The BackColor defines the color of the sheets background and BorderColor defines the color of the outline of a field. When selected, these options display all the available colors in a list; you may choose between System colors (the colors defined for your current operating system color scheme), a Custom colors list, or a list of Web colors.
1. Select the Ship To group box. 2. In the Control Properties window, click the BorderColor property. A drop-down list of colors to choose from displays. 3. Select the Custom color tab and choose a color to apply to the border of the group box. 4. Notice the group box border changes color. 5. Click OK (not pictured) to save your changes.
2 3
Change the Font Type and Foreground Color You can also personalize the Font Type and the Font Color (Fore Color) of text. Heres how: 1. Select the Name label inside the Ship To group box.
2. Click the Bold property and change the property from False to True. 3. Click OK to save the changes.
4. Click the ForeColor property. A drop-down list of colors to choose from displays. 5. Select the Custom color tab and select a color to apply to the group box.
6. Click OK to save the changes.
6 Change the Location and Size The Location property refers to the exact position of the control (or element) on the sheet. The location is defined as X and Y axis numbers. You can expand the property to change the X and Y axis or you can click and drag the element to a new position on the sheet. The Location property updates with the new X and Y axis points. In the example below, the Attention field is moved from below the Name and Address field to above the Name and Address field, next to the Ship To ID field. 1. Before the Attn field is moved.
2. After the Attn field is moved. The Size property defines the height and width of the control (or element) on the sheet. When the Attention field moved to its new location, the field was made smaller to fit in its new position. Notice the Height and Width properties changed to reflect this new size.
Change the Tab Stop and Text The TabStop property controls whether the item is included as users tab through the sheets within this program. True indicates that users can tab through this element; False indicates that a tab skips over this element on the sheet. To change the actual text that displays using the Text property: 1. Select the Attn field on the sheet. 1
2. Click the TabStop property to view the drop-down list for this property.
3. Change the property from True to False. While the screen captures in this guide cannot display the immediate change, know that now when you tab through the prompts on this window, you skip this field. 3
4. Click the Addr: label on the window.
5. In the Text property, enter Address. 6. Click OK to save the changes.
Modify Grid Properties

Grids display information through a series of columns and rows. Using the Control Properties window, you have the ability to hide fields (columns) so they do not display in a grid. To access grid options, click a grid within a sheet. The Control Properties window expands to display grid Column Properties. You can then determine the columns to hide or display by selecting the appropriate check boxes. Hide Columns in a Grid To hide columns in the Sales Order Entry, Lines Detail grid: 1. From the Tools menu, select Personalization.
2. The Control Properties window displays. 2 3. Click the Order Lines grid header on the Sales Order Entry summary sheet, Lines Detail tab. 4. Click the Column Properties drop-down list to display the Column Properties window. 5. Select which columns to Display or Hide by enabling (or disabling) the Hidden check box for each field (column). 6. You can also select the Toggle Hidden button to hide all columns. Click this button again to display them. 7. Click OK to save the changes. 4 5
7 8. The columns you want visible (their Hidden check boxes were not selected) now display on the Order Lines grid.
Import, Export, and Delete Personalizations

Once you have created and saved a personalization, you can export it to other users. These users can then import this personalization into their environments. To do this, login as a different user, import the personalization to a new computer and it is then applied to the current user account. If you decide you do not like some personalizations, you can also delete them. Export a Personalization 1. After saving a personalization, in the Control Properties window, click the Export button.
2. The Save As window displays. 3. The default save location is a folder called Export on your local machine.
3 4. The File name is the application name followed by an underscore and the user name who is currently logged into the application. For example, after personalizing the Sales Order form logged in as system manager, the export filename defaults to App.SalesOrderEntry. SalesOrderForm_MANAGER.xml in the Export folder. 5. The Save As Type is an XML file type. 6. Click Save. 1 5 4 6
7. To complete the export, in the Control Properties window, click OK.
Import a Personalization
Once a personalization XML file is exported, use the import button to import the file into another user account. You must first have the XML file in a location that other users can access. After importing a personalization, you must exit the program and launch it again to view it. Once a personalization is imported, it is stored with the new user account. To import the Sales Order Entry personalization: 1. When you have logged into the application with another user account, launch Sales Order Entry. 2. From the Tools menu, select Personalization. 3. The Control Properties window displays. Click the Import button. 1
4 4. In the Open window, the Look In folder defaults to the users Export folder. However, you may need to browse to the network location where the exported personalization is stored. 5. Select the file you want to import. In this example the filename is App.SalesOrderEntry. SalesOrderForm_MANAGER.xml. 6. Click the Open button. 5
7. Click OK in the Control Properties window. 8. Exit the Control Properties window and Sales Order Entry and launch it again to view the personalization.
Delete Personalizations You can always remove any unwanted personalizations using the Delete button in the Control Properties window. Once the delete button is clicked, exit out of the program and launch it again to refresh the window. The program displays without any personalizations. You can personalize many sheets within a program. However since personalizations are stored both by program and User ID, deleting the personalization removes all the changes you have made to the program.
To delete the Sales Order Entry personalization: 1. From the Tools menu, select Personalization.
2. The Control Properties window displays. Click the Delete button. 3 3. Exit the Control Properties window and Sales Order Entry. When you launch Sales Order Entry again, the form is no longer personalized.
You can also delete Personalizations using both Personalization Purge and Customization/Personalization Maintenance. This functionality is discussed in Chapter 6: Customization Utilities.

EpicorUserExpCust UserGuide 905700 Part1of3

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

EpicorUserExpCust UserGuide 905700 Part1of3

Încărcat de

Drepturi de autor:

Formate disponibile

Epicor ICE 2.

5 User Experience and Customization Guide

Epicor ICE 2.5 User Experience and Customization Guide User

About Epicor Software Corporation

Release 9.05.700 Distribution April 2012

STARTUP CONFIGURATIONS | CHAPTER 1

Chapter 1 Startup Configurations

EPICOR SOFTWARE CORPORATION | 1

CHAPTER 1 | STARTUP CONFIGURATIONS

Configuration Settings File

Configuration File Location

Make a Copy of Default

Multiple Configuration Files

The Configuration Editor

2 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

EPICOR SOFTWARE CORPORATION | 3

CHAPTER 1 | STARTUP CONFIGURATIONS

4. The Configuration Editor displays.

4 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

STARTUP 6 7 EPICOR SOFTWARE CORPORATION | 5

CHAPTER 1 | STARTUP CONFIGURATIONS

Settings - The Complete List

6 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

CHAPTER 1 | STARTUP CONFIGURATIONS

SETTING MESCustomMenuID MESImage ProductBrandIcon ProductBrandText ProductID ProductLogonImage ResourceFile

SessionManagerUri SplashImage SysmonPort ToolbarSettings Version

8 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

For example: <ContextMenuNestingLevel value =0/> DataCollectionUser

CHAPTER 1 | STARTUP CONFIGURATIONS

10 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

<Style value=C:\epicor\MyThemes\BlueMain.isl options=SpecifyName|None|Default/>

<Style value=BlueMain.isl options= SpecifyName|None|Default/>

<Style value=Default options=SpecifyName|None|Default/>

<Style value=None options=SpecifyName|None|Default/>

EPICOR SOFTWARE CORPORATION | 11

CHAPTER 1 | STARTUP CONFIGURATIONS

12 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

EPICOR SOFTWARE CORPORATION | 13

CHAPTER 1 | STARTUP CONFIGURATIONS

Sort Method Default

Sort Method Exceptions

STARTUP CONFIGURATIONS | CHAPTER 1

Run Time Arguments

EPICOR SOFTWARE CORPORATION | 15

CHAPTER 1 | STARTUP CONFIGURATIONS

Run Time Arguments List

16 | EPICOR SOFTWARE CORPORATION

STARTUP CONFIGURATIONS | CHAPTER 1

CHAPTER 1 | STARTUP CONFIGURATIONS

18 | EPICOR SOFTWARE CORPORATION

STYLING AND THEMES | CHAPTER 2

Chapter 2 Styling and Themes

EPICOR SOFTWARE CORPORATION | 19

CHAPTER 2 | STYLING AND THEMES

Style Theme Loading

| STYLING AND THEMES3 4 20 | EPICOR SOFTWARE CORPORATION