emxSystem.properties

3DLive.Environments = 3DLive, Designer Central

The "environment" is a group of business process products. The values for this property become options in the Environment drop-down list in the 3DLive Search Criteria dialog box.

3DLive.Domains.Engineering_Central = type_Part,type_HardwarePart

3DLive.Domains.Designer_Central = type_CATProduct,type_CATPart

The text after Domains in the property name must match an environment defined in the 3DLive.Environments property. Use the symbolic names for the administrative types.

3DLive.ExpandRelationshipPattern.ENVIRONMENT.TYPE=

3DLive.ExpandTypePattern.ENVIRONMENT.TYPE=

where ENVIRONMENT matches a value defined in 3DLive.Environments property, and the TYPE is defined for that environment's Domain property. Use symbolic names for administrative type names.

For example:

3DLive.ExpandRelationshipPattern.Engineering_Central.type_Part = EBOM

3DLive.ExpandTypePattern.Engineering_Central.type_Part = *

In this example, any object (based on the * wildcard for the second property) connected to the Part using the EBOM relationship should be found. If the expand type pattern property is blank, the object will not be expanded during searches.

3DLive.ViewTable.ENVIRONMENT.TYPE=table_3DLiveBasic

Use the symbolic name of the table. See Building a Table for details on creating configurable tables.

3DLive.ImagePaths.ENVIRONMENT.TYPE=

3DLive.ImageFormats.ENVIRONMENT.TYPE=

For example:

3DLive.ImagePaths.Engineering_Central.type_Part = 
$<to[relationship_ImageHolder].from.id>,$<from[relationship_PartSpecification].to.id>

3DLive.ImageFormats.Engineering_Central.type_Part = CGR,CGR

When searching for an image, the system follows the defined paths until it finds an Image Holder object, then checks that object for a file checked into the listed format. If none are found, the system continues searching the defined image paths. For each path defined in the image paths property, you must define the format. If the image is found on the first path, the first listed format is checked. If the image is found on the fourth path, the fourth listed image format is checked (you can provide the same format for all paths, if appropriate).

3DLive.ThumbnailPaths.ENVIRONMENT.TYPE=

3DLive.ThumbnailFormats.ENVIRONMENT.TYPE=

The ThumbnailPaths property follows the same format as the ImagePaths property; the ThumbnailFormats property follows the same format at the ImageFormats property.

emxFramework.FolderContentTypesThatTypesRequireGrants=type_Document, 
type_Part,type_RequestForQuote,type_Quotation,type_Package 

This property applies to objects added to workspace and project folders. The schema name for a folder object is Workspace Vault. Typically, when an object type is added to a folder, people with access to the folder should be granted access to that object. In Program Central, only grants for document types and their sub-types are made.

emxFramework.IncludeSubTypesForGrants=true

• true (default). Any sub-type defined for the defined types will be included in the access grants.
• false. the grants are made only for the specific types listed in the above property

eServiceSuiteSUITE_NAME.Directory 

where SUITE_NAME is the Central name of the application, such as EngineeringCentral for ENOVIA Engineering Central.

This is typically Apps/Framework/VERSION/APPLICATIONNAME.

eServiceSUITE_NAME.ApplicationPropertyFile 

where SUITE_NAME is the Central name of the application, such as EngineeringCentral for Engineering Central.

By default, this file is named emxAPPLICATIONNAME.properties. All properties files are located in Apps/Framework/ VERSION/UserInterface.

eServiceSUITE_NAME.ApplicationStartPage 

where SUITE_NAME is the Central name of the application, such as EngineeringCentral for ENOVIA Engineering Central.

This page is typically called after the application home page is invoked and loads the application properties file. This page must be within the directory specified in the directory property.

emxFramework.AutoFilter.Basic.InclusionList=type,current,owner,policy

emxFramework.AutoFilter.Attribute.InclusionList

As installed, this property is blank. You need to add the attributes for which you want to enable the auto filter functionality.

emxFramework.AutoFilter.Attribute.ExclusionList

As installed, this property is blank. You need to add the attributes for which you want to exclude from the auto filter functionally.

Autofiltering can be enabled/disabled for specific tables or structure browsers (by passing the URL parameter autoFilter=true/false); and individual columns can be defined with the Auto Filter setting (set to true or false). The included basic properties and attributes entered in the emxSystem.properties file will be filterable even if the specific column in the table/structure browser does not have the Auto Filter=true setting. If an attirbute is included in the inclusion list but the Auto Filter=false setting is defined on the column, then that column on the table/structure browser page will not be included for autofiltering.

