Jump to content


Popular Content

Showing content with the highest reputation on 10/10/2019 in all areas

  1. Version 1.0.0


    FileMaker® Server 16, introduced in April of 2017, brought with it the capability to use three oAuth2 Identity Providers to authenticate Identity Assertions made in attempts to access hosted FileMaker® Pro files. Google, Amazon, and Microsoft® Azure AD were the three Identity Providers. Since then various members of the developer community have sought ways to expand beyond those three providers to employ other Identity as a Service (IDaaS) options. Wim Decorte and I are pleased to advise that we have succeeded in an effort to expand the available Identity Provider services to additional systems. We have documented the underlying mechanism that FileMaker Server uses and have identified at least five new major IDaaS providers whose oAuth2 capabilities we can leverage to permit their use in the FileMaker Platform environment. We hope this means, among other items, that the FileMaker Platform can now be used at locations where heretofore it was disqualified due to lack of support of these Authentication options. We were aided in this endeavor to a substantial degree by assistance from Claris International, Inc. (formerly FileMaker, Inc.) working in a customer environment. This ratifies to a substantial degree the maxim postulated by well-known business author Tom Peters back in the 1970’s that “Innovation doesn’t come from the R&D Department; it comes from the customer base.”
    1 point
  2. I am a minimalist and I don't believe in piling up code just because someone reported problems using code they did not understand. This is especially true when answering questions here on the forum: I expect the reader to understand the answer, not to copy/paste it blindly into their solution. Therefore I concentrate on the problem at hand and leave additional potential issues to side notes, if at all. Speaking of understanding: if you think that both lists must be unique, then you too don't understand how this works.
    1 point
  3. Here is a short tutorial how to send Telegram message from FileMaker 16 (previous version needs to set target as field): 1. Find @BotFather from telegram 2. Send message: /newbot 1. Answer to questions (Bot name, bot username) 2. Get token (12345:AAFzdx1231sfasfddafskv_KBkARu5UdsdsfHM) 3. Find newly created bot and start conversation (/start) 4. Create a FileMaker script 1. Set variable ($cmd; "getUpdates") 2. Insert From Url 1. With dialog: off 2. Specify target as variable: $$response 3. Specify URL: "httpspost://api.telegram.org/bot12345:AAFzdx1231sfasfddafskv_KBkARu5UdsdsfHM/" & $cmd 5. Run the script and look for the $$response variable on data viewer 6. Get "id" of your user (1234567) 7. Edit the script to have variables: 1. $who; "1234567" (id of the user) 2. $text; "Hello, this was sent from FileMaker" 3. $cmd; "sendMessage?chat_id=" & $who & "&text=" & $text 8. Run the script again with new command and telegram message will be sent to you
    1 point
This leaderboard is set to Los Angeles/GMT-07:00
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.