Launchpad Live Community Call, Feb. 12

1 "Katie Cibulka" (3180363520)
00:00:01.899 --> 00:00:21.860
In today's digital landscape, you need both the power of custom solutions and the speed to deliver them. Building unique user experiences is critical, but it's often a deep engineering journey requiring specialized skills and time. But what if you could bypass that complexity for common UX needs? What if you could add powerful, high.

2 "Katie Cibulka" (3180363520)
00:00:21.860 --> 00:00:41.860
Quality UI functionality to your provider environments instantly. Introducing UX boosters on launchpad. We've created a curated catalog of pre built vetted, and approved components that you can publish with a single click. Find what you need and publish it directly to your provider environment. No setup.

3 "Katie Cibulka" (3180363520)
00:00:41.860 --> 00:01:01.860
No customization and zero coding required. This means instant enablement of new UX capabilities. The existing constellation custom component building tool.

4 "Katie Cibulka" (3180363520)
00:01:01.860 --> 00:01:22.436
Stop waiting! Start building better experiences faster. Supercharge your UX effortlessly. Explore the UX boosters catalog [email protected] slash UX-boosters.

5 "Tim Miranda" (1513945088)
00:01:22.436 --> 00:01:40.940
Awesome love it. Well, a great way to start off our 1st launchpad live for 2026. I'm Tim Miranda and want to welcome everybody here. This webinar this webcast is mainly targeted towards existing launchpad providers, but of course anyone is welcome to come and listen in and learn more about.

6 "Tim Miranda" (1513945088)
00:01:40.940 --> 00:02:02.220
What's going on with Launchpad. So why don't we get started? Alright, so I'm gonna introduce the folks that are gonna be talking today about some new features and cool experiences with Launchpad. We're gonna go over the new capability around parallel work processing, and then.

7 "Tim Miranda" (1513945088)
00:02:02.220 --> 00:02:22.220
We had talked in a previous webinar about the new agentic capabilities and launchpad, and we're gonna talk about how you can use those in landing pages. And then finally we're also talking about the new support for webhooks so that you can integrate with popular 3rd party services and use them directly from your launch.

8 "Tim Miranda" (1513945088)
00:02:22.220 --> 00:02:56.450
Launchpad workflows. We'll take some questions at the end, so please, as the webinar is going, feel free to ask your questions, and then we'll go from there and we'll talk about some upcoming events as well. So like I said, I'm Tim Miranda. I am a part of the launchpad provider's success team. I'm joined today by a couple of our product managers from Pega Product, Chloe Lowe and also Varun and I here. Very excited to have them here today. So why don't we get rolling?

9 "Tim Miranda" (1513945088)
00:02:56.450 --> 00:03:04.782
So Chloe, welcome. Thanks for joining us. Let's talk about this parallel work processing.

10 "Chloe Loh" (329978368)
00:03:04.782 --> 00:03:07.402
Glad to have you here. What.

11 "Tim Miranda" (1513945088)
00:03:07.402 --> 00:03:12.579
What are we talking about here? What, what is this problem this feature trying to solve here?

12 "Chloe Loh" (329978368)
00:03:12.579 --> 00:03:27.240
So this feature really provides a simple way for us to execute the same process across multiple different items, whether the process needs to, whenever the process needs to run independently as well as in parallel.

13 "Chloe Loh" (329978368)
00:03:27.240 --> 00:03:47.040
So you can imagine that there are many real world scenarios where you might need to create the same tasks for multiple different users or components within a case. So each of these tasks should be able to progress at their own pace. E.g., one task can be completed quickly while another might take a little bit longer and the system needs to be able to track them all independently.

14 "Chloe Loh" (329978368)
00:03:47.040 --> 00:04:07.040
So previously, yeah, previously modeling this kind of behavior really requires us to use child cases, which is a little bit more complex making the workflows a little bit harder to understand since they are outside of the main case itself. So we hope that this feature will help to make this, this requirements.

15 "Chloe Loh" (329978368)
00:04:07.040 --> 00:04:13.965
Simple simpler for us to actually handle. So yeah.

