Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

Command prompt commands waiting for response

Question asked by a.fanet on Jul 31, 2018
Latest reply on Jul 31, 2018 by fmpdude

Like • Show 0 Likes0
Comment • 11

I'm looking for some sort of way to execute an external application and wait for the application to return within a script, so that the return can be used as a variable in FIleMaker. I've tried about 5 different third party plugins, all without working, including Monkey Bread, 24U's toolbox, and BaseElements without any sort of success. Anybody here have functionality that does this for a windows system? Most of these are for things such as File Open and Save dialogs and other external tools that we use that require a returned value before FileMaker's script continues.

No one else has this question

Outcomes

11 Replies

Jens Teich Jul 31, 2018 8:08 AM
Mark Correct
Correct Answer
Have a look at SendEvent:

FileMaker Pro 16 Help
Like • Show 0 Likes0
Actions
a.fanet Jul 31, 2018 8:13 AM
Mark Correct
Correct Answer
I've tried this before as well, and I'm not sure how to get the applications return value
Like • Show 0 Likes0
Actions
a.fanet Jul 31, 2018 8:25 AM
Mark Correct
Correct Answer
Nor does it wait for the event to be finished
Like • Show 0 Likes0
Actions
Jens Teich @ a.fanet on Jul 31, 2018 8:53 AM
Mark Correct
Correct Answer
Yes that is indeed missing. Consider making a Feature Request at Product Ideas
Like • Show 0 Likes0
Actions
wimdecorte Jul 31, 2018 8:55 AM
Mark Correct
Correct Answer
Those plugins should work for what you have in mind, what is not working? Can you provide some more detail?
Like • Show 1 Like1
Actions
fmpdude Jul 31, 2018 9:01 AM
Mark Correct
Correct Answer
You can also use a micro-service using a Process class. There is an optional "waitfor()" method.

Seriously, not difficult to code.

Look at this relatively simple code (in this case it launches a regular DOS batch file, but the world is your oyster what you can do here):

public static void main(String[] args) throws java.io.IOException, InterruptedException { String path = "C:\\Users\\pathToFile"; Process p = Runtime.getRuntime().exec("cmd /c start /wait " + path + "\\RunFromCode.bat"); System.out.println("Waiting for batch file ..."); p.waitFor(); System.out.println("Batch file done."); }

Once you see how this code like this works (that does what you want, standalone for testing like above), you then just incorporate it into a simple micro-service and call that service from FMP using INSERT FROM URL.

This stuff works!

----

The beauty of a micro-service is that it works anywhere, with any operating system, on any computer, at any location, with virtually unlimited users. All for free. FileMaker or no FileMaker....a micro-service is totally independent so you can use it with any HTTP-enabled application (an application that can issue HTTP verbs like GET, POST, etc. Terminal, Browser? No problem.). What's not to love?! You Control The Code! (not some third party).

----------

Check out my two micro-service tutorials in the App Innovations Area:

Create Micro-Services Using Java and the Spark Java Framework
https://community.filemaker.com/docs/DOC-8871

The Simplest Micro-Service! (Python and Flask)
https://community.filemaker.com/docs/DOC-8852
Like • Show 0 Likes0
Actions
a.fanet Jul 31, 2018 9:15 AM
Mark Correct
Correct Answer
wimdecorte
Certainly.

We are moving our upgrading our solution from FileMaker 11 to FileMaker 17, while also converting from a 32bit to 64bit solution. Because of this, we have to modify our plugins. I've managed to replace our original External Shell plugin (with BaseElements ExecuteSystemCommand function), but we have a RunApp plugin which does what I am talking about here. This was a custom template developed using 24U's Custom Plugin template for 32 bit plugins (unavailable for 64 bit plugin creation).

The closest I've gotten is using MonkeyBread, creating a scripting structure like the one here below
Set Variable [$shell; Value: MBS( "Shell.New" )]
Set Variable [$run; Value: MBS( "Shell.Execute"; $shell; command )]
Loop
Pause/Resume Script [1 second]
Exit Loop If [ MBS( "Shell.IsRunning"; $shell ) <> 1 ]
End Loop
Set Variable [$output; Value: MBS( "Shell.ReadOutputText"; $shell; "UTF8" )]

When initially testing on FileMaker 11, it worked perfectly. That changed however when migrating to 17 as the Pause/Resume script step would move the tooltip from the called external application back to FileMaker, which would cause clients typing into or using the external application to re activate the applications window. We develop FileMaker as a data management tool to clients and new this would cause issues for our users.

ToolBox DoSystemScript and BaseElements ExecuteSystemCommand (with a timeout parameter of -1) would cause our solutions to crash.

fmpdude
Could you provide more details of what you're talking about here. We have the code for our original custom plugin so I'd like to figure out a way to do what you've said as it seems like it would be a quick and easy conversion.

I've looked a little at 360 works Script Master Run Shell Script Command as well and it seems like there has some intended functionality as well with a waitForOutput input variable. Does anyone have any experience using this function?
Like • Show 0 Likes0
Actions
fmpdude @ a.fanet on Jul 31, 2018 9:20 AM
Mark Correct
Correct Answer
Sure. This technique is simply running a tiny bit of Java code that does what you want from a small micro-service. The micro-service is just a REST wrapper around the Java code so you can call it using HTTP verbs like GET, and POST (from any application, including FMP).

IMHO, using Java in any FMP-ONLY plug-in (that is, NOT in a micro-service) is like having a Ferrari and only driving it in a small parking lot.
Like • Show 0 Likes0
Actions
wimdecorte @ a.fanet on Jul 31, 2018 9:22 AM
Mark Correct
Correct Answer
Does the BaseElements plugin option to wait for the result not work correctly then for you?

The other thing to consider is that you don't have to have FM wait in a loop, you can have your external app/script call back to FM in a number of different ways.
- you can use the FMP ActiveX control to run a script when the external app is done
- same with a URL call using the fmp:// protocol handler
- or just plain bypass the local client and have your external app write directly to FMS through any of the FMS APIs (XML, Data API,...).
2 people found this helpful
Like • Show 0 Likes0
Actions
a.fanet Jul 31, 2018 10:28 AM
Mark Correct
Correct Answer
fmpdude

When you mention using Java in a FMP-Only plug-in, what exactly are you meaning, because we're not really trying to use it outside of FMP anyway, and if there's a simple way to create a plug-in using Java code, we would certainly prefer that and just convert our C++ code used from our FileMaker 11 32 bit plug-in template
Like • Show 0 Likes0
Actions
fmpdude @ a.fanet on Jul 31, 2018 10:35 AM
Mark Correct
Correct Answer
I think 360 Works is an example of Java in an FMP-Only plug-in but I've never used it (nor would I).

The point really, to me, isn't that you'd use the Java code outside of FileMaker, though you certainly could. It's really that you can more easily abstract the call to the code -- usually only one line of code from FMP -- and the other reasons I listed above. But, having said that, it's funny how often some code one never thinks could be useful outside environment "A" (for example, FMP) becomes wanted in environment "B". Or, leaving environment A for environment B or C, etc. By using a micro-service you future-proof yourself.

Again, all for free.

INSERT FROM URL introduced in FMP 12.

But, I'm just making suggestions .... it's totally up to you how you proceed.
Like • Show 0 Likes0
Actions

Command prompt commands waiting for response

Outcomes

Related Content

Recommended Content