risk_value on Change Records Not PopulatedIssue The risk_value field on Change Records remains unset after completing the Risk Assessment, even though the risk field is updated based on responses/calculation. This issue can be reproduced by creating a Change Request, completing the Risk Assessment, and observing that the risk_value field remains unset.ReleaseXanadu Patch 7 ResolutionThe field "risk_value" only gets created with the Change Management - Risk Assessment [Legacy] plugin. The instance doesn't have that plugin installed, so the value will not populate. The instance is using a different and newer version of this called Change Management - Risk AssessmentWe've confirmed with the product team that once the Risk Assessment plugin is installed and the legacy assessments are migrated, "risk_value" becomes obsolete.