Which of these can be defined using step based fulfillment in Catalog Builder? Choose 2 answers

The correct answer is B. Subflow triggers D. Tasks. Step-based fulfillment in ServiceNow's Catalog Builder allows catalog administrators to define the fulfillment process as a series of discrete steps directly within the builder interface without writing Flow Designer flows from scratch. The two supported step types are: (1) Tasks

Service Catalog and Request Management

Question

Options

AApprovals
BSubflow triggers
CNotifications
DTasks
EPayment processing

How the community answered

(20 responses)

B
85% (17)
C
10% (2)
E
5% (1)

Explanation

Step-based fulfillment in ServiceNow's Catalog Builder allows catalog administrators to define the fulfillment process as a series of discrete steps directly within the builder interface without writing Flow Designer flows from scratch. The two supported step types are: (1) Tasks - individual work items assigned to fulfillment groups or individuals; and (2) Subflow triggers - which invoke pre-built subflows to handle automation or complex logic. Approvals are handled separately through the Approval engine and are not defined as steps in step-based fulfillment. Notifications and Payment processing are not step types available in this fulfillment model.

Topics

#Service Catalog#Catalog Builder#Fulfillment workflow#ServiceNow configuration

Community Discussion

No community discussion yet for this question.

Full CIS-ITSM Practice