The following table shows the sequence of precedence for determining which output template is used by an API. (Events use a similar sequence of precedence.) Note that templates are not supported for user exits.
Priority | Output Template Path and File Name |
---|---|
1 | setApiTemplate(file|xmlDocument) to YFSEnvironment When a file is specified, it is picked up from the INSTALL_DIR/extensions/global/template/api directory. |
2 | INSTALL_DIR/extensions/global/template/api/apiName.docType.xml |
3 | INSTALL_DIR/extensions/global/template/api/apiName.docType.xml (Sterling Selling and Fulfillment Foundation sample template; not for use in production.) |
4 | INSTALL_DIR/extensions/global/template/api/apiName.xml |
5 | INSTALL_DIR/extensions/global/template/api/apiName.xml (Sterling Selling and Fulfillment Foundation sample template; not for use in production.) |