I’m working on a Demand configuration in dmn_demand and trying to meet a requirement where the fields approved_start_date and approved_end_date must remain empty in the early lifecycle states (Draft, Submitted, Screening, Qualified). Users should be able to populate them manually later if needed.
I already identified a Business Rule that was copying values from start_date / requested_by into the approved fields and disabled it. However, the issue is still occurring.
From sys_audit I can see that approved_start_date is still being updated multiple times, by different users and at different times, even after disabling that rule. Flow Designer has also been checked and does not appear to be involved.
At this point I’m trying to understand what other mechanisms could still be populating these fields in SPM/Demand. Possible suspects I’m considering:
- Data Policies on dmn_demand
- State model / state transition scripts
- Other out-of-box Business Rules affecting approved dates
- Hidden baseline/planning logic in Demand configuration
Has anyone seen this behaviour before in Demand where approved dates are automatically derived even after disabling the obvious BR? Any pointers on where else ServiceNow might be enforcing or calculating these values would be appreciated.
