Running AppleScript in Bash

osascript -e 'tell application "FileMaker Pro Advanced" activate show window "Trust Reports" do script "Scan Trust Report" end tell'

This should work.

#!/bin/bash
#


function Do_FMP () {
`osascript <<-AppleScript
tell application "FileMaker Pro Advanced"
activate
show window "Trust Reports"
do script "Scan Trust Report"
return quit
AppleScript`
}


fscanx --pdf /scandata/Trust_Report


[[ $? != 0 ]] && say "It did not scan" && exit 1
Do_FMP
exit 0

Works better with an end tell.

#!/bin/bash
#


function Do_FMP () {
`osascript <<-AppleScript
tell application "FileMaker Pro Advanced"
activate
show window "Trust Reports"
do script "Scan Trust Report"
end tell
return quit
AppleScript`
}


fscanx --pdf /scandata/Trust_Report


[[ $? != 0 ]] && say "It did not scan" && exit 1
Do_FMP
exit 0

@VikingOSX

Instead of using command substitution to run your function in a subshell, you could remove the backticks and replace the curly brackets with paratheses. The function will run in a subshell. Like this ->

Do_FMP ()
(
osascript <<-AppleScript
tell application "FileMaker Pro Advanced"
activate
show window "Trust Reports"
do script "Scan Trust Report"
end tell 
return quit
AppleScript
)

Note: I defined the function with POSIX syntax.

Thanks Mark. I have no explanation how it is that I know about the subshell syntax, and consistently do not use it. 😉 Apparently, back-ticks are habit forming.

I do not understand why you want a subshell in the first place.

And backticks (grave accent) are lousy. $(...) is so much better 😝

And when you are ready, we can discuss <(...) as in

while read line

do

...do something with $line

...setting local variables that survive after the while loop

...because the while loop is not running in a subshell 🙂

done < <(command ...)

The <(...) notation with a while loop is better than "command ... | while read line; do ...do stuff...; done", because the while loop is in a subshell and any variables it sets will be lost when the while loop finishes.

But this is all off track, as wee have yet to hear from JFWX5 and if any of the osascript solutions work as desired in JFWX5's environment.

My use of back-ticks is muscle memory from my multi-vendor, UNIX employment, and does not mean that I do not know about (), $(), and < <() usage. I have Bash scripts here that take full advantage of these constructs. Habits are hard to break.