Launchpad Live Community Call, May 7

1 "Tim Miranda" (529138432)
00:00:04.139 --> 00:00:24.199
Hi, welcome folks. I'm Tim Miranda and we're here with the Launchpad live community call for May 2026. Glad to have you here. The target audience for this webinar is existing launchpad providers, but of course if you're new to Launchpad or exploring it, you're welcome here. We're gonna talk about platform.

2 "Tim Miranda" (529138432)
00:00:24.199 --> 00:00:44.199
Some enhancements, things like that. Of course you should check out launchpad.io for more information about the platform and upcoming events. We do have some exciting upcoming in person events that you should check out on our events page on launchpad.io. Most importantly we'll be at Pega World this year.

3 "Tim Miranda" (529138432)
00:00:44.199 --> 00:01:04.199
So if you or your colleagues are attending peg world, definitely register for the launchpad session. Lots of cool stuff and content happening there. We have provider panels so you can see what other companies have accomplished with Launchpad. We'll have awards for providers and other sessions and a whole lot more, so definitely check that out.

4 "Tim Miranda" (529138432)
00:01:04.199 --> 00:01:24.199
All right, so let's walk through what we're gonna talk about today. So, I'm gonna introduce our new agent skills that we have published to GitHub that let you do cool stuff to extend the platform and customize things by by coding them using our clause.

5 "Tim Miranda" (529138432)
00:01:24.199 --> 00:01:39.330
Standard skills. And then we're gonna talk about several developer productivity enhancements and tools that have been introduced recently, and we will walk through those all at once. And then finally we'll go through some.

6 "Tim Miranda" (529138432)
00:01:39.330 --> 00:01:57.450
New capabilities around agent to case processing and keeping track of of agent conversations and being able to see what's going on with those and then go from there afterwards, we will of course, we'll do Q and A throughout this session, you'll see some things being posted to the chat. If you have.

7 "Tim Miranda" (529138432)
00:01:57.450 --> 00:02:16.380
Questions, just post them in the chat or the Q and A, and we'll get to them at the end and of course you can also follow up with us through launchpad.io if you think of something you want to find out about afterwards and then we'll just talk about some other upcoming events that are happening. Alright, so with that.

8 "Tim Miranda" (529138432)
00:02:16.380 --> 00:02:36.380
Introduce who's here today. So I'm Tim Miranda. You may have seen me at prior webcasts and webinars. I'm a solution architect with the launchpad provider success group here. I have two speakers today, Allie who is a software engineering manager is part of our launchpad services organization at engineering and.

9 "Tim Miranda" (529138432)
00:02:36.380 --> 00:02:59.700
I have Rodhik who is joining us as a product manager, in our case management area of the platform. So excited to have them here show off some of the new stuff. All right, so why don't we get going here? So I'm gonna cover this one. So we recently published to Pega Systems GitHub.

10 "Tim Miranda" (529138432)
00:02:59.700 --> 00:03:19.700
Account, a new repo here called Pega launchpad agent skills. And what this is, is a set of cloud skill files that you can use with any of your vibe coding tools that you may have that understand agent skills. So it's not just cloud of course but anything that can work with those. You.

11 "Tim Miranda" (529138432)
00:03:19.700 --> 00:03:51.890
Use it in whatever idea that you're using. I use these in, in things like VS code, but, you know, whether you're using IntelliJ or even just command line, these will work. And these let you, they really help you in building out kind of custom things that you might want to extend the platform with. So, whether that's custom UX components that you might wanna cook up, custom functions that are written in Python or Java Java or node.JS that you wanna integrate in.

12 "Tim Miranda" (529138432)
00:03:51.890 --> 00:04:11.890
Or things like that. These really accelerate that process so that you can follow best practices and can guide you through that conversationally in your favorite vibe coding tool and really quickly get something that you can drop into your launchpad application to have that customized experience.

13 "Tim Miranda" (529138432)
00:04:11.890 --> 00:04:33.050
The next slide. So there's five skills, we'll be adding more here and these are about kind of adding things outside of of Launchpad and integrating them in, right? So we have a skill that really teaches your agent how to call launchpad over the DX API, which is our REST service for.

14 "Tim Miranda" (529138432)
00:04:33.050 --> 00:04:53.050
Surface for launchpad applications. And so instead of having to read a spec or sort of look at the different endpoints and stuff, you can describe what you want to do. Maybe you have your own front end application that you already have running or you may have other services and you want to programmatically integrate with Launchpad and create case.

