emxTeamCentral.properties

The properties in emxTeamCentral.properties let you configure several features within Team Central.

Related Function Property Name
Allowed Values Description
Greeting 
eServiceTeamCentral.showGreeting = true

  • true. The greeting displays.
  • false. The greeting does not display.

The default value is true.

 Controls whether the banner greeting displays (Welcome USER of COMPANY).
Images 
eServiceTeamCentral.externalLinkImage = images/utilTeamLogo.gif
If you want to change the default image, enter the name of the image file. Defines a default image used within applications if the project or person does not have an associated image. 
emxTeamCentral.ImageCheckin = true

  • true. Enables image checkin.
  • false. Disables image checkin.

The default value is true. If these images are not used, the default image for the host company is used.

 Removes the fields that let users specify image files for a company, workspace, and person.
Folder 
emxTeamCentral.DefaultCategories=Production;Design;Status;Testing;Busi
ness;ChangeDocs;Prototype;RefInfo

To add a new default folder, add ";ID" to the end of the DefaultCategories property in emxTeamCentral.properties, where ID is the ID for the new folder. Then add a property for the name and for the description in the StringResource file. For example, to add a folder called "Manuals and Readmes" with the ID "Manuals", you would change the emxTeamCentral.properties setting to:

emxTeamCentral.DefaultCategories=Production;Design;Status;Testing;Busi
ness;ChangeDocs;Prototype;RefInfo;Manuals

Then you would add these properties to the StringResource file: 

emxTeamCentral.AddCategoriesDialog.Manuals=Manuals and Readmes

emxTeamCentral.AddCategoriesDialog.ManualsDesc=This folder contains 
files for user guides and readmes
Configures default folders and descriptions by specifying IDs for each default folder. The IDs must be separated by semicolons and they cannot contain spaces.

This property works with the AddCategoriesDialog.ID and the AddCategoriesDialog.IDDesc properties in the StringResource file. For example, here are the properties for the default folder called Production.

emxTeamCentral.AddCategoriesDialog.Production=Production 
emxTeamCentral.AddCategoriesDialog.ProductionDesc=Current Workspace 
Production Documents

emxTeamCentral.Common.CheckforSubFolderName = false

  • true (default). Subfolders cannot have the same name as their parent folders.
  • false. A subfolder can have the same name as its parent folder. However, only one subfolder within the folder can have the same name as the parent folder. That is, 2 subfolders within a folder cannot have the same name.
 Defines if subfolders can have the same name as the parent folder (for example, if the folder name Computer can contain a subfolder also named Computer).
Route 
emxTeamCentral.DocumentsinMultipleRoutes = false

  • true. Documents can be added to multiple routes.
  • false (default). Documents can only be added to a single route.
 Defines if users should be able to add a document to more than one route. 
emxTeamCentral.CanRouteCheckoutDocuments = true

  • true. Users can add locked documents to a route.
  • false. Users cannot add locked documents to a route.
 Allows users to route documents that are locked for edit.
  
emxTeamCentral.globalReadSupport = false
 
  • true (default). Global read access can be granted.
  • false. Global read access cannot be granted.
 Defines global read access for folders.

If true, Workspace Leads can grant global read access for folders. Global Read access should only be enabled for folders whose documents need to be viewed by people who use an ENOVIA application, such as ENOVIA Sourcing Central, regardless of whether they are workspace members. For example, when also using ENOVIA Sourcing Central, Global Read access should be given to folders that will be used to store standard content documents for RFQ templates. When these documents are added to RFQ templates and then to RFQs that are based on the templates, all buyers and suppliers who have access to the RFQ will be able to view the documents. Except for these very special cases, Global Read access should not be given.

The standard workspace accesses apply for Global Read folders: people must have Read access to the folder to view documents. 

emxTeamCentral.SetTaskEscalationDeltaDays=20
For example, if the property is set to 20, workspace owners can choose to send task due notifications up to 20 days before or after the task due date. Defines the number of days a workspace owner can choose for task escalation notices. 
emxTeamCentral.RouteVisibility=true

  • true. All route members can access details for the route as soon as the route is started, even if their task is not yet pending. The route is listed in the My Routes list on the My View page. After a route member completes the task, the route is no longer listed in the My Routes list. (Although the route member can still access the route through the task details.)
  • false. The My Routes list only contains routes the user owns and route members cannot access route details until their task is pending.
 To Defines the visibility for routes.
