Which IRL function needs to be manually migrated to ARL?

Question

Options

• Areset ()
• BgetCurrrentTask ()
• CsetMainTask(String)
• DTasklnstance.getTask ()

• A
  3% (1)
• C
  6% (2)
• D
  92% (33)

Explanation

TaskInstance.getTask() requires manual migration because it is an instance-level method accessed through a TaskInstance object - this compound call pattern has no direct automatic equivalent in ARL and must be explicitly rewritten by the developer to match ARL's task retrieval model.

reset() (A) is wrong because it is a lifecycle utility method with a straightforward automatic counterpart in ARL. getCurrentTask() (B) is wrong because ARL provides a direct equivalent function, making migration automatic. setMainTask(String) (C) is wrong because it is a standard setter whose signature maps cleanly to an ARL equivalent without manual intervention.

Memory tip: Think of the dot - TaskInstance.getTask() is the only choice using object-dot-method notation, signaling that it depends on an intermediate object (TaskInstance) that doesn't exist in ARL's API surface, which is exactly why it can't be auto-migrated.

No community discussion yet for this question.