Symptom
Validation rule on value in case description field is triggered a second time after updating with value
Environment
- Product: SAP Service Cloud Version 2
- Customization for SAP Service Cloud
Reproducing the Issue
- Activate the Determination Rule in Case Service - set to raise an error if the Description field is empty.
- Create a case.
- Add mandatory fields.
- Do not add a value to the Description field.
- Save and open (error is raised as expected).
- Add a value to the Description field and Save and open.
- Error is still raised despite value in the field.
Cause
System limitation: the Case Description is modeled as a Note entity association in Service Cloud Version 2. This architecture prevents the expression-based onPostHook validation from recognizing the in-transaction update to Description, so the validation error persists even after a value is entered.
Resolution
- Implement an External Post Hook on sap.crm.service.caseService (POST/create) to validate Description:
- Create an External Hook with type validation on the Case create event.
- In the external service, check description/content; if empty or unknown, return a validation error response to block creation.
- Disable the internal expression-based onPostHook validation rule for Description to avoid duplicate and persistent validation errors.
- For preventing edits after creation, enforce read-only behavior for the Description (Note) via UI/authorization configurations; dynamic properties for the standard Description are not supported.
See Also
refer to: Create External Hooks
Keywords
case description, validation error, caseService_customLogic, external hook, post hook, onPostHook, sap.crm.service.caseService, expression validation, note entity, description mandatory, read-only after creation, thing inspector, dynamic properties , KBA , CEC-CRM-CZM , Customization for SAP Sales/Service Cloud , Problem
SAP Knowledge Base Article - Public