Hello, Siberians. Welcome to lessen 7.6 off Model seven Off this car stated, is that Reserva one Microsoft as your tactic design.
He had 11 objectives for this video.
We'll start out by introducing the geologic up service.
Now we'll proceed to cover how this service walks, introducing you to the concept of connectors, triggers and actions.
Well, then, look at some of the options that we have. When we talk about as your logic up connectors,
then we'll talk about geologic app from the price in perspective. Let's get into this.
Let's talk about geologic caps
has a lot of couples that cloud service that helps us to shadow, automate on orchestrate tasks, business processes and walk flows when we need to integrate applications, data systems and service is across enterprises and applications.
Now let's put that in plain English. What exactly does that mean?
This is way of Mace.
Not all applications are solutions require right in court,
some applications or some solutions as simply walk flows.
do I need to write code if I want to send email notifications with Office 365 when an event happens in another system application on a service. The answer to that question is no, that does not require me to write full blown code to achieve that.
A lot of solutions at just moving information from 17 extra. Another seven. It is just integration solutions. And that's where geologic maps comes in handy
because logic ABS comes with a number off tribute connectors so that developers can focus on their boots on their blocks of court on Just used the connectors toe integrate existing systems with one another.
Let's look at our little bits, so as a logic caps as different p less that supports it.
So number one pill, I say it's all about a P I. So it has this connectors, which AARP reviewed a P I wrappers around different integrations with different systems, and service is
it's all survivalists. You don't have any visibility into the underline infrastructure. That's funny, Nigel Logic cars were simply the define and the sign our walk flows, and that's about it.
It's no court now, their waist for house tow, walk and design logic haps with court,
but in many cases off for many years, cases will be doing that designing logic captures in the visual designer.
It's events driven, so it fits right well into events Tribune architecture, where they can be tree gas and that they can be actions taking off different triggers.
We have a visual designers. Why mention where we can officially design integration between disparate Service's
on? It's an integration platform. It's all about integration, off applications and service is and getting different applications to talk and integrate with one another.
And it's all about workflow.
Let's look in ma details at hours. Your logic cap works.
Where would create an agile logic after sauce?
The key points that we need to know is it Butte around This thing's called connectors Now a connector. It's a proxy. It's a wrap around a p I. So in not awards this our tribute actions and tribute tree guests prib ute
capabilities that been wrapped around
it behind that we can simply select different options that we want on its unusual logic of just ties them together. It will make more sense, as I carry on
so again, the foundation off a geologic cats that this one's called connectors.
three guesses and actions.
Some connectors only have actions they didn't have triggers.
Some connections on the after gays and no actions why some collectors have both actions on triggers.
Let's look at that a little bit more.
Let's take an example off office 365 Outlook.
That's a connector that exists in as your logic.
Now this connector as set intrigue is,
for example, it a streak is that when an email is received when a new email election is shared? Mailbox When a new email mention in me arrives when an email is flags, when an upcoming event is starting Cem on, that's not on exhaustive list. That's just a sample of some of the tree Gaz
that disconnect or has beauty into that.
What does minces They can use any of this event or action
to lead into another parts off my workflow,
the same office tree, sick five Outlook connector, as said in actions Off, for example, it has action to say, sent an email, sent an email from a shed mailbox and an approval email, updates event and many other actions. Beyond this,
let's take another connector. The Tweeter connector,
the trader connector, for example, has set in tree guests like one of the tree together he has is when a new tweet is posted.
And at the same time it has set in
like some of the actions that this connector has posted a tweet tweet get following, get followers. So this attribute, let's take the http connector.
So, http, for example, as a tree golf when heads the tippy request is received on as an action off invocation to be request
finalist. Take an example off Salesforce connector.
So So this was a popular CFM application. Just cloud based
it as bute in Tree gets like when a record is created, when the record is modified on Butte in
actions like create a job creator records to lead a job. Eletrica.
So, David, Where you get in that where does all this time with a geological Elijah logic cap means is that I can do integration across all these disparate service's. However, I want to
with a combination off actions on triggers. So, for example, I could say,
when have I knew twit is posted?
I want you to invoke an exit to bury quite Sonam, tying the connector, a trigger off treater, a tree to trigger that's revealed. I'm tying that into an http action
to say, when a new tree it is supposed that I want you to invoke on http request How about another one
when in new treatise posted, send an email.
I don't need to write code for that. I could just tryin does walk flow together and get that to work
Another one. What about when an email is received? Created job in sales for us?
Whenever somebody sent an email into into a name and address, I want you to automatically create a job in sales Falls that somebody can action
on. Finally another one say when htp requests receive sending up for Val email.
So this is what as your logic happy's great hat on. By the way, it is just a simplified explanation that I'm giving to you,
because the truth is with as your logic, perhaps we can be much more detail. We can go
tie in action Internet action on, then take perimeters from the previous action on, then use that as import fun of the action that we're defining so we can go in tow, complex orchestrations and complex walk flows. But you get the idea. The Honda line idea behind the service.
So how many connectors that we have? It's a gallery of collectors. It has lots off connectors, beauty and the lister you're seeing on the screen again. This is not an exact civilised, because more connectors have been added all the time for a lot off clouds. SAS based applications for a lot off azure service is
for a lot off other types of services.
You can even build custom connectors for your own custom applications, so that's also a possibility.
Let's talk about pricing briefly.
So when it comes to a geologic caps where we pay for his would pray for the trigger would pay for the action with pre for connection or the connector executions. And they're different types of connectors also, and they have different costs associated with them. So, for example, but from standard connectors
as our logical provide and the price connect us for access and enterprise systems like ASAP and IBM. MQ
ondas attached a bit differently. By the end of the day, what we pay for if ways in the conception based model would pay for the trigger before the action on will pay for the connector executions
it brings me to the hand off this lesson. Thanks very much for watching, and I'll see you in the next lesson.