15 "Tim Miranda" (529138432)
00:04:53.050 --> 00:05:27.319
This start to workflows, access data from the launchpad, data store. That skill will quickly get you hooked up with the DX API and guide you through the configuration that you need to do in launchpad as well. You can also use this to help you build, use our web embed capability so that you can embed in the launchpad user experience directly into your existing portal or web application. And I have an example here for the 3rd one, you can, there's a skill around creating custom UX components, so if there's some special.

16 "Tim Miranda" (529138432)
00:05:27.319 --> 00:05:57.889
Little control or even like a page that you want to build. Maybe you already have some existing UX assets. You can use that to quickly have it wrapped in a way that it could be used in launchpad, and then also deploy it directly into launchpad. You can see on the right here I'm showing a simple example, but within a few minutes, one of my colleagues used that skill, built a, slider toggle type setup there and then drop that directly into.

17 "Tim Miranda" (529138432)
00:05:57.889 --> 00:06:17.889
To their launchpad and user UX as a control, so that skill made it very easy to, to get that from idea into something that's running in launchpad. You can also there's a skill also around custom server functions. So again, if you have existing code assets like a Python module.

18 "Tim Miranda" (529138432)
00:06:17.889 --> 00:06:37.889
Or, a jar that you you use or maybe something that's open source that you want to use as part of your workflow and launchpad. That skill will let you get it defined, wrapped, and then show you how to upload it into Launchpad and then integrate it into your workflow. We even have a skill where.

19 "Tim Miranda" (529138432)
00:06:37.889 --> 00:06:54.269
Where if you have or want to create a custom front end that will be interacting with Launchpad over our React SDK, it will very quickly let you whip that up and you show you what you need to configure and actually walk through.

20 "Tim Miranda" (529138432)
00:06:54.269 --> 00:07:14.269
Getting the react SDK authenticated against launchpad, instead of having to read through a bunch of documents. So it's super easy to install these skills, in your repository, they're using the agent skills open standard. So the way we structured them, they should work with a variety of different vibe coding agents and tools. You can install single skills if you.

21 "Tim Miranda" (529138432)
00:07:14.269 --> 00:07:34.269
There's a particular one here that you're Oh I definitely want to check this one out. You can just use MPX to install these skills or you can install the full collection into your workspace as well. Really, really easy to do. It'll walk through, it'll even customize the install based on what tool you're using. So whether it's cloud or something else, make sure it puts stuff in the right place.

22 "Tim Miranda" (529138432)
00:07:34.269 --> 00:08:09.079
This for you so you just get up and running and start to do some development there. So, yeah, definitely check this out. It's up on GitHub, on the, on the Pega Systems account and we'll be adding more to it as time goes on. Cool. All right, so let's get into our next topic here. I want to introduce allie. She is gonna cover a bunch of stuff done under developer productivity enhancements and some new tools that are available. I think she's actually gonna show us all of these at once. So hi Allie, let's interested to see what you got.

23 "Tim Miranda" (529138432)
00:08:09.079 --> 00:08:10.060
Here.

24 "Ali Jordahl" (1548658688)
00:08:10.060 --> 00:08:29.749
Hey, yeah, thanks for having me. Let me share my screen here and and walk us through some cool tools. So I've been working the last few months to really, increase our usability in our launchpad application. And what that actually means is just.

25 "Ali Jordahl" (1548658688)
00:08:29.749 --> 00:08:49.749
Making it easier when you 1st come into the application or whether you've been in here for a while to just do the things you need to do, to debug your application, to add new features, all of that. And I think today Tim, what would be useful is to share maybe some of our automation capabilities.

26 "Ali Jordahl" (1548658688)
00:08:49.749 --> 00:09:09.749
That we've recently added to really make automations which are such core parts of our, you know, logic within our application and often require a lot of, kind of finessing and updating and debugging. We have a few, three new tools that I think will be, will be really helpful for those to show everyone.

27 "Ali Jordahl" (1548658688)
00:09:09.749 --> 00:09:29.749
Today. So I'm looking here at my, my case type for an audit case. And what I'm looking at for this workflow is I'm actually gonna take a look at this prepare audit automation that we have. So once I create an audit in my 1st step of my workflow, I'm going to load up some policies for that audit, and then I'm going to do some preparations.

