Nice use of CustFunc with AppleScript, Benjamin! Would that we had the ability to do more with the OS (every flavor) from FM that's x-plat...
-- sent from myPhone --
thanks. I have it fixed.
no clou how this could have happened.
btw, we missed you @ FMK2014
Thanks. Could not attend because of
- new job, not to do much with FileMaker
- other meetings in this week
You can do the same directly with MBS Plugin:
and for iOS you would need to have a php script which you can trigger it from FileMaker with plugin or insert url script step.
As I mentioned, the Mac OS can be handled with a simple AppleScript. No PlugIn needed. It's simply 1 Script step with my cf used.
Since Plug's don't work on iOS, even yours MBS-Plug couldn't help!
I'm confident that this can be solved by a [openURL] task with a dedicated fmp URL to adress the iOS Notifications Center as similary as we already do to prompt phone to dial or to trigger other iApp's.
Unfortunately there is no protocol on iOS to do what you want. It typically requires setting up a notification server that's registered with Apple.
To work around this, you will need to call another app on the iOS device to generate the notification, or you could use something like the Pushover app (what I use). Pushover creates a special email address for that device. To send a notification, have FileMaker send an email to that address (and more for other devices if need be). I use this to notify me of any errors on a production system. It really works for any system that can send emails so it's not FileMaker specific.
If someone is interested in more options like a script triggered when notification is shown or clicked on, they should check the plugin. The AppleScript is for a few simply options only.
For iOS, I just saw that FileMaker would have to enable push notifications for it's device and find a way for us to get to the device token. Than we could use that token to send push notifications to FileMaker Go.
thanks a lot. This looks really promising. I've already downloaded all the ressources and will start analysis. Not sure yet if this works client-side OR sending message via a workflowdata's server.
I'll keep you updated about progresses. Don from FileMakerProGuru's is already expecting me to solve this challenge and to deliver a example-file :-)
Hello, I'm the developer of AlertFlag.
AlertFlag works exclusively client side. In iOS there are effectively 3 notifcation engines:
1) Scheduled local notifications - Requires no notification server or token, but the exact time the notification should fire needs to be known when the notification is scheduled.
2) Significant location change - These are geofence-style notifications
3) Push notifications - These require a server, network access, application tokens, etc.
--AlertFlag uses the first variant.
--I've considered adding support for the second variant. It wouldn't be catastrophically difficult, but there just wasn't enough interest.
--You could theoretically do the third, but I don't know if you could ever get it approved. You'd have to be braver than I am to write the code and set up the server and *hope* you could get it through the approval process.
I suppose that technically your AppleScript demo introduces a fourth:
4) Display a notification right now.
2 things about the AppleScript approach.
a) That command appears to have been introduced in 10.9. My guess is it won't work at all in 10.8, though I'm willing to be proven wrong
b) That command allows you to raise a notification, but clicking on the notification just activates FileMaker. It doesn't pass any information to FileMaker. If, for example, you raised 2 notifications, clicking on one would not inform FileMaker about *which* you'd clicked on.
Great you joined in
Is there any insights you can share about AlertFlag, which serves as a middleware between FMGo AND iOS Notification Center?
- how is communications between AlertFlag AND iOS Notification Center built up?
- what programming language and expressions is used to adress Notification Center?
I still live in hope that Notification Center can be prompted by a OpenURL Scripttask in FM. That's the way we deal with other iApps which serve as middleware for dealing with credit card readers for example. This trick allows to handover parameters forth and back.
Just curious ...
When is Notification Center best used, e.g. for errors, warnings, reminders ?
Can you give an example ?
> I wrote a routine to push messages by FMP to the Apple Notification Center
this is among concideration that should be taken verry carefully.
My concideration is that a message should be of great priority, maybe exceeding usual funtions of your FM-Solution to stress the Notifications Center which lays outside of FMP.
General Error and Warning messages regarding GUI and user interaction should stay inside FMP.
In my case, it's just a warning when subscription plan ends. (My product-case: a annual fee which ends after 12 month)