Embedded Files
Context
Context
The entity template editor is used to create and edit entity templates. Entity templates are created to define the behaviour of an entity class. Examples of an entity class are a 'Project' (from the PPMAnywhere solution) or an 'Audit' (from the GRC Anywhere solution). An entity class can have more than one template defined for it. For example a 'Project' might have a 'Waterfall' template or 'Agile' template depending on the methodology. The 'Audit' class might have templates for an 'Internal Audit' and an 'External Audit'.
Accessing this page
Accessing this page
This page can be accessed from the Entity Templates Dashboard. From the menu, select Admin Center under the Administration section.
From the administration workbench, select Entity Types from the Templates section.
Creating a new entity type
Creating a new entity type
If this page has been accessed by selecting the '+' option on the Entity Templates Dashboard the form will be in edit mode with blank attributes.
Updating an existing entity type
Updating an existing entity type
If this page has been accessed by clicking on an existing template in the Entity Templates Dashboard the form will be in view mode.
Click on the pencil icon to make changes.
Basic attributes
Basic attributes
The Info section contains the basic attributes of an entity template..
Status reporting
Status reporting
Select the report type that should be used for status reports created for entities of this type.
Report types are defined in the configuration layer. Refer to Report Template Configuration for further details.
Selecting a type does not mandate that status reports must be submitted for this entity.
Planning
Planning
This section defines how work is planned for an entity. A number of different approaches are supported.
Governance and time capture
Governance and time capture
This section defines both the governance process and the rules about time recording against entities using this template. The governance process represents the workflow for the entity and will typically model the approval stages or 'gates' that the entity must pass through from initiation to completion.
Security
Security
The security section defines who can see entities of this type.
Control processes
Control processes
This section defines the control processes that the entity will use.
The control processes include the full RAIDDA (Risks, Actions, Issues, Decisions, Dependencies, Assumptions) log plus 'Lessons Learned'.
For each one of these to be enabled, select the form from the list. The form, known in the platform as a process template includes a governance workflow which dictates how the control is managed from start to finish and may include assignment and approval steps. The PPMAnywhere solution comes with a set of pre-defined templates for each of the controls but these can be customised or new ones configured to suit the entity type.
Impact of making changes
Impact of making changes
Changes can be made to an entity type even after entities have been created of that type. The following table defines the potential impact of changing.
Google Sites
Report abuse