16 "Tim Miranda" (1513945088)
00:04:13.965 --> 00:04:40.044
So, so I see here you you're using like a reimbursement use case here. So for each of the charges, it looks like it's spinning off work for each for each thing. Can you tell us a little bit more here once these things are done and they're, they're done in parallel, maybe worked on by different people and stuff like that, are there what are the options around moving the case forward from there?

17 "Chloe Loh" (329978368)
00:04:40.044 --> 00:05:06.929
So there's two main options for us to move the case forward at this point of time so they are caught the all or any options. So basically when an all is selected, the case will wait for all the different sub processes within the case itself to be fully completed before moving forwards. So this is very, very useful in scenarios where like in approvals where you need every single one independent of approval to provide that approval before we can move on with the case.

18 "Chloe Loh" (329978368)
00:05:06.929 --> 00:05:26.929
So the other option is any. So when that is selected, the case will move on as long as one of the sub processes that has been spun off is completed. And all the remaining other sub processes that have been initiated will be automatically canceled. So this is useful in situations such as incidents.

19 "Chloe Loh" (329978368)
00:05:26.929 --> 00:05:39.759
Response. So when one team member has already taken action for that particular incident, then it NO longer needs to bend it. So all the other sub processes that has been spun off can be removed.

20 "Tim Miranda" (1513945088)
00:05:39.759 --> 00:05:58.129
Okay, cool. Yeah, so this this looks super useful. I've done this kind of pattern before with like parent child cases, but I like this because it really lets you just pull in the right people to kind of do whether it's approvals or do some work on the case and they can work.

21 "Tim Miranda" (1513945088)
00:05:58.129 --> 00:06:16.576
Independently on it, and it looks like you can also do that with multiple things or or objects in the case as well and kind of a process around against each one. Do you expect sort of in the future that there might be, more options with this feature coming?

22 "Chloe Loh" (329978368)
00:06:16.576 --> 00:06:53.098
Yeah, definitely. So we want to continue to be able to expand on top of this feature. So, one enhancement might be the ability to support different kind of sub processes and to get them to all run at the same time. So currently now we need to spin off the same task for each item at least maybe we can consider abilities to have different processes for different tasks. And another enhancement is to include more flexibility in terms of the joint condition. We talk about all and any just now, but we might want to have when conditions for you to have more flexibility in general.

23 "Tim Miranda" (1513945088)
00:06:53.098 --> 00:07:03.038
That makes sense, yeah. Being able to maybe define a decision rule that says, you know, when a majority of people approve this or or selects a certain condition.

24 "Chloe Loh" (329978368)
00:07:03.038 --> 00:07:04.141
Then the case.

25 "Tim Miranda" (1513945088)
00:07:04.141 --> 00:07:18.175
To move forward or the case will get rejected, that really lets you model the exact processes that you need. Well, that's really cool. Well, thank you for introducing this. I've actually started to use it with one of my providers already, so.

26 "Chloe Loh" (329978368)
00:07:18.175 --> 00:07:20.001
Exciting.

27 "Tim Miranda" (1513945088)
00:07:20.001 --> 00:07:26.277
Alright, so why don't we, why don't you stick with me Chloe cause we're also gonna talk to you about our next topic as well.

28 "Chloe Loh" (329978368)
00:07:26.277 --> 00:07:27.674
Okay.

29 "Tim Miranda" (1513945088)
00:07:27.674 --> 00:07:35.343
So tell me about this here. This is agents and landing pages. What what's the big thing that's new here in launchpad?

30 "Chloe Loh" (329978368)
00:07:35.343 --> 00:08:07.029
So the big change in this particular agent is compared to what you have learned before about agents I'm sure in some of the webinars here is that previously agents were only available within object views itself, so where their role was limited to helping the users to understand or to act on their specific one case. So the big change now is that the agents can NO longer have to operate within a certain case or business object and states they are now exist on application level and can.

31 "Chloe Loh" (329978368)
00:08:07.029 --> 00:08:32.899
Help the users even when they are not working within a certain case itself. So they now serve as general public assistance for the whole application as a whole. So, basically this helps to create a lot of new possible interaction patterns where we can imagine helping users initiate common process from say the homepage and guiding them to the right workflows and answering questions about what actions they can take.

