Standard configuration refers to the settings and configuration found in the solution templates provided by The Anywhere Company. The purpose of this document is to help ensure that further configuration is done so in alignment with the standard configuration. Alignment with standard configuration will have a number of benefits:
Minimise upgrade impact: Alignment with standard configuration will result in lower impact during upgrades.
Standardised reporting: Many standard reports and dashboard expect data in standard columns. Aligning further configuration with standards will increase the likelihood that that configuration still works with the standard reports and dashboards.
Reduced effort: Non-alignment will potentially result in the need for additional reporting configuration requiring additional effort.
Improved integration: Alignment to the standard configuration will help ensure that additional configuration integrates well with standard entities. For example, form copy capability easier to implement and maintain if the storage is aligned.
All new Content Area Definitions created in the system will come with a set of standard settings. These settings are used to determine the visual presentation of the Content Areas based on the definition
Within The Anywhere Platform there are certain tokens that are available throughout the system that can be utilised in order to generate dynamic or contextual data:
Portfolio item controls refers to the following entities:
Risk
Issue
Change Request
Assumptions
Decisions
Actions
Dependencies
Lessons Learned
When configuring these entities, be sure to leave the storage columns as shown in the table below.
When configuring new entities of this type, ensure that these columns are included in the new entity using the storage columns, tokens and validations listed below. If the field is not required on the new entity it is recommended to include it and simply hide it using the status dependencies.
Portfolio entities refers to the following
Portfolio
Programme
Project
Proposal
Service
When configuring these entities, be sure to leave the storage columns as shown in the table below.
When configuring new entities of this type, ensure that these columns are included in the new entity using the storage columns, tokens and validations listed below. If the field is not required on the new entity it is recommended to include it and simply hide it using the status dependencies.