By design, integrations do not write all of the data returned from a command to the context. This prevents large context size and enables you to store only the most relevant information.
The Extend Context feature enables you to save additional data from the raw response of the command. For example, when a command runs to retrieve events from a SIEM, only some of the event fields are written to context, according to the integration design. With Extend Context, you can save additional fields specific to your use case.
Extend Context can also be used when the same command is run multiple times in the same playbook, but the outputs need to be saved to different context keys. For example, you might want to execute the
!ad-get-user command twice, once to retrieve the user's information and again to retrieve the user's manager’s information. By default an integration command writes the data from the same command to the same context key. By using Extend Context, you can write the command’s response to a custom context key of your choice.