32 "Chloe Loh" (329978368)
00:08:32.899 --> 00:08:35.119
Okay.

33 "Tim Miranda" (1513945088)
00:08:35.119 --> 00:08:50.279
Cool. Yeah, so I see here like in this kind of use case, you have, an agent right on the the homepage on the dashboard when someone logs in and they're not just talking to them about purchase requests, but the other workflows involved in this kind of application.

34 "Tim Miranda" (1513945088)
00:08:50.279 --> 00:09:10.279
The user can interact with the different workflows, the data. So, you know, I've used our agent capabilities in, in my cases, so in the case displays, I built I built apps where the user can go and interact with the case itself. When I'm evaluating.

35 "Tim Miranda" (1513945088)
00:09:10.279 --> 00:09:25.436
Agentic workflows and and kind of conversational aspects of my application. What would, what are kind of like the patterns I look for to choose whether I wanna have the agent directly in my case versus this kind of thing where I have it in a landing page?

36 "Chloe Loh" (329978368)
00:09:25.436 --> 00:09:50.649
Yeah, so the case difference really comes down to whether the user is trying to work from within a case itself or interacting more broadly with the application as a whole. So object agents are designed to access users within the context of a specific case. So imagine if they want to ask detailed information about the case itself or want to perform specific actions in that specific case, e.g., being able to transfer assignment in the case itself, then.

37 "Chloe Loh" (329978368)
00:09:50.649 --> 00:10:10.649
I would want to use the object level agents. On the other hand, landing page agents are more useful to assist users outside of a specific case. So they are ideal for getting users to get started, understanding how a case type as a whole, what the workflows are being able to navigate the application as.

38 "Chloe Loh" (329978368)
00:10:10.649 --> 00:10:26.235
So, a simple way to think about it, if the user is already inside case, then to use a object agent. If the user is on the landing page then and needs help getting started on initiating work, then use a landing page agent.

39 "Tim Miranda" (1513945088)
00:10:26.235 --> 00:10:32.759
Cool, it makes a lot of sense. Yeah, I I know in a previous webinar we had introduced the.

40 "Tim Miranda" (1513945088)
00:10:32.759 --> 00:11:01.206
The concept of agents, the conversational agents, and agentic workflows here. So seeing it extended here where it's something that you can use from a landing page, from a dashboard, gives me a lot more options as, as a developer, so this is pretty cool to see. What so what kind of things are coming in the pipeline here, around agents using them in landing pages? What can I be looking forward to?

41 "Chloe Loh" (329978368)
00:11:01.206 --> 00:11:30.849
So this release really builds the foundation for landing page or application wide agents, and we want to make sure that their capabilities continue to grow with time. So one area might be expanding the type of actions that agents can perform, so today our agents can initiate actions such as creating case types and whatnot from their landing page itself, but we want to make these tools easier to configure and more seamless and more powerful in the future. We will also want to continue making sure.

42 "Chloe Loh" (329978368)
00:11:30.849 --> 00:12:03.289
We can better integrate agents across the whole applications. So when you switch between landing pages as well as a particular case, how do we make sure that the switch itself is seamless and easy to configure? And finally, one very important area is the ability to chat with data. So, in the future we want to make sure that we are able to do that more efficiently, so you can imagine the landing page agent being able to answer high level questions, provide summaries or insights into all the different cases you have in the application.

43 "Tim Miranda" (1513945088)
00:12:03.883 --> 00:12:23.509
Cool. So when I'm, when I'm configuring an agent here, say for landing page, what are the kinds of things I should think about in terms of sort of the, what I tell it, where do I get like the preloaded data versus something that might be a tool to, to get more knowledge about something versus an action tool?

44 "Tim Miranda" (1513945088)
00:12:23.509 --> 00:12:29.416
So, you know, how, how do I think about the differences between those things?

