Process classes for <file_order_source> and <file_order_sink> with Agent Cluster failover

Using a process class with multiple agents should be enabled for file order sources on remote JobScheduler Universal Agents.

• If there are multiple agents defined in the process class, the first available agent is used for monitoring or (re-)moving the file
  • If the connection to an Agent from a process class is lost, the next available agent from that process class is used for monitoring.

Users of this feature must ensure that the Universal Agents work on the same resources (mounted file systems...) as a switch of the Agent might occur within the execution of a jobchain (e.g. a file is triggered on agent 1, processed on agent 2 and deleted on agent 3).