The URL parameter autoFilter overrides all other autofilter properties and settings. See Methods for Filtering a Table.

emxFramework.BackgroundProcess.ServerUniqueIdentifier=ServerIdentifier

emxFramework.BeanMapping.PreliminarySearchFiles = 

customMappingFile.properties,emxIntegrationsBeanMappingFile.properties

emxFramework.Preferences.ToggleBrowserToolbar = true 

• true (default). The browser toolbar remains visible.
• false. The application pops up a new window without the browser toolbar after the user logs in, and closes the browser window used to log into the ENOVIA products.

emxFramework.Calendar.Events = NON-WORKING|yellow|selectable

This property only affects date fields or columns defined with the Calendar Function and Calendar Program settings. The non-working days are those associated with a calendar defined for a Location related to the field/column where the date is being set.

Any events listed for a calendor show as yellow when a user opens a date chooser. For example, if Sundays have been defined as events (that is, non-working days), then the date chooser would look like this:

As installed, NON-WORKING is the only event defined. If your business processes require additional types of events (for example, you want to display holidays in a different color than weekends), you can create a custom JPO:method that returns a string of dates to the date chooser. See the Java Docs for details on the Calendar Program and Calendar Function settings for a datefield or column.

emxFramework.DateTime.DisplayFormat = MEDIUM  

• SHORT (e.g. 12.13.52 3:30 pm). Date fields for some ENOVIA product pages contain logic that compares the date the user enters with another date. For example, the task definition pages compare the task due date with the current date. If the DisplayFormat is set to SHORT, only dates between 1950 and 2049 can be entered and compared correctly on such pages. If users need to enter dates outside of this range, choose the MEDIUM format.
• MEDIUM (e.g., Dec 12, 1952) (default)
• LONG (e.g., December 12, 1952)
• FULL (e.g., Tuesday, December 12 1952 AD 3:30:42 pm PST)

emxFramework.DateTime.DisplayTime = false  

• true. The date display includes the time.
• false (default). The date display does not include the time.

If no TimeZone preference is set, then the DateTime is shown in the browser's time zone. The time is shown in terms of GMT+/- hh:mm, (e.g., Saturday, August 21, 2004 12:45:00 PM GMT-04:00). To get the time in a format like EST or PDT, set the TimeZone preference to a specific zone.

The JSP can override this setting.

eServiceSuites.eMatrixDateFormat = MM/dd/yyyy hh:mm:ss a  

If you change the values for these properties, make sure there are no trailing spaces at the end of the format. For example, if you remove the "a" at the end of the default format, remove the space that precedes it also.

eServiceSuites.eMatrixInputDateFormat = MM/dd/yyyy hh:mm:ss a 

Must be the same format defined in either MX_NORMAL_DATETIME_FORMAT or MX_TERSE_DATETIME_FORMAT. By default, it is the same format as NORMAL.

When the user chooses a date/time using the Calendar chooser (the standard UI mechanism for entering dates in ENOVIA products), the system converts this localized date to the format defined in this property. The system then attempts to parse the date/time using the format defined in NORMAL. If the format does not match NORMAL, the system parses the format using TERSE.

emxFramework.CalendarDisplay.YearsBefore = 2 

emxFramework.CalendarDisplay.YearsAfter = 3 

emxFramework.CalendarDisplay.CustomYears = 1995 

Specify the number years after the current year to be included in the Year drop-down list that is displayed when a user clicks the calendar icon. Specify any years to include in the calendar drop-down not contiguous to the currently defined years.

This property sets the number of years before the current year to be included in the Year drop-down list that is displayed when a user clicks the calendar icon.

emxFramework.Application.Name = ENOVIA 

emxFramework.Common.defaultPageTitle = ENOVIA 

eServiceSuiteFramework.Directory = common 

eServiceSuiteFramework.RootDirectory = .. 

eServiceSuiteFramework.CommonDirectory = common 

eServiceSuiteFramework.ComponentDirectory = component 

If you change any directory structure or names, you need to update these properties.

eServiceSuiteFramework.StringResourceFileId = 
emxFrameworkStringResource 

emxFramework.EnableURLNotification = true 

• true (default). Links are enabled.
• false. Links are disabled.

emxFramework.NotificationAgent = VALID_ENOVIA_USERNAME 

The value for this property should be the username of the user the system notifications should appear to be from.