28 "Ali Jordahl" (1548658688)
00:09:29.749 --> 00:09:47.069
Steps and I have this automation open here in another window. What I really want to show 1st of all is, you know, I've got quite a few, different things going on here, maybe not as complex as I'm eventually going to build it out and I'm kind of mid builds here.

29 "Ali Jordahl" (1548658688)
00:09:47.069 --> 00:10:07.069
And, the 1st thing you might notice is that I actually have a, a placeholder for the policy name here and that's because I'm actively developing this automation. I'm continuing to try to test it. And I really don't know what I want to set here. So I don't really want this step to execute. Well, what we have now, which I think is.

30 "Ali Jordahl" (1548658688)
00:10:07.069 --> 00:10:37.579
Super exciting and I personally have have certainly benefited from in the last few weeks is actually being able to disable my automation steps now. So what I'm just going to do here, hit disable and that's pretty much it. So I can disable a subset, I can disable the full step here. What's really, really nice and what I use a lot on this is I can actually like clear this value so rather than having a placeholder have nothing there, remind myself when I enable the step that I need something.

31 "Ali Jordahl" (1548658688)
00:10:37.579 --> 00:10:57.579
Thing there, and I can hit save on my automation, and this validation is going to work just fine because we're not validating your disabled steps. So this allows you to kind of have if you have maybe like an expression that's half baked and you wanna work on, you can really enable disable. I could also use the run rule.

32 "Ali Jordahl" (1548658688)
00:10:57.579 --> 00:11:16.298
To test this automation, and it won't, it'll skip those disabled steps and you can see my step numbering as well has updated to not include that disabled step there. So that's the 1st thing that I'm using all the time, to really just help with my automation development.

33 "Tim Miranda" (529138432)
00:11:16.298 --> 00:11:36.019
Yeah, I I spent a lot of time in automations when I'm I'm building outs cause they're really powerful, they let you do a lot of procedural stuff evaluations, integrations and stuff. And so being able to iteratively kind of put some placeholders in or some stubbed out steps, go back, you know, edit some other rules, add some of the supporting stuff that you want to call.

34 "Tim Miranda" (529138432)
00:11:36.019 --> 00:12:05.179
They come back here and turn them back on. Yeah, I think that I've been using this a lot in the past couple weeks. This is a great improvement here and yeah, NO, this is cool. And, you know, the other thing is you may not have the thing that you want to call. So if you're setting something on the right hand side of a set step, maybe you want to use configuration or like you have a configuration so that each subscriber has a different value so you may want to go set that up 1st and then un uncomment it out and then be able to use it.

35 "Tim Miranda" (529138432)
00:12:05.179 --> 00:12:06.381
Here, right? So.

36 "Ali Jordahl" (1548658688)
00:12:06.381 --> 00:12:26.119
Yeah, and that's actually something else, really something else I wanted to show as well, which is we now have on not just our automation rule, but on all of our expression enabled rules, we are adding the subscriber settings option. So for this policy name, e.g., I might want to set this for each of my subscribers.

37 "Ali Jordahl" (1548658688)
00:12:26.119 --> 00:12:46.119
To my application, it might be different depending on, you know, how that subscriber is operating. I can actually now just hit this here and see a really lovely dropdown of the configuration settings that I want to add. So this is we, you know, you could use these configuration settings before.

38 "Ali Jordahl" (1548658688)
00:12:46.119 --> 00:13:06.119
More in your automations and your expressions, this just makes it super easy, and to be honest, it just gives me a little bit better configurability when I'm doing something like an automation. It's one less step I need to do. I also like that this is filtering out into the configuration settings that I actually.

39 "Ali Jordahl" (1548658688)
00:13:06.119 --> 00:13:23.285
You would be applicable for what I'm setting with this field. So I'm only seeing a configuration setting that has that text type that I'm looking for for that policy name. It just makes it easier for me to find what I need and, and to be able to work with this here.

40 "Tim Miranda" (529138432)
00:13:23.285 --> 00:13:52.009
Yeah, that's great. I mean, the, the configuration aspect of launchpad is super powerful for subscribers, you know, you can set up like here you have simple kind of, you have different values for different subscribers. You could have entire rules that are configurable and extendable by subscribers. But to be able to just kind of drop it in and say like this is where I'm gonna set this here, you know it's coming from a configuration and you have different types of fields, like you said, you might have text fields like you're using.

