Skip to main content

When to use these helpers

These helpers summarize configured inverse relations. An empty or unconfigured relation can yield zero, null, or an empty summary; do not treat that as proof that no work exists.

Calling style

Call a helper as planningOpenRiskCount($inverseRelations). Not every helper is available everywhere: validation, form, and document-template helpers have distinct context contracts. Editor suggestions are not proof that a helper is supported at runtime.

Complete function reference

planningActiveIncidentCount

Counts active incident records. Signature: planningActiveIncidentCount(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningActiveIncidentCount(...).

planningBiaCompletionPercent

Returns business-impact-analysis completeness percentage. Signature: planningBiaCompletionPercent(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningBiaCompletionPercent(...).

planningBlockedDependencyCount

Counts dependencies whose status is blocked or at risk. Signature: planningBlockedDependencyCount(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningBlockedDependencyCount(...).

planningControlCoveragePercent

Returns control-coverage percentage. Signature: planningControlCoveragePercent(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningControlCoveragePercent(...).

planningExercisePassRatePercent

Returns exercise pass-rate percentage. Signature: planningExercisePassRatePercent(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningExercisePassRatePercent(...).

planningOpenFindingCount

Counts planning findings whose status is not closed. Signature: planningOpenFindingCount(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningOpenFindingCount(...).

planningOpenRiskCount

Counts planning risks whose status is not closed. Signature: planningOpenRiskCount(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningOpenRiskCount(...).

planningProcedureReadinessPercent

Returns procedure-readiness percentage. Signature: planningProcedureReadinessPercent(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningProcedureReadinessPercent(...).

planningResourceCapacityUtilizationPercent

Returns effort divided by capacity as a percentage, or null when capacity is unavailable. Signature: planningResourceCapacityUtilizationPercent(inverseRelations, allocationSemantics?) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningResourceCapacityUtilizationPercent(...).

planningResourceCostSummary

Returns a grouped text summary of resource cost amounts by currency. Signature: planningResourceCostSummary(inverseRelations, allocationSemantics?) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningResourceCostSummary(...).

planningResourceEffortHoursSummary

Totals effort hours for matching planning resource allocations. Signature: planningResourceEffortHoursSummary(inverseRelations, allocationSemantics?) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningResourceEffortHoursSummary(...).

planningResourceNumericSummary

Totals a chosen numeric resource field for matching allocations. Signature: planningResourceNumericSummary(inverseRelations, fieldKey, allocationSemantics?) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningResourceNumericSummary(...).

planningResourceQuantitySummary

Returns a grouped text summary of resource quantities by unit or type. Signature: planningResourceQuantitySummary(inverseRelations, allocationSemantics?) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningResourceQuantitySummary(...).

planningResourceVarianceAmount

Returns actual minus planned numeric resource amount. Signature: planningResourceVarianceAmount(inverseRelations, fieldKey, plannedSemantics = "planned", actualSemantics = "actual") Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningResourceVarianceAmount(...).

planningRiskInherentExposureTotal

Totals inherent risk exposure scores. Signature: planningRiskInherentExposureTotal(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningRiskInherentExposureTotal(...).

planningRiskMitigationCoveragePercent

Returns the percentage of risks with a mitigation signal, or null when no risk records exist. Signature: planningRiskMitigationCoveragePercent(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningRiskMitigationCoveragePercent(...).

planningRiskResidualExposureTotal

Totals residual risk exposure scores. Signature: planningRiskResidualExposureTotal(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningRiskResidualExposureTotal(...).

planningScenarioCoveragePercent

Returns scenario-readiness coverage percentage. Signature: planningScenarioCoveragePercent(inverseRelations) Example:
Availability: Configured planning inverse relations only. Empty/unconfigured relations can return zero, null, or an empty summary. Note: It can also be written as a transform when the first value is the input: value | planningScenarioCoveragePercent(...).

Before you publish

  • Start with a known value and confirm the expected result.
  • Handle null, empty text, and empty lists deliberately.
  • Do not place secrets, access tokens, or sensitive personal data in an expression.
  • Read expression contexts and availability before copying an expression between features.
Planning metrics, resources, and resilience helpers in KayanOS