For example, suppose the properties value is set to a user called MGreene, whose Full Name is defined as Meg Greene and the email address is defined as mgreene@host.com. A system notification that a user receives in an email application would look like this:

From: Meg Greene [mailto:mgreene@host.com]

Sent: Thursday, April 11, 2002 4:09 PM

To: VCP User

Subject: 'Folder Created'

Business Object: Workspace Design Team 0000000004

'Folder Created' on 'Workspace' 'Design Team' '0000000004' at 04-11-2002 04:22 PM

http://host:7001/enovia/common/emxNavigator.jsp?objectId=34400.35078.64661.42476

emxFramework.NotificationLanguages = en 

Default = en (English).

emxFramework.IconMailLanguagePreference=English,German,French,Italian,
Japanese,Korean 

emxFramework.IconMailLanguageLocaleEnglish=en

emxFramework.IconMailLanguageLocaleGerman=de

emxFramework.IconMailLanguageLocaleFrench=fr

emxFramework.IconMailLanguageLocaleItalian=it

emxFramework.IconMailLanguageLocaleJapanese=ja

emxFramework.IconMailLanguageLocaleKorean=ko

eServiceEngineeringCentral.emxCreatePersonBusObject= FALSE 

• true. Creates a new user when a deleted user logs in.
• false (default). Deleted users cannot log in.

eServiceEngineeringCentral.emxSafetyVault= eService Production 

LifecycleMassApproval.type_ECR.RelatedObjects.Connections=relationship
_AffectedItem

LifecycleMassApproval.type_ECO.RelatedObjects.Connections=relationship
_AffectedItem

LifecycleMassApproval.type_Part.RelatedObjects.Connections=relationshi
p_PartSpecification

LifecycleMassApproval.type_CADDrawing.RelatedObjects.Connections=relat
ionship_PartSpecification

LifecycleMassApproval.type_DrawingPrint.RelatedObjects.Connections=rel
ationship_PartSpecification

LifecycleMassApproval.type_CADModel.RelatedObjects.Connections=relatio
nship_PartSpecification

In many cases, a parent object cannot be approved until all of its child objects have also been approved. For example, an ECO cannot be approved until all of the Affected Items controlled by the ECO have been approved. These properties allow users to approve the parent and all its children at the same time.

These properties list the relationship to use to determine if another object must be approved in order to approve the selected object. As an example, the first property defines that if an ECO is connected to another object (such as a Part) using the Affected Items relationship, then the user can approve both the ECO and the Part at the same time.

LifecycleMassApproval.type_ECO.RelatedObjects.ConnectionDirection=to

LifecycleMassApproval.type_ECR.RelatedObjects.ConnectionDirection=to

LifecycleMassApproval.type_Part.RelatedObjects.ConnectionDirection=to

LifecycleMassApproval.type_CADDrawing.RelatedObjects.ConnectionDirecti
on=from

LifecycleMassApproval.type_CADModel.RelatedObjects.ConnectionDirection
=from

LifecycleMassApproval.type_DrawingPrint.RelatedObjects.ConnectionDirec
tion=from

If you add a property for the RelatedObjects.Connections for an object type, make sure you also add the property for the RelatedObjects.ConnectionDirection for that object type.

Used by the mass approval feature, these properties define which side of the relationship that the listed type is on (to or from). For example, if and ECO is connected to a Part using the Affected Items relationship (the first prooperty above), then the ECO must be on the to side of that relationship in order for both the ECO and Part to be approved at the same time.

ematrix.common.disableAllExports=false

• true. Turns off all export to Excel features.
• false (default). Export to Excel is available.

Not all applications refer to this property.

ematrix.common.icon.spreadsheet=../common/images/buttonContextExcelExport.gif

The above property must be set to true for the icon to be visible in toolbars.

emxFramework.FcsEnabled = true 

• true (default). FCS is enabled.
• false. FCS is disabled.

You must also enable FCS as described in the System Manager Guide

emxComponent.QuickFileAccess.Relationships.Default = 
from[relationship_ReferenceDocument].to.id, 
to[relationship_ReferenceDocument].from.id 

emxFramework.UseApplet = true 

• true. The applet is used for uploading files.
• false (default). The applet is not used.

emxFramework.Applet.MaximumNoFilesLimit=200 

emxFramework.UseDownloadApplet = false 

• true. The download applet is enabled.
• false (default). The download applet is disabled.

emxFramework.ServerTimeOutInSec = 86400 

