Seems a benefit of stored processes is that a single stored process could be invoked by lots of different applications (web report studio, stored process web app, EG, office-add on, information delivery portal, blah blah). Sometimes the code executed should vary, depending on which application invoked the process.  For example, a stored process might give user option of using a prompt to set _odsdest= html | rtf | pdf.  If that stored process is invoked from SPWA, all should be fine.  But if it is invoked from office-add on and user selects PDF, the stored process should force the destination to be rtf or html, because Excel knows not of pdf.  Or maybe I am coding a javascript alert, which I guess would only work when the process is called from SPWA or IDP. Is there a macro variable (or other environment variable) that can reliably indicate what sort of app invoked the stored process?  So I would use it the same way as in vanilla SAS, I use &SYSENV to determine if code is being run in interactive mode or batch? Thanks, --Q. ... View more

Hi, As I understand it, when Web Report Studio (WRS) invokes a stored process, the only output format it can receive from the stored process is the SASREPORT (xml) format. Is that correct?  And also, it looks like WRS can only receive PACKAGE results, not streaming results? The implication of this is that if I have a stored procedure, and want the user to be able to specify _ODSDEST= pdf | rtf | html, the user CANNOT use WRS to invoke the stored procedure, because WRS is only happy receiving _ODSDEST=SASREPORT. Correct? So basically, WRS can receive (and create, and store, and edit) reports in this SASREPORT (xml) format.  And that is really the only file format "supported" by WRS.  (with I guess exception that if you register a pdf, looks like its possible for WRS to display it, and could create a pdf through "print" command). Thanks, --Q. ... View more

Hi All, I'm new to stored processes, and have just "finished" my first stored process.  It allows a user to pass a few parameters, and makes a little report. I have been running it through the Stored Process Web App.  And was thinking I would basically send the URL around to users, and they could do the same. Then it was suggested that I create a report in Web Report Studio which will be a shell for the stored process, and have users go through web report studio to run the report. Was wondering if people have thoughts as to benefits of using WRS to package a stored process? As I understand it, the main functionality of WRS is to allow less-technical people to *build* reports.  In this case, I don't expect anyone to want to build a custom report incorporating the output of this procedure as a sub-report.  So I don't yet see much benefit to packaging it as a web report.  Except it sounds like maybe I can do some more formatting of the WRS pages, and I guess if we have a whole library of reports the WRS might provide an organization scheme (but the indexing provided by the stored process server seems plenty useful for that). Thanks for any thoughts, --Q. ... View more