41 "Tim Miranda" (529138432)
00:13:52.009 --> 00:14:03.943
In here, you may have amounts or thresholds, you may have flags that are like booleans. So it'll let you see exactly the ones you can use in this particular statement. So yeah, that's pretty cool. Yeah.

42 "Ali Jordahl" (1548658688)
00:14:03.943 --> 00:14:24.943
It is, it is. It's, it's very useful and the final thing that I I want to show you and everyone today, so I'm gonna actually disable this again because I don't need it. And what I want to do now is actually show something that we have for our background automations. So we have this op. Oh, sorry.

43 "Tim Miranda" (529138432)
00:14:24.943 --> 00:14:28.688
Oh NO, go ahead. I was looking at the last stuff here, so, ok.

44 "Ali Jordahl" (1548658688)
00:14:28.688 --> 00:15:01.759
Yeah, yeah, yeah. So yeah, we can see on the bottom here I have this executing background checked, and this is for something where I don't want this to block my end user, waiting for it, right? So this might be a longer running process or something like that. You can see I have this background audit prep here, that might take a little bit longer and what might happen is you might need to be debugging this background call as well, right? And now we have a really easy way to do that, that I personally.

45 "Ali Jordahl" (1548658688)
00:15:01.759 --> 00:15:21.759
I am a big fan of. So I already have a preview loaded up here of my application and I'm just going to show us how we can actually trace that background automation step really easily, and most importantly, really clearly as a kind of sub process within our broader automation.

46 "Ali Jordahl" (1548658688)
00:15:21.759 --> 00:15:41.759
For my application. So what I'm going to do is I'm going to create an audit here and I'm going to choose the ISO type and I'll just set my due date to next week, a week from now, and I'm going to label this you know security audit for launch pad.

47 "Ali Jordahl" (1548658688)
00:15:41.759 --> 00:16:02.179
And I'm going to, before I hit submit, I will remember to turn on my tracer here. And the tracer, I'm sure many of you have used, right? Super useful, and it's going to trace all the steps. Now, before I might not have had great visibility into my background automation to see exactly how that was.

48 "Ali Jordahl" (1548658688)
00:16:02.179 --> 00:16:30.649
Running. If, e.g., I was debugging something there or unsure why something wasn't working or or whatnot. So when I hit submit, what this does is it submits and if you remember from when I was showing the case type, we all gather these audit details, but we're also going to execute this prepare audit automation, which calls my background automation. What I'm going to do now, i'll pause my tracer and I'm going to just search background here and I can actually.

49 "Ali Jordahl" (1548658688)
00:16:30.649 --> 00:16:50.649
Actually see quite a few background jobs, and I can also see my automation and I'm going to open up in my new window a tracer, and this tracer is going to be updating while my background automation is running. So I can actually see, you know, the step numbers exactly what I would see for a.

50 "Ali Jordahl" (1548658688)
00:16:50.649 --> 00:17:10.649
Regularly executed automation in a separate kind of context so I can see and really debug that as a separate entity. So this is something that I just find really useful as I'm building more complex applications, which is one of launchpads real strong suits. I'm able to do this training.

51 "Ali Jordahl" (1548658688)
00:17:10.649 --> 00:17:30.479
Thing now and we can actually just go to the homepage as well just to confirm, ok, I see my new audit is created for my background automation. I see the due date has been set. Maybe I don't see this framework name has been set yet, so I'm gonna use the tracer to identify why things didn't get set, all of that good stuff.

52 "Tim Miranda" (529138432)
00:17:30.479 --> 00:17:49.519
Yeah, NO, that's having that in a unified place. I mean, in any kind of runtime where you're kicking stuff off in the background, it's it's usually hard to kind of see not just the results of that, but also like what process it went through. So to have that just in tracer whereas developer I can make some.

53 "Tim Miranda" (529138432)
00:17:49.519 --> 00:18:21.680
Changes, go to preview, trace through the foreground process that's running and automations but also see the what happened with the background one saves me a lot of time and makes it really easy to debug stuff as I'm going through. So, yeah, this is a, this is a great new feature like all these put together, and we're also not mentioning that there's other developer productivity stuff that's that's been done recently that's upcoming as well but this is a great kind of way to connect the dots through these, these ones so.

54 "Ali Jordahl" (1548658688)
00:18:21.680 --> 00:18:43.567
And you'll notice I even just use some of them that I at this point have just become natural, right? I generated comments for my automation. I also, you know, could have used the, the fill form functionality here if I was just going quickly and wanted to test, so lots of great things that just become a part of your development experience. Yep.

