Steve-Evangelista
I may be misreading/misunderstanding the capsParams.js file, so take these with a grain of salt ;) 1. If the "optional" var contains the parameters that should be available on every CAPS operation, then I'd recommend these four changes... a. Drop "TransformType"; this was deprecated prior to the first CAPS RTM release b. Add "DatesInUtc" - this is actually supported on any & every operation. You can use all the CW date variables on every operation (including in your XSL) and so, by extension, you can use "DatesInUtc" on every operation. Example: http://2010test.corasworks.net/sites/caps/_layouts/CorasWorksApps/CorasWorksApplicationService.ashx?RequestType=GetVersion&XsltLocation=%SiteURL%/Resources/CAPSVariables.xslt&DatesInUtc=true c. Add "ContentDisposition" - this allows you to set the ContentDisposition response header on any & every operation (used to trigger a file download response by a browser when using XSL to generate a document) d. Add "RedirectURL" - this is an optional parameter available on any & every operation when you want to redirect a CAPS response to something other than CAPS (i.e. a custom web service, some other API, etc). 2. The "checkVariables" operation lists "DatesInUtc" as required but that's not the case; it's optional (though this would be superseded by 1.b. above, if I'm correct on what the "optional" var is for) 3. Add an optional "ListType" parameter to ProcessBatchData - this is used to support Insert/Update/Delete capabilities against External Lists/ECTs. Hope these help :)