Route and Route Task Properties

These properties configure routes. For general usage, route properties are defined in emxComponent.properties. Email notification properties are definfed in emxSystem.properties. For routes added to Bookmark Roots and to manage Bookmark Root content, properties are defined in emxTeamCentral.properties.

This page discusses:

emxComponents.properties for Routes and Route Tasks

If you want to change the default values, enter your changes in the emxComponent.properties page object. For more information, see Editing Properties Using MQL.

Property Name Property Description Valid Values
emxFramework.Routes.RouteVisibility Defines how routes are listed on the Routes summary pages for route members. When true, routes are listed for the route owner and all members. When false, routes only show for the route owner. True or False
emxComponents.RouteDefaultAction Defines the default action for route tasks. The value you enter is automatically entered for a task when a route is created; the route creator can change the value. One of the following:
  • Approve
  • Comment
  • Notify
emxComponents.Routes.ShowCommentsForTaskApproval Defines whether the Comments field is shown for tasks with Approve actions. True shows the Comments field.

Allowing assignees to enter a comment and choose an approval option opens the possibility of a user entering conflicting information. For example, the assignee could choose Approve but enter a negative comment.

 True or False
emxComponents.Routes.ShowAbstainForTaskApproval Defines whether Abstain is displayed as an option for route tasks with Approve actions. True includes Abstain as an approval choice.

This property is also applicable for the Route Management app.

 True or False
emxComponents.Routes.DefaultContentType Defines the default business object type to search for when adding content to a route. This value does not prevent other types from being searched for, it just determines the type pre-loaded into the search page. For example: emxComponents.Routes.DefaultContentType=type_Document Symbolic name of an object type
emxComponents.Route.AddPeoplePreference Defines whether a user must enter at least 1 character (in addition to the * wildcard) for the User Name when adding people to a route or route template. When false, users can enter the * wildcard by itself in the User Name field of the Add people dialog box.

If your company has many people defined (thousands), the search could affect performance if using the * wildcard by itself.

 True or False
emxComponents.Routes.EnforceAssigneeApprovalComments Defines if the Comment field on a route task is mandatory. True makes the field mandatory; false makes the field optional. True or False
emxComponents.Routes.EnforceOwnerReviewComments Defines if the Comment field for the route owner (when Route Owner Review is set to Yes for a task) is mandatory. True makes the field mandatory; false makes the field optional. True or False

emxSystem.properties for Routes and Route Tasks

If you want to change the default values, enter your changes in the emxComponent.properties page object. For more information, see Editing Properties Using MQL.

Property Name Property Description Valid Values
emxFramework.Routes.Notification.Link.Enable3DSpace Determines the target for links in email notifications or 3DNotification. When false (the default), links for routes open the properties for the route in Route Management and links for tasks open in Collaborative Tasks.

When true, links for routes and tasks open in Collaboration and Approvals.

Default is false.

 True or False
emxFramework.Routes.EnableMails Determines if email notifications are sent from Collaboration and Approvals in addition to email notifications from 3DNotification.

If this property is set to false and the user does not enable email notifications in 3DNotification, they will not receive any email notifications for route and task events. They will receive a 3DNotification for events they have enabled.

If this property is true AND the user enables email notifications in 3DNotification, they will receive 2 notifications for each route and task event.

Default is false.

 True or False

emxTeamCentral.properties

If you want to change the default values, enter your changes in the emxTeamCentral.properties page object. For more information, see Editing Properties Using MQL.

Property Name Property Description Valid Values
emxTeamCentral.DocumentsinMultipleRoutes Defines if users should be able to add a document to more than one route. When false, a document can only be included in a single active route. True or False
emxTeamCentral.CanRouteCheckoutDocuments Allows users to route documents that are locked for edit. When false, users cannot add locked documents to a route. True or False
emxTeamCentral.InBoxTask.YellowDelay This property is not included in emxTeamCentral.properties and must be added if you want to use it.

Defines how many days in advance of a due date that a task is considered "approaching the due date". Without this property, a value of 1 is used. This property allows you to choose a different number of days.

 Positive integer
emxTeamCentral.SetTaskEscalationDeltaDays Defines the number of days a Bookmark Root owner can choose for task escalation notices. For example, if the property is set to 20, Bookmark Root owners can choose to send task due notifications up to 20 days before or after the task due date. Positive integer
emxTeamCentral.RouteVisibility Defines the visibility for routes. When 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.)

When false, the My Routes list only contains routes the user owns and route members cannot access route details until their task is pending.

 True or False