55 "Tim Miranda" (529138432)
00:18:43.567 --> 00:19:01.647
No, that's cool. And then, so what, what can we expect in terms of more changes going on? Can we get, you know, how do we get feedback from clients and like what, what are we looking in the pipeline here for stuff like this?

56 "Ali Jordahl" (1548658688)
00:19:01.647 --> 00:19:26.679
Yeah, great, great question. I think I see my job within our engineering teams as really being translating that client feedback into meaningful changes in our product. So we're always taking the feedback that we get from our providers, that our providers get from their subscribers even, and translating that into really high impact changes. So a few other things that we've.

57 "Ali Jordahl" (1548658688)
00:19:26.679 --> 00:19:46.679
Done in the last few months that, that I just think are are notable in addition to filling the form with AI, which saves me so much time when I'm going through a test flow. I have a screen I have like 25 fields. I don't want to have to type out a value for all those every time I test my flow. That has saved me a lot of time and a.

58 "Ali Jordahl" (1548658688)
00:19:46.679 --> 00:20:06.679
Of itself. Also using those configuration settings across other expression supported rule types. So using those in my integration rules and other things like that has been really helpful. I can update my field types as well. It's something that we kind of focused on as a better experience changing the types of my field.

59 "Ali Jordahl" (1548658688)
00:20:06.679 --> 00:20:26.679
Builds, after I've already have them, I've already I had envision in my blueprint, I start working on my application, I realize, you know what, this text needs to be a text paragraph, vice versa. I can easily change that in my application and we made that process really nice and neat. So we're, we're always taking that feedback and, and trying.

60 "Ali Jordahl" (1548658688)
00:20:26.679 --> 00:20:36.563
Have a really quick turnaround in terms of high impact for listening to, to you all and understanding what makes our product even better.

61 "Tim Miranda" (529138432)
00:20:36.563 --> 00:20:51.460
Very cool. Awesome. Well, thank you so much. I've directly benefited from this myself as I building a new app this week and was using all of these things that you showed off, so, appreciate your time. Thank you. And great.

62 "Radosław Nowak" (488712448)
00:20:51.460 --> 00:20:52.949
So I'd like to introduce.

63 "Tim Miranda" (529138432)
00:20:52.949 --> 00:21:13.323
Productik here, he's from our product management group. We've got some exciting new stuff coming here with agent processing, and keeping track of the history of of chats that are happening with agents. So welcome Ronikk, thanks for joining us today. Tell me a little bit more about what's going on with these new capabilities.

64 "Radosław Nowak" (488712448)
00:21:13.323 --> 00:21:35.309
Hi team hi all on on the audience. So yes, last time I was presenting to you like three three months ago and we've been introducing agentic capabilities in general to launchpad. And at that point of time we introduced them very generically, very flexibly.

65 "Radosław Nowak" (488712448)
00:21:35.309 --> 00:21:55.309
Where you could execute well you could have agent execute any automation or any data page for its knowledge. Now we are extending this to basically grasp the core advantage of launchpad which is predictable workflows. So now with a single click.

66 "Radosław Nowak" (488712448)
00:21:55.309 --> 00:22:17.204
You can expose a particular case type to your agent, and that's it from the authoring standpoint. With a single click you get case creation, you can get assignment processing and everything is handled for you, 100 100 % within the platform. Cool.

67 "Tim Miranda" (529138432)
00:22:17.204 --> 00:22:30.286
Alright, yeah, so let's, and then we, yeah, we had the conversation history as well. Yeah, I mean it was a great foundation that we talked about last time. Why don't we take a look? Show us what you have. Yep.

68 "Radosław Nowak" (488712448)
00:22:30.286 --> 00:22:58.929
Yeah, so as you said, we also have this conversation history where I can see my previous chats with the agent and I can continue them at any point of time so I can get summaries for each of my conversations so that I can, I can I can easily distinguish them in the list. Here, here it's showing that I have my previous conversations, I can open any of them. And yes.

69 "Radosław Nowak" (488712448)
00:22:58.929 --> 00:23:31.508
Now what is this major feature is that now all the workflows are exposed here. So you do not need to configure any, you don't need to play with any data types, you don't need to play with any automations. All of those capabilities are out of the box exposed to your agent widgets, you can place agent widgets anywhere in your application on the landing page or or in a case in the context.

