After completing a command in the Program Command shape, what happens to the destination document?

The destination document in a Program Command shape is passed on to the next stage in the process after the command completes. This behavior is integral to how Boomi processes data. Once the command has executed, the output is typically used for further processing or transformation in subsequent steps of the process.

In a typical Boomi process, the flow of documents is designed to continue efficiently and effectively, allowing for seamless transitions between components. Passing the document on after completing the command enables downstream operations to utilize the result of the command execution, which may involve transformed data or some output derived from the executed command. This is crucial for maintaining the overall workflow and ensuring that subsequent operations have access to the relevant data they need to function properly.

The other options imply outcomes that do not align with the typical behavior of the Program Command shape in Boomi. The deletion of the document, reverting to the original input, or triggering error logging does not represent the logical flow of operations within this context. Thus, the correct understanding of the Program Command shape emphasizes that the document continues along the process for further handling.