Question 110
A new extension's mandatory rule inadvertently blocks unrelated incident records after being applied to the parent table. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. An inherited field may have per-table overrides; editing the parent entry can affect every child table unexpectedly. Verify prerequisites with: Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. Scenario: A new extension's mandatory rule inadvertently blocks unrelated incident records after being applied to the parent table.
Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. An inherited field may have per-table overrides; editing the parent entry can affect every child table unexpectedly. The appropriate response is: Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. Scenario: A new extension's mandatory rule inadvertently blocks unrelated incident records after being applied to the parent table.
Incorrect Answers
Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. This step may apply to Reference fields and display values in the data dictionary but is not one of the complementary requirements in this case. The intended pair is: Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. Together with: Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. Scenario: A new extension's mandatory rule inadvertently blocks unrelated incident records after being applied to the parent table.
Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table. This step may apply to Table extension and inherited task fields but is not one of the complementary requirements in this case. The intended pair is: Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. Together with: Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. Scenario: A new extension's mandatory rule inadvertently blocks unrelated incident records after being applied to the parent table.
When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values. This step may apply to UI Policy actions for conditional field behavior but is not one of the complementary requirements in this case. The intended pair is: Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. Together with: Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. Scenario: A new extension's mandatory rule inadvertently blocks unrelated incident records after being applied to the parent table.


