What configuration should be applied for attended DU framework automations?

For attended Document Understanding (DU) framework automations, the choice to turn off Persistence Support and Background Running is appropriate for several reasons.

Attended automation typically requires close interaction between the user and the automation process. By turning off Persistence Support, the process ensures that it does not attempt to maintain state information or resume execution in scenarios where the user is not actively engaged. This setting reinforces the direct and immediate interaction model that attended automations are designed for.

Likewise, disabling Background Running aligns with the attended nature of the automation, where user involvement is necessary at each step. When Background Running is not enabled, the automation will run in the foreground, allowing the user to see actions as they occur and intervene if necessary, which is a crucial aspect of attended automations.

In summary, the focus of attended automations is on real-time user interaction, so having configurations that support user visibility and control, rather than allowing the automation to operate unnoticed in the background or to persist between runs without user engagement, is essential to ensure the automation is effective and user-friendly.