Parse actions added to the API assembly after migration

The migration utility apicm archive:port-to-apigw and apicm archive:port-to-apigw-v10 commands add parse actions to the API assembly depending on the policies specified in your migration configuration.

Review the API assembly to determine if any of the parse actions or other actions added by the migration utility can be removed. For more information, see Fine-tuning APIs after migration.

Parse actions are added to the assembly according to the rules in the following tables.

Table 1. Parse actions added to the API assembly after conversion of policies to 1.0.0 or 2.0.0
Policy	Where the parse action is added
If a `POST`, `PUT`, `DELETE`, `OPTIONS`, or `PATCH` method is found	As the first action in the assembly
invoke 2.0.0	After the invoke action, except when invoke is the last action in the assembly.
json-to-xml 2.0.0	Before the json-to-xml action
proxy 2.0.0	After the proxy action
validate 2.0.0	Before the validate action
xml-to-json 2.0.0	Before the xml-to-json action
xslt 1.0.0 or 2.0.0	Before the xslt action

Table 2. Parse actions added to the API assembly after conversion of invoke and proxy policies to 1.5.0
Policy	Where the parse action is added
invoke 1.5.0	A parse action is added after the invoke if any of the following are true: `stop-on-error` is specified `final-action` is set to `false`. This is the default setting. `x-ibm-gateway-optimize-invoke` is explicitly set to `false` The parse action is added because there can be a subsequent use of the output.
proxy 1.5.0	A parse action is added after the proxy if `final-action` is set to `false`.