Configured Fields Overview

Creating Configured Fields Video

Configured fields are user-created fields that allow you to define and maintain data specific to your organization. For example, you can track information such as Strategic Importance or Main Stakeholder.

Configured fields are created in the context of an object and can be used in views on pages that support that object. For example, you can create an Activity configured field and use it on the Activities page as a column, grouping band, sorting option, or filter criterion. Configured fields are global, so they can be used across all workspaces, projects, portfolios, programs, and ideas.

Oracle Primavera Cloud fields are categorized by data type, including: boolean, cost, date, integer, list, number, or text. Multi-currency is supported only for data type cost for formula configured fields. For configured fields of data type cost, you can select the Currency tab in  Settings to choose which currency to view cost data. For some types of data, you can define a formula or statement to calculate values for a field. For a configured field of data type cost, the cost formula calculation is performed and saved in base currency then converted to project currency. For configured fields that are data type number and integer, using cost fields as part of formulas will only produce one value. This value is always calculated and displayed in base currency. For more information on creating or using custom formulas, consult the Oracle Primavera Cloud Expression Language Guide on Oracle Help Center.

Configured fields have different character limitations depending on the purpose and type. List configured fields have a character limit of 128. Text configured fields for the following objects have a character limit of 255: programs, ideas, strategy, documents, files, reports, and more. Text configured fields for the following objects have a character limit of 2,000: projects, activities, WBS nodes, tasks, and more.

You cannot delete a configured field if it is used in another configured field, a form, a workflow, or a field mapping.

Documentation on adding a configured field to a specific object can be found under that object.

Restricted Configured Fields

A configured field that is designated as restricted can be viewed by anyone with access to the portfolio, program, or project, but only the users with workspace-level Restricted Configured Fields Edit privilege can edit it. Users with this privilege can restrict any configured field by selecting the Restricted check box when adding or updating a configured field in Summary and Settings for a program, project, or portfolio in a workspace. For example, if a configured field is updated as a result of a workflow decision, you can set the configured field to restricted to prevent users from updating the field. To learn more about permissions, contact your application administrator or see Permission Sets Overview in the Application Administration Guide.