Question 790
A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. Verify prerequisites with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.
Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. The appropriate response is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.
Incorrect Answers
Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience. This step may apply to Core platform lists versus forms and workspaces but is not one of the complementary requirements in this case. The intended pair is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Together with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.
Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. This step may apply to Instance properties and scoped configuration control but is not one of the complementary requirements in this case. The intended pair is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Together with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.
A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. This step may apply to Record producer versus catalog item selection but is not one of the complementary requirements in this case. The intended pair is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Together with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.