45 "Chloe Loh" (329978368)
00:12:29.416 --> 00:12:55.349
So are there's several sets of different configurations that you can have within an agent rule itself. Number one is the set of data that you want it to have access to. So within an object you will be giving them access to a specific specific case while within a landings page agent, what you'll be doing is to give them access to a list of different cases or a list of different case types.

46 "Chloe Loh" (329978368)
00:12:55.349 --> 00:13:15.349
As well. Other than that, we also need to think about how is it that we configure the tools. So the tools really is what are the different actions that this particular agent can to perform. So you will be able to set exactly what tool or what actions this agent can perform, so one such action could.

47 "Chloe Loh" (329978368)
00:13:15.349 --> 00:13:29.839
Potentially be creating a new case, another can be updating the case itself. This also makes sure that because you configure it yourself, you make sure that you restrict them from performing actions that you do you do not want them to perform.

48 "Tim Miranda" (1513945088)
00:13:29.839 --> 00:13:46.969
Got it. Yeah cool. So this this looks great being able to not just use them case displays, but add them to our landing pages and you can have certain personas have access to an agent in their landing pages and maybe other personas that don't need it. You know, so you.

49 "Tim Miranda" (1513945088)
00:13:46.969 --> 00:14:14.695
We have a lot of flexibility there and be able to get at all the different case types and data types from that landing page agent, gives me a lot of options here. So cool. Well, I appreciate your time. Thanks for introducing this for us. I'm sure people are gonna start playing around with it and adding this to their existing apps because they have the case types, they have their workflows, they can layer the agents over very easily. So thanks Chloe. Appreciate it.

50 "Chloe Loh" (329978368)
00:14:14.695 --> 00:14:16.406
This team.

51 "Tim Miranda" (1513945088)
00:14:16.406 --> 00:14:41.522
Cool. All right. So let's go over to webhooks here, very exciting new feature that's getting introduced. Varun, thanks for joining us. Tell me about webhooks, why did we introduce this and and what do they do? Varun, you maybe muted here, just to double check that.

52 "Varun Nair" (3373747200)
00:14:41.522 --> 00:15:15.579
Yep, thanks. We got you. Thanks Tim. So the applications that we are building would have to increasingly kind of interact with external applications as well. Let's take a few examples like you have a loan customer onboarding for a loan application. At some part of the flow, you would want to delegate the the contract signing responsibilities to a provider like DocuSign, right? And DocuSign would keep informing us about the status of the the signature verification and all. And they would do.

53 "Varun Nair" (3373747200)
00:15:15.579 --> 00:15:35.579
That through webhooks, right? Another example would be that you create a cart in Shopify and then you create an order, right? And we have created an application that would take care of fulfilling that order in terms of managing inventory, creating shipping etc. You would also want to have another part of that appli.

54 "Varun Nair" (3373747200)
00:15:35.579 --> 00:15:55.579
Application which takes care of managing the customer reward points etc. Right? So normally what one of the, the, the major protocols that are used for this is webhooks, which are essentially HTTP post requests that are given to us, right? So this particular feature allows launch.

55 "Varun Nair" (3373747200)
00:15:55.579 --> 00:16:15.579
Applications to receive external event information through webhook request, which means we actually get a HTTP post along with data associated to that event. And then we can configure on the launchpad side one or more actions we take to be done, right? So that's fundamentally that what this feature.

56 "Varun Nair" (3373747200)
00:16:15.579 --> 00:16:32.240
That provides it's it allows us to react to external events from external applications. We can make our applications more autonomous because we are automatically taking these actions, we can reduce manual interventions by, by adopting this feature.

57 "Tim Miranda" (1513945088)
00:16:32.240 --> 00:16:52.309
Cool. Yeah, I, had done some work with DocuSign for a provider a little while back and yeah, I think this is great cause cause the traditional way to to interact with that kind of service would be like polling, so having to periodically reach out to that service and say are you done with the work yet? And now, now with this web.

58 "Tim Miranda" (1513945088)
00:16:52.309 --> 00:17:16.201
Capability sounds like we can have a lot more efficient interaction here where the service can reach back to Launchpad and and let us know when it's completed something. I see as, as, you know, you were talking about this that we have two rule types here that have been introduced, the event trigger and the event action. Can you tell me more about the the differences between those, how they work together?

