Name: Celigo Spring Platform Update
Uploaded: 2025-05-21T16:16:09.192Z
Duration: 55 min 36 s
Description: Celigo Spring Platform Update

Transcript for "Celigo Spring Platform Update": Alright. We're live. Good morning, good afternoon, or good evening depending on where you are in the world. On behalf of all of us at Swango, I'd like to thank you for taking us the time today to join us for our platform update. My name is Dave Wallen. I'm director of platform product marketing at Celigo. And along with me today, I've got two of the best product leaders in the industry, Tony Curcio and Tyler Lamparter. You guys wanna introduce yourselves? Dave, I don't know if I could talk what you did. That was really generous though, but, yeah, I'll I'll try. Tony Curcio, my I'm able What was that, Dave? I said you're the best I know. How's that? Okay. Fair. Fair. That that helps qualify a bit and takes a little bit of the pressure off. So yeah. Tony Tony Garcia, senior director of product management. I lead our investments on the platform core, some of the work that we've been doing with API management, as well as artificial intelligence and a few other strategic projects, and very happy to be here today. Tyler? Yep. And I'm Tyler Lampard. I'm a product portfolio strategist here at Celigo. Help with pretty pretty much all aspects of Zaligo, and I'm sure you guys have seen me in various places on other webinars and community forums. So happy to be here and walk through what we've been doing the past three or four months. Alright. Yeah. So we've got a full agenda. We've got some great demos from Tyler. But before we get into it, a couple of quick housekeeping items. There's an attendee engagement bar on side of your screen where you can access the group session group chat, which a lot of you have already done. Submit questions through the q and a, and we prefer the q and a versus the, the session chat so we can manage those things. And you can view and download some other resources we've attached. We do encourage you, again, use that session chat throughout the webinar to drop your comments and share your thoughts with your fellow attendees. At the end, there will be a survey, which we do appreciate. You know, you're taking the time to share your feedback. It helps us to to create and make these better as we move forward. I guess, you know, let's just quick quick next yeah. Sorry. I'm I'm I'm moving on this one forward. Yes. So agenda. We're gonna start with a look at the most important platform updates from those last few releases, including the mapper two point o enhancements, our new Flow Builder UI. Next, we're gonna introduce you all for our brand new API builder, and that brings the intuitive Flow Builder experience to API development. We'll highlight some advancements we made in connectivity for the platform. We'll look at some things in the b two b manager product. I think that's it. Are we ready to get, started, guys? Yeah. Let's do it. Tony, take it away. Alright. Thanks, Dave. Yep. So I'll get it started with platform updates and and, Tyler and I will pass baton back and forth a bit as we go. So you would have seen in our March release, we introduced the next generation flow builder and, it's got this little interesting slider up on the top. So if you've been opening up, flow builder for the last two months and you're still seeing things that look like bubbles instead of rectangles, it's probably because you haven't slid that little new UI, component there. We've left it up there because we wanted to test and see what people thought and responses been great. So excited that we've been able to, not kind of force change on everybody, but let people slowly adopt the new UI. And again, let's see. Been great response we've had so far. Thank you and the channel for, the chapter. Yeah. And good to see some friendly names that we know, and I'll say good morning to folks as well. So, we in the, May release are making this the default for new users. So if you are a new user to the platform, you'll still have a little slider there. If you're an existing user, we won't force you on that, in this cycle. If you do have feedback, we would still love to hear from you on, what you have been experiencing, particularly if something's made you toggle it back. We've been doing a lot of follow-up with folks to just say, hey. We saw you flip it forward and then flip it back. Anything we should know. And so do please, feel free to give us that feedback. We'd love to get that as we go. So like I said, this is now the default user experience for the new flow, new builders into the environment. We will look to probably in q three, maybe q four, but maybe as quickly as q three, make this the only, builder experience going forward. And so we're working out plans of migration. My anticipation is by July, we'll we'll kind of flip the flip switch for everybody, and you will, still have again the opportunity to go back for a little bit. But, again, the response has been so positive. We just wanna make this the improved way to work. I did it on the fire screen. I won't go back. But, you know, there is some, new features. So you see, here even in this screenshot, there's a nice cloning feature. If you've configured a flow step and you say, you know what? I've just done the lookup to go get this thing and I need now I need another lookup to go get this other thing, or I've done my one update, now I need to do my other update, or I did an update on the other branch, I view an insert. You've probably set up most of the flow stuff what you need, and you really just need to do a small tweak to get the other one. Use that little clone feature, copy the flow stuff directly for you, put it just to the right. You drag and drop it anywhere on the screen you want to and do the little kind of couple of tweaks you need in order to get the additional or change functionality. It's a much more productive way to work. And, you know, we we do plan to do a lot more features in the UI. We'll start to see quite a bit of that coming out of the q three time frame. K. One of the, maybe more contentious features, I know not everybody loves AI all over the place, but this one, does have some benefits to it. So, as you click the new flow step create, you would have seen I think we launched this in April, so also here in the May release, is the, flow step suggestions. So, you collect select rather the application you wanna work with. And if you put in a name, we'll start to also filter down based on name, based on description, but even as early as just the application. What shows up on the right side of the screen, if you had a kind of question what that might be, is, flow step recommendations. So it's using all of the information that you've provided, the application, the flow step name, the flow step description, and you set up that combination to give you recommendations. So if we already know how to do something like a Shopify order, that will pop up to the top for you. It will have a match score based on how much information you've given it. Now, of course, you could just click next and go build the flow step however you would like to. But if you would like to get the benefit of these are already configured out of either our marketplace, things that we've built, from Celigo or other partners, that appear in the marketplace or from your own environment because you had built a flow like this last week. You had one of those flow steps. You don't necessarily need to go dig through all of your old flows to go find that. We'll bring that suggestion right up here to the front for you, and, again, help you to reuse things you've already built, use it as a template and modify as you go forward, or, again, get you from the marketplace things that we've built. So, hopefully, this is a great productivity improvement as well. Alright. Next set of things with, the, within Flow Builder context. We are standardizing any of the previews to be quite consistent. There's a little bit of variability in some of them had this feature, some of them didn't have. And so, progressively, this should be and now almost everything in the May release, where you have the line numbers as well as the expand collapse, for hierarchical constructs. So assume in the scenario that you have a long, payload of information, maybe a couple hundred lines. Obviously, there's some applications that give you back a lot of data like that or you may be constructing payloads like that. And you like to quickly look at areas. So this will give you the ability to just collapse down to just those areas of focus that you'd like to include and focus on. We, also recognize in the line numbers some advantages with even things like our office hours. If you haven't come to office hours, if you have questions, Tuesday afternoons, we run office hours every week. It's free. Anybody can join. You can ask any question. You just kinda get in line as you join. We keep an inventory of who's joined and when, and then we just go down the list and tackle one question after another. So this is in addition to things like support and the connective community where you can also ask lots of questions. Office hours has got folks like Tyler and myself, Kelly, and a bunch of the guys who here at Celigo just love to dig in. So, anyway, we're on that call and oftentimes we say, you see, like, online 18 that there's this particular field. That kind of collaborative work style, my numbers just makes a lot of sense. And, of course, you can imagine even setting something to your colleagues and say, yeah. I was looking at the preview. If you look down here at the office, other state online 19, again, you'll see what I'm talking about. Right? And so this just helps people to get that context. So we wanna make sure you're productive but also productive collaboratively and have better ways to work with data. Right? A very data driven enriched environment, want data to be as pervasive as a validation tool in your hands, you know, as any other tool you can work with or even better. K. You'll start to see us also, scrubbing a lot of the interface. So, you know, we're talking about really the spring, but, this is coming up in May. But in March and April, you would have seen a lot of progressive shifting of the the buttons look a little bit differently, the fields look a little bit differently, the highlighting looks a little different. We've been swapping out and upgrading our design system back end. And so we've been taking very standardized components to face lift to those components, and just rolling that out progressively across the the product at large. So, in May will be a very large push of where the design system components, show up. I would say everywhere, but it's actually not exactly everywhere. There's some long polls for upgrades to table layouts, upgrades to a few other areas of the product that you'll start to see in some of the other releases this year. But, you'll you'll you'll notice, you know, very specifically once well, if you're in Europe, you would have seen it yesterday. If you're North America, you'll see it tomorrow where, things just look a little bit sharper. A little bit crisper, a little bit more standardized as we get all of the design system components, excuse me, refreshed and put out across the product. So again, another, and Tyler, I'll I'll let you say, there there's one of these product features that I know you are a big fan of. You have been waiting for this standardization opens up the doorways to some other things. So, like, we don't talk about road map so much here, but, like, I do wanna tease out a bit road map. Craig, in office hour or in the chat has already teased it out. But, Tyler, you wanna take a second? Yep. So I'm sure I mean, this is kind of our most voted for feature. One in the older product board portal that we had available for people to vote on and see kinda what was on the road map. And now, I think Neri posted in the community for product feedback, again, for this particular feature and it instantly became the top voted for feature within a few hours. So and I'm sure most of you know it's dark mode and so this is one area of the product that we are working on to get, hopefully, sometime this year. All of the new design system rollout has been built in a way that it can easily, well, relatively easily be toggled on, for the entire system. So all the designs that we've been working on in the background, designers have been building out both light and dark mode, versions of them. And so it's been, pretty cool to see all the dark mode, visualizations that they've been working on. So that should be hopefully coming out sometime this year. But now I'm super excited and I know most users are as well. Thanks, Tyler. Yeah. I think, yeah, Tyler and I see the world differently. Maybe because I'm color blind. I don't know. But, yeah, I like light mode. He likes dark mode. So we'll be working collaboratively together in ways that we like the best. So looking forward to that. Alright. And, Tyler, I guess, you take it from here. Right? Yep. Yeah. I can take this. So one other thing we've done is kind of remove a lot of what we call snack bars. So the little notification that you get in the top right, which now in a new UI are in the bottom left. Historically, whenever we built out new things, we've maybe been overzealous in the number of notifications that we've been giving you, and a lot of them in particular aren't super helpful. So, basically, we went through a cleanup of, you know, is this snack bar really even helpful for users. So we've reduced a lot of noise by removing these. If you see any others that you particularly, you know, maybe don't find necessary, we can evaluate it. I think I found another one yesterday. So it's just it's constant, you know, when do we get more context users where it's helpful but not, you know, birding notifications for you when it's particularly not useful. So go on. The next one is the removal of developer mode. So this is in the May release that came out just yesterday and today. We've seen with the new so we've just released API builder earlier this year and API builder, you know, it was kinda coupled with the older my API term and functionality. And to use my APIs in the past, you had to toggle developer mode. And when we when we released API builder, you also needed to toggle developer mode to get to it. But now given that API builder is a pretty primary use case for a lot of companies and we want a lot of people to use it, it's super valuable. The toggling of this developer mode really wasn't useful for customers. It mainly only hid in the left navigation. It hid scripts and, stacks and my a p or, well, now API builder and APIs. And it didn't really hide anything on the flow canvas itself. So for example, if you if you built a script on the flow, you couldn't actually see it over in your left resources, pane. So it just kind of had it had a disconnect between I can do these things in the flow, but I'm like, you you know, I can't do it in the left I can't see my resource in the left navigation. So we just decided to remove it altogether. So that is removal of developer mode. And then one other one we've done in the past quarter is update the login page. I'm sure pretty much everybody that's logged logged in has seen it. We, you know, we allow customers to do single sign on using their own IDP into Celigo. But in order to do that, they had to basically bookmark a unique URL for themselves to log in. So they had either the main login page where they couldn't use SSO or they had this bookmark page. And then if they had interactions where you they're logging into community or they're logging into our support center, they would be directed to the login page but have no option to use single sign on to log in. So it basically forced you to go to the single sign on link, log in, then go back to, you know, Zendesk help center, log in. So the interaction point there was a little awkward. So what we did was change the login page to be just email address first. And after populating your email and clicking continue, it determines, you know, what is your method of login. From there, if you do have single sign on set up, it'll redirect you to your single sign on provider. If you don't have it set up, it'll just show the password field and then you, you know, put your password in and then you log in like normal. So this simplifies it a lot for people. In the cases where maybe your SSO provider is down, so there could be cases like in an admin situation where, maybe your IDP is down but you still need to get into Celigo. If you are SSO optional, there is a manual mode option to log in with the user username and password. And then there was on implementation. We didn't have, like, a certain tag added to, the username and password field. So a lot of we got some feedback where users browsers weren't auto filling their username and password like it was before, because the browser wasn't detecting it. We fixed that in the May release as well. And then mapper two dot o enhancements. So whenever you've been using pre built, imports and you've had to map in fields like, for example, I've had to map in creating Jira issues from from the new community based off the product feedback. We, you know, in our metadata model, we basically if you're going to create an issue, right, we have in our metadata, we know that these particular fields are required to create an issue in Jira, for example. But there were cases where maybe you'd go into the mapping and you didn't you didn't know everything that you wanted to map from the start, but you weren't able to basically save your progress at the time. You had to clear all your mappings or you had to make dummy mappings and then save and then come back and edit it or you'd lose all your progress along the way. So what we've done is we've added indicators that fields are required for that application, but we don't force it upon save. So now you can save your mappings, without mapping to all the required field. It was just a lot it was a great improvement for, by basically bypassing that requirement. And then there were certain times where cases in cases like Slack, for example, you know, it it would be like a conditional mapping where if I'm going to, like, a text block, it would have these required fields. But if I went to, just a plain text message, it would have these other required fields. And so Mapper wasn't set up to handle, like, conditionally required fields. So it would be a hindrance in those cases as well. Alright. And then, additionally, for databases and file providers, we've enhanced the, the default for when something is null. So typically, in mapper, if you've mapped to a particular source field and that source field is blank, it usually just drops the mapping to keep it more, it keeps the payload smaller. But in cases for, like, databases and for creating, like, CSV files and excel files, you typically need a placeholder. So for a database, right, you've got, you would either put, like, empty strings or no values into those fields or a CSV file. You'd have a, you know, you'd have a blank entry into that column, and then you'd move to the next column. So by dropping that field, you either had, like, a misalignment in the the ordering of values, or in the database case, you had to go through every mapping and set use null as default, in order to, you know, have the null or empty string in that default. So what we've done is whenever you're creating new mappings for these databases, we default it to instead of dropping the field, we'll default it to use null as a value for inserting. And then for file storage services, when you're going to a CSV or Excel file, it'll do that as well. So so it won't do it for, like, JSON or EDI or, x or XML, but for just those specific cases, it'll default to the users null. And then next, so we I'm not sure how many people have started using this yet, but, lookup caches has been a great improvement over the past quarter. So lookup caches, if you're not super familiar yet, they help you do many things. So basically, it's a storage table instantly go where you can store anything to to, to kind of improve your lookup. So I'll give a couple examples. One being, a lot of times you have to convert maybe, states to state codes or countries to country codes or a lot of in in a lot of cases, whenever you're doing order imports for maybe Shopify to NetSuite or your ecommerce store, Amazon to NetSuite, you almost always need to do some type of some type of lookup along the way for item, for example. And it's just a simple, like, skew to the NetSuite internal ID. And there can be cases where, you know, you got hundreds or thousands of orders and we're doing this lookup on five lines of an order on every order. So it's just it's just an inefficient process to have to do that lookup against NetSuite every time for every item, every order. So lookup cache really lets you make these more efficient. And so in the demo that I'll show here in a second, what I've done is, created a lookup table, basically, of all of my items in NetSuite and it's just a simple SKU to NetSuite ID mapping. That way, the flow itself, I don't have to use as much API or I don't have, as much API calls against NetSuite, which helps in my concurrency against NetSuite and what I have to pay NetSuite to, you know, increasing the concurrency that I'm allowed there. But it also just speeds up the flows a lot because you've just you already have this value in hand. You don't need to do all these additional API calls. And then so that's lookup caches. The enhancement here for May release that just dropped yesterday and today is you can now use lookup caches in, hooks within your flows. So you've been able to do lookups on, you know, flow steps, but now within a script itself, script hook, you can do, lookups against your cache table. So this could be for complex logic that you need to handle within a script, or really really if you just would prefer to handle it that way as opposed to a a flow step, this would be for you. And with that, I will go into a demo real quick. Stop sharing. And find the share button. There we go. Alright. Hopefully, you can see this, Tony. Yep. Yep. Looks good. Cool. Alright. So what I've done here is I've set up an integration for spring twenty twenty five updates. I have one flow here that is populating my cash table. So I've got two exports. One being getting items items from NetSuite and it's just a simple I'll preview here and get ID and SKU back. So I've got ID and I've got SKU. And this is mainly for my if I wanna run this daily, or weekly and then I've secondarily, I have a listener for listening for new items. That way, my lookup cache is always up to date. As new items are added into NetSuite, it's immediately added into my cash table. And on this import step here, I just have a simple, post to that cash table, with all the keys and values. If I go look at that cash table here on the left nav, you can see all my entries here. My key in this case is the SKU and my value is the NetSuite internal ID. So when I go over to my flow that's a Shopify order export to NetSuite order import, you can see I'm getting orders from Shopify. Here we go. I've got various line items here, and you can see these line numbers here that we've now put in. But you can see I've got line items. I've got the Shopify line ID along with the SKU. So in this case, SKU 123. When I head over into my transformation, again, you can use these lookup caches in transformation under, typical lookup step, lookup mapping. And then now in the scripts, in my preset page script, I have a function here to grab all the SKUs from, every order here in the data input, goes and fetches the keys for depth for that lookup cache, and then it maps all the results back in. So if I preview preview the data here and search for NetSuite ID, you can see here's the lookup result from the transformation and the same lookup result from the script. So we think this will be super valuable for people for complex logic, and you can use this as well in API builder and, the more classic, my API or JavaScript APIs. Awesome. And then lastly, we're supporting lookup caches in ILM. So as of today yesterday and today in EU and NA, you can now have snapshots and pools and merges for integrations that reference that are referencing lookup cache. And with that, I'll pass it on to you, Tony. Alright. Thanks. Yep. We'll move into API management. I knew I forgot something earlier and so I got my Celigo gear. So I'm ready for the rest of the conference now. So, yeah. So, we wanna represent. So we gotta represent. Okay. So API builder, was launched in, the mid, late March time frame. It's been enabled today in all plans, although, it's a special preview period for, standard license users. So if you have access to it, I wanna make sure that you're aware and, you know, there's a little header that we put out there. So everybody should be aware of that. Just like to make sure. And you'll see, it was launched with the old design system as far as the builder. So we call this API builder. You're not building flow, you're building APIs. But it is largely the same skill set you know and love from flow builder just, represented in a way that can build APIs. So a few new concepts, we'll go through the new concepts on the next page as far as what is this request bubble and the response bubbles. I will say it it does run-in a very purpose built API engine on the back end. So, flows run-in a way that is a a high level of sort of SLA resiliency where, transaction comes in. It gets processed by the first step. It goes to the second step. If there's an error, of course, we capture that error. We have all of our error management functionality. We do all the AI on that error to make sure that we can classify it correctly as as far as how we represent it. All of the things that we do with respect to retries and and such. Again, there's a lot built into the way flows execute that way. API is, well, and again, let me continue that. And you can go in and you could restart it from that point in time, and it will carry on. And it knows, of course, it finished the first two bubbles, so it will just continue on after that and auto resolve and auto, you know, retrial the things that we do around flows. That's a certain class of service. APIs is a different mindset. It is I have a piece of data I'm calling from either maybe another flow or I'm calling it from an external party, and you want to be able to respond to that user immediately. So let's say there is an error. Well, that user needs to know because they're building a web store, a front end, a partner, invoice, sorry, inventory check. Right? That response needs to get back right away. And, of course, you might need to give them error codes if it didn't go successfully. Let's say credential expired, etcetera. And so, the the resiliency of how that transaction gets managed, it's really a different contract you anticipate if it's a flow versus an API. So given that, the API is a very low latency engine that executes all of the flow steps as quickly as it can to either a successful outcome in which you get a nice response and payload, you know, affirmation that the update you tried to do was successfully applied or an error, and the error could be a customer that you've defined for when things go south, you know, and, of course, sometimes they do. And so, it it's good to keep that in mind. And now kind of you can combine the best of both worlds and say, well, I have a flow, and I would like at a particular flow step for it to do this chain of things in an API. And that could be, you know, set of two, three, eight, whatever you like. And it can include branching and other logic. And the flow will manage that granularity of, well, it got to this step. That step happened to be one of these API building things that I built. And the contract around it, because it failed, is I'm managing that failure in my flow. So, again, you can think about how these pieces can be combined to get you a I'd like this thing to run as a unit, and then I'd also like this level of service ability within my automation around how these things get pulled together. So, again, I I you know, we we really did design this to be very complimentary how they can execute. Okay. Now, API builder, you might have recognized in 2024, we launched API management as another part within the product. API builder doesn't, only come with API management. So if you have, Integrator IO, you have professional enterprise, you can do API builder. We have the API tokens as part of Integrator IO. You can say I've built a token, and I'm gonna give that to my web team, and they can use this API I built, And you don't get API management in that. You're just using API builder, its ability to build those APIs through our local approach, and you get security based on token. But a lot of organizations are looking for more than that. They're looking for, well, really like a developer portal that I can customize to my brand, or I'd like JWT tokens as a security model for my third parties. That's where API management kicks in, giving you that ability to socialize those endpoints to either internal or external developer communities, add additional types of government governance and security policies. So if I say API builder, I mean, use something like builder to build that API endpoint, and it comes with lightweight security, token based API management, all of those other things, which are those additional governance and management layers and custom portal, etcetera, etcetera, etcetera. So okay. So, what is API builder? Again, it's, you know, just like you know, but it's got a few new properties associated to it that are beyond what you would have in a flow. So it's a customizable endpoint. So if you've used listeners and things, we hard code give you a particular endpoint you can hit. This is something you can name. So it can be very specifically if you're familiar with the open API definition and swagger, pet store is the hello world of of o of open API. So, you know, you can have slash pet slash store slash office hours or whatever you'd like to have. Those are all nameable. It has versioning associated to it. So you could say this is v one of this particular API at this particular endpoint. You could define multiple methods through some of the other means within Celigo. We have basically post, but these could be get. They could be delete. So you've got all the variability on method. We have, logging, inherently built in, so you have a record to what was the API request, and what was the API response as part of your run history. And, the ability to generate open API spec like you would in a couple of other places within Integrator out, but, you know, we have very specifically here ability based on all you've defined with the get, with the custom URL, and the methodology within your other two nodes we're about to talk about, how that all comes together to form an open API spec that gets generated automatically out of your low code experience. Okay. So the request note is basically just what are we listening for, what is it expected to receive as far as path parameters, query parameters that works off that custom URL you've defined as one of its properties. And it will define the, then the, you know, in in a particular places like put or post, you have access to your body that you can define as well there. And then the response node, we define two paths automatically for you when you build a new API builder. Canvas, you get the success path, what would you like to be responded with, and the error path so you can respond in kind, when there is a failure point. So, again, everything else is basically like Flow Builder, run time aside, because, again, the API risk, that you build will run-in a low latency mode, very fast throughput, and ability to get to end very quickly. And then, of course, you have these additional components on needed to request for the response side. So you can return a payload, in addition to just the you know, again, if you hit an endpoint today, we would say, yes. We have received the request. This goes that step beyond to say, the request was received process through and got to this particular result. And so, again, these launched in March. It's available in everybody's plans. Professional and enterprise users go beyond the, trial period that standard users get. Okay. And then, again, in Europe today well, yesterday, North America today, tomorrow, I guess. This will also be available within a UI experience. So, we've, we let Flow Builder go first because we had so many people using Flow Builder, and API builder was the the fast follow on that particular point. So, this will also have the, flag to go back and forth if you want, but you, can, you know, continue now just working with new UI for both viewer experiences, flow and API. K. I think that was it on that. Yep. I will move on to connectivity. So some connectivity updates. Of course, every release, we've got tons of new and enhanced, connectors. In this case, I won't go through all these, but high level Amazon Business, Prime, ClickUp. I think we put, Discourse in here, which is, like, our new community as well. So we're constantly adding new connectors. And on the next slide here, if you have for if you ever need a new connector, and we can put this to the test here, but our team said we can get new connector up in two to four weeks. So if there is a connector that you see or that you're using that's not in the list and it has an open open API spec available or a good API documentation, just let us know. In community, there's a form. If you go into the product feedback category into the about section, there's a form here to submit a new request for an application, and we should be able to stand that up, very quickly. And then, additionally, if you have trading partner requests for b to b, like, for b to b manager, for example, we have been told the same thing there, two to four weeks for a new trading partner. As long as you've you know, you can provide the EDI spec doc, we should be able to get that up and going very quickly. Next, we've got a few key highlights for new connectors. Workday connector would be a large new highlight. So the Workday connector that we currently have was based off of the, HTTP framework, but they're, you know, Workday is, like, super complex and most people wanna interact with it in the kind of older SOAP APIs. The newer connector just has a ton more functionality for users. The older one's been renamed to Workday HTTP, and then this one has been renamed to just Workday. So if you're using Workday, I'd highly suggest checking out this new connector. It lets you interact with Workday in a SQL based manner, whether you're, you know, exporting data from from Workday just, via SQL queries and you can use Citibank.ai to help build those queries for you. And then when you're importing into Workday, again, also SQL based like insert and update queries there. And then next for NetSuite, we've got a enhancement here for supporting inventory details on a few new, or inventory detail sub record mapping. So some users can now if they need to go to inventory status change records as a sub record, you can now do that for those particular sorry. For the inventory status change record type, you can now do, inventory detail sub records for them. We've had a few customers that have had this requirement and now you can do it without needing a NetSuite hook. Additionally, we've enhanced this path to file URLs. So on under each export, you have particular cases where a response has a URL for for a file to download. Instead of having, like, an additional step that you need to do the look up, to go grab the file, we just have this this field in the export where you can specify the path to these file URLs and we'll just automatically download them and store them as a blob key, within that export data. Because there's a lot of cases where the images could be stored in different places. You can see in the screenshot here the base URL for it is in three different places. So you would have had to have, like, three different connections which would go against your license entitlement, which is just not a great, user experience especially for a file that's just publicly available to go download. So now this has been enhanced to accept JSON path. So instead of having to write out, you know, attachments zero, attachments one, two, three, four, five, you can now just have the JSON path itself and we'll loop through all of that automatically for you. The next is enhancing GraphQL. So I know probably a lot of people are being forced into GraphQL because of Shopify, pretty much forcing everybody to go into it. There were some weird quirks over on the GraphQL connector that we've, made better. So the query and operation name and variables fields, they historically were just a single line text field. And if you ever modified that text field within the main editor or sorry, within the main, like, import or export step, it would basically remove all the formatting that you had within that query or within your variables setup. So what we've done is converted this to a text area. So now if you edit it in line here within the main import or export set up, it won't basically break all of your formatting. And then if you, of course, open up the entire, AF editor there, you can edit your format and whatever you want, it'll be maintained. So this has been updated for exports and imports and on the connection form as well under the how do I test this connection page. And then next, we've got enhancements to s three connections. The s three connections have historically not had any concurrency setting for them. And so we've been fine trying to find all the connectors where we maybe don't have this concurrency setting, enabled, and s three is the next one on the list here. So now if you're doing anything with s three, you can set this concurrency up to, you know, twenty, twenty five, and have all of your imports and exports run faster. You probably you probably don't even need the auto recovery feature enabled. I was looking at s three documentation. I mean, their their API limits are, you know, incredibly fast. So 25 concurrency is never gonna hit the 3,000 a second that I think Amazon allows for. So next up, more Shopify GraphQL enhancements. Previously, whenever you were using GraphQL with Shopify, you'd have to use the generic GraphQL connector and then connect to your Shopify instance with a token. Now we've just built in GraphQL to the native Shopify connector. So you can easily whenever you go create a new connection for Shopify, you can choose GraphQL, and use the native connector. So this helps simplify licensing, because people were having to have, two different endpoints on the licensing. One for the generic connector, one for the rest API. So now all the licensing has just been consolidated together under the native Shopify connector. If you need to migrate, maybe from the generic GraphQL over to the Shopify connector, I did build out a template that I put in the marketplace for doing that migration. Basically, you just choose here's the connection. Here's my old connection. Here's my new connection. It'll go through all those exports and imports and move them over onto the new Shopify connector. So it should free up an endpoint for you, but also simplify, you know, what you're looking at actually seeing Shopify instead of the generic GraphQL. And yep. Same thing. Build a GraphQL GraphQL queries, the native connector. And then we have a migration tool. So if you haven't migrated yet to GraphQL from REST, if you go under into the playground area, there's a Shopify REST to GraphQL, tool to help you convert all of your exports and imports. So, basically, when you go in there, you'll see a list of your exports and imports, that are on REST API currently, and then we've used AI to help convert all those REST exports and imports into GraphQL. So if you give that a shot, if you haven't migrated over to GraphQL yet, it should get you pretty close to, pretty close to the finish line for migrating those over onto Graph. Next up, IBM d b two connector. Probably not super common nowadays, but we still have some, customers that, you know, everybody keeps legacy technology for a while. In this case, we can now support IBM d v two for those cases where you are still holding on to, this ancient technology. So the funny thing is I I was from IBM. So that that's Tyler's underhanded way to, like, jack me for the bark in the comments earlier. So touche, Tyler. Touche. Yep. And with that, I'm not even familiar with IBM d b two here. I assume a snapshot is like a table equivalent in, in IPF. Yeah. I was looking at this title. Actually, they they meant screenshot when they said snapshot. But, yeah, this is standard, as you would expect for any other database, SQL's NC compatible. And, we have the AI helpers to to write SQL, you know, which are aware of your metadata. They go out to the database, figure out what you're trying to ask for, and it goes figures out which metadata tables and columns will best meet what you ask. And then that's available for a variety of our connectors now and also applicable in this scenario too. And then last up is b two b manager. So b two b managers are offering for, doing a lot of transactions for with your EDI partners. So here are all the new connectors, eighty four Lumber, Big Lots, Michaels. And again, if you need more connectors or trading partners that we don't have on the list, just let us know, fill up the form, and we can get that up and going very quickly. Oh, that was another slide another slide of new connectors. And lastly, that's pretty much it. So we've got additional resources here. Builders hub, where you can see videos of various things on platform, the new lookup caches, for example, or blogs about, particular areas of Celigo, or how to do things just in the industry as a whole. Celigo help center, Celigo connective community, online trading with Celigo University, and then, of course, off tower. So all these are meant to help out. Community is great to have other people respond to stuff, answer questions, kinda just builds on, you know, if you run into one thing, somebody else goes in community, they can find the exact solution for their potential problem or blocker later at a later date. University for, you know, new users just getting into the platform, learning how to use Celigo. Then, of course, the help center for actual structured docs of how to use things in the in the product. And then the connective roadshows. We've got six roadshows this year. Two have already been done, New York City and Chicago. Tony had hosted both of those. I'll be in the Salt Lake City roadshow on June 4, and then we're figuring out here for Dallas, Toronto, and Miami the exact dates there and who's gonna be there. But I'd mark these for your calendars. Let us know if you can join, and we'd be happy to have you. Yeah. Maybe just another word on that too. It's a good, session to meet with your peers. It's about a full day event on-site. We, provide a nice lunch, of course, and a happy hour afterwards. So maybe if that's motivating. But the content is great. And so it's a bit of best practices. It's some deep dives into topics like the API builder and and b two b. So if you're not familiar with EDI and your company is exploring how do you optimize in that area, again, you'll have a a great, session. This thing has been manned by, some of our kind of North America Solution Consultants in those sessions. So, looking forward to, you know, them being able to repeat some of what we saw, a lot of interaction from customers and partners who are coming to these. Just to go deeper, gets the face to face time on the industry. And then, of course, birds of a feather lunches. So we did some deep dives on those topics including artificial intelligence as part of both the workshops as well as birds of its feather lunch round tables just to kind of discuss across the table what are your ideas, where are you going with these In in both directions, you know, us at Toledo, what are we seeing, and what are you exploring as part part of your organization? So, yeah. They've been great events. We're looking forward to doing a lot more of these. And like and I'll add add some more as well. Like Tony said, we don't typically do much road mapping on this session. But if you join us for these sessions, you might get some sneak peeks into, our next six month booking road map. So and then I think we do have one on here that we haven't maybe announced yet, Tony. One on here. Yeah. Oh, another city. Yep. Mhmm. Yeah. We're still exploring, expecting to get one in Hyderabad maybe next month as well. So, Tyler and I are actually both be in our India Lab working with the team on some workshops, and we thought, hey, what a nice time to maybe also get from there. Budget still being worked out on that one, but, maybe stay tuned. Yeah. Speaking of announcements. So, yeah, we're we were we're pleased to announce that, we we are once again visionaries in the Gartner Magic Quadrant. And big thanks to all of you out there for being great customers, for being great partners, but most of all, by engaging with us at formats like this and and the others, the connective and by, you know, by stretching your platform, by finding new ways to use it, by sharing your ideas and feedback because in the end, you're the most crucial factor, that grows, drove drives us to to create the platform and and meet Gartner's requirements because, really, we're meeting your requirements. So it's great news for us. Hope it's great news for you too because it's validation from Gartner that you've made the right choice and a tremendous choice, for your integration platform. You know, they actually said, so we mesh a customer centric approach with innovative integration technology solutions. We're building up you know, with a building future proof technology and AI driven automation that will help you to drive your business. And that's really what we're we hope to be is to help you drive your business forward. And, really, you know, we're we're we're pleased and proud, but it's thanks to you. So I think with that, you know what? Onto the QA. Alright. We had one, first one down there around, lookup cache. So if we have tens of thousands of SKUs, would it still be efficient to use lookup cache? What's the recommendation for when to use or not to use? So I think a little bit of background on how we've implemented lookup cache is I think we we're using if you're familiar with Redis cache, that's what we're using behind the scenes for for this lookup cache. So as far as efficiency and performance, it's about as efficient and as performative as you can get. It's built off exactly to do what you're doing, look up a key, get the value. So I would recommend it in almost all situations where you've got tons of lookups going on for semi volatile data. So I maybe wanna recommend it for highly volatile data such as, like, inventory numbers, right, that can change with just a simple order being imported or created. But I would do it for, you know, say, items or even, like, customers. I would do it where you're having to do lookups and it's just a simple, you know, ID to ID mapping. Again, it's very efficient. I would recommend it almost in all cases. Dave? Yeah. He asked one about the, API enhancement for required parameters and validation. We did spend some time in development thinking about this, Dave, and recognize that in our API management tool, we we have those capabilities already. Configuration based approach to, again, putting policies on your APIs and you could enforce required fields or not enforce. In API builder, of course, in the logic of your API, you can insert tests, which might be branch conditions, etcetera, to route based on things being or not being there. So, at this point, it's not one of our immediate things. We do have some other, you know, very high value things I think you'll like on API builder coming up in the next couple of releases, but that one is not on our immediate because we already have kind of the the way an API builder to do it and then the API management way who enforce it very specifically at the proxy tier where, you know, again, if you're getting into that level of maturity about your API program, might be a more interesting route for you. And feel free to reach happy to connect offline on that, Dave. Looks like there's another for API there, Tony. Clone APIs. Yeah. I did in the chat answer that, but I'll have to stay here too. So that is on our immediate road map where we're developing that actively. So introducing the same kind of ILM capabilities that we have for flows on APIs is is something we're working on. I expect it in, frankly, the August. I think I wrote the summer. Probably our August release is what it's targeted for. Disclaimer applies there as well, of course. You know, it's not a commitment. So I don't make purchase decisions based on that. I don't know that we have the, we don't usually talk again wrong map, but we probably should put the disclaimer on the front of these going forward, David, just case we had talks like this one. Yep. Alright. Instructions from legal. There we go. I think we provided the new connector link. Yeah. Attend Celigo training by instructor led training. Yeah. We we do have some great classes there. David, I don't know on hand have that link. I'm not sure if you can find that real quick. But, Swingle University, has a a master class. I think forget if I rename that one. Okay. But, Sumida, we'll we'll get that to you if we don't get it in the in the call here. And then, q and a. Alexia, you're in the background monitoring. Yeah. If we could post the q and a along with this too, that'd be great. I think we could do that. Alright. I think that's it for questions we needed to reply to. David, anything else you have? Yeah. No. Anything else? No. No. I was gonna say if there's no other questions, again, thank you so much for joining us today. Thank you for being the best customers, for providing us with the final feedback that we need to continue to to improve and innovate on the platform. Thanks for me. Tony, Tyler, any last words? Maybe I'll I'll just add one. If you thought the Gartner MQ q is good and as visionary, wait till the critical capabilities comes out. If you get that report to look for that, I'm very happy about the way that one looks for something new as well. That's a teaser, Dave. I'll I'll put that out there. On the, looks like there's one thing in the chat real quick. Page doesn't exist for connector link. You have to log in to community. It's under the product feedback category, which is behind, behind login. So if you see that, I think it gives you, like, a four zero four, but it has, like, a a login option there, and then you should be able to see it. Alright. I think we're good, Dave. Okay. Thanks, everybody. Alright. Take care. Bye. Ancient technology. Come on, Tyler.