IDENTITYIQ-ENGINEER practice question 21 of 25

Is the following statement about workflow step types and their usage true? Solution: When a wait step is encountered in a foreground workflow, the user will notice this, because the screen will freeze for the specified number of seconds.

Full set: 121 questions

Domain Troubleshooting

Answer options
A: Yes Correct answer
B: No
Correct Answer:
A. Yes
Explanation

The statement is true. A foreground workflow is an interactive, synchronous process where the user interface (UI) waits for the workflow to complete before rendering the next page or providing a result. A "Wait" step is designed to pause the server-side execution of the workflow. When a wait step is used within a foreground workflow, it halts the process that the UI is waiting on. This directly results in the user's screen appearing unresponsive or "frozen" in a loading state for the duration specified in the wait step, leading to a poor user experience and potential for HTTP timeouts.

Why Incorrect

B. No: This is incorrect. A wait step in a synchronous, foreground process will block the execution thread, causing the user interface to wait and appear frozen until the step completes.

References

1. SailPoint IdentityIQ 8.1, Business Process and Workflow: In the chapter on "Workflow," the distinction between interactive (foreground) and non-interactive (background) processes is fundamental. The documentation emphasizes that interactive processes, which are tied to a user's session, should be designed for rapid completion to avoid negative user experience. The guide states, "Interactive business processes are those that are launched from the user interface and for which the user is waiting for a response... These processes should be designed to complete as quickly as possible." This principle confirms that any delay, such as a wait step, will directly impact the waiting user.

2. SailPoint IdentityIQ 8.1, Business Process and Workflow: The "Workflow Steps" section describes the Wait step's function as pausing the workflow's execution. It notes, "The Wait step is used to pause a workflow for a specified period of time or until a specific event occurs." When this pausing action is applied to an interactive process that the UI is dependent upon, the UI must also wait, confirming the statement's accuracy.

Scroll to Top