70 "Tim Miranda" (529138432)
00:23:31.508 --> 00:24:00.811
Alright, so here you have an agent that is just in the landing page when I log in and I can just start conversing with it and having it kick off workflows and work walk through that those same workflow step workflow steps that I might traditionally kind of be like show a form, show a form, but here it's being done conversationally following the guardrails of that workflow. Cool. Yeah it's all the way through all the different steps and asking the required info.

71 "Radosław Nowak" (488712448)
00:24:00.811 --> 00:24:19.928
When when you're talking about the traditional UI, what is great here is that you do not need to know where a particular option is in the UI or which case you should use. If the agent has those cases exposed, you just tell the agent what you want to do and the agent will pick it for you automatically and guide you through the through the process.

72 "Tim Miranda" (529138432)
00:24:19.928 --> 00:24:38.369
That's great. I mean the fact that I can build a single workflow and as a provider, I could decide to expose it sort of interactively through a set of forms or conversationally and not have to build specific workflows and processes for those different types of uses makes this.

73 "Tim Miranda" (529138432)
00:24:38.369 --> 00:24:57.539
Save me a lot of time and also I'll know that that same set of steps, the automation, the decisions along the way are gonna be executed and honored, whether it's done this way or or through a set of forms saves me a lot of time. So very cool. So this is actually now.

74 "Tim Miranda" (529138432)
00:24:57.539 --> 00:25:20.884
Of Finishing off a case and finalizing this instead of having the user have to kind of look, you know, go from screen to screen. So here it's actually created an actual booking case. Okay. So now you can open it up, you can take a look at the booking. It's a real case in the system, and all of the stuff that's that's been filled in by the agent, that's awesome. Exactly.

75 "Radosław Nowak" (488712448)
00:25:20.884 --> 00:25:36.289
And as you can see here, we can have any complexity of the case behind this agent. So the the workflow can have any automations, decisions, connectors launched to other systems, anything that Pega, that.

76 "Radosław Nowak" (488712448)
00:25:36.289 --> 00:25:44.466
Much can give you everything is available to the agent behind the process basically.

77 "Tim Miranda" (529138432)
00:25:44.466 --> 00:26:03.649
That's great, yeah. I think that, you know, this is a great example again of, of sort of how the workflow, the outcome of your app is, is the central thing. You focus on that in your development and we take all the kind of non outcome related stuff off.

78 "Tim Miranda" (529138432)
00:26:03.649 --> 00:26:19.770
Table for you. So you can just drop in a conversational agent, you can have them walk through forms, you can have a custom front end that's using that same workflow or even drop that agent into your own portal, however you want to do it. And, we make sure that.

79 "Radosław Nowak" (488712448)
00:26:19.770 --> 00:26:27.506
Link it with what you you were talking about at the beginning with the skills and and use it through the X API.

80 "Tim Miranda" (529138432)
00:26:27.506 --> 00:26:30.328
So any any way you like you can come.

81 "Radosław Nowak" (488712448)
00:26:30.328 --> 00:26:48.791
Operate with this and soon we will be exposing the same through MCP that the great premier will be on Pega world. So once again the invitation to everyone and that's when when when we will expose exactly the same processes, the same capabilities to MCP.

82 "Tim Miranda" (529138432)
00:26:48.791 --> 00:27:14.449
Yeah, there's a lot of stuff coming that you'll be able to see at Pega World around using agents and AI in your application development as well and the runtime. And so I, yeah, definitely, again, a big plug for Pega world. If you or your colleagues are, going register for the launchpad sessions, you're gonna see some really neat stuff there. Yeah, so this is this is awesome.

83 "Tim Miranda" (529138432)
00:27:14.449 --> 00:27:34.939
Again I'm gonna be using I have been using this in some of the new apps I've been building even the last couple weeks and it just, it feels very turnkey, you know, it's like I built my workflow, I know, I know what outcomes I'm trying to put into my app because that's, that's my differentiator for my app as a provider is really the workflows and the, the, the.

84 "Tim Miranda" (529138432)
00:27:34.939 --> 00:27:50.969
The magic in them and then be able to very easily just have them be used conversationally or from form to form, you know, takes all of that off the table for me. So this is cool. Yeah, anything else you wanna highlight here Ronik?