59 "Varun Nair" (3373747200)
00:17:16.201 --> 00:17:31.549
Yes, yeah. So there are two aspects of the use cases that I saw told. One is how do we configure our applications to receive HTTP post requests from outside? And this has more to do with the elements of an HTTP request like.

60 "Varun Nair" (3373747200)
00:17:31.549 --> 00:17:51.549
HTTP, the request body, the request headers, the URL, and the data itself comes either as a, as a JSON or you form URL encoding. So we we in this particular event trigger rule, we configure aspects of the, the URL aspects of.

61 "Varun Nair" (3373747200)
00:17:51.549 --> 00:18:30.917
Transforming that plain Json data into a, into a data type that we can launchpad can process. So that's the event trigger part. Event action allows you to kind of subscribe to a trigger, which means that for a given trigger there can be more than one action and they're like totally decoupled, right? So event trigger happens and it stops there and then there are multiple event actions. They are totally independent from each other. Like one action can fail, but that doesn't mean that the other would fail, right? So, so that kind of a decoupled nature, this is a common public publisher subscriber patterns that we use in application development and and that's how this is implemented.

62 "Varun Nair" (3373747200)
00:18:30.917 --> 00:18:41.416
So that's why we have two rule types, one for the the configuration part of receiving a trigger and the other to define different application behaviors when, when this particular event happens.

63 "Tim Miranda" (1513945088)
00:18:41.416 --> 00:18:57.800
Gotcha. Yeah, that's cool. So when it comes to event actions, a simple one I can think of is like creating a case or creating a data record based on the response. Are there other kind of actions currently supported or coming in the pipeline?

64 "Varun Nair" (3373747200)
00:18:57.800 --> 00:19:16.969
We we have started with create cases, so the only action that's supported now is that you can create cases and using those cases kind of you can kind of do a lot of other things like updating other, other objects etc within on this one, yeah. But I mean, we would kind of eventually increase this to support more things that we already support.

65 "Varun Nair" (3373747200)
00:19:16.969 --> 00:19:19.040
Through DXA PS.

66 "Tim Miranda" (1513945088)
00:19:19.040 --> 00:19:36.389
Okay. No, yeah. I I think the ability to create a case makes it easy for me as a developer because I can have a workflow that sort of its purpose is to respond and like deal with the response from the service, maybe update some records, update some other cases, things like that.

67 "Tim Miranda" (1513945088)
00:19:36.389 --> 00:19:53.697
So yeah, that that's pretty straightforward. Cool. So, and then do we expect any other, so there's the event actions, right? And then, event triggers. Do we expect any additional kind of trigger support in the future as well? Yeah.

68 "Varun Nair" (3373747200)
00:19:53.697 --> 00:20:16.389
So we we have started with webhook requests, webhook events, but a lot of other I mean there are other ways also of publishing a change by external applications like an email, right? So we can create email listeners, file listeners where we need to be intimated when a file is loaded at a particular location and events doesn't necessarily have to be external. We can have internal events like we can publish when case change.

69 "Varun Nair" (3373747200)
00:20:16.389 --> 00:20:38.226
Changes like case status changes, case stage changes, a data is updated. So having a robust system of events can kind of make our application more, more kind of autonomous and automated, right, in terms it these kind of changes drives the application without manual intervention. That, that's the, that's the vision that we have related to this.

70 "Tim Miranda" (1513945088)
00:20:38.226 --> 00:20:58.279
Yeah, makes sense. Yeah, so this is cool. I like I like what I'm hearing here. I've I've had I've integrated with several services like that, like we said, DocuSign and some others. I like that this kind of decouples the actual workflow from responding to the events and actually doing the initial API.

71 "Tim Miranda" (1513945088)
00:20:58.279 --> 00:21:29.869
Guy call and stuff. So it's a it's it's easier for me to think about as, as a developer, so this is cool. And having the independently defined event actions so that an event can be triggered and, and multiple other things can happen, also makes it so that I can kind of think kind of workflow centric here instead of really thinking about orchestrating the integration, which is great. So, yeah, looking forward to using this one as well. I haven't had a chance to try it, but it's it's live in the product.

