Is there any way to perform "save as PDF" Script Stap over the WebDirect ?
I know , Web Direct is not supporing this directly but would it be possible if I use "Perform Script on Server" ar anything else.
Please Help !!
You could Perform script on server and save to the server's Temp or Documents path and have the server side script send an email with it attached. Would that solve your problem? There are other things out there you can do with server plugins such as FTP the file somewhere.
You pretty much answered your question.
Use "perform script on server" to generate a PDF and import it to a container field that can be accessed on webdirect.
Set Variable - $path - Get(TemporaryPath) & "pdfname.pdf"
Save Records as PDF - $path
Insert File - table::container - $path
I am completely new/inexperienced with respect to a lot of the great stuff that got added to our toolkit with v.13. A good example of this is PSOS.
I am hoping you could please help me understand something that confuses me in your post.
My impression is that PSOS runs with the characteristics of a FMS scheduled script and therefore has the following considerations:
- The script is unaware of the client's current context
- The script can only perform script steps which have "Server" compatibility
If the above is true, then wouldn't the Save Records as PDF step be unavailable in the OP's scenario?
If, on the other hand, the Save Records as PDF script step is available, then this is really cool and I guess I am misunderstanding some part of how this works. Since I don't have any real world experience with PSOS yet, I figured I should ask and see what the scoop is. If I'm not getting it, I'd like to know better.
Any help would be appreciated.
Thanks & best!
Save Records as PDF is NOT supported on PSOS.
There are options to get round this by creating PDF files from scratch using ScriptMaster and iText (which requires some learning but absolutely works) and probably the MBS plugin.
I am speaking about this method at the Montreal CQDF in about a month.
ah yes, in my pre-coffee morning posting I completely forgot about that aspect. Of course most/all server steps that are not supported as scheduled script steps are also not supported via PSOS.
Another alternative would be to have webdirect call a robot computer to run it within a specific context to bypass the server limitation. IE http://www.360works.com/remotescripter/ - shows a video using the same technique to bypass the same limitation in IWP.
I tried to run "Save as PDF" script and save generated PDF in a container. Then Export container. But "Save as PDF" is not working in server side script too.
I tried to do same but it is not working.
As was noted below, it's not supported as part of "perform script on server"
Hello, - This discussion happen in long back and we might have some better solution now I think. Do you have something to suggest other than remotescripter. - Thank you
Have you ever found a workaround for this?
Maybe you check the Catalog example coming with MBS Plugin.
I made it for a client which creates product catalogs on FileMaker server using our DynaPDF functions.
You can use a 'robot' to generate the PDF for you. The robot can be triggered via the Web Direct session and can trigger back the WebDirect session once the PDF is complete using 'Perform Script On Client' (PSOC). We have a working example on Modular FileMaker and a Blog Article on our website explaining the technique.
Hope this helps,
Joris Aarts — ClickWorks
I'm stumped about how this can work if Server can't make a PDF, so I wonder what you think of this idea (for a Mac, not Windows Server).
Allow the Web Direct user to execute a script that saves a Snapshot Link and stores it in a designated folder on the Desktop of the Server. Then a Folder Action created in Automator would open and print any item that lands in that folder, using a FileMaker Pro client to open the FMPSL file and then Print.
Am I dreaming of the impossible?
You are certainly not dreaming of the impossible. It is even much easier: you don't need snapshot links nor automator. Just only need a FileMaker 'robot' client connected to the server and some native FileMaker scripting. See the examples mentioned below.
Retrieving data ...