\\nTo add logs messages to a particular flow/sub-flow, specify the flow name (the specification could closely match the name) and\\na description of where to add the log message, what it should contain and what should be the log level e.g. the following command\\nwould add a debug log message to log the contents of placed orders in the process-orders-flow when the placed orders variable is set\\n
\\n\\n```example\\nAdd debug logs in the process orders flow to log if an order is placed or a canceled order.\\nPrint the value of variables in such cases.\\n```\\n\\n\\nTo add new error codes to an error handler, specify the error handler and the error codes with a short description of those error\\ncodes e.g. the following command adds the http error codes 403 and 408 to the global error handler\\n
\\n\\n```example\\nAdd 403, 408 http error codes to the error handler\\n```\\n\\n\\nTo rename a particular flow(or any other entity), specify the existing name of the flow(or entity) and the new name e.g. the\\nfollowing command changes the renames the order-publish-flow to publish-order-flow\\n
\\n\\n```example\\nRename the order-publish-flow to publish-order-flow\\n```\\n\\n\\nTo rename a particular field in DataWeave, specify enough information to idenitfy the field and what the new name of the field\\nshould be e.g. the following command renames the `email` field in `member-enrollment.dwl` DataWeave file to `email_address`\\n
\\n\\n```example\\nRename \\\"email\\\" field in member-enrollment.dwl to \\\"email_address\\\"\\n```\\n\\n\\nTo change the transformation logic of a particular field, specify enough information to identify the field and also specify\\nthe logic e.g. the following example changes the logic for populating the `enrollmentChannel` field in `member-enrollment.dwl`\\n
\\n\\n```example\\nIn the member-enrollment.dwl file change the logic of enrollmentChannel to be\\n\\\"Pos\\\" if membership number starts with 100 and \\\"Ecom\\\" otherwise.\\n```\\n\\n\\nTo update connectors, specify a small phrase to identify the connector (this could be the exact connector name or a phrase that\\nmatches the connector name) and specify the version number that you want to update the connector to. The version number should\\nhave a major, minor and patch component e.g. the following command would update the mule http connector to version 1.9.2\\n
\\n\\n```example\\nUpdate the mule http connector to version 1.9.2\\n```\\n\\n\\nTo add a new field/fields to an existing transformation, specify enough information to identify the transformation and specify\\nthe object and the fields to be added. Also specify the logic to populate those field e.g. the following example illustrates\\nhow to add fields to the transformation in `member-enrollment.dwl`\\n
\\n\\n```example\\nAdd the following changes to member-enrollment.dwl.\\n\\n- Add memberAddress object and below fields under it, mapping is specified below.\\n\\n - address1, payload.address1\\n - address2, payload.address2\\n - city, payload.city\\n - state, payload.state\\n - zipCode, payload.zipCode.\\n\\n- Add membershipExpirationDate field and the value should be a date which is two years after the enrollmentDate.\\n```\\n\\n