72 "Tim Miranda" (1513945088)
00:21:29.869 --> 00:21:37.263
So I will take a look very soon. Thanks for I really appreciate your time and this is a cool new feature.

73 "Varun Nair" (3373747200)
00:21:37.263 --> 00:21:40.301
Thanks. Alright.

74 "Tim Miranda" (1513945088)
00:21:40.301 --> 00:21:48.777
Cool. All right, so I think now we can take any questions that might have been offered by the audience.

75 "Katie Cibulka" (1145779456)
00:21:48.777 --> 00:21:49.324
So ok.

76 "Tim Miranda" (1513945088)
00:21:49.324 --> 00:21:51.921
Yeah, I don't know if we have anything on the docket here.

77 "Katie Cibulka" (1145779456)
00:21:51.921 --> 00:22:00.562
We do. So we had a question, does the webhook, does it support JSON responses?

78 "Varun Nair" (3373747200)
00:22:00.562 --> 00:22:35.444
Yeah, so so the request body can be Json or form URL encoded. We give a standard response to be provided when we get the request back to the provider with a status code. That cannot be dynamic. E.g., DocuSign sends us that customer signed document, right? We can always configure the event trigger to respond with 200 and a message, ok, right? But we would be looking at how much more dynamic we can make the response like adding some more case related data to that particular response that we give, right?

79 "Tim Miranda" (1513945088)
00:22:35.444 --> 00:22:37.044
Cool.

80 "Katie Cibulka" (1145779456)
00:22:37.044 --> 00:22:48.807
Chloe, a question for you on the agents, how does the agent determine which data to use when answering summarization questions?

81 "Chloe Loh" (329978368)
00:22:48.807 --> 00:23:08.869
Yeah, so, so the landing page agents themselves do not actually automatically inherit context from the UI, which might be something that people expect. Instead, the data that the agent can access to is explicitly configured by the app developers in the agent blue itself. So.

82 "Chloe Loh" (329978368)
00:23:08.869 --> 00:23:25.799
So this means that the agent will only have access to the data that you give it access to. So our developers have full control over it and agents will not be able to access information in your application that you have not given the access to.

83 "Chloe Loh" (329978368)
00:23:25.799 --> 00:23:29.804
Great.

84 "Katie Cibulka" (1145779456)
00:23:29.804 --> 00:23:39.024
And then, just on the parallel work processes, how does this feature differ from using child cases and when do we use each?

85 "Chloe Loh" (329978368)
00:23:39.024 --> 00:23:54.099
So both of them are similar in the sense that import create parallel processes or parallel work, but they are really designed for different situations. So this particular feature is suitable for more lightweight parallel processes that operate.

86 "Chloe Loh" (329978368)
00:23:54.099 --> 00:24:21.229
Within the same case because what it does is to allow you to spin off assignments for each item at least while comp encapsulating them within the same case life cycle still. So child cases on the other hand are better suited for more complex workflows where you expect the workflows itself to require its own life cycle. So multiple different stages, multiple different processes and different assignments. There will also be great when you want.

87 "Chloe Loh" (329978368)
00:24:21.229 --> 00:24:47.141
To actually spin off like hundreds of different tasks at the same time, so because they will be easier to track from say a landing page or inside page. So as a general guideline, use this feature when you want to highlight small groups of assignments within the same case and child cases when you expect a larger unit of work or a huge number of units of work. That's all.

88 "Katie Cibulka" (1145779456)
00:24:47.141 --> 00:25:01.003
Okay, another question for you, can we use events triggers for case urgency? So e.g., if you change the urgency based on the up connect based on the update case.

89 "Varun Nair" (3373747200)
00:25:01.003 --> 00:25:24.939
Yes yes. So, if your use cases that when when we receive a trigger event gets triggered, we want to update the urgency of a case, right? We can do that. The thing is that the action that is supported is creating a case. So we can create kind of a triage case that's that the only thing that does is call an automation and, you know, up updates the, updates the urgency of.

