[Music] well hello and welcome to tech now the web series for servicenow admins builders and developers on a variety of platform topics my name is chuck tomasi from servicenow senior developer advocate i've got to update that slide i just realized my title was wrong note to self i've been with service now for about two ten and a half years i i don't know what year it is anymore it's been like 10 years in the last 12 months it's crazy but uh no really i started in 2010 was a customer for a couple before that and always focused on custom applications integrations and the platform in general have a couple of hobbies outside of what i do for work but many of them are closely related to work so we won't get into that instead i'm going to turn it over to craig stepp for his introduction and i'm craig stepp i'm a program manager for cloud labs i just noticed that my title's wrong yes i'm actually a lead staff develop programmer i specialize in cloud automation and i produce all the backend uh infrastructure that we use for our classes when we when we uh do training uh through servicenow whether it's at the knowledge conference or any of the training that we offer uh through servicenow and sometimes uh partners and all that kind of stuff would help out with their infrastructure i've been with servicenow for almost seven years so coming up on uh seven years that's that's actually uh a long time seems like just yesterday and i will turn it over now to jeremy hey folks my name is jeremy duncan platform architect on our workflow design studio team used to be known as our solution innovation team but we recently rebranded i started as a customer on the servicenow platform about nine years ago so pre aspen i have 16 years of enterprise service management experience most of that being an it and i t secure information security excuse me um started my knowledge experience back in 2013 got to speak about a product called technopedia by bdna was a fun experience and have enjoyed the knowledge conferences ever since can't wait to get back in into the live conferences and be with you folks just a little bit of personal uh fun fact about me i was a reserve police officer for seven years recently retired for medical reasons but enjoyed that a way to give back to my community so wonderful a pleasure to be here and i will move it on to our wonderful speaker mr yaron hi there my name is euron guez i'm a manager in platform and engineering my title is correct um i've been at servicenow for exactly three years i hit my three-year date just a couple days ago which is exciting um prior to being a manager i was a staff software engineer on the agent workspace team helping to build out that product in prior to service now i had co-founded a data security startup and i worked in m health and financial industries as well when i'm not coding i'm playing piano singing working in the garden hiking camping cooking and playing with my one-year-old son happy to be here today's agenda we're going to review the process automation and designer playbook continuing on from the last episode and we're going to talk about the playbook configuration and options and of course a demonstration to do a little q a afterwards so just to tell you that uh when his audio is doing a little better chuck participates in breakpoint it's his own podcast from servicenow it's a developer podcast where he interviews servicenow developers and people around servicenow for the podcast and you can go subscribe to that there's a link down below just search for breakpoint and you should be able to find it in pretty much all of the podcast um directories all over the internet so i also want to tell you if you're interested in participating in doing that a little bit of development like a lot of others um around servicenow you can go to the developer.servicenow.com and you get a free personal developer instance there's all kinds of documentation uh lots of developer resources there for you to actually get involved and start building out applications on your own or just seeing what servicenow can do for you so go over there and check that out at thedeveloper.servicenow.com and now we will start off with the process automation designer and i'll turn it over to yarn thank you very much so this is part two of a two-part series on process automation designer and playbook two new products that shipped in paris first we have some legalese safe harbor statements everything you see here for future releases shouldn't influence buying decisions behind every great experience is a great workflow that is the philosophy that really drives these two products process automation designer and playbook experience as we broke down last time they are two different products process automation designer is a no code designer for authoring cross enterprise workflows in a single unified process fancy way of saying it's a process builder on the other hand playbook experience is a ui platform for viewing and interacting with business process workflows in real time both can exist independently of the other but they work extremely well when coupled together now what problem we trying to solve with playbook we're really trying to get at the fact that fulfillers who are working on tasks or processes don't have a simple simplified task-oriented view of a multi-step process there's a lack of visibility you have to click in and out of a lot of related lists to do your work it's hard to see where you are in the multi-step process and what's the current state and it's hard to know what to do next you have to scan through forms fields notes um in order to figure out what exactly is on you so the vision for solving this is playbook it's in order to provide a way to visualize and interact with business process workflows in real time via a simple task-oriented view in order to ensure a consistent response to commonly encountered situations and those words are bolded for a reason this is bi-directional for visualizing it a process as it is moving but you can also interact with that process it can go both directions and all this is happening in real time as the process updates the ui updates and as a fulfiller or any other user interacts with playbook updates the process in real time now the anatomy of a playbook everything starts with a parent record you may recall from last time session that processes have triggers that are defined based off of when a record is created or a record is updated that is often referred to as the input record but in our sense we refer to as the parent record in this case the parent record is open within agent workspace and you can see here that within agent workspace we have a playbook embedded within a related item panel so for those familiar with workspace you can add items to any form that shows up as these tabs here and what we recommend we ship for out of the box playbooks is to add a playbook as a related item panel to your form so we can see the playbook rendered here as such the playbook itself is broken down the lanes from the process automation designer are rendered as stages here as an accordion that can be extended by default we expand any lanes that are in progress and the activities within that lane are rendered as cards and those are also expanded by default if that activity is in progress how we actually go about rendering that activity depends on its experience type and its experience properties which we'll describe shortly i'd like to take a step back for a bit and just reiterate what are the roles involved in all this who are the different user personas because there are several on the far left hand side we start with a developer the developer is the one who's working in flow designer to working with flows actions activity definitions in order to automate individual pieces of the business process they are building the building blocks that the process owner will use and encapsulating complicated logic into reusable pieces next you have the process owner the process owner is the one who is going to work in process automation designer to build processes in order to organize the pieces of the business process into a cross enterprise workflow so they're going to take the building blocks that the developer has provided and wire them up together next you have the workspace administrator they are the one who is going to be configuring playbook experience defining what that user experience should be in order to configure the appropriate views of the business process for the right users they're the ones who will be embedding the playbook into the workspace and configuring how it can show up highly configurable as we'll show finally you have the agent the agent is the one who is working in agent workspace on the playbook and actually doing the work completing individual tasks within the business process so how do we render these activities now activities are powered by flows and flows can be thought of as a black box they can do anything and everything and it's hard to know exactly what it is that they're doing from the outside so what we do is we categorize these activities using activity experience types an experience type will loosely define what we can expect from a user as a way to experience what this activity is the experience type will define a collection of experience properties that can be mapped to work being done by the flow and then we will render that to the user in a meaningful way our default render is what you can see here it will interpret those experience properties and provide support for forms attachments checklists sla countdown timers rich text deep linking dot walked field references as well as clickable actions buttons and drop downs and a really rich experience as a way to interpret what those different properties are on the right hand side all the texts that you see in red these are our sample experience properties that are associated with the experience type called record most the majority of times the experience type will be a record because this is servicenow and everything is really record driven and you'll see that it exposes a property called icon which will control the icon in the top left a tagline title description these label value pair fields we refer to them as record fields it's a comma separated list of fields on a given record will render as such if any of those fields are references themselves it will be clickable to open up that record reference record in a new tab if you tell us to show a checklist and the associated record with this activity contains a checklist we will show it forms attachments the buttons that i mentioned before and a dynamic footer all of which will also make more sense once we get to the demo which is why i'm talking so fast so enough time for it now we also support custom experience types and custom renderers so if you don't like the experience types that we ship with you can define your own and you can define any collection of experience properties that make sense for you so you can choose what of those experienced properties you want to expose we also have a framework for building custom renderers in the paris release this is pretty much targeted for our own business units and app teams such as csm and itsm to create custom renders it's a little bit more trickier to do it as a third-party customer or partner however in rome and beyond we are planning on adding this ability to build these custom renders in ui builder so some of the custom renders that we ship with you can see here a list render if you want to render an activity not as a record of the form but instead as a list of records or as a knowledge article and show a little preview of the knowledge or record or as a create record you want to embed a new record form as opposed to an update record form each of these experience types that correspond to these custom renders will expose different properties for example a list experience type will expose well what table is this list what's the query what's the conditions and so on and so forth now the way that you interact with a process that's moving in real time is through declarative actions these allow agents to interact with these business workflows they can run server scripts against associated records they can dispatch client actions within workspace for example to open an associated record in a new tab they can display custom modals for example to show an activity stream in a modal they support rich conditional logic server conditions client conditions user role crud access anyone who's familiar with declarative actions from workspace they power the buttons that you see in the top of lists related lists field decorators they're heavily used already in workspace and we use them in playbook as well the way that we integrate this with process automation designer is those experienced properties i described before when you edit an activity definition you can provide hard-coded values for those experience properties for example you can fill in a title that you want to show in this card but more powerfully you can use pill pickers to map those experience properties directly over to anything that's happening within the flow so not just the flows explicit outputs any of the actual outputs of the steps within the flow you can map to these experience properties and really dynamically control what that user experience is not only that but this is all updating in real time so as the flow is progressing as the flow is outputting different data at different steps along the way the ui can reflect that and show different information this can be really powerful if you couple it with things like decision tables that can determine what fields to ask for or what forms rather and also of our associated records have record watchers on them so this doesn't depend on process automation designer if if activity is associated to some random incident and an agent in the field updates that incident on their mobile phone totally outside of process automation designer that will update in the playbook in real time as well everything that you're going to see in this demo is highly configurable this is a platform after all we want your admins to be able to customize this as it suits your business use case there is a filter where you can filter activities in real time you can control what fields are in that filter if a form is too big to fit in the card we actually show in the modal you can control when that happens by default if you wanted to show an sla in a sla timer countdown timer in a card we're going to show the sla that's going to finish first but you can override that and specify a different role you can control the roles required to view certain activities so that two different users a manager and a customer can be interacting with the exact same playbook and see completely different activities based off of their role you can control which activities are expanded by default i mentioned that we expand activities that are in progress but you might want to create an override role and say you know what i only want to expand activities that are in progress but are also assigned to me so that it will really highlight the work that needs to get done to a specific agent i mentioned custom renders activity actions and the location within workspace so now for the fun stuff we're going to jump into the actual demo to see this in real time let me go ahead and share my screen okay so here we have process automation designer from last session and these are the lanes and activities and this i recommend if you find anything interesting today and you want to play with it yourself um you can go check this out um here we have an analysis lane a remediation lane we're not going to dive too deep into this because we did last time um but what we're going to see in the analysis lane there's an introduction a wait for condition where it's going to wait for issue type to be provided as soon as the issue type is passed in this step is complete whether it's done the playbook whether it's done somewhere else doesn't matter then it's going to create a child task that's associated with that issue type it's going to use these pill pickers to insert references to the number create links to the actual issue assign it to a user it's going to let the agent send the slack message last time we showed how to build a custom activity definition to collect info from the user and selena slack message and finally it's going to wait for that task that was created in the last step to be complete using the pill pickers again you can see it's using the record from the last step and it has a wait for condition to be closed complete so let's see how this actually appears to a user so i'm going to jump into the custom workspace that comes with this lab the improve work lab and i'm going to create a new issue and just say how about a new coffee maker now because this issue now has a running playbook for it a playbook tab will show up and we can jump over that and see the lanes that from this step are now rendered as an accordion the first lane analysis is expanded the introduction is expanded and we see some helpful text we have two declarative actions here one to skip the step one to mark it as complete the fill issue type this is again is a wait for condition it's waiting for issue type to fill then and it has an activity experience defined to embed these three fields so even though issue type is the only field that is provided we can that's required we can fill in these other fields as well and do some work on issue now because the issue type has been filled in that step automatically finishes it goes to the next lane you can see that it skipped over the first step completed automatically because that was an automated step there was nothing for the user to do it just created the task however we can see some information about what that task was created we can see that it was assigned to able the record number and so forth next we can see the option to send the slack message to the team so if i say coffee maker sounds like a good idea and hit send that finishes and if i jump over to slack we can see that we just got a nice message real time coffee maker sounds like a good idea to me and then it has this last wait for condition where it's waiting for that child task to be complete so if i opened up that task in a new tab here marked it as complete and went back we'd see now that that work has been done this playbook has been completed as well so before we expand on this and make this user experience a little better let's see where those fields are coming from so if i jump back over here and i take a look at any of these properties here for example let's take a look at the issue fill issue type activity and go to a configure activity in addition to the required inputs that this takes you can always switch over to the advanced view to look beneath the hood and see how this activities experience has been configured now you can see the experience type is record you can see all the experience properties associated with the experience type of record and you can see that a lot of them have been filled in and many of these have been customized already for the specific type so we can see the tagline is fill issue type if i pull up this little reference guide we can see tagline goes up here the icon has been set to be an asterisk that's the icon here there's no title or description but we can see that form fields have been filled in as a comma separate list of issue type priority location that's why we show those three fields i'm going to actually kick off another one so we can see this in real time this is kind of a dangerous idea we can see here are those three fields that were set up um you can provide a comma separate list of form fields or form view or both just know that the form fields you list have to be in that view for permissions purposes and if you don't provide a view it's going to look for them in the default view that's why you see this here you can choose to show attachments on the associated record or on the parent record you can make the attachments read only you can show an sla timer if one exists to show a checklist if one exists or mark a task as automated which just renders it a little differently so all those map one to one but you can also see that you can use these pill pickers to pull some of these values from the underlying flow if you prefer so for example these issue type fields these form fields they have to come from some record so that's where you always see at the top of almost every experienced property associated record what is the record that's driving this experience and we can see the pill picker here is that the record that's driving this experience is specifically the record that we're waiting on we're waiting on some condition to be met that's the record that we're going to show in this case now we don't expect process owners to do this we don't expect them to switch to the advanced view and fill all these fields in for their specific case they can if they want to if they want to customize it but we expect the developers to fill these in ahead of time and to create very specific activity definitions that solve specific use cases so rather than a process owner dragging and dropping in a wait for condition they would drag in something specific now let me give an example and we'll actually walk through that so let's go and go to the last step we'll skip over this let's make this experience a little bit better you know we're waiting for a task to be completed but we had to go when we had to uh click in here to see the actual task to see we don't have any information about this so let's create a custom activity definition to improve this experience something that a process owner could just drop in so we'll call it um wait for iw task completion this table here allows us to limit it to a specific parent record you know we don't want this wait for iw task completion to show up in any random process it's not really relevant so we're going to just say limited to ones for iw issues that was what the trigger was if we went back here we can see this process was kicked off any time an iw issue was created so we're only going to show it in those and now we choose an automation plan this can be a flow or flow action in our case it's just a flow action so wait for condition we'll hit save to see that flows inputs we can see what's asking us for those conditions so we're going to go ahead and pre-fill these it's going to wait on a task and it's going to wait for that task state to be one of this way the process owner doesn't have to build the condition builder it'll already pre-fill them for them we're still going to leave record blank because the process owner does have to wire in which record they're waiting for next we will switch over to the activity experience and we'll choose an experience type of record and we'll save and now we'll see all the experience properties for the record type so for table we know that we're waiting on a task associated record we're going to use the pill picker here and map it to the input of this wait for condition and specifically the record that it's waiting on let's go ahead and put the records number into the tagline so we'll pilpick over to that record again and now we'll search for its number uh icon let's maybe throw in a document title wait for iw task completion and then description we can put in some helpful information say waiting for and let's get the assigned to again wait for condition a little larger on that yeah sure hopefully it won't take away from the layout experience a little bit uh was that better thank you sure sorry about that so here we can pill pic into the record and find the assigned to and we'll take that person's name waiting for so and so oh all right apps my mistake i hit delete let's do that again oh and something strange is happening here and then we'll throw in that record number one more time okay and let's start with just that let's go ahead and save this new activity definition and now in the designer we're going to delete this generic wait for condition and add our custom one wait for iw task completion and if we configure it we can see again the conditions and the table are already pre-filled for us there's nothing that the process owner has to specify other than which record they're waiting on so here we'll go to the activity list we'll see that we're going to access the automated create record step and we're going to go to its outputs and access the record that it generated there that's what we're waiting for we'll reactivate this and we will now kick off a new skip through this quickly now we have a much more useful card here you can see the tagline the icon waiting for able to complete this uh and very useful but we still have to get to this record somehow right we don't want them to have to go to the task that word that's where declarative actions come in so let's go ahead and add a little header icon to this where we could click on something to open up that record and see what its state is so we're going to go under playbook activity actions we'll click new and we'll call it view iw task we'll give it a unique name and now this can be a ui component such as a modal a client action or a server script we're going to make a client action and we're going to choose preview record which is the client action that opens up a record in the new tab and workspace for table this is specifically for iw tasks and we're going to render this as uh we could choose button a header drop down menu or a header icon we'll choose header icon and for this let's just choose an eye icon now for our conditions let's make sure that the user has read access to this record um and i think that's really all we need to do here so we'll save this because this doesn't change the way the process runs in any way we don't have to kick it off again we can just reload this record so i'm just gonna hit the back button reopen it refresh and sure enough we have a little eye icon here view iw task where we can open that in a new record great now the thing is we still need able here to go and mark this as complete do some extra work what if able is actually viewing this record what if we could add a close button here so let's do that one next click new and call this close iw task and this time we'll run a server script again on an iw task and this will be rendered as a button we can choose primary secondary tertiary we'll leave it as primary now for these conditions they actually need to have right access because they're going to be updating the record and we only want this button to show up if the it's not already closed so we're going to go and say is not one of closed and then we're going to jump over to the server script field and set the state equal to 3 which is for close complete because this just extends the task table and then we're going to update the record just like a ui action and now if we refresh we can see there's now a close button and if i clicked on this it would actually close this record but i'm not going to do that yet i'm going to show how we only want the person who can close this is to be the one who's assigned to we want to have different experiences for different users if we go back to conditions here we can add another condition and we'll say assigned to is me and now that button goes away because i am not able but if i impersonate able that button comes back uh there it is now what if we wanted to um say well this is great but i want able to actually be able to not just one click close i'd like them to be able to find provide some closed notes so maybe update the priority do some other work now in this case maybe there are some ui policies we want to observe business rules so rather than and we want to have a custom layout so rather than just provide a comma separately to fields i'm going to create an actual form view a fully featured form view to embed here i've already done this ahead of time so we're going to jump over to the activity definition that we just created and under the activity experience now i'm going to jump to form view and use the one i created called playbook now i can't just kick this process off again because the moment we click activate we now block down snapshots of all these different activity definitions so they're not going to reflect any changes we made to activity definitions that's on purpose you never know what processes might be in the wild if someone updates the definition you don't want to break something that's already out there so i could delete this and re-add it but instead i'm just going to go and show how a process owner could override something if they wanted to i'll switch to the advanced view i'll go to the activity experience i can see here that form view has not been set because we're using a snapshot again so i'll just add it here and i'll reactivate it now the next thing we have to do though before this will work is this activity assignment the close button we now need to say that this requires form fields form fields required because now it's no longer just doing something on its own it's actually submitting the form if there's no form to submit no fields this button isn't going to show up because it wouldn't make sense likewise if there's no button on a form we render the form as read-only the reason we do that is so that you can control when a form is actually control editable or not when something can be submitted by adding a submit button i'm highlighting this because this trips people up all the time we still get support requests saying hey my form is read only and you have to go in here and mark this form fields required you're without a submit button the form will be read only and i'll show the use case of why that's important if i went here and kicked off another process here we see a read-only form the priority we expect expected start the close date this is that form field read-only because there's no uh close button we're not the one who's assigned to it so we don't want to show them a field like this but if i go and impersonate able and refresh able c is the actual rich form with the layouts with the date pickers the ability to change the priority and say i'll do this next week and close the task completing the job and furthermore if i go back and expand that now i can see it's read only again and uh with the dates of what i submitted because if you recall if i end impersonation and go back to that definition for that button we had a condition on there not only does it have to be assigned to able but the state has to be not be closed complete and complete or skipped since the task is now done uh you can't go back and re-edit that form we could if we wanted to uh you know make another button that says reopen or change and require form fields and also those form fields will be editable again again we're making this as granular as possible so you can really control this experience very you know basic sampling of some of the things you can do with these pill pickers and with these fields and controlling the experience there's a lot more here now in terms of configuration everything is wrapped up in what we call playbook experiences all the configuration records all the things that you can control are bundled up into this master config record that way you can create custom playbook experiences for different scenarios we have a custom improved work playbook csm provides their own complaint playbook hr has their own all their groupings and configuration records it is optional if you don't specify one by default we will use the global playbook experience which is the defaults and it's also granular you can you can override specific parts of the global playbook experience so if i look at the global playbook experience i can see here that it defines a configuration record which lets me specify whether or not to show activity state and cards what fields we want to filter on whether to filter on the card status which assigned to field we should use for those badges um this guy this badge here if you want to use a different field instead of assigned to the maximum form field to be shown a card before a form is shown in modal and sla configuration you can also override it for a specific playbook not just for a specific playbook experience one process definition so if you don't create your own configuration and you can see the improved work one for example actually in this case it does but if you don't create a specific configuration it's going to use the global one in addition to our configuration record you can see we have these activity overrides this is where you can specify what you want to override and when so for example if i take a look at the say knowledge article override we can see that we have a when to apply tab and a what to override tab if the type is ever knowledge we want to override the renderer and render it with a knowledge card renderer instead so you can filter based off of the type the input table conditions on the input table the associated table conditions on the associated record any of the activity property conditions tied to this type you can build condition builders around them and then what's override you can choose to override the render you can choose to override the expand state if you want to expand it for example if it is assigned to you or you can require specific roles to view that activity if the user doesn't have access in those roles that activity will be invisible to them so that's it for the demo we have a couple more slides to jump through here just to wrap up so some key features we showed this lets you visualize and interact with processes in real time you can define user interactions with declarative actions you control the user experience with activity overrides you can integrate playbook experience into any workspace you can extend the experience with custom activity renders we support processes built to process automation designer as well as hr life cycle events and we have a framework for extending others as different product lines decide to use playbook experience as their front end and because this is on the now platform it's extendable with everything and now platform can do from service level management performance analytics machine learning etc anything the platform can do you can embed direct nothing is dependent on on pad for example we are investing heavily in this product there's a lot of features coming down the pipeline just in quebec there's the ability to cancel the playbook once it's been running the ability to manually trigger playbook so you don't have to wait for conditions to be met you can do it based off of a user action declarative actions for specific playbook experiences so if you want to have actions that don't have the potential to bleed into someone else's playbook experience from csm to itsm and so forth you can do that in quebec declarative actions for specific activity definitions so if you want to just have a process owner drag and drop something on there and know that it's going to have a save button you can have that uh we'll have it declared about is that not only can be activated on an activity but can be activated on an entire stage or an entire playbook we have a brand new very modern ui that we're really proud of activity state mapping the ability to control what the status of a card is and the ability to add playbook to any page with ui builder not just workspace all that is coming in quebec lots of ideas for rome and beyond that still very much in the planning stages stage conditions ad hoc activities nested playbooks grouped activities custom playbook layouts playbooks for creating new records building custom activity renders and ui builder in a modern admin experience so you don't have to rely on all the forms and fields we just showed so it's a great time to get involved it's a great time to start playing with this building your own playbooks because the future is really bright and that is it for me thank you wonderful thank you very much a lot of good demo there were some questions in here about uh you know this is a part two it was it was clearly stated that by what we should have done is put a link to part one somewhere on the registration page or whatever uh we will take that into account if we ever do a two-parter again in the future so thank you very much we do have a question that just came in as i was talking will playbooks have an equivalent to flow designers code snippets to be able to use slash trigger playbooks from business rules or other elements of code i think we need some differentiation between the playbooks and the uh the process automation designer and the playbook experience so do you have any thoughts on that yarn sure if i understand the correct the question correctly in quebec we do provide um we are providing a um a scriptable method where you can fire off any playbook manually you just give the the scope name of the playbook a parent record you want to fire it on and it will execute that and you can do that based off of a declarative action or a ui action so you can present the agent with a button to launch a playbook on some child record for example we have another question that just came in where can i practice for both pad process automation designer and playbook experience i'm not mistaken you can do that on the personal developer instance if you've got a paris instance over at developer.servicenow.com so head over there get that i think it's turned on by default in paris but you may have to activate a plug-in i've got to check on that there was uh something about yeah i believe you have to activate something yeah the not only the process automation designer plug-in but look for the one what was it the special one around custom apps or the custom tables uh there was something in there that if you if you go to the uh the lab the creatorcon lab it lists all the plugins that you should activate nice playbook working we should bring that deck back up where is my sorry i'm still getting familiar with actually right all right i'm going to trust you on that one because yep there it is ccw 1001 i'm i'm looking for my live view and i've got to pop that out i've got the q a in front of me we've got a new control panel in front of us people so apologies for a little bit of the confusion and stumbling around but yes this will be available online you can do that i walk through a a step-by-step process automation designer uh lisa holdenstein who i believe is on this video and also the person on the left hand side of that picture put that all together so get a paris instance or you want to go do this with one of our instances you could do that as well so look forward to walking through that situation are there any other questions craig or jeremy as i put flip around panels on here where can you find the lab um you can ah good question thank you jennifer you can go over to now learning dot or you can go to i believe it's servicenow.com creatorcon.html and log in and find the session there so either the creatorcon 2020 digital experience page from our main page or write to now learning and search for ccw 1001. i think you can also find it on developer.servicenow.com just do a search for ccw1001 should have the lab guide and that will give you instructions on how to get started on that so lab guides in one place simulator and with the walk through materials on another it all comes together in a wonderful experience uh inactivity definition instead of the fulfiller seeing the read only form fields or the form field in the activity definition can a deep link be configured for a task we are waiting on or a related task item did you catch that era yeah we kind of did that we um we added a uh that i icon as that declarative action that would let you open up that record in a new tab so it's not done automatically we definitely we're we're taking approach with this to really give the admins a lot of control and to not make a lot of assumptions for them so if they want to add an icon because maybe you want that to be a button maybe you want to be a drop down maybe you don't want it at all you can add that and you can also add that conditionally so you can say for example add a button that says if it's not assigned to you in which case you can't close this you can't see the form then we'll give you a view record like for example i am going to be a little pedantic on one element that i saw you do when you're putting together that action where you said uh the state is one of and he said close complete close incomplete and close skipped all of those set the active field to false so think about another alternative of saying active is false or active is true it's it's the inverse because what i've seen in the past is people will say oh we need a new state and it'll be a new open state or new closed state being active equals true or active equals false and you have it's no fun going by and looking for all of those actions that are choosing state or finding them later going why isn't this working when we're in this one state so think about the ways that active is impacted by state and you can often shortcut a lot of these uh maintenance issues later on good idea choiceless gotta love them but i do like the is one-off that came along years ago and it wasn't part of the original platform that i grew up with and when i discovered it went oh this is so nice right do we have anything i'm kind of surprised to use pandantic in a sentence all i like to pass on the uh the occasional tips of experience that we get in this show you know we've all got lots of lots of experience and nuggets of information that we can share so when i see like okay that's a different way that i hadn't thought of let's share those okay thank you very much yaron let me just do the closing we invite you to join us next month where i promise the audio will be better when we start i will fix this up in post and get it posted out to youtube as well but registration is already open for tech now number 82 if you go to bitly slash tn82 reg you can find it there craig is going to be our instance data replication or idr subject matter expert so he is actively working on that right now to pull together all the information he can and show off how you can tie two servicenow instances together and exchange data very quickly this is not building complex rest integrations and whatnot that you may have experienced in the past so i remember it's really a cool product and i see a lot of flexibility in it uh for a lot of use cases so looking forward to it give yourself a christmas present join us december 15th an early christmas present december 15th 8 a.m pacific time or whatever that is in your time zone we look forward to that go over and sign up for that right now if you want there's also a link in the resource panel for that as well other reference information of course all this is good stuff from the docs site go to the community if you've got questions the developer portal if you want to go get a free personal developer and just play around with some of these things see if you can build out a process automation designer watch video number one that's over at bitly tn 80 blog so i do have a system of madness to these bitly links that i distribute because i got to remember them it's really hard to remember a community link with a society in it so i shorten them up for you and for me yeah don't share sis ids out that'd be crazy read those over the phone yeah uh we also have plenty of others over at this bitly lake bitly servicenow tech now that's the master that's the home that's the index of all the episodes we've done to date going back to early 2013 so you can see you know the different hosts and the different haircuts and you know it's kind of fun as we go through this but always that same theme music for whatever reason so if we didn't get to your q a today many apologies we are running a little uh short up on the end of the hour and we will answer those online and send you a notification with a link right to the community article with your answer to those questions thank you very much for joining us today i don't do we have any last minute we'll do we've got a couple minutes let's uh check do we have any last minute q a that needs uh filtering through this through yaron well we've got him here he asks craig and jeremy i'm actually looking um i don't see anything we haven't really spoken about already all right then that's asking if pad uh if the cd uh the creator con 1001 will include playbook yes if you go and do that automated lab it'll set up as an instance with everything pre-configured for you you just walk through the lab exercise so pretty straightforward i say jeremy already answered it so yes jeremy's on top of it thank you gentlemen for joining us thank you yarn for sharing the uh playbook you know the peanut butter and jelly we had peanut butter last month we got jelly this month so i'm not going to sing this on but you get the idea we'll move on and uh hope you can join us next month dear viewer for december 15th when craig talks about idr until then take care be safe and talk to you soon [Music] you