Embed Size (px)
Citation preview
#devcon19
An introduction to Claris Connect
Sangita Banerjee, Giuliano Iacobelli
#devcon19
Agenda
Sangita Banerjee, Giuliano Iacobelli
#devcon19
Agenda
Sangita Banerjee, Giuliano Iacobelli
• Recap of Visionary Keynote• Why Claris Connect?• Feature Summary• Flow• Demos• Managing and Running Flows• Roadmap• Q&A
1 Evolve the existing FileMaker Platform with new capabilities & modernize
Invest in new products: Claris Connect and Claris (next-gen)21 Evolve the existing FileMaker Platform
with new capabilities & modernize
Invest in new products: Claris Connect and Claris (next-gen)21 Evolve the existing FileMaker Platform
with new capabilities & modernize
Why Claris Connect?
Growth of SaaS
Growth of SaaS
Build on your own?
✓ Use DAPI✓ Custom coding✓ Host middleware
✓ Authentication✓ Authorization✓ Monitoring✓ Logging✓ Data formats✓ Maintenance✓ Error Handling✓ Rate limiting
#Claris
Claris ConnectIntegration and Orchestration Platform (Launch FY20)
CLOUD
ON PREMISE
#Claris
Claris ConnectIntegration and Orchestration Platform (Launch FY20)
CLOUD
ON PREMISE Agent
Connectors 100+
Sunday
12
Sunday
12
Sunday
12
Sunday
12
Cloud / On-Premises connection Scalable cloud infrastructure
Extend with custom code
Realtime with webhooksConnect any app
Approval Workflows
Features
Versioning Error Handling
Scheduling In Built Utilities
#devcon19
Easy as 1-2-3
Select App
1
Select App
1
Select action
2
Select action
2
Configure action
3
#devcon19
Flows
What is a flow
"When [a new form is submitted on Formstack], then [add a subscriber on Mailchimp]."
Claris ConnectNew submission Add Subscriber
TRIGGER ACTION
Creating a trigger
Claris ConnectNew submission Add Subscriber
TRIGGER ACTION
A Trigger an event which a Flow will be "listening out" for. This means that the flow will react and start when the specified event has occurred.
Trigger
Event driven architectureClaris Connect leverages webhooks to just sit and wait for an HTTP request from the third party service notifying something. Webhooks are a better way to listen for real time events and avoid waste of bandwidth and computing resources.
Client
Server
Client
Server
New data!
Thanks!New data?
No. No. No.
New data? New data?
Creating an action
Claris ConnectNew submission Add Subscriber
TRIGGER ACTION
Actions carry out an operation in your target app, usually a create, update, or search operation. Each action requires a set of input fields and typically returns data.
Actions
Actions carry out an operation in your target app, usually a create, update, or search operation. Each action requires a set of input fields and typically returns data.
Actions
Actions carry out an operation in your target app, usually a create, update, or search operation. Each action requires a set of input fields and typically returns data.
Actions
Step data are output data from a trigger or an action step of a flow.
Data mapping
Step data are output data from a trigger or an action step of a flow.
Data mapping
To successfully act on user’s behalf against a third party service. Claris Connect supports multiple authorization protocols used by cloud services. OAuth 1.0, OAuth 2.0, Basic Auth, Custom Auth.
Connect account
Connecting to FileMaker
Add SubscriberNew Lead Create Record
FileMaker Connector - Trigger
The FileMaker connector will rely Scripts to receive out notifications of record changes. With this, FileMaker solution developer has full control on how, when and with what data a Flow should be triggered on Claris Connect.
The FileMaker connector available on Claris Connect has fully baked FileMaker Data API in it. This allows your Flows to push and pull data of FileMaker solutions and also to run FileMaker Scripts.
FileMaker Connector - Actions
Dynamic fields lookup
Each FileMaker solution has different layouts, and each layout has different fields. FileMaker connector leverages Metadata API to dynamically adapt your connector to your data models.
Dynamic fields lookup
Dynamic fields lookup
Dynamic fields lookup
Dynamic fields lookup
Dynamic fields lookup
FileMaker connector in action
Add SubscriberNew Lead Create Record
#Claris
Conditions
Flows can have multiple paths and this can be achieved with Conditions. An IF-Then block that allows your Flow to do different tasks depending on the data that is being processed.
#Claris
Scheduling Flows
The Scheduler tool triggers a Flow any time you pick. As time passes, it executes time-centric automations that can be used to get daily reminders for recurring duties or spin up a weekly checklist of documents.
#devcon19
Built-in apps
Sometimes you need to manipulate data, with a math operation, a text transformation or a date formatting in a Flow.Utilities comes to rescue for this.
Utilities
Adds human approval within your flows. Complex tasks requiring human judgement can be directed to an approver, then subsequently redirected based on whether the task was approved or rejected.
Approvals
Yes
Create Opportunity
Reach out?New Lead
No
A full fledged REST client to configure custom HTTP requests defining every single attribute (headers, body, url, attachments..). Perfect for any last mile integration when an API is not available in the connectors list.
Webhooks
Code Blocks
Extend workflows with custom NodeJS code.
Code can also be run as a standalone HTTP call. No provisioning. No deployment.
#devcon19
RUNNING AND MANAGING FLOWS
Flow History is where you can see all the activity from your Flows of a project. It's a log of everything that Claris Connect tried to automate on your behalf.
Execution History
Flow History is where you can see all the activity from your Flows of a project. It's a log of everything that Claris Connect tried to automate on your behalf.
Execution History
Explore the full details of the HTTP requests and responses of each single step of the workflow.
Execution History
Whenever a workflow is saved, a new version is created, and is added to the list of existing versions. Users can check the changes made over the time and restore previous versions with a single click.
Versioning
Autoreplay makes your Flow smart enough to retry an action so you don't lose an execution of a workflow. If a step in a Flow fails for unexpected reasons (timeout, internal server error..), the Flow will retry the action up to 5 times.
Fault tolerant
service
Retry Queue
✓ Encryption at REST✓ Encryption in transit✓ AWS KMS
Security and Infrastructure
✓ Elastic infrastructure✓ Microservices oriented✓ Resilient
✓ Extend with custom code✓ iOS native app✓ Siri shortcuts integration
Roadmap highlights
✓ On Premise support✓ Team collaboration✓ Connector Kit
FileMaker and APIs: Real-World ExamplesCris Ippolite, iSolutions1.30pm - Osceola C
More on APIs and Claris Connect?
Introduction to MicroservicesMike Beargie, MainSpring2.45pm - Osceola D
Q&A
