A developer was reviewing an Orchestration process whose "main" attribute is set to Main.xaml in project.json. However, the process is not pausing as intended.
What is a possible cause for this issue?
A developer was reviewing an Orchestration process whose "main" attribute is set to Main.xaml in project.json. However, the process is not pausing as intended.
What is a possible cause for this issue?
The 'Wait for Form Task and Resume' activity is designed to pause the execution of the process until a specified task is completed or resumed. If this activity is called in a workflow other than the Main.xaml, such as GetApproval.xaml, it would not have the intended effect of pausing the entire orchestration process. The main workflow should handle the pausing mechanism to ensure the process halts as expected.
The answer is C. Process created a task in the Orchestrator. In an Orchestration process, if a task is created in Orchestrator using the “Create Form Task” activity but the “Wait for Form Task and Resume” activity is not used, the process will not pause as intended. The “Wait for Form Task and Resume” activity is necessary to pause the process until the task in Orchestrator is completed.
It is B -> "Suspends the execution of the current workflow until a specified Action is completed". https://docs.uipath.com/activities/other/latest/workflow/wait-for-form-task-and-resume
The "Wait for Form Task and Resume" activity is specifically designed to pause the execution of the process until a form task is completed or resumed. If this activity is called in the GetApproval.xaml workflow instead of the Main.xaml workflow, it would not have the intended effect of pausing the entire process.
I think is B