If files do not complete the upload or download within the number of seconds set here, the process times out.

emxFramework.Unix.JavaPlugInURL=http://java.sun.com/j2se/1.4.2/
download.html 

emxFramework.Windows.JavaPlugInURL=http://java.sun.com/products/
plugin/autodl/jinstall-1_4-windows-i586.cab 

By default, for Windows it points to an auto-install cab file; for Unix it points to a Java-plug-in download page on the Sun web site. For Windows, it is Auto-install, but for Unix (Solaris, HP, AIX) it points to download URL.

emxFramework.FilterParameterPattern= 

For example:

emxFramework.FilterParameterPattern = <script,<input,<form

Use caution when using this property. If an incorrect character is specified, it may render applications unusable.

eServiceSuiteREGISTEREDSUITE.Help.Directory = XXXUserMap
eServiceSuiteREGISTEREDSUITE.HelpFile = emxXXXHelp.properties

where:

• REGISTEREDSUITE is the name of the ENOVIA product, such as EngineeringCentral or Requirements.
• XXX is the product identifier, such as ENG for Engineering Central or RMT for Requirements Central

For example:

eServiceSuiteEngineeringCentral.Help.Directory = EngUserMap
eServiceSuiteEngineeringCentral.HelpFile = emxENGHelp.properties

Change the values for these properties to the names required by a custom help system.

eServiceSuiteREGISTEREDSUITE.ApplicationPropertyFile = emxREGISTEREDSUITE.properties

where REGISTEREDSUITE is the name of the ENOVIA product, such as EngineeringCentral or Requirements.

For example:

eServiceSuiteEngineeringCentral.
ApplicationPropertyFile = emxEngineeringCentral.prop
erties

emxFramework.IconMail.ShowSelects = true 

• true (default). The search page for persons includes a Search In option to select a company.
• false. The Search In option is not included in the Person search page.

emxFramework.IconMail.FindSelection = My 
Company,Customers,Suppliers,Collaboration Partners 

eServiceSuiteFramework.InitializationFile = 
emxCommonAppInitialization.jsp 

SUITEKEY.InitializationFile = JSP_INITIALIZATION_FILE

SUITEKEY.PropertyFileAlias = NAME_OF_APPLICATION_LEVEL_ATTRIBUTE

For example, for Engineering Central, the property in emxSystem.properties is:

eServiceSuiteEngineeringCentral.PropertyFileAlias = 
emxEngineeringCentralProperties

The property name of the alias is also set in "application" for every application using the same property mentioned above. For Engineering Central, it will be as below.

