Hello everyone,

We have implemented a unified interface, CreateUpdateTask, which supports both insert and update operations. In certain scenarios, external systems may still retain old FSM Task IDs. When a task has already been archived, these systems might attempt to perform an update by submitting an XML request containing the archived task_id. The current behavior results in the creation of a new task record with the same task_id. This is undesirable, as the referenced task_id is no longer present in the active (live) schema. The expected behavior in this case is to reject the request and raise an error. Is it possible to enforce this validation strictly through configuration, rather than implementing custom logic? Except for that, the newly created task will not be archived since there is another task with the same keys in the archive tables.