Quarterly Integrator.io Product Update – Register

Quarterly Integrator.io Product Update – Register2020-10-05T20:05:54+00:00

Quarterly Integrator.io Product Update

Watch Now

Kim Lougheade Kim Loughead Head of Product Marketing
Matt Graney Matt Graney VP Product

We’re starting something new! Please join us for our first Quarterly Integrator.io Product Update. You’ll learn more about what’s new with Celigo integrator.io, see demos of cool new features and be able to interact with our product team.

In this session, we have lots of exciting updates to share, including a new and improved UI and a number of new features to improve and scale your use of integrator.io.

What will you see?

  • Walk-through of our new and improved UI
  • Introduction to Celigo University
  • Improvements to Advanced Field Editor
  • Introduction to a new feature - Custom Forms and Settings

Watch Today!

Full Webinar Transcript
Good morning, good afternoon, everyone. My name’s Kim Loughead. I’m the VP of Product Marketing here at Celigo. I’m excited to have with me today Matt Graney, our VP of Product Management at Celigo. So we’re kicking off something new today. We’re excited to bring you our first quarterly product update for Integrator.io. So this will be one of, obviously, an ongoing series that we will bring to you throughout the coming months. So, Matt’s going to go through some exciting product updates. I won’t steal any of his thunder. Just a couple of housekeeping items before we get started. So, the session is being recorded. You guys are all on mute, so if you have any questions, please type your questions into the Q&A panel. We will have plenty of time at the end to get to your questions. And we will be sending out a recording of the session after we’re done, so you should expect that in your inboxes so you can refer to it later. So with that, I’m going to hand it over to Matt. All right. Thank you, Kim, and thanks, everyone, for joining us today. As Kim said, a lot to talk about, and you’ll be pleased to know, we still might not need the full hour. And I’m not going to kill you with too many slides, because we’ve got a lot of exciting things to demo and it’s always more fun to show things in the product than just talk about them on slides, anyway. So, I’m going to give you a walkthrough of the new UI. Some of you have already been playing around with it and have seen it in beta, but it’s coming to the fore very shortly. And then, I’m going to dig into a couple of areas in particular, one related to what we call the Advanced Field Editor. I’ll show you that in the product, so you know exactly what I mean. We’ll talk about the improvements we’ve made to the knowledge base and community, and ask for your engagement there. Celigo University, again, a resource available to you all. And then, a completely new area called Custom Forms and Settings. I’ve left that to the last because it is a bit more of an advanced topic, and at least from a developer point of view, it might be something that developers want to stick around for and others may not. As you’ll see, you’ll end up being a user of these things without necessarily being a developer of them. So stand by for that at the end. Okay. So I’m not going to spend too much time on slides, but I’ll begin and end with this, that we have been building a new UI for quite some time. Our existing GA, generally available UI, is based on a JavaScript front end called Ampersand, which was a very fine choice when we made it five years ago. But if there were front end wars, I think it’s fair to say, Ampersand wasn’t on the side of the victors, and it doesn’t have a thriving community. Meanwhile, React was sort of incubated out of Facebook. It’s got a very active online community. Answers to every conceivable question are likely already out there. So it meant a lot for us, not just for that reason, but it does offer many other advantages in terms of how we build. But from a user experience point of view is really what we want to talk about today. So that new UI is already available in beta. In our August release, just shy of a month from now, it will become the default UI, but we will still have the legacy UI available to you just a click away. But we will be take it out to pasture in Q4 hopefully because clearly we don’t want to carry two of these UIs around, and I think you’ll find the move to react would be pretty seamless and, dare I say, enjoyable. Not least because you get a range of new features and I’ll be highlighting some of these today, and we’ll come back to this slide because I can almost use that as a summary after I get through the demo. All right, so with that I am actually going to switch straight into a demo by the power of– ah, there we go. Okay, so for us at Celigo, all internal employees have had this UI be for the last little bit. Right, so we are already in this day in, day out and using the internal community to help with not just QA, but also feedback on useablility and so on, so there are some aspects of this that haven’t changed. We still have this concept of integration tiles and your homepage, and I don’t think you’ll find anything here too foreign. Probably the big thing to notice is now your navigation is mainly on this left sidebar which is collapsible, and very quickly you’ll train yourself to know what these different icons mean. It may take awhile at the beginning which is why you can keep it open, but everything you would expect is here: obviously a homepage, the various tools whether that’s Flow Builder, Data Loader, or the Dev Playground. I’m going to come back to Dev Playground in a second near the end because it’s a great way to understand a lot more about how things work in Accredo IR, so there’s some of the high-level tools, individual resources. Now if you’re not a manager in an account, if you’re just manager of individual tiles, you might not see all of those. If you’re an owner you’ll see some additional options as well, and also if you’re in developer mode you might see some differences, but obviously connections are key. Imports, how get data in and out, your scripts and so on all here neatly collapsible. Some various things in the center. Celigo University we’re going to talk about in a little while and the marketplace. Okay, so left nav instead of a top nav. We’ve also just made it a bit easier to move around now for our channel partners or services partners and internal employees. We often belong to multiple accounts, like here for example. I belong to a bunch, including some customer accounts. They’ve added me because they wanted me to take a look at something, so it’s very easy just from this drop down to switch between accounts. There’s a little delete icon here which allows you to remove yourself from an account, and the toggle between Sandbox and Production is very easy as well. What we’ve done too, with Sandbox is given that a coat of paint. Not to be too literal, but we went through something the color of sand to make it just really obvious when you’re not in Production anymore because well, it sometimes wasn’t so clear. You’ll only see this if you’re license is for the Sandbox. In this particular account, I’m not the owner so the owner is actually my other account so my profile page here will just have the basics, but you notice I am in developer mode and if I were to turn that off, you’d see certain things disappear. You can read all about that in the Help doc. We’ve done a pretty thorough overview and revision of all the Help text throughout the product just to make it much easier. We view this as kind of a first line of defense. We want to obviously make the user experience such that you don’t even need the help text. If you do need it, it’s right there. And if you need more than that, of course, we’ve got the knowledge base. And I will get into that in just a second. You’ll notice here we now have this sort of breadcrumb approach. In the user experience, it’s referred to as a breadcrumb. And it will become important when you’re working in flows and integrations. So I’ll come back to this as well. Now we live in an imperfect world. And sometimes, you may still find for whatever reason, a need to go back to the old UI, and I wanted to show you that it’s just a click away. When you’re on this homepage, you can just say, “Take me back,” and it’s going to show you the familiar environment that you’ve been used to. And equally, if you want to see what I’m seeing, all you need to do is click on try our beta. Okay? And I think if you were to do a sort of a head to head or a side by side comparison of these, you will find that the user experience here is cleaner and snappier. It’s just a lot more responsive. Pages tend to load a little faster. And as I’ve already mentioned, this is where you’re going to see a lot of the new capabilities in the product. Okay. So that’s kind of the general orientation. Now, let’s get into one of these tiles here. You notice by the way that each of the tiles now tell you what’s inside. So my standalone flows, I’ve got 32. I’ve got one flow here, and so on – right? – so it just makes it easier for clients to see what’s going on. And we do have plans to extend this further. The little icon here also indicates the permissions I have. Here, I’ve got manage permissions, and I pretty much have that throughout. If I only had monitor permissions, then instead of a little gear, it would look like an eye, like a human eye, so that it’s clear that I can only look at it and can’t change anything. All right. So let’s get into my tile here. And again, some of this may look fairly familiar, but we’ve tried to put everything together and just make the navigation a lot easier. So you’ve got flows this is sortable. Obviously, there’s only one entry in here, and just made it a bit easier to see what’s going on while having less commonly used actions just a click away in the actions dropdown. So this is sort of a pattern where establishing throughout. The run dashboard is also located here. So this is largely unchanged. In our next quarterly update, I think we’ll have some more to share about what’s happening in the dashboard as we revamp our error management. But we’ll save that for then. I can easily see the connections. You also get a nice indication whether it’s online or not. Again, you have the usual things that you’d expect. Suddenly signing up for notifications, and this allows you to choose exactly what you want to sign up for. By default, we don’t automatically subscribe you to be notified of errors because we didn’t want to be spamming people. But we do sometimes notice that our users haven’t even bothered to sign up for notifications and so aren’t aware when their flows are erroring out. So if you not done that I’d encourage you to do so. You’ll find it in a similar place in the ampersand UI. I should add too anything you do in this UI or in the ampersand UI, it’s all the same back end, so there shouldn’t be any issue. You should be able to pretty much move between them which does mean if you were to encounter a bug in a particular area of this UI, you could always go back, make whatever changes you need in ampersand and then come back to react. And you should be able to just carry on as you were. The audit log is available right here, so this is a list of all the changes that I’ve made. It just makes it easy to see what’s been changed and by whom, whether it’s by– well, obviously, I’ve been in here a lot, but also if any changes were made by, for example, by the API, at the moment in this account, I haven’t invited any other users except myself and my colleague Milad, but it’s all accessible right here. Okay, so that’s, again, just orientation from within the integration tiles. Now I’m going to go ahead and build a flow. So let’s go ahead and create flow. We got rid of the wizard /concept to just provide you with a canvas, because we got some feedback that said that the wizard was a little disorienting, because it wasn’t always clear what you were actually doing. So here, it’s just a matter of adding a source and adding a destination as the beginning those first few steps. So this application list includes type-ahead capabilities. So if I were to type SOF here we go with Microsoft. But what I want to do actually is Postgres, and I’ve got an existing connection to Postgres. I don’t want to use an existing export, I want to create a new one. All right, the first thing to note is that we’ve added this export panel. You’ll see it here in a second. So if I happen to know my database schema and in future, we’re going to make this even easier too. But if I say “Select star from customers.” I’m going to grab all the records from customers and hit preview. It’s going to actually give me the first page of results. So we’ve done this before in the sample data field of the ampersand UI, but it was not ever formatted like this, and it made it kind of difficult to see exactly what you were looking at. Here, you see that first record, the country is Germany, this is a live view. So if we were to say where country is Mexico and run the preview again, you’ll see we’ve got a new result. All right. So that’s one thing. If I go ahead and hit save, I haven’t actually done all the things I need to do. So the UI helpfully highlights these mandatory fields in red, when the time is right. So we’re obviously getting customers, and we’re going to say get all of them as opposed to getting just those that have changed since the last time I ran this, and I think we’re good there. All right, so we’ll go ahead and save that, and I now have my export in place. The next thing to know here is that we’ve tried to declutter the UI. In the past, you had a lot of icons, and it was a little difficult to know what’s going on. So now, we, instead looking to reveal the power when it’s needed. So what we’ve done is added a little plus sign here, and this exposes the various tools available. So scheduling, this is for transformation for filtering or for JavaScript. So if we just go into each of these. There we’re only going to stay on here if we keep them in place. So, if I were to define a transform, here we’ve got the incoming data, exactly our sample from Mexico. And let’s say, out of this, we wanted “company name” just to be “company” and we wanted “contact name” to be “contact”, right? And many of you already know how to do this. And here we are in the preview. We’re adding, in our next release, a little auto-preview checkbox, so you could opt to say, “always preview this”. So this is pretty much unchanged. But the other thing we’ve done here, that I’ll mention while I’m on this page, is also providing the option to do transformations via JavaScript. Because this UI is fairly simple. It allows you to do things like to take the phone number, and– oops. That’s my own phone number. On autocomplete here. But it allows us– sorry, my browser is getting in the way here. I’m going to cheat and say “fax”. And make that, instead, look like this. We’ll say that’s “contact.name” and this is “contact.fax”. And preview. So you see, we’re changing the structure of the data. So you can do some decent things here. And better yet, for more complex transformations, you can run JavaScript. And I’m not going to go through this here, but we have samples in our knowledge base now that allow you to see exactly the code that you could run to produce a transformation. So you could insert a stub and basically take this record, transform it any way you like. This is an example of an AFE, Advanced Field Editor. And we’re going to be talking a bit more about the improvements we’re making here. And it’s gradually rolling out through the product. But one thing to note is that this is able to be reconfigured. At the moment, we’re not allowing the panes to be resized by dragging them, but we are providing layout options. So here’s a three-column one. There’s this kind of one and two. And then, in some cases, it actually makes sense to see it in sort of wide mode. And then, of course, you can come back to this fashion. So, transformation is just an example. But if I were to– I think we’ve got everything we need here. Preview. And then we could save that if we want, and it would leave this bubble in place. Okay? So basically, these bubbles only appear when you need them instead of cluttering everything up. And it just makes it look nice and clean. All right. So now let’s move on to adding a destination. I’m going to add a couple of different destinations because they’ll give me a chance to highlight a couple of different things. So the first destination, we’re just going to send a file to FTP. I’ve got an existing site here. And we’re just going to dump a customer file, and I want to generate a CSV file. So now, when I go to generate one of these CSV files, I have a helper. Again, very much as we saw already, we have this concept of an AFE, this Advanced Field Editor. So, what this is doing is providing me a very nice kind of real-time feedback integrated view of how my results are going to look. So if I go back to– this is essentially what we have in this is essentially the behavior you can see in the ampersand UI today. And one of the big changes we’ve made around the eighth is that in the past, it was always these data arrays. And it might be a single element. It could be an array like this. And it was just difficult sometimes. We’re observing our customers having some trouble navigating around these data elements. There was only about one result. And it’s possible here. This is editable to grab this one, copy a new one, right? So now, we know we have a couple of them listed, right? So you could make changes like that. But it just wasn’t all that convenient. So what we’re doing here with io 2.0 is we’re giving you a lot more sense of what you’re actually looking at. So this isn’t just data. This is actually a batch of records coming from my export system. And I’m now showing some examples, multiple results instead of just one, because I want to see exactly how this is going to– how it’s going to look. And it’s much more interactive. So here, the column delimited by default is a comma, but I could change that. Let’s say I wanted it to be a semicolon, and we’ll see that I’ve got the order preview checked. So you’ll notice it immediately changed. We could see what it’s going to look like if I have the header included. Now, customer ID, it’s all appeared there. We haven’t made it too quick when it does the auto preview because otherwise, it’s really annoying because it will be changing almost too rapidly. So we added a little delay in there and all the other options available too. So you can basically configure your CSV generation in a much more, convenient interactive manner. And when you hit save, then the options I chose are available right here, okay? And we can just dump this in a file, a folder named after me, and we’re done. Okay, so that’s the first example where we’re using this advanced field edit to make it much easier to see what’s going on with the file I’m about to generate and just make that whole thing seamless. Now, if we wanted to add another destination here, I’m actually going to choose HTTP. And I’ve got different options, whether I’m going to import, do a lookup, either looking up files or looking up records or transferring a file. So we’re making these things, bringing them really front and center because these are the common patterns. But for now, I just want to import the records, and I’m actually going to try to import these into QuickBooks. And I’m not going to go through the whole process, but it will make it kind of clear what’s going on. So here, I have the ability to toggle between views. So in this case, it’s QuickBooks. So I can toggle back to the QuickBooks view of my import. And instead of having to define kind of the raw HTTP queries myself, we’ve exposed the names of the API’s available. So in this case, it might be customer, and it might be create a customer. So I’m pulling customers out of a SQL database, maybe archiving them off in a file. And now my next step, I want to write them into QuickBooks. So this is one way of doing it. And for many operations, that’s all you need to do. But what we’re also doing here is– and we’ve had this in the past in ampersand as well, is giving you the ability to switch to a more detailed view if you need it. And in this case then, you can build your, in this case, a relative . So this is building the actual call that you’re going to make. And again, use one of these APIs. So again, these AFEs, these Advanced Field Editors are going to appear wherever– essentially wherever you have sample data that is going to drive the result that you’re looking for. So in this case, the sample data is going to drive what we are trying to do over here. So this is what we call a template. A template, meaning that we’re going to take a standard pattern, we’re going to plug in values from the data and see what happens over here, right? So I don’t know if this makes sense for QuickBooks. But if I were to add a field, we can say this is going to be company name from the data. And when I preview, we– well, I got an error in here myself. So let me just get rid of this and preview. And now, oh, I made a mistake there too, the demo effect. But you essentially can plug in your own data. But what we’re doing with 2.0 is making this available in more– making it clear that you’re working with a record, instead of again this data construct. You’ll still have access to all the various functions. So now, in fact, see I’m used to using the new one. Now I forgot how to use the old one. Now we should be able to see this, where we’ve got the name of the customer here. So maybe, in fact, this would be customer ID. And you notice that it understands. Oops! I added an extra thing in here. And here, we’ve got the customer ID. This is building the relative URI. But if we were looking to build the HTTP request body, again, we’ve got a similar type of idea. You’ve got the old way of doing it, which is essentially what you see in the ampersand UI. And then we’re introducing with h2.0, a new set of capabilities beyond just this. So what you’ll see in the end is a lot more helper functions will come into play that will just make it much easier to build out these request bodies and so on. So this is more advanced capabilities. But whenever you’re working with integrations, especially when you’re doing lookups, it’s all about how do you take existing data that you’ve got from one system and roll it into what you’re doing with the other system. And that’s a big motivation behind this f2.0 tutorial. So I’m not going to go ahead and save this right now. But I hope you get the idea of what we’re doing there. Okay, so the next on the list here is I wanted to highlight the developer playground. We’ve already seen some of these editors already. But under the Tools option, we’ve introduced a Dev playground. And this allows you to see a lot of what I’ve just been talking about and see them in action. So you can choose various bits of data. So let’s say some Nested JSON record. And then, for example, see what that’s going to look like if you’re using this to build a URL, right? So again, you can start using this data if you were to say, https://example.com and / get and passing a parameter like the order ID, right. So this is a great way to get used to seeing exactly how this works. You notice the value, which is the value for order ID, in this case, gets plugged in down here. It also introduces a whole lot of functions as well. You can think of these functions as Excel macro functions. And yes, we’ve had these in the product for a while before, but with this editor now, these are becoming much more accessible to you. And you’ll also find them much better documented in the UI. I’m sorry, in the knowledge base as well. But you can choose other data as well. We’ve already looked at CSV. But if you wanted to look at the CSV parser, this time we’re pulling in the data, so well, clearly the comma– the delimiter is a column. Yes, we can see this has a header so we can turn that on and just see that we’ve got A much better way of understanding exactly what’s going on throughout the product. So a great way to experiment and understand and just become more comfortable with exactly how the product is working. Okay. So the other couple of things I wanted to highlight here is more on the technology side a little bit for those who need it. You will notice now. If we go to create a new connection, and let’s say I’m going create a HTTP connection. We now support generic Oath. Now, we’ve always supported Oath for a range of different endpoints, but it typically required us doing the work, Celigo doing the work to work with a software vendor and someone to get integrated,io registered as an app. And that can sometimes be a little cumbersome and sometimes and not even feasible. So we’ve instead exposed this directly. And if you choose this, of course, there are a lot of different options available for configuring the– but this a quite an important thing here because it just makes it a lot easier to get access to the right applications. Okay. So I wanted to just now touch on the fact that we’ve made significant improvements in how you can get the help you need. So I’ve already shown these little help bubbles, field help text, throughout. Okay? So the next layer of help is, indeed, the knowledge base, the help center. So this has changed enormously in the last six months. I think we can all agree that in the past, documentation had some holes and we’ve made a concerted effort to make big improvements. It looks a lot better for one thing and there’s a lot more content, up-to-date content as well. If I just choose one here, of course, you can search for this handlebars one. We were just talking about handlebars, and we’ve gone through and captured them all with examples. And it’s just much, much easier to use than it was before. So this is a big thing. Obviously, we also have– if you’re integration app customer, all your integration app docs have also been captured as well. Flow diagrams were applicable as well, to make it much easier. So if you’d given up on our docs in the past. And I know some of you had. I really encourage you to go back because this is a great resource. And we are really committed to continuing their improvement. And I want make sure that you’re taking advantage of those. So that’s the knowledge base. The other part of this that we’re just getting started with is community. So the community has sort of been there a little bit in our knowledge base for a while, but we haven’t been too active. But we’re stepping that up beginning with integrator.io, and we’ll be looking to do something similar with the integration apps as well, but you can see now a growing number of posts, a small but growing number of followers, so we encourage you, if you’re using integrator.io directly, to register here. It’s a great place, say with this one, with the enhancement request to get engaged with our product management team. and on this one, you’ll see a lot of tips and tricks, how to– like this one, how to use a source field as part of a file name in an FTP import. This is the sort of question that we see comes up a lot. Even if it’s documented in the help, sometimes this is the way people think about it and want to just make a very specific investigation to get their answers. So this is early days, but we are committed to this. It’s part of our objectives to be posting daily on this so you’re going to see the content grow quickly. Obviously, there was search capability and we’re really keen. Equally, anyone in our team can create posts and any customers can comment on posts as well. Okay, clearly, this is still where you register your tickets. The next thing I wanted to mention is Celigo University. Celigo University, it’s a separate app that you SSO into. So there’s no separate credential required. Obviously it looks and feels a lot like integrated IO. Well, I haven’t even done the basics yet myself, but we have a number of different learning paths defined to take you through the product like fundamentals, various basics, building your own flow, and so on, introduction to the different types of mapping. These are all the building blocks that are really critical to being successful for integrated IO. With our new UI, we’re trying to make it as obvious as possible, what needs to be done. But sometimes you need that extra bit of background to make the right selections in the UI. And this is a free resource that’s available to everyone. And I strongly encourage you to get through the basics. In some case for our office hours, which many of you take advantage of where for repeat visitors, we’re actually insisting that they go through this because chances are that questions are answered. There’s even a little test at the end. So we’ve invested a lot in this and it’s an ongoing effort as well. And we’ll be rolling out more of these as we go. Okay, so let’s see how have we gone so far? I’m just going to switch back briefly to the slides. So we’ve shown you a little bit about all of this stuff. I’m going to come to custom settings in a second. So we talked about the knowledge base and all the improvements there. We talked about Saligo University. It was actually launched back in April. So if you haven’t checked that out already, please do so. You can get points and so on as well for that if that’s what motivates you. And the last topic I wanted to get to here was around custom settings and forms. And I’m just going to set the context here with a couple of slides because I think it’ll help. So custom settings, as the name suggests, is the ability to define settings, to allow more technical users to add new settings to the resources in their flows. So in this little screenshot, I’m adding with a simple JSON structure, two fields, notify email with a value of user example and a debug level. These don’t mean anything to anyone else except for me and in the context of my own flow. So I can add settings like this to integrations, to flows, connections, exports, and imports. And once I’ve got these settings in place, I can use the values of these settings to drive the behavior of the flow. So obviously, if the debug level was set to two, maybe in my flow, I would would do something different. I would enable an extra import that would send additional debug info to Splunk, or dump more data to an external database. So and then if I switched it back to debug level of zero, there would be no debugging, right? So it allows you to make setting changes like that, and change the behavior of the flow. So custom settings drive the behavior, and if you’re technical enough, you could set the values to these, using the settings field, but the way that we’re encouraging this is actually via custom forms. So as the name suggests, a custom form is simply a way that a user can set values for the custom settings. Okay? So clearly building these forms, because it might need to integrate with other data is a more technical prospect and one that an IT user or a more technical user would need to do, but the goal here is once that’s been built, then it makes it much easier for a non-technical user to use the form, and to make sense of it. And you can see actually in the dev playground, some examples of that. And I’ll just show you that in a second. All right, so I’ve described it, but it’s definitely going to make a lot more sense when I want to demo it. So let’s switch over. So the first thing I’m going to do, actually, is take you back to the developer playground just so you can see how this works. And if I choose a simple form as my data structure, and then go down to this simple forms editor, you can see that, this definition here is what shows up here, right? So this is all live as well. That’s why I’ve got the auto preview. So it’s some URL with handlebar support. If I change that, now uppercase, I can define my own help text, which is just here. And this one, because it’s a type relative URI, it happens to be one that I can bring up one of these as these AFEs. These Advanced Field Editors for, right? So we’re actually giving you access to all the same capabilities that we use in the product ourselves. So that’s one example. If you wanted something more sophisticated, like a collapsible form, here’s one like this where you’ve got different things available and you can even test the form and see, “Okay, I’ve got create selected, I’ve got confirmed delete, this is blah,” Right? So you can see that the json that I want in the settings to drive the behavior, my flow is actually just being the values are just being set by what I’m doing in this UI. Alright, so let’s put this in context with a real example. And just like in the good cooking shows, here’s one I prepared earlier. And this is meant to be a really simple example of sending opportunities from Salesforce to a Slack channel. Now getting data out of Salesforce requires that you can query Salesforce, writing data into slack requires you to know how to map fields. And it’s not super difficult, but the idea of a custom form makes this even easier. So here I am with my opportunities export. You can see that all I’m doing is select name, owner name and the amount from the opportunity. The export panel shows me sample data. This is, again, a live view as we’ve seen before and then on my import, I’m just trying to post a message to a given channel, the channel being defined in the mapping. Okay. So when I look at settings, I have a lot of different places where settings can be. But in this case, I’ve added settings to the flow itself. And under this custom area, I’ve got a number of different options here. I can choose the date of the opportunity. Right? So the form is being defined, and I didn’t need to do anything other than to find the– that it’s a date field. And I can choose a different day. I can choose the size of the opportunity. The sales rep field, that ones not working right this second in my demo. And I’ve got a list of various Slack channels. And as a user then, all I need to do is say, yeah, I’m going to post to test. I’m done with anything else I want to do, and I just hit save and that’s it. And now, my flow is configured. So what has happened then under the hood is that it’s actually– here’s one of our [inaudible] this time for a filter. I see the this sample record as before. But in addition to that, I see these settings objects. I see the earlier thing I had for notification email and debug level. And I see the details in the flow of the values I just set. So the minimum amount, the date. And now, these attributes of the data are available to me in the flow. So my filter logic is saying if the record is greater than what I’ve configured in the flow. So settings dot flow dot min amount. In this case, it’s that number there. And if the owner name equals the sales rep, then I can– that will be a record that I choose to pass through. So again, what I’m able to do– so all these fields that are available either from the data, like record dot anything is coming from the data. And settings dot anything is coming from the settings I’ve defined. And again, filled out with a custom form. So if we just to see how the sausage is made, as they say, I’ve basically just defined a bit of JSON here. I’m not going to go into it. It is a bit more of an advanced feature. You’ll notice, by the way, in all our editors now they’re much more user friendly. We’ve got this collapsing, so you can see how my created after minimum amount sales rep and Slack channel are all these fields here. And makes it very easy to know what’s going on. So these are things that you can learn from looking at the developer playground and coming soon to the knowledge base as well. And that’s all that I would need to do. I could define this hitting test form will give me values. If I made a change here, I could test it and see that this changed. And then, what’s the use case here? Well, imagine you had lots of different types of opportunities in Salesforce, and lots of different Slack channels because different people were interested in it. So let’s say you’re a sales team, and you’re focused on the western region of US. Then you could easily configure exactly the same flow. And just use the settings to say, hey, I only want those from the western region. Now, without having to go in and change the query, you could just change the filter instead by modifying the settings. Then someone else who’s responsible for the eastern region or is looking at, high value opportunities, that could again, use exactly the same flow, and get what they need out of the tool as well. Okay, so this is definitely an advanced feature from a development point of view, to allow you to build the forms that you need, and configure flows and modify their behavior, but from an end-user point of view, this is intended to be as simple as just filling in the form and clicking Submit, and away you go. I see this button only because I’m in developer mode. If this was turned off, I wouldn’t even see that. And again, we have settings available in lots of different places on the integrations, the flows, the connections and the imports and exports. So pretty much everywhere you need them to be as a way of driving the behavior of the integration flows themselves. So I know we’ve covered a lot here today. I’ll Just go back here to say, firstly, thank you for your time. A lot of what you see in this upcoming work, both what’s already generally available, as well as what is coming in say our August release, is driven by feedback we’ve heard from you. I’d just invite you to keep that coming. This is not intended for support, of course, or as a substitute for support, but product feedback at Saligo.com is a great way for you to tell us what you think about some of the changes we’ve made, if there are any glitches that you might see that maybe aren’t ready to support, and just engage with us. If you have some feedback you’d like to give us and maybe even enhancement requests, we’d certainly be happy to engage with you there. Okay, so with that, I’m going to hand back to Kim to see if our audience has any questions. Yep, we got a few more early on when you were going through some of the if stuff. So a couple from Jack. So the first one was, will you be able to create JavaScript within the JavaScript tabs? So this goes back to the first stuff that you were showing on the exports. Yes, you will be able to create a JavaScript directly here. If that was the question. I insert a stub, I’ve now got the sample data. I’ve now got the beginnings of my script, and so I can write JavaScript directly here. So perhaps the question might have been, so that’s the hook. But if you were looking to write JavaScript for a transformation, the answer is yes. You wouldn’t be able to do that here. I think the button to insert the stub is missing, but that’s available and similarly for filters, you can do the same for filtering as well. So if that was the question, the answer is yes. You can write JavaScript directly. Now, I’m always curious to understand if the need for JavaScript is because it’s just easier and faster as a user, or if because there’s a perception that there’s a missing feature in sort of the point and click side of the interface. So, jack, if you have any additional feedback on that, we’d be happy to hear from you. Great. There was another question from David. Is there a difference between the JavaScript transform and the JavaScript pre-saved page hook? Yes, there is. So we have a lot of different places where JavaScript can can come into play. If you think about it, these are happening in order, right? So the data is coming out of my database. What I can then do is transform it. And I don’t think I saved the changes before. But let me just do this as an example. Well, actually what I’ll do first is show you here in the filter I’ve got everything. Whereas if I first do the transformation and say a contact name is name and preview, we should have only one thing, and hit save, then obviously the bubble is going to persist. But also when I get to the filter– don’t know why that’s taking so long. There we go. It’s taking its time there. So now that bubble persists. So now if I add the filter, I now only have that one thing. So this is an area that earlier in IO it was a little fragile I would say. Where you couldn’t be sure that you were always going to get the right data at this point. And by the way, for those of you who know sometimes in the ampersand, there was an extra button for add missing field. In this case, you don’t need that. You can just define a new field here. And then it becomes immediately available [inaudible]. And then it’s only at that point that you get to your pre-save hook. So it’s happening in order. I think that’s the point. You’ve first transformed– after you transform your filter, and then you do the pre-save. Likewise, on the JavaScript elsewhere, you can run code before the mapping, after the mapping, after you’ve submitted and, in this case, [FTP?] after you’ve done the submission and then even post aggregation. Which is after we put all the results together in the file. And then there’s even for after a response mapping as well if you were doing that. So we basically tried to put these hooks– make them available anywhere they’re needed. So that if the UI doesn’t allow a feature that you can dig in and get it done with JavaScript at least. And over time, of course, we want to find that right balance and not force you to write scripts for everything. Or else that would not be the right direction. Cool, thank you. So, another question from Sean on the connecting to Salesforce, do you have to install a package, or just allow permission? Yeah. For the way our Salesforce integration works right now is it does install a package. And we do that mainly because it provides a lot of extra capabilities on the import side. It allows us to do a much tighter integration. So the answer is yes, there is a package to install when connecting to Salesforce. Okay. And last question so far, on the developer playground– so some people aren’t seeing that. So how do you get to developer playground? I know you have the [inaudible] on developer mode. Maybe you can exactly. That’s it. You notice it disappeared. It’s just about turning on the developer mode. And that’s where it appears. Okay? Yeah. So that’s the answer. You just need developer mode turned on. Perfect. And then on the custom forms, the example was good, but do you have any customers that are actually using it now or any real-world uses of it that you could describe? Well, it was the one that I mentioned that– like with that Salesforce to Slack. This is the type of thing that we’re going to be doing in our Marketplace. Right? So I didn’t go to the Marketplace here. But you can imagine if we get to the point, we should be able to go and have a– here we’ve got Salesforce to Slack. Right? And when you install it, it should be just as simple as what I described. Right? So we are using this ourselves. And like many ideas, they sort of begin when they solve our problems. Right now, we don’t have any customers using it. It was only released in our June release about three weeks ago. And what I expect though, whenever we’ve discussed this directly one on one with customers, I get questions like, so, does this mean we could dot, dot, dot? And there are plenty of use cases. And a lot of them are about how do I as a more technical user, get my integrations to a point where I can hand them off to people that are less technical? So that’s really the point. I don’t know. I mean, for us internally, I’ll give you an example. We use Gainsight to handle customer success. And it does a lot of things. It’s a place for customer success managers to log their calls, to create follow-ups. We’re integrating to that, some of the telemetry about customer use of the products, just so we have a one-stop-shop. The Gainsight licenses are not cheap. And so we have this need for our VIP customers. We want to make sure that more stakeholders are engaged. So how do we, in a very seamless way, enable sort of for our top-tier customers, the customer success manages to deploy a flow that can get all this information from Gainsight and anywhere else into a forum like Slack, where more people, other stakeholders who might not have a Gainsight account could get to it? So maybe at the click of a button, a CSM could choose one of their VIP customers, automatically generate the Slack channel using the API to do so, automatically subscribe or invite to that Slack channel a standard set of [inaudible], integrate with Zendesk to pick up all the support tickets coming from that customer, plus whatever additional events that come in from Gainsight. And do that all themselves. Right? Today that would be– there’s no two ways about it, right, that would take a little bit of work to do, even if it is rinse and repeat. But I want to– I think this is an example where a customer success manager who’s not super technical, provided they have the right permissions and the right account, would just be able to hit the deploy button, make one or two selections going through a config wizard, which is another one of the possibilities here. And just deploy it instead of really having to handcraft their own integration. So that’s one real-world example that we’re looking at. And again, every conversation I’ve been in, there are more ideas like that that come up with our customers too. So looking forward to hearing what you might have in mind. So that was the last question. Just one statement. So everything you saw today is included in the current licensing. So there’s nothing here that you would need to change or modify your license to access. You should have access to it today. And with that, we don’t have any additional questions. So I’m going to do a last call while I thank Matt for his time and effort putting all of this together. Certainly hope you guys found the information useful. We’d love your feedback on these sessions specifically. They are for you. So we want to make sure you get as much value as possible out of them. So anything that we can do to make them more valuable, please give that feedback in the survey that you’ll get after the webinar’s done. So with that, I’m going to again, thank Matt. And thank all of you for your time today. Thank you all