90 "Varun Nair" (3373747200)
00:25:24.939 --> 00:25:40.745
Another case. Th that's that's one one way of doing it because case creation is only action we support. Going forward if we support say case wide actions, right? That that can be leveraged to do it in a more simpler way, but today we have to create a triage case.

91 "Tim Miranda" (1513945088)
00:25:40.745 --> 00:26:03.122
Yeah, I think having having to kick off a new workflow is useful too because an event action may actually be like multiple steps or set of processes. So being able to create a case that then goes and updates another case's urgency and maybe create some data records and things like that would be useful anyway, so that makes sense.

92 "Katie Cibulka" (1145779456)
00:26:03.122 --> 00:26:17.923
All right. Another question for you about agents, the agents and landing pages. Is there anything that developers should be doing differently with their application design now that landing pages are available? Sorry. Yeah I.

93 "Chloe Loh" (329978368)
00:26:17.923 --> 00:26:36.739
I think with landing page agents, we really introduce a new way for users to design their applications and for users to, well, for our developers to design their applications, for users to be able to initiate and interact with workflows in the applications. So traditionally when a user come to.

94 "Chloe Loh" (329978368)
00:26:36.739 --> 00:26:56.739
The application they need to try to figure out how best to actually use the particular application, what you can do, what are the things that needs to be done. However, with agents, we can use them as basically a toll guide and allow them to to allow users to ask them basically how do I use this application? Why.

95 "Chloe Loh" (329978368)
00:26:56.739 --> 00:27:16.153
What is the, what can I do here? What when I want to do something, what is the best way to do it? So this basically allows any pages to not just serve as simple navigation hubs, not just as insight providers as well but intelligent assistance as well.

96 "Katie Cibulka" (1145779456)
00:27:17.520 --> 00:27:30.443
Great. All right, one more question here for sorry for a room. Will we have out of the box event triggers as part of platform?

97 "Varun Nair" (3373747200)
00:27:30.443 --> 00:27:57.719
Hi, so this is a, this is a foundational framework as well on top of which we would be able to add lot of out of the box event triggers for common services and applications that we would want to integrate like say Webex, DocuSign, Twilio, payment gateways, et cetera. And that would mean that as provided providers, you would be able to kind of easily use them, reduce your application development time in terms of.

98 "Varun Nair" (3373747200)
00:27:57.719 --> 00:28:13.064
Creating those triggers, testing them etc. All you would have to do is configure the an existing trigger for your specific subscriber use case and then start creating actions. So that's the plan. Makes sense.

99 "Katie Cibulka" (1145779456)
00:28:13.064 --> 00:28:18.323
All right. I think that's all we have for now. Tim, do you want to wrap up?

100 "Tim Miranda" (1513945088)
00:28:18.323 --> 00:28:37.439
Cool, yeah, let's wrap up here. So I want to remind folks, that there's lots of other enhancements and new stuff going on in launchpad almost on a daily basis at this point. If you go to launchpad.io and the resources and the documentation, you can see the release notes, a lot more details about.

101 "Tim Miranda" (1513945088)
00:28:37.439 --> 00:28:55.349
Changes, new capabilities, things like that along with the help documentation. And we have some upcoming events coming, so we have the next launchpad live coming with even more stuff on 26 March.

102 "Tim Miranda" (1513945088)
00:28:55.349 --> 00:29:15.089
And then we got a couple of new ones coming that we're excited about a new series here, it's a provider spotlight, so on 12 March, we're gonna be talking with about how they built an AI 1st inspection solution directly in launchpad. And then 24 March, we're gonna be chatting with about their.

103 "Tim Miranda" (1513945088)
00:29:15.089 --> 00:29:31.649
AI 1st payment investigations application that they built in Launchpad as well. So very excited to to be able to talk with them coming up in March. And of course follow us on LinkedIn, so you'll be able to see as these new events are coming up and check out our other resources on launchpad.io.

104 "Tim Miranda" (1513945088)
00:29:31.649 --> 00:29:49.696
Thanks everybody for joining. Appreciate it.