Project Pipeline Custom Property Mapping Guide

When a pipeline task moves into a stage configured to create a project, Fluid automatically builds the new project by copying details from the source action.
This guide explains how the system maps action custom properties to project fields — and how to ensure your pipeline boards are configured for accurate and consistent data transfer.

Overview of the Project Creation Flow

Feature Availability – Project creation through the pipeline is only available when the Show Project Pipeline feature flag is enabled, and the user has Editor-level access on the action’s board.
Creating the Project Template – When a pipeline task triggers project creation, Fluid converts the action into a project setup model using
Copying Custom Properties – Fluid copies custom properties in two passes:
- Mapped fields: Known properties (e.g. dates, methodology, owners) are promoted to project fields.
- All other properties: Ensures any remaining action properties are also transferred, so no data is lost.
Final Project Creation – The project is created and saved in the system. A reference link between the source action and the new project is recorded in Action.PipelineGuid.

How Custom Properties Are Mapped

Fluid automatically recognises and promotes certain custom properties to first-class project fields. These are detected by key name or display label (not case-sensitive).

Below are the mappings currently supported.

Date Properties

Action Property	Project Field	Notes
`Implementation Date`	`Implementation Date`	Converted from timestamp to a readable date.
`Start Date`, `End Date`	`StartDate`, `End Date`	If one is missing, default rules (below) apply.

Date Defaults:

No start or end date → start = today, end = blank
End date only (future) → start = today
End date only (past) → start = end
Start date only → end left blank
End before start → end left blank

Number Properties

Action Property	Project Field	Notes
`Amortization Period`	`AmortizationPeriod`	Saved as an integer value.

Yes/No Properties

Action Property	Project Field	Notes
`Cap Eligible`	`CapEligibility`	Applies the Yes/No value.
Confidential	Confidential	Applies the Yes/No value.

Linked Project Lookups

Action Property	Project Field	Notes
`Reporting Program`	`ReportingProgram`	Matches to the referenced project or programme by ID.

Text and Dropdown Properties

Text fields and dropdowns are only transferred if they contain valid or recognised values.

Action Property	Project Field	Lookup Source
`Discretionary`	`Elective`	Matches Fluid’s “Discretionary” configuration.
Tier (custom)	`Tier`	Matches against configured tiers.
`Project Type`	`ProjectType`	Matches Fluid’s configured project types.
`Project Category`	`Category`	Matches configured project categories.
`Funding Source`	`FundingSource`	Matches configured funding sources.
`Methodology`	`Methodology`	Used when no template/methodology ID is already defined.
`Template`	`Project Creation Template`	Requires the Show Project Templates flag.
`Capitalization Profile`	`CapProfile`	Matches the configured capitalisation profiles.
Confidential	IsConfidential	Set with "Yes" or "Confidential" value
`Requirements`	`Requirements`	Appended to the project’s description.
`Description`	`Description`	Merged with the base description.
Cost Centre (custom)	`CostCenter`	Matches configured cost centres.
Proposed Solution	`ProposedSolution`	None
External Reference	`ExternalReference`	None
Secondary Reference	`SecondaryExternalReference`	None
`Portfolio`	`Portfolio`	Matches configured portfolios.
`Sub-Portfolio`	`SubPortfolio`	Matches configured sub-portfolios.
`Business Driver`	`Driver`	Matches configured business drivers.

Person Properties

Person fields are linked using the user ID. When valid, the user is automatically added to the relevant team role in the new project.

Action Property	Project Field	Role Assignment
Owner	`Owners`	Added to the Owners list
Primary PM	`PrimaryPMs`	Added as Primary Project Manager
Editors	`Editors`	Added as Editor
Business Owner	`BusinessOwners`	Added as Business Owner
Executive	`Executives`	Added as Executive Sponsor

Rich Text and Weighted Option Fields

Rich Text – Transfers formatted text (ValueHtml) to preserve layout and styling.
Weighted Options – Removes any numeric prefix (e.g. “10 - High”) and keeps only the label (“High”).

Unmapped Properties

Any custom property not explicitly listed above is still transferred to the new project as a project custom property.
This ensures that even new or customer-specific fields remain available under Prop.<Key> in the project record.

Error Handling

If any property cannot be converted (for example, an invalid user reference), Fluid logs the issue in the job console and system logs.
The remaining properties continue to process — ensuring that one bad value never stops project creation.

Feature Flags to Check

Show Project Pipeline – Enables pipeline-based project creation.
Show Project Templates – Required if you wish to pull template or methodology information from action custom properties.

Best Practice for Administrators

When designing pipeline boards:

Use consistent property names across actions and projects.
Ensure dropdown lists match configured project catalogues (e.g. types, portfolios).
Enable both Show Project Pipeline and Show Project Templates features.
Regularly review your mappings to align with new configurations or naming conventions.

By following these guidelines, your pipelines will create projects seamlessly — with accurate data mapping and complete traceability from the original action.