85 "Radosław Nowak" (488712448)
00:27:50.969 --> 00:28:18.399
So, regarding the the history of of of the case of of the conversation. So, here it's we can we maintain separate history for all your contexts, so for landing pages it's separate. You can have different agents in your applications. You can have an agent next as a context context full agent next to your each case instance. So then it's specific to a particular case, so you can have.

86 "Radosław Nowak" (488712448)
00:28:18.399 --> 00:28:33.590
Any conversations in, for any cases maintained separately we which gives you this flexibility of, of, of having things organized where you would expect them.

87 "Tim Miranda" (529138432)
00:28:33.590 --> 00:29:06.028
Oh, that's great. Yeah, that's great for the end users to be able to see that, but also just from like an audibility and and predictability point of view, being able to kind of see what's been happening with these executions with these conversations and really drill down into like, just like with with any, you know, kind of, conversational experience being keep your context from past conversations useful for both like the subscribers that are like managing this app but also the end users that, that are using it as well.

88 "Radosław Nowak" (488712448)
00:29:06.028 --> 00:29:37.073
Yes, the subscribers can have insight into all the conversations of their customers. They can have an agent like summarize all the conversational conversations of all customers so they can get really comprehensive information what are the what what people are needing from from your application and how they are using it and and and you really can boost your productivity or your your outcomes with with such approach.

89 "Tim Miranda" (529138432)
00:29:37.073 --> 00:29:50.508
Very cool, awesome. Well, thank you Roddeck for your for joining today. A lot of stuff to explore here for folks. Definitely take a look at all these new capabilities and try them out in your application.

90 "Radosław Nowak" (488712448)
00:29:50.508 --> 00:29:51.448
Thank you.

91 "Tim Miranda" (529138432)
00:29:51.448 --> 00:29:57.332
Right, so let's talk next steps here.

92 "Katie Cibulka" (964323840)
00:29:57.332 --> 00:30:14.067
Alright, we are gonna go into Q and A right now, so I will, we got one question for you, allie, and how can you wait for completion of a background process within the process?

93 "Ali Jordahl" (1548658688)
00:30:14.067 --> 00:30:33.739
So I'm not sure if it's asked it's asking within the context of the tracing or just the actual process itself, so I'll address both. For the trace it should work just like if you are running an automation for like in the regular tracer of foreground automation. So you'll see those.

94 "Ali Jordahl" (1548658688)
00:30:33.739 --> 00:30:53.739
These Traces appear as the automation is executing. Once it's finished, you should be able to see in that pop up window all of the traces listed there nice and neat for you and it is separate, which is nice so you can kind of see that come in. For actually waiting for the, the process. So the background.

95 "Ali Jordahl" (1548658688)
00:30:53.739 --> 00:31:13.739
Automation itself is meant not to cause any weight on the side of the end user. So as an end user, you'll notice like my case, my sub case creation might have still been happening, but I didn't actually see any loading on my end or anything like that as I was waiting for.

96 "Ali Jordahl" (1548658688)
00:31:13.739 --> 00:31:33.739
For that, it's happening in the background, meaning when it completes, it completes, you'll see the results. In that case I was creating a new audit case. So I saw those results when I went to my homepage. If this was something that had taken, you know, a few minutes, I would just need to refresh my home page and see when that showed up.

97 "Ali Jordahl" (1548658688)
00:31:33.739 --> 00:31:57.806
Up, but the real point of the background automation is that you're not making anyone wait, you're not having that wait time. It's something that's not going to be urgent enough to have the user kind of waiting for that spinning wheel or or waiting for the process to complete. So it's really useful for those longer running processes or just things you don't want to be time that the user spends.

98 "Tim Miranda" (529138432)
00:31:57.806 --> 00:32:13.859
And you there's a pattern that I've used a lot where you may want to kick this off in the background not and have the next few screens or interactions not have to wait for that. But there maybe a point in your workflow where you do know you got you you need those results, whether it means waiting for it or not. So you could have it.

99 "Tim Miranda" (529138432)
00:32:13.859 --> 00:32:33.859
In the background, say create some child cases that are, you know, linked to that parent and you can use the weight shape in your process when it makes sense to wait for those children to fully complete processing. And that's a way to sort of have it let the user get through some work while that's happening in the background, but then at some point the the parent case has to sort of.

100 "Tim Miranda" (529138432)
00:32:33.859 --> 00:32:42.125
Chill out at a spot until the the children are complete. So you have that option as well.

