CAD DOUBTS

PoojithaVap
Tera Contributor

1. Which of the following is NOT a Flow Designer feature?

A. Run a flow from a Catalog item

B. Call a flow from another flow or subflow

C. Add stages to a flow

D. Test a flow using the “Run as” feature

Is it B OR D?

2. What are the features of Flow Designer?

A. Add stages to a flow
B. Call a flow from another flow or subflow
C. Test a flow using the "Run as" feature
D. Support JavaScript code to test conditions that trigger the flow. E.g., Run a flow from a Catalog item
E. Perform form field data validation at client side

6 REPLIES 6

Hi @Chaitanya ILCR 
Could you please give an example to testify option D. Support JavaScript code to test conditions that trigger the flow. E.g., Run a flow from a Catalog item or any related article?

Thanks & Regards
Mayank

nityabans27
Kilo Patron

Hi @PoojithaVap,

1. Correct Answer: D. Test a flow using the “Run as” feature

Explanation:
Flow Designer does not support a “Run as” feature natively to test flows under different user contexts. You can simulate actions or impersonate a user via Flow logic or ServiceNow impersonation, but there’s no built-in “Run as” option.

  • A is valid – Catalog items can trigger flows.

  • B is valid – Subflows can be called within flows.

  • C is valid – Stages can be added for visualization and tracking.


2. Features of Flow Designer

Correct Options:

  • A. Add stages to a flow 

  • B. Call a flow from another flow or subflow 

  • C. Test a flow using the "Run as" feature  (Not a native feature)

  • D. Support JavaScript code to test conditions that trigger the flow  (Condition builder allows scripted conditions)

  • E. Perform form field data validation at client side (Handled via UI Policies or Client Scripts, not Flow Designer)

Final Answer: A, B, D

If you found my answer helpful, please accept it as a solution and mark it helpful.
Thanks and regards
Nitya Bansal