Updating Activity Assigned to a Non-Working Resource

Before 4.1.6 if an existing activity was assigned to a resource with non-working calendar or inactive resource or had to be moved to such a resource with the update, upon an update such activity was canceled with the 'Queue is invalid' error message.

Since ETAdirect 4.1.6, such activity will be updated as requested, but it will be moved or canceled:

IF: 'update_activity' command is performed for an existing activity

AND activity is currently assigned to inactive route (non-working day, inactive resource, etc.)

AND command does not have to move/reschedule activity ('external_id'/date not specified or are the same as existing)

THEN:

IF the fallback/default pool is specified

activity is updated, and moved to fallback/ default pool for that date

ELSE activity is updated, but not moved/rescheduled and not canceled

IF: 'update_activity' command is performed for an existing activity

AND command is to move activity to inactive route (non-working day, inactive resource, etc.)

THEN:

IF the fallback/default pool is specified

activity is updated, and moved to fallback/ default pool for that date

ELSE activity is updated, but not moved/rescheduled and not canceled