The RIDAC workflow can be modified by using which recommended feature?

The out-of-the-box (OOTB) processes for RIDAC items (Risks, Issues, Decisions, Actions, and Changes) within ServiceNow Strategic Portfolio Management are implemented as classic workflows. The standard and recommended tool for modifying these existing, state-based processes is the Workflow Editor. It provides a graphical canvas to configure the activities, transitions, and conditions that govern the lifecycle of RIDAC records. While Flow Designer is the modern tool for automation, the legacy RIDAC processes are maintained through the Workflow Editor.

B. Project Form: The form is a user interface for viewing and editing data on a specific record; it does not control the underlying process logic or state model.

C. Flow Designer: While a powerful automation tool, the standard OOTB RIDAC processes are not built with Flow Designer; they use the classic Workflow Editor for process management.

D. Service Catalog: The Service Catalog is an application for ordering products and services. It is unrelated to configuring the backend workflows for project management records.

1. ServiceNow Product Documentation - Workflow Editor: "The Workflow Editor is a graphical user interface for creating, editing, and managing workflows." This documentation establishes the Workflow Editor as the primary tool for managing classic workflows, which are used by the RIDAC processes. (ServiceNow Product Documentation, "Workflow Editor," Quebec release and later).

2. ServiceNow Product Documentation - Project Management: The documentation for managing project artifacts like issues and risks describes their state models (e.g., Open, Work in Progress, Closed). These state models are controlled by underlying business rules and workflows. The documentation implicitly points to the use of classic platform features like Workflow Editor for customization. (ServiceNow Product Documentation, "Manage project issues," Utah release and later).