Translate entities
When you translate an entity, you are translating specific attributes of the entity. You can translate an entity's attributes at any time. You can translate all entity attributes at the same time or you may choose to translate specific entity attributes as you need them.
Entities can be broken down into three categories: configuration, master data, and transactional. See Key concepts for a definition of these categories.
Translatable entities
Translatable entities are a specific set of entities (configuration and master data entities) whose attributes can be converted to another language. Table 5-1. Translatable entity types lists these entity types.
If a migrator is available for an entity, you can migrate it from one PPM instance to another. Migrating configurations using entity migrators and workflows lets you automate and standardize a change-control process for your PPM implementation. For more information on migrating entities, see the Installation and Administration Guide.
Table 5-1. Translatable entity types
|
Entity Type
|
Entity ID
|
Migrator Available
|
Description
|
|
Activity
|
74
|
|
Simple categorization of requests, projects, tasks, packages, or miscellaneous. For more information on activities and their use, see the Financial Management User Guide and the Time Management Configuration Guide.
|
|
Business Objective
|
68
|
|
Business goals that can be prioritized. For more information, see the Program Management User Guide.
|
|
Charge Code
|
76
|
|
Link between work items and charge accounts. For more information, see theTime Management User Guide.
|
|
Data Sources
|
505
|
Yes
|
Provides data displayed in PPM Dashboard portlets. For more information, see the Creating Portlets and Modules and the Installation and Administration Guide.
|
|
Decisions
|
29
|
Yesa
|
Workflow steps that require an external action to determine the outcome. For more information, see Deployment Management Configuration Guide and Demand Management Configuration Guide.
|
|
Executions
|
28
|
Yesa
|
Workflow steps that are used to perform specific actions. For more information, see Deployment Management Configuration Guide.
|
|
Modules
|
470
|
Yes
|
A container for one or more PPM Dashboard pages. For more information, see Creating Portlets and Modules and the Installation and Administration Guide.
Note: You cannot export modules using reference codes or primary keys. You can export definitions only for a full list of modules.
|
|
Portlet Definitions
|
509
|
Yes
|
Customizable file that defines the look and feel of a portlet. For more information, see Creating Portlets and Modules and the Installation and Administration Guide.
Note: You cannot export portlet definitions using reference codes or primary keys. You can export definitions only for a full list of portlet definitions.
|
|
Region
|
473
|
|
Defines the regional calendars for resources and currency display settings. For more information, see the Financial Management User Guide and the Resource Management User Guide.
|
|
Report Types
|
17
|
Yes
|
Defines available reports. For more information, see the Reports Guide and Reference and the Installation and Administration Guide.
|
|
Request Header Type
|
39
|
Yes
|
Defines the collection of fields that appear in the header region of requests. For more information, see the Demand Management Configuration Guide and the Installation and Administration Guide.
|
|
Request Status
|
23
|
|
A value linked to a workflow step to drive the request logic during the life of a request. For more information, see the Demand Management Configuration Guide.
|
|
Request Type
|
19
|
Yes
|
Defines the Web form that users see when they create or view requests. For more information, see the Demand Management Configuration Guide and the Installation and Administration Guide.
|
|
Role
|
516
|
|
Describes resource requirements for resources, staffing profile positions, and tasks. For more information, see the Resource Management User Guide.
|
|
Scoring Criteria
|
529
|
|
Qualitative rankings to evaluate proposals, projects, and assets. For more information, see the Portfolio Management Configuration Guide.
Note: You cannot export scoring criteria definitions using reference codes or primary keys. You can export definitions only for a full list of scoring criteria.
|
|
Security Group
|
15
|
Yesa
|
Specifies members and access grants to control access to specific sections of PPM. For more information, see the Security Model Guide and Reference.
|
|
Skill
|
318
|
|
Abilities associated with resources. For more information, see the Resource Management User Guide.
|
|
User Data
|
37
|
Yes
|
Additional information specific to your business process or organization. For more information, see the Deployment Management Configuration Guide and the Installation and Administration Guide.
|
|
Validations
|
13
|
Yes
|
Determine the acceptable input values for user-defined fields and possible results that a workflow step can return. For more information, see Commands, Tokens, and Validations Guide and Reference and Installation and Administration Guide.
|
|
Workflow
|
9
|
Yes
|
A digitized process composed of a logical series of steps that define a business process. For more information, see the Deployment Management Configuration Guide,Demand Management Configuration Guide, and the Installation and Administration Guide.
|
|
a. Decision and execution entities are migrated with workflows that reference them. Security group entities are migrated with other entities that reference them.
|
Back to top
User requirements
In order to run the Translation Details and Translation Summary reports, you must have the System: Submit Reports access grant. By default, you have this access grant if you belong to the PPM Administrator or PPM All Access Grants security group.
To use the translation scripts, you must have the Sys Admin: Manage Translations access grant. By default, you have this access grant if you belong to the PPM Administrator or PPM All Access Grants security group.
Back to top