application.setAttribute("eServiceSuiteEngineeringCentral.PropertyFile
Alias", "emxEngineeringCentralProperties");

All applications should use the alias name defined above and should use the following method to avoid duplicate instances of the same property object in "application" scope.

propertyAlias = 
(String)application.getAttribute("eServiceSuiteEngineeringCentral. 
PropertyFileAlias");

emxFramework.ShowLanguageForFileCheckin=false 

• true. A drop-down list of languages in included on the checkin page.
• false (default). No list of languages is provided.

Users can use the list to specify the language the document is in. The file content language will be used by Verity during searches. This allows Verity to search documents written in multi-byte languages for multi-byte characters.

emxFramework.Lifecycle.MassPromoteDemote.Enable=true 

• true (default). Any table or structure browser page that includes both the Type and State columns will also include the Promote and Demote buttons on the page toolbar.
• false. Promote and demote buttons do not show on toolbars.

This property can be overridden for a specific page using the massPromoteDemote URL parameter as defined in URL Parameters Accepted by emxIndentedTable.jsp.

emxFramework.Lifecycle.MassPromoteDemote.<SymbolicNameofPolicy>.From.RelationShipList

emxFramework.Lifecycle.MassPromoteDemote.<SymbolicNameofPolicy>.To.RelationShipList

Objects connected to the to side of one of the defined "To" relationships are treated as parent objects and objects connected to the from side are treated as child objects.

emxFramework.Lifecycle.MassPromoteDemote.ExcludeTypeList

emxFramework.FullName.Format = <Last Name>, <First Name> 

The property accepts these three sub-keys, which are all fields that are filled in when a person is added in an ENOVIA product: <First Name>, <Last Name>, and <User Name>. For example, you could change the format to <First Name> <Last Name> or <User Name>. The default format is <Last Name>, <First Name>.

ENOVIA Business Process Services includes a conversion utility that lets you populate the Full Name field if you decide to change the full name format. See Settings Supported by emxCreate.jsp for details. Additionally, ENOVIA Business Process Services includes trigger programs that run when the person's name is changed to update the Full Name field. For more information, see Automation for Persons.

emxFramework.DecimalSymbol=, 

This is a server-wide preference setting. The value for this property should be the same as defined for MX_DECIMAL_SYMBOL in the enovia.ini file: MX_DECIMAL_SYMBOL=,

For more information on setting the decimal character for ENOVIA Live Collaboration and Oracle, see the Live Collaboration Database Installation Guide.

emxFramework.DigitSeparator = false 

• true. Uses the comma as the thousandths separator.
• false (default). No separator is used.

If the decimal symbol is set to comma, then the thousandths separator is a period. Otherwise, the separator is a comma.

The JSP that displays the field must make use of this property to display the separator.

emxSystem.pageHistory.limit=50 

Default = 50. This means that when a user visits the 51st page, that page replaces the first page visited in the list.

emxFramework.History.maxRecords=2000 

Default = 2000.

emxFramework.LifeCycle.ApprovalPasswordConfirmation=TRUE 

• true (default). A Password Verification page appears when users apply a signature for lifecycle promotion or demotion. Users must enter the password they use to log in for the signature to be applied. This is only for signatures applied using the Lifecycle and Approval pages. See Lifecycle Page. For instructions on using this verification with external authentication (Single Signon), see Configuring Approval Verification with External Authentication.
• false. No password verification is required for promotion.

emxFramework.LifeCycle.ExternalAuthenticationURL 

emxFramework.Routes.EnableFDA=false 

• true. Task assignees must enter their password. These approval options are available only for tasks with Approve actions.
• false (default). No password is required for these actions.

emxFramework.Routes.ShowUserNameForFDA=true 

• true (default). Users must enter their username in addition to the password for approvals.
• false. The username is not required; the user only needs to enter their password.

emxFramework.Routes.VerificationCount = 3 

The default value is 3. When a user reaches this limit, the system logs the user out and inactivates the user.

emxFramework.Routes.NotifyPeople = Test Everything 

When using the route task verification with external authentication, several additional setup steps are needed. Additionally, the last three properties listed above are ignored and only the EnableFDA property is used. When external authentication is used with the EnableFDA property set to true, the system requires both the user's username and password. If the user enters incorrect information, the system redisplays the username and password page. There is no verification count limit and the user is not inactivated.

emxFramework.PopupSize = Small,Medium,Large,SmallTall,MediumTall

emxFramework.PopupSize.Large = 960x700
emxFramework.PopupSize.Medium = 812x500
emxFramework.PopupSize.Small = 412x400
emxFramework.PopupSize.SmallTall = 412x700
emxFramework.PopupSize.MediumTall = 812x700

emxFramework.PopupSize.Default = Medium

• Large
• Medium
• Small
• SamllTall
• MediumTall

You can use the Popup Size setting for a form to use a different size window than the default; that setting supports the same sizes listed here.

mxFramework.Dialog.ProcessingText = false 

• true. The processing text is displayed.
• false (default). The text is not displayed.

emxFramework.Javascript.BadChars =  < > \ [ ] | 

emxFramework.Javascript.NameBadChars =  " # $ @ % , * ? \ < > [ ] | 

emxFramework.Javascript.BadCharsForCheckinDesc =  < > \ [ ] | 

emxFramework.Javascript.FileNameBadChars = ' # $ @ & % 

emxFramework.InputFilter.BadChars=

<|>|"|'|%|;|)|(|&|+|-

ENOVIA cannot filter out the & and + symbols because they are used for specific functions.

emxFramework.InputFilter.BadRegExp=

Add a pipe-separated list of regular expressions to be filtered from being stored in the database.

\\<.*?(?i)script.*?\\>

If you enable input filtering in web.xml, you should add the above value to this property.

emxFramework.InputFilter.ExcludeParameters = treeLabel|contentURL|url

emxFramework.spellchecker.URL = 

../SpellChecker?cmd=script&doc=wsc

emxFramework.Toolbar.MaximumLength = 15 

emxFramework.PowerView.Channel.Label.MaximumLength = 17

eServiceSuiteFramework.URL = common/emxNavigator.jsp 

emxNavigator.Home.ContentPage = emxNavigatorDefaultContentPage.jsp 

In addition, you can configure this feature to include related objects in the report. For example, an ECO might not be able to be promoted because a part is not in the required lifecycle state. Based on the policy governing the object to be promoted and its current state, you define which relationships to follow to locate related objects to include in the validation report.

These properties have no value when installed; you must define a value if you want to implement this functionality.

emxFramework.PromoteTrigger.Validation.To.Rels.<symbolic name of 
policy>.<symbolic name of current state> 

For example:

emxFramework.PromoteTrigger.Validation.To.Rels.policy_ECOStandard.stat
e_PlanECO=relationship_VaultedObjects,relationship_WorkFlowContent

emxFramework.PromoteTrigger.Validation.From.Rels.<symbolic name of 
policy>.<symbolic name of current state> 

For example:

emxFramework.PromoteTrigger.Validation.From.Rels.policy_ECOStandard.st
ate_PlanECO=relationship_NewPartPartRevision

emxFramework.TypeAhead=true 

• true (default). Type ahead functionality is enabled.
• false. All type ahead functionality is disabled, including any JPOs configured for any chooser fields.

 emxFramework.TypeAhead.RunProgram=true 

• true (default). JPOs configured for chooser fields are executed.
• false. No JPOs for any chooser fields will be run, even if configured at the field level.

When using a JPO and method to retrieve possible values, the pop-up box initially shows the recent entries by the user. When the recent entries do not match what the user types and the specified number of characters has been entered, the JPO retrieves matching values from the server.

The recent values are stored in the Revision field of a cue object in that user's context.

emxFramework.TypeAhead.RunProgram.CharacterCount=2  

The property value can be overridden by the TypeAhead Character Count field setting. If data values for the field typically start with a prefix, this value can be set larger than the size of the prefix so that the JPO retrieves a smaller data set.

emxFramework.TypeAhead.SavedValuesLimit=10 

emxFramework.FullTextSearch.TypeAhead.Suggestion.Limit = 50 

The default value is 50. If more than 50 objects match the text entered by the user, More... shows, and the user can continue to type characters to narrow down the suggestions list.

This property does not affect the pre-defined Person, Organization, or Type choosers, or if a custom JPO is used to implement the type ahead feature on a field.

emxFramework.Toolbar.ShowPageURLIcon=true

• true (default). The shows on all toolbars for all components in all ENOVIA applications.
• false. the is not included on any toolbars.

This property can be overridden for a specific form, table, structure browser, or other configurable component using the showPageURLIcon URL parameter. See URL Parameters.

See Copying the URL for the Page for instructions on using .

emxNavigator.UICache.ComponentAge = 3600 

Default = 3600 seconds ( 1 hour)

The cached data for any given administrative object or trigger information expires based on this pre-set amount of time (ComponentAge). Once expired, the next request for that specific data is dynamically obtained/cached fresh from the database and the cache life is reset for that object.

emxFramework.ViewerExtensions=jt,dwg,svg 

If a user attempts to view a file whose extension is not in this list, the system does not attempt to open the file in a viewer, even if a viewer has been registered and installed. Instead, the system handles the file as it does any standard file for the application you are in. The standard view behavior for applications is to attempt to open the file in the browser and if the browser does not recognize the extension then it prompts the user to save the file.

emxFramework.FormatsWithViewerPreference = format_JT 

For example, if you want users to choose preferred viewers for JT and ACAD files, set this property to format_JT, format_ACAD. See Setting Up 2D and 3D Viewers for more details.

When a user chooses to view a file with a format assigned to a 2D/3D viewer, the system first looks for a preferred viewer specified in the person's profile. Each user can specify the preferred viewer for a format or the administrator can specify it. If the system finds a preferred viewer for the format, it opens the file using that viewer. If it does not find one, the system does not launch any viewer.

Based on this property, the applications dynamically add fields to the Person profile pages. The system constructs the labels for the fields by appending "Viewer Preference" (from the ViewerPreferenceLabel string resource tag) to the format name (resolved from the symbolic name).

<FormatSymbolicName> <ViewerPreferenceLabelTag>

For example, when the FormatsWithViewerPreference property is set to format_JT, the system adds a JT Viewer Preference field to the Person profile pages.

The system populates the preference fields by listing every viewer assigned to the format (done using the Viewer Registration wizard). If a tip has been defined for the viewer, the tip text is used to represent the viewer in the drop-down list. If there is no tip text, the name of the program object for the viewer servlet is used.

emxFramework.Viewer.ServletPreFix= /WEBAPPNAME/servlet/