There is a business rule called "Populate parent field in sc_task table" that sets the value of the "Parent" (parent) field to be the same as the "Request item" (request_item) field if the "Parent" field is empty at the time of update.
We have a use-case where we'd like to use the Parent field to relate Catalog Tasks to another record type, but I don't want to disrupt any processes or functionality that relies on the Parent field being populated with the Catalog Task's parent RITM. I would hope/imagine that any logic or relation between the 2 should go off of the "Request item" field.
Conversely, if a Catalog Task is created independent of a Request Item, then it doesn't have that field populated, and thus the Parent would stay empty, so I don't know if it matters all that much, or if this is just logic that ServiceNow added for the sake of populating the field.
In a nutshell, if I were to deactivate this business rule, would there be any unforeseen consequences that I should be aware of?
