IOS-158 practice question 5 of 10

A manager receives an alert informing them that the quantity of an item shipped to a customer is less than the quantity the customer ordered. What happens when the manager clicks the “Resolved” button on the alert?

Full set: 41 questions
Answer options
A: The alert returns to the beginning and notifies the next manager in the task
B: The alert continues to process the ION Script or Mapper
C: The alert is resolved and no further processing occurs unless a workflow is attached to the alert Correct answer
D: The alert is resolved and no further processing occurs
Correct Answer:
C. The alert is resolved and no further processing occurs unless a workflow is attached to the alert
Explanation

When a user clicks "Resolved" on an alert, the status of that specific alert instance is updated to "Resolved," and its lifecycle is considered complete. However, this action serves as an event within the Infor OS platform. If the alert was generated as a user task within an ION Workflow, the workflow engine is notified of the "Resolved" outcome. The workflow will then proceed to the next activity connected to this specific outcome. If no subsequent activity is defined, the process branch terminates. Therefore, further processing only occurs if a workflow is configured to act upon the resolution event.

Why Incorrect

A. The alert returns to the beginning and notifies the next manager in the task This describes a rejection or escalation path within a workflow, not a resolution, which signifies successful completion of the task.
B. The alert continues to process the ION Script or Mapper The ION Script or Mapper is typically used to generate the alert based on a business event, not to process it after a user resolves it.
D. The alert is resolved and no further processing occurs This is only true for a standalone alert not governed by a workflow. It is an incomplete statement as it ignores the primary capability of ION Workflows to orchestrate processes based on user actions.

References

1. Infor ION Desk User Guide for Infor OS. In the "Workflow modeling" chapter, the "User Task" activity is described. A User Task can have multiple custom outcomes (e.g., 'Resolved'). The workflow diagram explicitly defines what happens after each outcome. If the 'Resolved' outcome is connected to another activity, the process continues; if it is connected to an 'End' event, it stops. This confirms that further processing is conditional on the workflow design. (Reference concept: User Task outcomes in workflow definitions).

2. Infor OS Administration Guide. The "Task Management" section details the lifecycle of tasks and alerts. It explains that user actions update the task status, and these status changes are events that the ION workflow engine can use to advance a business process. This supports the principle that resolving a task can trigger subsequent automated steps if a workflow is attached. (Reference concept: Task Lifecycle and Status Events).

3. Principles of Business Process Management (BPM). Academic literature on BPM, often covered in university information systems courses, establishes that a human task step within a process model has defined outcomes. The completion of the task triggers a transition in the process model based on the specific outcome chosen by the user, which aligns directly with the behavior described in option C. (e.g., as taught in courses like MIT's 15.564 Information Technology and Business Processes).

Scroll to Top