Initial JSP 
emxTeamCentral.FrameworkTarget=

If no page is specified, the system goes to the standard My View page.

 Specifies a JSP to call when a user first logs in.
Keyword Search 
emxTeamCentral.KeywordSearch=ON

  • ON. Shows the keyword search field.
  • OFF. Removes the keyword search field from the search pages.
 Gives users the ability to search for text within checked in files. To work, you must install and configure Verity, Inc.'s K2 product. Contact the Verity Support Center for help on integrating with Verity K2 software. For information on configuring full text search within ENOVIA products, see the System Manager Guide.
  
emxTeamCentral.EAIVismarkViewerEnabled=false
 
  • true. Displays the JtFile Checkin option on all document checkin pages.
  • false (default). Does not display the JtFile Checkin option.
 Defines how 3D JT are uploaded. If your system has been configured for 3D JT file viewing (which includes installing the viewer and integration software, and registering the viewers and assigning formats), you can use the lin (when true) to check in JT files to folders and routes. Integrations with Viewer Registration is supported. For instructions on registering viewers and setting them up for users, see Setting Up 2D and 3D Viewers.
  
emxTeamCentral.eVisClientObjectName=eVisClient 
emxTeamCentral.eVisClientObjectRevision=0
#emxTeamCentral.eVisClientObjectVault=eService Administration
  Set the values for these properties with the business object's name, revision, and vault. The vault property is commented out and should not be used. Defines the business object that contains a preferred viewer application for users to download. When the system is configured to let users select their preferred viewer for files like .JT, a Download option is displayed on the profile page. To select a preferred viewer, say, e-Vis, download the appropriate installation program. Also see Setting Up 2D and 3D Viewers.
  
emxTeamCentral.eVisViewerRole=
  Use the symbolic name for the role, such as role_Buyer. Defines the roles for a viewer.

If a role is specified for a property and a particular viewer is set up for selection as the preferred viewer, then the perferred viewer list shows the names of only those who are assigned that particular role. If the viewer Download option has been configured, then the system displays the option for all those who choose that particular viewer as their preferred viewer.

If a role is not specified for the property, the system lists the viewer as a preferred viewer selection for all users. Also see Setting Up 2D and 3D Viewers.
  
emxTeamCentral.ObjectDetailsFiles = true
    Configures the Properties page for another ENOVIA application's object (other than Team Central) attached to a route. For example, users can access the Details page for objects that were routed from other applications and for objects added to folders and routes. (These settings do not apply to the object details page that can be accessed when an object is attached to IconMail.)
  
emxComp.ShowAttachements=TRUE
 
  • true (default0. Users can see that an object is attached to an IconMail message.
  • false. Users will not be able to see objects attached to IconMail message. There will be no indication that a message has an object attached.
 Allows access to objects attached to IconMail messages. By default, users cannot attach objects to IconMail but they can view details about objects that are attached to a message from another application.
  
emxComp.AttachementURL=
  If needed, enter the URL address for a JSP. Specifies a custom JSP to use for viewing object details.

If no page is specified, the system uses emxCompObjectDetails.
  
eServiceSuiteTeamCentral.emxTreeAlternateMenuName.SYMBOLIC_NAME__OF_TYPE=TMCSYMBOLIC_NAME_OF_TYPE
  Define the alternate tree as described in Building a Navigation Tree.

Replace SYMBOLIC_NAME__OF_TYPE with the symbolic name of the needed type.

Replace TMCSYMBOLIC_NAME_OF_TYPE with the name of the alternate tree you have defined. Here are a few examples of alternate tree properties. See the properties file for a complete list.
eServiceSuiteTeamCentral.emxTreeAlternateMenuName.type_Message=TMCtype_Message

eServiceSuiteTeamCentral.emxTreeAlternateMenuName.type_Meeting=TMCtype_Meeting
Defines alternate tree menus (the Categories menu that displays on an object's Properties page) to be used for types that are also used in other ENOVIA products. Types used in multiple applications, referred to as common types, include persons, companies, documents, and locations. The alternate tree menus let each application define its own tree categories for these common types. When a user views details for one of these common objects from ENOVIA Business Process Services, the system uses the tree menu object listed here instead of the standard tree menu object. (The standard tree menu object for a type has the same name as the symbolic name for the type. For example, the standard tree menu for meetings is named type_Meeting).