101 "Katie Cibulka" (964323840)
00:32:42.125 --> 00:32:49.699
Okay, another question for you Radik. What LLM model stands behind this?

102 "Radosław Nowak" (488712448)
00:32:49.699 --> 00:33:19.599
Yes, so, so for each agent you can select the model large language model that you, that you like that you think that will be best handling the requests sent to the agent or you can use the default option which is recommended by launchpad at any given point of time because as we know, there's progress and evolution or revolution of agentic capabilities, so.

103 "Radosław Nowak" (488712448)
00:33:19.599 --> 00:33:42.499
We keep pace of, of, of what new models, new llmiss appear and which ones will best handle your processes. So all of those that are leading like from anthropic, Gemini, GPT, all of those are available to you of if you want to manually.

104 "Radosław Nowak" (488712448)
00:33:42.499 --> 00:33:45.009
Choose.

105 "Katie Cibulka" (964323840)
00:33:45.009 --> 00:33:52.406
Great. And then another one for you, can a single agent work with several case types?

106 "Radosław Nowak" (488712448)
00:33:52.406 --> 00:34:20.669
Yes yes, so you basically have a checkbox for each case type in your application and you, you, you, you can have any, any checkboxes selected to expose those particular cases to a single agent. You can have any number of agents also, of course, give them different instructions so that they behave that way or that way. But yes, they can, they can operate on on on those case types that you select even multiple.

107 "Katie Cibulka" (964323840)
00:34:25.265 --> 00:34:53.200
Okay, cool. Let's see, any more questions? I know Al, you had talked about AI before, but we have some more coming I guess. So it's always exciting some new features around AI. Alright. I don't know if I see any other questions. All right, so let's go ahead and wrap it up. Let me get the slide up at the end.

108 "Tim Miranda" (529138432)
00:34:53.200 --> 00:35:09.749
Sure. Of course, if you have questions afterwards, you can reach out on launchpad.io and get in contact and find out more. So of course again I want to highlight Pega World that's coming up, lots of announcements, awards, provider panels.

109 "Tim Miranda" (529138432)
00:35:09.749 --> 00:35:27.689
If you are attending Pega World and you want to see the launchpad session where all that's happening, go to this link to go register. If your colleagues go into Pega world, get them to register, see everything new that's going on with launchpad. A lot of exciting stuff there. And then.

110 "Tim Miranda" (529138432)
00:35:27.689 --> 00:35:46.949
We will also coming up next week, we'll be in Santa Tell for the Saster conference, so you'll be able to meet launchpad folks there, talk to them about your, your apps, your ideas, your use cases, learn more about it, and really dig in, so check us out there if you're attending that.

111 "Tim Miranda" (529138432)
00:35:46.949 --> 00:36:06.949
And we also have our next, this, this launchpad live community call. Our next one is on 16 July. You can see our announcements on LinkedIn. You can also go to launchpad.io under the resources and events and see what's coming up and get this on your calendar.

112 "Tim Miranda" (529138432)
00:36:06.949 --> 00:36:16.949
So that, you'll be able to see what new enhancements we have between now and July and the platform as well.

113 "Tim Miranda" (529138432)
00:36:16.949 --> 00:36:36.949
Lots of stuff going on, and then coming up, we're gonna announce a series of regional road shows where we'll actually be in person in a few different places, Toronto, Waterlou, new York and Boston, and you'll be able to really talk directly with our launchpad leadership and see, and really kind of dig into.

114 "Tim Miranda" (529138432)
00:36:36.949 --> 00:36:48.029
How you can use Launchpad for your to build new apps, to augment existing apps to enhance capabilities in your apps and really dig in there.

115 "Tim Miranda" (529138432)
00:36:48.029 --> 00:37:06.779
Alright, and let me see. So, like I said, go into launchpad.io, you can see what events are coming up. You can we'll also have blog posts that are getting posted there all the time under the resources, check out our agent skills up on GitHub and.

116 "Tim Miranda" (529138432)
00:37:06.779 --> 00:37:23.999
Dig in as existing providers, dig in, check out these new capabilities that we're showing off today, and let us know what you think, but I appreciate everyone's time here, really liked what we saw today. Thanks for joining and we'll be posting this up on launchpad.io so you can.

117 "Tim Miranda" (529138432)
00:37:23.999 --> 00:37:40.544
See the video, see what we went through, if you wanna look back, but see you with the next one and thanks for joining.