iCIMS Hacks: Smarter Integrations Start Here (2/6/26)

Planning an iCIMS integration? This session digs into how to get started the right way. We cover the iCIMS developer site, choosing between standard, API, and custom integrations, common derailers like vendor API limits and missing field mapping, and why scoping conversations matter before you build.

https://systemadmininsights.com/

Transcript

Copy Transcript Copied

04:02 Alright. So let's go ahead and get started. Welcome everybody 04:04 to System Admin Insights, a community of highly creative system 04:08 administrators getting the most value out of ISIMs. And welcome 04:11 to anybody who's joining us for the first time. Today, 04:13 this is an experiment 04:15 with hosting this call in circle. So bear with us 04:18 with any technical difficulties. Let us know how it goes 04:20 for you. And if there's any issues that that prevent 04:23 you from participating fully, 04:25 just send me a DM in the platform, and we 04:27 will work on that and figure it out. We like 04:29 to start with a little gratitude 04:32 every call. So today, 04:34 I am grateful for my 04:36 sister, 04:37 Alyssa, who is the queen of dad jokes. And this 04:40 has been a tradition 04:42 between us for for as long I mean, our entire 04:45 lives. And so and so she hit me with this 04:48 1 yesterday. She said, why should you buy a funeral 04:51 home? 04:53 And my answer was, 04:55 because of the inevitability of death, creates a fully recession 04:58 proof business. 04:59 And she said she said no. She said, it's a 05:02 unique earning 05:04 opportunity. 05:07 Peter Peter Peter appreciates it. 05:10 Yes. That is Terrible. 05:14 That is that is fully 50 percent of my dialogue 05:16 with with my sister. And, yeah. So what else have 05:19 we got in chat here? So Caitlin says, 05:21 Caitlin says, there's fluffy snowflakes outside my window. All the 05:25 other ones have been at night, so I've missed them. 05:27 Got it. 05:29 Vivian's grateful for family. Me too. Liam says, wish my 05:32 cat would hang up in the office. My cat hangs 05:35 out in the office too much. In fact, I have 05:36 a I have to have a I have a bell 05:38 to get rid of her when I'm on calls. 05:40 Patrick says, grateful for Super Bowl Sunday. 05:44 Alright. Michelle, looking forward to the Super Bowl. Go hawks. 05:47 Terry says 27 years married to the same Wonder Woman. 05:50 Alright. That's beautiful, Terry. Thanks for sharing that. 05:53 And we got Sherry coming in with 1 here. 06:01 Alright. Sharice is looking forward to Super Bowl halftime show. 06:04 Yeah. Me too. 06:06 Alright. So, 06:08 this recording is, 06:10 gonna be in the platform, so you can view it. 06:12 It'll get auto posted, and the transcript will automatically feed 06:14 the AI in here. So all the conversations we have 06:17 about ISIMS, you'll be able to reference with the, with 06:20 the transcripts and with the AI. 06:22 And we will start with Vivian. 06:26 Vivian Larson, HR technology strategist at IRD with a forthcoming 06:30 book 06:31 called from 0 to ATS hero. We've been working on 06:34 this for months, and it's it's in Vivian's it's Vivian's 06:38 career and brain in book form. And, 06:41 I worked with her on editing it, and we're looking 06:43 to release this very shortly, 06:45 probably by the end of the month. 06:47 So, 06:48 we are looking forward to sharing that with our members. 06:51 Vivian, you're gonna talk to us today about the ISIMS 06:54 developer site. Is that right? Yep. So I'm gonna talk 06:57 we're We're actually gonna do several now you knows on 06:59 this because the topic is just too much to talk 07:01 about in 1 of these sessions, 07:03 and I don't wanna bore everybody. We do still have 07:04 questions that everybody wants answered on these calls, so it's 07:07 not gonna be the me show. 07:09 But, essentially, 07:10 we've gotten a lot of questions 07:12 from a variety of our customers about, I have an 07:15 integration. I think I have an integration. I might wanna 07:18 do an integration. How do I do it? 07:21 And so we're gonna do a couple of now you 07:24 knows about, 07:25 the developer site and about the process of getting ISIMs 07:29 involved in an integration so everybody is in the loop 07:33 on what needs to happen, and some of it's stuff 07:35 that you wouldn't really intuitively think of. 07:38 So 07:39 there's a poll. Do you wanna launch the poll for 07:41 me, Alex? 07:43 Caitlin, you got it ready to go? So this we 07:46 had to do a workaround for poll functionality in Circle 07:48 because they don't have native poll functionality the way that 07:51 Zoom does. 07:52 Caitlin, how's it be? You on it? Yep. Great. Alright. 07:55 So the way we're gonna do this, 07:58 is we're gonna post the question, 08:01 and then we're gonna thread the 08:03 options. 08:04 And you are going to emoji the option that you 08:08 select. 08:09 That is our workaround for 08:11 rigging pull functionality. So Caitlin has a first question there. 08:15 You need to initiate a new integration or update an 08:18 existing 1. What is your first 08:21 step? 08:21 So let's see here. Option a is contact your account 08:24 manager to verify the connector is available in your contract. 08:27 Option b, enter a case with help desk to get 08:30 to to get the implementation queue to get in the 08:33 implementation 08:34 queue. 08:35 Option c is verify your vendor is available in the 08:38 ISIMS marketplace. 08:40 Option d 08:42 is request a scoping call 08:45 with 08:46 a solutions consultant to map out requirements. And option e 08:49 is reach out to your customer success manager for guidance. 08:54 First of all, bravo. 08:56 We did it. We did it. Okay. So react to 08:59 react to the reply there, 09:01 with the 1 that you're voting for. Oh, it's working. 09:04 It's multi select, folks. So if you wanna if you 09:07 wanna go ahead and select the ones that you think 09:09 are relevant, it must be 1. Select. 09:11 That's wonderful. So we've got 3 votes for select. 09:15 3 votes for 4 votes for option c. 09:19 Votes are incoming. 09:21 We'll get this 10 more seconds. 09:27 Where should I be seeing this? So it's in chat. 09:30 Yes. So if you haven't found the chats, it's at 09:32 the bottom of the screen. 09:33 So at the bottom of the screen, depending on how 09:36 wide your browser browser window is, 09:39 it should be 09:41 there's a there's a share screen icon in the middle, 09:43 which is to the right of the camera icon. 09:46 And to the right of the share screen icon is 09:48 the chat icon. Are you still not seeing it, Peter? 09:51 I see the chat. Okay. So click the chat, 09:55 and 09:56 you will see, 09:59 Caitlin has the most recent 10:02 chat there. She says you need to initiate new integration. 10:04 And if you click 10:05 replies, 10:06 view thread Ah. Then you can see the replies there. 10:10 I see it. Okay. 10:13 Yes. Okay. 10:14 So there's a very good reason this is my first 10:16 question because it's everybody's first question. I need an integration. 10:19 Now what? 10:20 And 1 of the things when I worked for ISMs 10:23 that we would frequently run across was that there's, like, 10:26 nope. There's no real good place to start. There's not 10:29 a lot of clarity. Customers didn't even know what they 10:31 didn't know because a lot of times folks that are 10:33 doing this day job are not IT people. They are 10:37 folks like you and me who started out as HR 10:40 recruiters, and this is not how we are trained to 10:43 think. 10:44 So 10:45 there are a number of good answers, 10:48 but there are also a number of best answers in 10:51 this list. Every single 1 of them is a possible 10:54 path, 10:55 but the 1 that is the most 10:58 appropriate path is d. 11:01 And the reason that I say that that is the 11:02 most appropriate path when I'm looking at your numbers here, 11:05 it only 2 people selected it, 11:08 is because 11:09 you come into an integration conversation with an idea in 11:12 your head of what you want. 11:14 And when you actually talk to someone who understands the 11:17 technical challenges of building an integration, 11:19 your perception of what you need will evolve 11:23 and change. 11:24 So I will frequently start with folks who think that 11:26 they need an API integration with all the balls, bells, 11:29 and whistles back and forth. And when you actually figure 11:31 out what they want, they want a single flat file 11:33 packet that'll take, like, 5 minutes to build. 11:36 So 11:37 before 11:38 you engage an ISIMS resource because that is a process 11:40 and we will get into that, 11:42 you wanna really understand what you're building, what you need. 11:45 And then 11:46 c, 11:47 verify that your vendor is available on the market place 11:50 is also really important thing to make sure that you've 11:53 done before you engage anybody at ISIMS. Because if they're 11:56 not, 11:57 there's 2 different layers of integration with ISIMS. They're standard 12:00 and custom. 12:01 That's any SaaS provider 12:03 across the board. This isn't an ISIMS thing. This is 12:05 SaaS software. 12:06 So standard and custom simply means you're building it yourself 12:10 from scratch, which means you need a developer 12:13 or 12:14 you already have a framework or a backbone that ISIMS 12:17 has navigated with vendor, 12:19 and that backbone is something that they can give you. 12:21 And you can work within that backbone. 12:24 There's pros and cons to both sides, but if they're 12:26 not on the marketplace, you're 100 percent guaranteed it's custom, 12:30 which means that there may not be an ability 12:33 for the 2 of you to do an integration between 12:36 ISIMS and whoever the vendor is on account of the 12:38 fact that it their the technologies haven't been evaluated by 12:41 both companies to see if they can communicate with 1 12:44 another. 12:45 It's very rare with API 12:48 available and with the way that ISIMS API is structured, 12:51 that it's not a possibility. 12:53 But ISIMS will need a developer on their side to 12:56 actually build the the protocol to connect the 2 systems, 13:00 and the vendor will need a pro an an, 13:02 someone on their side from a development perspective to develop 13:05 the protocol. So if it's a completely new vendor who's 13:08 never worked with ISIMS, it can be a very long 13:10 process. 13:11 So that's why starting with the marketplace, 13:14 is it available is your first step. And then your 13:17 next step, if you're positive it's available, is to reach 13:19 out to your account manager 13:22 to tell them what you're trying to do, account manager 13:24 or CSM, if you're lucky enough to have a CSM, 13:27 and then see if they can schedule a call with 13:30 a scoping, 13:31 solutions consultant. Doctor Rob Bursey about this before today's meeting, 13:36 and he said that this step is the 1 he 13:37 wished more customers would actually do. 13:40 And the main reason for that is because 13:43 in my experience, 13:44 hundreds of integrations 13:46 starting a lot of these conversations. The customer doesn't know 13:49 what they don't know because they don't know what's possible 13:52 coming into an integration discussion. 13:54 So they come in with 1 idea and then either 13:57 they're shut down because they don't know how to communicate 14:00 what they're trying to do, 14:02 or it's physically not possible to do what they're trying 14:05 to do, or there are technical limitations, 14:07 or there are regulatory 14:08 limitations. 14:10 I've had some 14:11 rare ones where folks wanted to create, like, email integrations 14:15 and the emails contained PII. 14:18 And so ISA just nope. Isn't gonna do that because 14:20 it's a major security risk. So, 14:24 like, you need to understand when you're trying to build 14:26 an integration, what it is you're trying to do, and 14:29 whether it's technically possible. So that step is a big 14:31 1. Any questions before I keep talking at you? 14:35 No? Alright. So go ahead and launch the second question. 14:40 Second question is incoming. 14:42 Mhmm. 14:45 So the question 14:51 is before selecting your integration type, 14:55 what do you prioritize? Option a, 14:58 speed and cost, 14:59 which means choosing standard API to get started faster, 15:03 b, creating a master list of all fields and values 15:06 that you might need with a 2 to 3 year 15:08 outlook, 15:10 c, understanding if you need bidirectional sync capabilities, 15:15 d, evaluating all 3 options, flat file versus standard API 15:18 versus custom API, 15:20 and e, whatever my vendor recommends as their default 15:25 connection. 15:28 Options are loaded up in the most recent chat message. 15:31 You can click where it says replies, 5 replies, view 15:34 thread, 15:35 and start voting. Voting is coming in. 15:40 We've got a couple of votes for option d evaluating 15:42 all 3 options. 15:47 D is pulling ahead 15:49 followed by c and b. 15:52 Nobody's choosing whatever my vendor recommends as a default connection. 15:57 If I'm being surprised by that. I would choose that, 15:59 but I would feel judged for choosing it in this 16:01 group. So I didn't vote for it. 16:05 So, Christine, to vote, you would put an emoji 16:07 on the option. So if you hover over the option 16:10 and click the smiley face, you give it a thumbs 16:13 up. 16:14 Alright. So, Vivian, it looks like Dee has pulled ahead 16:17 by significant margin evaluating all 3 options, flat file versus 16:20 standard API versus custom API. 16:22 What do you think? 16:23 So 16:25 I want everyone to take this with a grain of 16:26 salt that I've built hundreds of these integrations. 16:30 So my level of understanding 16:33 is different. But 16:35 personally, 16:37 I find that a is the choice most people pick. 16:40 And meaning 16:42 standard integrations are fast. 16:44 Standard integrations are preconfigured. 16:47 It means that you have an out of the box 16:49 set of fields that you are going to be 16:51 expected to, 16:53 map your process and your system configuration to 16:57 and deliver, and they will turn around fast. 17:00 Standard integrations are the ones that we have the most 17:02 help desk cases for within 6 months. 17:04 Because standard integrations do not take into account the fact 17:07 that every single customer that uses an ATS 17:10 is not standard. 17:12 Everyone has done something extremely custom, and standard integrations don't 17:16 give you the flexibility 17:18 of the customization 17:19 that you are looking for. So 17:22 in the framework 17:23 of ISIMS, 17:26 API is really 1 of your more 17:29 flexible 17:30 options. 17:31 And the standard API is the 1 that I would 17:33 recommend going for because it is the most stable. 17:36 There are a set of fields that are preconfigured as 17:39 available. 17:40 But as opposed to I know you're hearing standard and 17:42 standard. This is 1 of the confusing things about the 17:44 way that they name their stuff. 17:47 It's a what's on first, who's on second kind of 17:49 conversation because you're hearing standard API and you're hearing standard 17:51 integration out of my mouth. These 2 are not the 17:54 same thing. 17:56 A standard integration 17:57 is the vendor has a list of stuff that they 18:00 want from ISIMS 18:02 1 through 50. 18:04 Standard API is here are all the possible things you 18:08 could potentially call 18:10 within ISIMS 1 through 1000. 18:13 The difference between the 2 of them is if you're 18:15 building an API integration using the standard API, 18:19 you can customize whatever within that list of fields 18:22 that are and options and items within the standard API 18:26 are available to you, and you can build what you 18:29 need to collect 18:31 even though it's standard 18:33 versus a standard integration 18:34 is rigid. It's this is a list of what you 18:37 got, and we can't 18:38 within reason, there there are 1 or 2 areas that 18:41 they could potentially customize. 18:42 But for the most part, you are stuck with whatever 18:45 the standard list is. And if you have gone and 18:48 customized your system extremely 18:50 everybody hates those ex education fields. They're ancient. They stink. 18:54 They don't work well. A lot of people will go 18:57 out of their way to get rid of the the 18:59 education fields and put in a custom education field. Well, 19:01 now guess what? 19:02 You can't send education as part of most of your 19:04 standard integrations because you're no integrations because you're no longer 19:08 using the standard field within ISIMS, and you've been gathering 19:10 data in a place that isn't available in the standard 19:13 integration anymore. Oh, Vivian. Sure. For a second. Go ahead. 19:16 Yeah. Yeah. Sherry commented, I've never been able to use 19:18 anything standard. There's always something we need that is not 19:21 included. Yep. 19:22 Yeah. 19:23 So standard is a 19:25 going I'm gonna tell you a little bit of a 19:27 long history story and date myself here. Going back to 19:30 2008 19:32 when I was working at KBR 19:34 implementing Brassring, 19:36 there was this mindset that we were going to start 19:39 creating plug and play 19:41 integrations. 19:42 And that mindset has stayed within 19:45 the ATS world. 19:47 I've talked about it and complained about it to friends 19:49 at Workday and friends who work with SuccessFactors and a 19:52 girlfriend who works at Dayforce and a friend of mine 19:54 who works at SAP. We all have the same 19:57 executive battle with the leadership mindset that there should be 20:01 this plug and play ecosystem 20:04 with all of these different systems. You find in this 20:06 you find the same thing with with, Salesforce, which is 20:08 another big SaaS software where they think that everything should 20:11 be plug and play. But, unfortunately, 20:14 the nature of software is that it is customized for 20:16 the user, 20:17 and there is no such thing as plug and play 20:20 in these worlds. If you think physical hardware, 20:23 your laptop could have a completely different DRAM set than 20:26 somebody else's, and those 2 manufacturers' 20:29 hardwares have different firmware, and the firmware doesn't talk to 20:32 1 another. So 20:34 it's the same thing. Let me think of, more non 20:37 techie answer. Well, if I could jump in, I think 20:39 a lot of people's expectations 20:41 are set by, 20:43 b to c software experiences. 20:45 Yeah. Google is so easy to use. It integrates with 20:47 everything. It's easy. And Google's also 1000000000000 dollar company or 20:50 whatever. Right? And so, like, 20:52 subgiant 20:53 things that we use every day, 20:56 it gets more complicated. Right? Mhmm. Don't ever get anybody 20:59 who does app development get started on Android. 21:02 Yeah. But, anyway, so it's 21:07 standard is this 21:09 ideal, 21:10 pretty everybody thinks it's gonna be perfect because it's a 21:13 set of fields, and it's speedy, and it's fast, and 21:16 it's wonderful. 21:18 But really take the time. That's why the previous question 21:21 I was saying start with a solutioning expert is so 21:24 important. 21:25 Really take the time to understand your ecosystem, what you've 21:28 built within ISIMS, 21:29 and what your 21:30 benchmarks 21:31 of crucial information are 21:34 before you decide. 21:36 It doesn't matter flat file API, custom standard. None of 21:39 that matters. What matters is, are you a special squirrel 21:43 or are you a simple Sally? And if you are 21:46 very special, you've built customizations 21:49 and workarounds 21:50 around fields that are standard within the system, those standard 21:53 integrations are gonna be a pain point for you for 21:56 the most part. And the place where I see this 21:59 pain the most is HCM integrations, 22:01 especially HCM and data warehouse 22:04 integrations, the, you know, Workday, Dayforce, 22:07 SAP, Oracle, all of those. They have a set of 22:10 standard integrations that ISIMS will ask you 22:14 to first look at because they are 22:17 preconfigured 22:18 and they are the quickest timeline and turnaround for their 22:21 integration 22:21 specialist to help you stand up, which is attractive on 22:24 both sides. ISIMS has the resource, has a defined time 22:27 frame for the resource to work with you. You have 22:30 the resource on your vendor side. They have a defined 22:32 time frame. They can work with you, and it looks 22:35 great on paper. 22:36 But at the end of the day, if you didn't 22:38 really sit down and analyze what you need in your 22:41 system's architecture, 22:43 that final product 22:45 may be 50 percent of the end goal of what 22:48 you were trying to achieve. So I'm gonna shut up 22:50 now. Questions? 22:54 Alright. So, 22:56 I have a question. When you say, when you say 22:58 standard, it's it's their 22:59 ISIMS calls it as prime. Right? 23:02 So so this is another place where they've relabeled things 23:06 and named them different things throughout the year. So, yes, 23:09 Prime Okay. And Standard are the same thing. I think 23:12 they've moved away from Prime. Prime is just a kind 23:15 of, 23:16 standard integration. 23:18 Okay. 23:18 Yeah. 23:20 Thank you. 23:21 So at the top of the hour, we're gonna move 23:22 over to our member questions. We've got questions from Christine, 23:26 from Tanya, Amanda, 23:28 Peter, another 1 for Christine, and Cheryl. 23:31 But we're gonna we're gonna do 1 more poll. Vivian, 23:33 is this a good point to transition to the third 23:35 1? Great. Yep. So Caitlin's gonna load up the final 23:37 poll question. 23:38 And the question is, what derails integration projects most often 23:42 in your experience? 23:44 Option a will be starting with standard API, then discovering 23:47 we need custom mid implementation. 23:50 Ouch. Question, 23:51 option b is realizing too late that we needed bidirectional 23:55 sync. 23:55 Also, ouch. Question c, incomplete field mapping and missing must 23:59 have data points. All of these are making me cringe. 24:02 Option d, underestimating timeline and resource resource availability, 24:06 4 to 6 plus week queues. Or option e, vendor 24:09 API limitations 24:10 we didn't know about upfront. 24:12 I have no idea, frankly. What derails integration projects most 24:15 often in your experience? 24:20 Sorry. I'm gonna let everybody answer. 24:24 Alright. Give another 24:25 10 seconds. 24:29 I was reading that as what is the thing that 24:31 most derails are where you're asking for people specific experiences. 24:34 Got it. Okay. Yeah. 24:35 Alright. So c, incomplete field mapping and missing must have 24:39 data points, 24:40 is actually option e is now leading with vendor API 24:43 limitations 24:44 we didn't know about upfront with 8 votes. 24:48 It looks like that's a clear winner. Vivian 24:50 Yeah. What do you think? 24:51 It's kind of all of the above. 24:53 And the reason I say it's all of the above 24:55 is I've been in a scenario where every single 1 24:57 of these is what's happened to my customer. I've even 25:00 been in scenarios where every single 1 of these happened 25:02 to 1 customer on 1 integration. 25:06 So that was a nightmare. 25:07 But, essentially, I agree with Eve being the 1 that 25:10 most people have 25:12 problems 25:13 with, and that is a pivot point for me. I'm 25:16 gonna drop something in the chat, and that is something 25:19 I don't know if all of you are aware of, 25:20 but if you're not aware of, you really need to 25:23 be. So ISIMS has spent 25:25 a ton of time and effort in documenting every single 25:29 piece of their 25:31 integration functionality. 25:32 There are gaps. 25:34 They don't always 100 percent line up, but there is 25:37 a group in that, in the organization now that is 25:40 very 25:41 dedicated to trying to keep this thing as up to 25:43 date as humanly possible. 25:45 So the developer site, I'm gonna just quick flash over 25:48 to it in the 5 minutes that we have. If 25:50 you are not, 25:53 then you see my screen. 25:55 No. I don't wanna share this window. 25:58 Share this window. Okay. So if you are not familiar 26:00 with the developer site, you should be seeing an ISIMS 26:02 page right now. Everybody seeing it? Okay. This is the 26:05 ISIMS developer site. 26:07 So anytime you have an integration, 26:10 start here. And start here with a technical resource because 26:13 this resource, it's a fabulous resource, 26:16 but a lot of us have no idea how to 26:17 read it because we're not technical people. 26:20 It actually if you look into the developer site, it 26:23 will go into calls 26:26 and the specific 26:27 call structure 26:29 that you need in order to do the different payloads. 26:32 And so this can be a lot if you don't 26:34 really know what you're gonna do. So in the next 26:37 series of now, you know, I'm gonna be deep diving 26:39 into each and every individual piece of this. But if 26:42 you have not requested access because it is behind a 26:45 login and it isn't something they have open to everyone, 26:50 you're gonna wanna go to the link that I just 26:52 dropped in the chat 26:53 and 26:54 ask them to create a new user for you. You've 26:57 got a new user request form, 26:59 and just go in here and familiarize yourself with us. 27:02 This is a really important resource for you to know 27:04 even if you're not currently in the process of looking 27:06 at integrations 27:07 because it gives you the ability to see all of 27:10 the different potential integrations that ISIMS has. 27:14 It gives you the ability to to I identify some 27:17 of the different 27:19 kinds of integrations, whether they're API, whether they're flat file, 27:23 etcetera. And it actually gets into the specific nitty gritty 27:27 of every single 1 of the integrations that is out 27:29 there. So it's a really great resource you really need 27:32 to familiarize yourself with even if you're not currently 27:35 in the process of planning an integration. 27:37 So any questions on this? Boy, we got Jeff Mueller 27:41 on the call here today. Jeff, you got anything to 27:42 say about integrations? 27:46 Wow. Unexpected pressure. Yep. 27:49 You're welcome. 27:52 Yeah. No. I'm just it's I I think Vivian's hit 27:54 every point. And and I'm just gonna say that the 27:57 the 1 thing that drives me the craziest is having 28:00 because I'm experiencing it right now with a, 28:03 a certain ATS and trying to trying to do some 28:06 work with them is 28:07 their ATS documentation 28:09 is straight trash, 28:11 and it doesn't do 28:13 some, like, of the most fundamental basic things you would 28:15 expect 28:16 ATS API integration to do. And it's make it because 28:20 it's not well documented, because it it lacks basic functionality, 28:24 you know, my customer is like, what what do I 28:27 do here? The answer is you can't make the vendor 28:29 change the API. 28:31 You can't make, you know, hang out new, 28:35 new endpoints. So 28:37 what I've been trying to push 28:39 a lot more is make sure if you're gonna use 28:41 a vendor, make sure they can actually do it. It's 28:43 like, It hit the vendor. It turned out to be 28:45 a nightmare, and it's gonna be ongoing. It's so now 28:47 they're stuck with this for, like, 2 or 3 years. 28:50 It's it was just a poor decision. You know? So 28:52 make sure 28:54 your vendors 28:55 can do what you want them to do. Mhmm. By 28:58 the way, Jeff has a business called Ironclad Consulting, and 29:02 they do data migration, everyone's favorite thing. 29:05 In fact, we we send referrals out to Jeff for 29:08 the work that he does with data migration. So that's 29:10 that's why I picked on you today, Jeff. Yeah. That 29:12 was great. That's for Jeff too. Jeff and I have 29:14 worked off and on together on data migration projects for 29:17 15 years now. So yeah. 29:20 I 13. 29:21 I'm old. 29:23 Still. 29:24 You're in good company. 29:26 Ariel has said you can also request developer side access 29:29 for your other internal technical resources and your vendor contacts. 29:32 Yeah. Ah, that's good. They're not too precious about giving 29:35 access. They just want everybody to go here first because 29:38 they spend all the effort to actually build this resource, 29:41 and it's all written down there. So familiarize yourself with 29:44 it. It's a great place to go. 29:46 Great. I was typing something in the chat, and so 29:49 I wasn't fully listening. But I think Jeff may have 29:51 mentioned what I was typing in the chat, and that's 29:53 a recent gotcha that we had from, like, a payment 29:56 and contract standpoint. 29:58 So I 29:59 was not aware that you can't just pay for the 30:03 API fee for 1 year at a time. So let's 30:05 say you have a new vendor and you want there 30:07 to be an API and you want your contract with 30:10 a vendor, you only sign for a year. 30:12 ISIMS will 30:14 force you to pay the fee for your whole contract 30:17 period. 30:18 You can swap out the connector for a different vendor, 30:22 but you'll be stuck with that connector if you're in 30:24 a multiyear contract. So that's 30:27 really a bummer. You know, my feedback to them was, 30:30 wow. That really limits us from being able to try 30:32 to test new vendors when we have to commit, you 30:34 know, if you have a multiyear contract with ISIMs. 30:38 So something to keep in mind as well. 30:41 Thanks for sharing that, Jessica. 30:44 Alright, Vivian. How are we doing? 30:46 So that's all I wanted to cover for today. I 30:48 think the deep dive into the developer side and going 30:50 into the various pieces, we're we're gonna do that in 30:53 some upcoming now. You know, it's here. If there's anything 30:56 particular, like, 1 of our folks asked about a, apply 30:59 framework 31:00 that's actually in here. 31:03 So if there's anything in particular on this developer site, 31:07 go in there, look at it. If there's anything in 31:09 particular you want me to deep dive into in 1 31:11 of the upcoming now you knows, please post that in 31:13 circle, 31:14 so that we can continue the conversation. And, I'll make 31:17 sure in the now you know to mention and then 31:19 I'll go into further depth on it. But as we 31:21 continue this series, we're gonna talk about this probably for 31:24 the next 4 meetings or so. 31:26 Alright, Vivian. Thank you so much 31:29 for sharing all of that juicy 31:31 knowledge today. We're now gonna move over to our 31:36 full member questions. I will share my screen. Here we 31:39 go. 31:43 Alright. 31:44 Here we are. So we're gonna start with the questions 31:47 that are posted here in circle and then open up 31:50 it open the the conversation up to the floor. If 31:52 you're not on our paid tier yet, feel free to 31:54 drop questions in chat at any time. 31:57 But if you're a paid member and you haven't posted 31:59 your question yet, make sure you put it here in 32:00 the platform so we can prioritize it. Okay. So let's 32:04 start off with Christine. Christine, you had 2 questions. You 32:07 wanna pick 1 to go first here? 32:10 Actually, we talked about the LinkedIn applied network. Oh, we 32:12 did. I knew that. We did. Okay. How about this 32:14 next 1? 32:16 Terry actually sent me the answer already. So thank you, 32:18 Terry, for that. 32:20 I just had to remove it from her the person's, 32:24 their, login, 32:26 groups they were allowed to, and so she was in 32:28 the send from. I don't know how she got that. 32:31 We've I've been looking in the system for, I don't 32:33 know, it feels like forever trying to figure out how 32:35 to take it off, and Terry solved it in 17 32:37 seconds. So thank you for doing that, Terry. That was 32:40 awesome. Nice. 32:41 SAI to the rescue. Thanks so much, Terry. 32:44 Alright. So let's go to 32:48 Tanya. Tanya, are you in the call? 32:50 Yep. I'm here. Okay. So Tanya has a question about 32:54 screen tab configuration. 32:56 You wanna tell us about this? Yeah. So we ran 32:58 into an issue where we realized our recruiting team had 33:02 more access to background check information 33:05 than we would like. 33:07 In our integration with First Advantage, it basically imports a 33:10 PDF 33:11 of the background check. So even if you don't have 33:13 access to the First Advantage system, 33:15 you can still see every single detail on somebody's background 33:19 check, which 33:20 our HR teams are responsible for background checks. So 33:25 went into 33:26 the back end of the system just to see what 33:28 I could hide. 33:30 The hidden tab or hidden button is of is visible 33:34 there, but it was grayed out for the background screen 33:37 sections. 33:40 So I went to a TSE, and I was like, 33:41 hey. Can you just do this for me because it's 33:43 grayed out? And they said that's not possible. 33:45 So a little bit of a tease that it's visible 33:47 there but isn't actually usable. 33:50 And they said the only thing was to hide the 33:52 entire screen tab, which then you lose access to screening 33:56 questions, assessments if you have those set up, all of 33:58 that type of stuff. 34:00 So got a lot of really great suggestions 34:03 from everybody of just things like, hey. Maybe try this, 34:06 maybe try that. I think the route we're gonna go 34:09 is actually with the, 34:12 integration. 34:13 We can turn off the recruiter's visibility to it entirely. 34:17 They're not initiating background checks anymore, so it should solve 34:20 the problem for us. 34:22 But if you have recruiters initiating the background check and 34:25 somebody else evaluating, 34:27 then that solution wouldn't really work. 34:30 So You can hide the fields globally 34:32 for screening 34:34 in the background. 34:35 ISIMS can do that for you. 34:37 So they can't hide the tab. They can't hide the 34:40 background check, 34:41 but there's a set of fields that it sends the 34:44 information to. So you can actually hide those fields from 34:47 the user. It's not something you can do at a 34:50 user admin level, but a dev admin level should be 34:53 able to do it. 34:54 Okay. Because there's 2 34:56 there's 2 tabs. There's, like, our prime background screen and 34:59 then our regular background screen, 35:01 and they both contain the information. 35:04 And there was background screen, you can hide. The prime, 35:06 you cannot. Yeah. So, 35:09 I think for us, just removing it 35:12 with the integration works. But if, again, if somebody is 35:15 a bit more, 35:18 sharing responsibilities around background checks or 1 person does the 35:21 first piece but not the second, 35:23 that solution probably won't work for them. But 35:25 I think Security rule option would have been 1 of 35:28 the suggestions I made as well. 35:30 I think your route is the best way to go. 35:32 So 35:33 but just for the learning in the team, if you 35:35 don't want to hide it through the integration, 35:38 a security rule is something that you can build where 35:40 if the 35:42 background check is present 35:44 or if that field is not blank, then you can 35:46 hide the tab. 35:48 It does limit functionality. Like, they'll still you'll you're still 35:50 hiding the tab. You wouldn't be able to go see 35:52 screening questions or anything like that, but you're hiding it 35:54 much later in your process where it's less relevant for 35:57 you to look at screening questions. And then you should 36:00 still be able, even if the tab is hidden, 36:03 to attach them via email. If you're sending them out, 36:06 your user has permission to do that, or pull them 36:08 into reports if your user has that those permissions as 36:11 well. So 36:12 Okay. That's good to know too. Thank you. 36:15 Yeah. 36:16 By the way, I just wanna say hi to Jen 36:17 Theobald. 36:19 Thanks for joining today. Jen used to be a super 36:21 TAM at ISIMS, 36:22 and she's now at Air Methods. 36:24 So welcome, Jen. 36:27 Alright. Let's go on to our next question. 36:31 Amanda, are you on the call? 36:34 Don't see Amanda on the call today. 36:36 Let's see here. 36:38 Patrick, you're here. We've got Big Oops with confidential portal 36:41 posting on LinkedIn. 36:43 Uh-oh. Wanna talk us through this 1? 36:47 Yeah. We had a 36:54 Patrick, still there? 36:59 Let's see. I hear typing. I do not hear Patrick. 37:05 Patrick is typing. 37:07 Mic issue. Uh-oh. Okay. 37:10 Give me a few seconds here. 37:15 Can you hear me? Yep. Got you now. Okay. Alright. 37:18 Recruiter posted posted a job to the confidential portal. 37:22 They didn't want it to go out to anything else 37:25 but that and got a message for the marketing team. 37:28 Hey. This job also was on LinkedIn 37:31 as well. 37:32 What could we have done different to make sure that 37:36 it didn't post to the social media? Was it the 37:38 social distribution 37:39 toggle that should have been clicked? 37:41 Because I'm not sure. 37:44 Make sure Google Analytics is turned off for that portal. 37:51 Step 1. 37:52 So there's a step there's in the background. There's a 37:55 setting called turn on Google Analytics for this portal, which 37:58 means it's being sent via the XML feed. 38:02 So when someone scrapes you through the standard XML feed, 38:06 those jobs are in there. So so whoever set your 38:09 confidential portal up missed a step if it is there. 38:13 There. Okay. Alright. I will double check that. Thank you 38:15 for that. Yeah. Social distribution 38:18 is a very sad sundown function within ISIMS. I wish 38:21 still Lyft existed because it was a very cool feature. 38:24 But LinkedIn basically cut it down cut it off at 38:26 the knees in the late 2 thousands, 38:29 in the late tens. 38:31 And it's really I don't know too many customers who 38:34 are still using social distribution. They haven't taken it off 38:37 because we're SaaS and everybody's in the same platform. There 38:40 might still be some customers using it, but social distribution 38:43 is probably not your culprit. 38:45 Okay. You would have had to go into a totally 38:47 different system to set it up. 38:51 Got it. Any other thoughts on Patrick's issue here? 38:57 Alright. Thank you, Patrick. 39:00 Next I would also sorry. Just 1 other thing. I 39:02 would also reach out to your LinkedIn folks if you 39:04 have a rep or an account manager and just let 39:07 them know to block the URL 39:09 for your confidential portal from their scraping. 39:13 Okay. Alright. I will double check with them then. Yeah. 39:18 Great. Alright. So, Cheryl, you have a question. Cheryl, are 39:21 you here? 39:26 I'm here. Sorry. Yep. Hi. Do you guys hear me? 39:29 Yeah. Okay. 39:31 I've 39:32 I've seen this before where 39:34 a company has, like, multiple brands and then they brand 39:37 their job postings. 39:38 I can't recall if I saw it on my career 39:40 sites or the portals, 39:42 but we need to I'm not quite sure exactly where 39:45 we plan on branding certain things, 39:48 but I was just wondering if somebody could give me 39:49 a high level overview of how that's actually set up. 39:53 If I recall, the, like, logo was part of 39:56 a location 39:57 profile or a company profile, but I can't remember. So 40:00 I just wanted to kinda get a high level of 40:03 how that's set up. 40:09 Liam, 40:10 can you speak to that then? A little bit. It 40:13 was set up before I actually started, but we've done 40:15 some work, 40:16 as far as, like, modifying it, so I'm familiar. So, 40:20 it sits under, like, the 40:23 the location or data search. 40:25 So we have location fields under there for company location, 40:28 but then we also have, 40:31 company fields, brand fields, and a lot of that information 40:34 kind of, ports over to us from UKG. 40:37 But you're you're right that we do have 40:40 the actual 40:42 JPEG logos 40:43 stored as a field within our our brand 40:47 values, 40:50 along with, 40:51 like, company description information. 40:53 And then as as far as, like, the career sites 40:56 of the portals go, 40:57 they pull those specific fields into certain sections. So I 41:01 can 41:02 I could share our, 41:05 company career site, the public 1, if you wanna see 41:07 what it looks like for us? 41:09 Yes, please. That would be great. And then I can 41:12 that kind of explains what I was looking for, which 41:14 was 41:15 is that how it's typically and then do you use, 41:17 like, the postable fields just to be able to post 41:20 out, like, the logo or something as part of the 41:22 job description? 41:28 Not postable 41:29 fields. 41:31 So we we use ISIM's career sites, but then we 41:34 also have, 41:35 a third party company called Clay Global that did our 41:39 design for it. So it's like 41:42 a 3 company 41:44 project. 41:46 Unfortunately, I wasn't part of the project team that that 41:48 set it up. So hard for me to answer, but 41:51 I can confirm that we do use the logos from 41:55 the 41:56 the brand profiles, 41:58 and there is a specific field within that that we 42:00 pull from. 42:01 Got it. Got it. Okay. 42:03 And we also do that with, like, email templates and 42:06 things like that because we're Reyes Holdings is 1 42:09 1 company that we have multiple entities underneath us. So, 42:13 we set up the brand image variables within our email 42:17 templates and things like that so that when recruiters from 42:21 different businesses use the same email templates and brands correctly 42:24 for them too. Right. Nope. Oh, that's awesome. 42:27 That makes sense. 42:30 Okay. 42:30 Alright, Cheryl. Thanks. Oh, please go ahead. Thank you. 42:38 Alright. Let's go to, 42:42 Caitlin. 42:43 This is an article or is this a question? 42:46 That was just a reflection. This is a reflection. Got 42:49 it. That's right. Workflow protocol. Great. Thank you for sharing 42:52 that. 42:53 Cathy has a question though in the chat. Cathy has 42:55 a question in chat. Alright. 42:57 Let me find it. 43:02 I gotta stop sharing. That's what's going on. Alright. So 43:05 here we go. So, Cathy, 43:07 you said I missed if you said that social distribution 43:10 was sunset. Not sure if that is what was said, 43:12 but if so, is there an alternative we should use 43:14 in lieu of social distribution? 43:17 Social distribution was a really cool free functionality 43:20 that ISIMS offered, and it is not sunset in the 43:23 sense that it no longer works. If you've already got 43:25 it configured, 43:27 it is still out there and functioning in the world. 43:29 It is developmentally dead, meaning they are no longer doing 43:32 any development work on it to my knowledge. 43:35 So 43:36 social distribution, 43:38 was an ability for you to auto post jobs to 43:41 Facebook, if you have a company Facebook or something along 43:44 those lines. That functionality is still very much up and 43:46 active. But the LinkedIn piece of it, where 43:50 prior to, like, circa 20 18, 43:53 it used to be able to go out and look 43:54 at LinkedIn profiles and give you a list of possible, 43:58 like, LinkedIn profiles that matched your search or those kinds 44:01 of things. No longer works because LinkedIn shut the door 44:04 on the ability to do that kind of thing. 44:07 So when I say social distribution is dead, it is 44:09 not being pushed. It is not an actively marketed feature 44:13 within ISMs, and it is no longer being improved or 44:15 developed. But if you actually have it and are working 44:18 with it, it's not like they're gonna shut it down 44:20 on you. 44:24 That help? Yes. Thank you so much. 44:27 Okay. Great. 44:28 So we also had 44:31 I think that's it. 44:33 Tanya, I think we got your question about how you 44:34 handle a request for non electronic, etcetera, 44:37 previously. 44:39 Alright. So the floor is open. Who else has a 44:41 question today? 44:43 You can drop it in chat if you can't do 44:47 if you can't speak right now, 44:50 or you can just jump in. 44:53 Yeah. This is Ariel from. 44:54 I have a question. 44:56 And, oh, I actually also have an update on I 44:59 I missed the call after I posted that, 45:02 our jobs 45:03 were mysteriously 45:05 posted everywhere. 45:07 So I do have an update on that, which is 45:09 a fun Easter egg for anyone else that might wanna 45:11 check their configurations. 45:14 We 45:15 gave our business partners 45:17 full access search 45:19 at their very strong request, and 45:22 we didn't wanna do it, but we did. And, 45:26 I 45:28 I personally only use, like, a few of the searches 45:31 and just didn't really, 45:34 you know, clock them having 45:36 access to more searches, 45:40 thinking that they would just utilize the ones in their 45:41 dashboards. 45:42 And it, 45:44 when I was going through the implementation piece, you know, 45:46 I was trying to look and see, okay, what do 45:48 I need to take away to try to prevent them 45:50 from inadvertently doing things? 45:52 And as far as, like, posting jobs goes, that was 45:54 something we knew that we didn't want them to have 45:56 access to. So we, you know, hit the posting tab. 45:59 We took away the posting center button in the job 46:01 search because in the ISEN's documentation, that was, like, where 46:04 it says 46:05 is the only place you can bulk post it on 46:07 post jobs. But it turns out in the job posting 46:10 search type, which I do not use because all those 46:13 fields are available in the job search, 46:15 there is a cancel post button there. 46:19 And so I guess a VP had been trying to 46:21 run a report on, like, posted jobs 46:24 and pressed that button. And 46:27 there is a pop up that says, like, are you 46:28 sure? And I think she was just moving through and 46:31 didn't realize that she had done that. 46:34 And that is how she accidentally canceled the postings for 46:37 all of the posted jobs. So 46:39 it was definitely just, you know, kind of an eye 46:42 opener of, like, okay. Well, definitely, we just I actually 46:45 ended up, 46:46 taking away the search 46:49 drop down from their toolbar completely, 46:52 because I essentially just I only want them to go 46:55 to their dashboard to the reports they have made for 46:57 them. And then if they really want to, of course, 46:59 they can still edit the search forms there, and they 47:01 still have access to the searches. But that way, it's 47:04 less likely that they're gonna go and 47:06 be running other kinds of search types. 47:09 So, yeah, that was the it was not a gremlin. 47:11 It was a confused 47:13 business partner from the Netherlands, 47:17 pressing a big red button that we didn't know previously 47:20 existed. 47:21 So that was the update on that. And then, I 47:24 do have another question actually 47:26 about, 47:27 hidden field hiding fields 47:30 on the job 47:32 when no security rules are applied. 47:35 So the reason why I want to do this is 47:37 for the hiring managers. So, essentially, I'm trying to, 47:42 the business wants to make the create job process more 47:45 streamlined in terms of, like, they don't want the hiring 47:48 manager to even, like, see 47:50 the fields at all regardless of whether or not they 47:52 have to actually input values for them. They don't even 47:55 want them to see them at the time 47:57 they're in the create job screen, 47:59 so that it just looks more streamlined. 48:03 But then, of course, like, those fields then will be, 48:05 you know, populated later, and then they will be read 48:08 only at a later time. 48:10 And so I tried to, use a security rule that 48:13 was grabbing, you know, if the job is in preapproval, 48:17 because I was told by TSE, 48:20 apparently, incorrectly, that that would capture that time because it's 48:23 kind of a weird situation. It's in the create job 48:26 screen. Like, technically, the folder is pre populated as preapproval, 48:29 but it's not, like, really a job yet. So I 48:32 myself was doubtful that it would actually you know, that 48:35 the 48:36 field settings would take effect there, and they did not. 48:39 So 48:40 they were basically like, oh, well, if you just hide 48:42 them without any security rule applied, 48:45 then that will make it take effect 48:49 in the create job wizard. 48:51 And then as the other security rules that come into 48:53 play, like, you know, the job I have 1 where 48:56 the the job is pending approval, 1 where the job 48:58 is approved, and 1 where the job is closed. Then, 49:00 you know, when 49:02 I configure on, like, the pending and the approved security 49:05 rules, 49:06 I'll unhide and then make read only. I'm just wondering 49:10 if there is anything that I'm not thinking of or 49:12 any other implications that I'm not aware of in terms 49:15 of having a field hidden 49:18 without security rules applied just because, generally speaking, I know 49:21 that that is 49:23 you know, can have 49:25 issues. 49:26 So I'm just kind of wondering if anybody else has 49:29 any kind of experience or insight. 49:33 Do you have any conditional field logic configured on any 49:35 of those fields? 49:40 Some, but not 49:42 yeah. Only only some. So there's 1, like, 49:45 for, like, if addition or replacement. 49:47 Like, some are, like, they'll drop down other fields, 49:51 but not a ton. 49:52 Okay. So if a field is hidden from a user 49:56 and you have conditional field logic applied 49:59 and you don't have the conditional field logic doing the 50:02 hiding 50:04 or you're hiding the field itself manually in field hiding, 50:07 it may break the CFL. 50:10 Okay. I see. It's a bug. It's not supposed to 50:13 work that way, but I have seen it do it. 50:15 Like, even later on if the field is unhidden at 50:18 a later point when 50:20 Yep. 50:21 Oh, it'll just break it completely. It will break it 50:23 completely, or you have to go back and rebuild the 50:25 rule. I've had I had an implementation of a rule 50:28 that had, like, 16 different layers to it, and it 50:31 was so painful because we couldn't figure out what the 50:33 problem was 50:34 until we went into the hiring manager user and found 50:36 out that the field was hidden at the field high 50:38 level 50:40 instead of it wasn't a security rule. It was just 50:42 they hid the field, 50:43 somebody in configuration, and it just kept breaking the rule 50:47 for whatever reason. It would work for 1 user. It 50:50 wouldn't work for another. 50:52 Shoot. 50:53 Yeah. So just be careful if you have CFL configured 50:57 on any of the fields that are affected by what 50:59 you're trying to hide. 51:01 Any fields that are gonna be hidden. 51:03 Correct. 51:04 Now if you write the rule to hide the field, 51:08 it's a different story. 51:12 Because you can hide a field using CFL. 51:17 Yes. But what, 51:21 like, would that take into 51:23 effect, like, in that create job? Login group specific. 51:27 Oh, yeah. No. Okay. Yeah. That's right. That would not 51:29 work. Okay. 51:32 Thank you. Yeah. That's the kind of information that I 51:34 need to get. 51:36 Yeah. That that's an unfortunate gotcha, 51:39 when it comes to CFL. Now 51:41 I am going off of information from 20 19, the 51:44 last time I implemented a really crazy CFL. 51:47 So reach out to the help desk, ask a how 51:49 to question, 51:50 ask them if they fixed that bug. They might have. 51:54 I doubt it, but they do. Also. 51:57 Yeah. 51:58 CFL is already kind of buggy. 52:01 Yeah. 52:02 Yeah. Okay. Thank you. 52:04 I'll have to make sure that that is not being 52:06 used anywhere. 52:08 Thank you for the question, Mariel. 52:10 Thank you. 52:14 So if you're open oh, hold on 1 second. 52:19 Oh, there we go. Alright. So so if you're interested 52:21 in joining our paid tier, if you're on our, free 52:24 tier right now, it includes on demand consulting sessions with 52:27 the IRD team, ISIMS discussion moderated by our team, access 52:32 to our full course library, 52:34 and a whole lot more. I'll drop a link to 52:36 a form you can fill out to apply. We hope 52:38 that your employer can sponsor your membership, but if they 52:41 can't, we'll work something out. So I'll drop that link. 52:44 There you go. 52:46 And we'd love it if you could give us some 52:47 feedback on how this session went for you today. 52:51 I'll drop that link in chat as well. It's a 52:53 very quick little survey. It'll take you about 60 seconds. 52:56 Okay. With that, who else has a question today? We've 52:59 got another 10 minutes. 53:06 Floor is open. 53:18 Jen, can I pick on you? Because I'm curious to 53:20 see how things are going. 53:23 Jen Theobald. 53:26 Can you hear me? Yes. We can. How are you 53:28 doing today? Hey. Good to see you. 53:31 It's been a while. Yeah. You're going good. 53:35 AirMethods is a really interesting company. You know, I've spent 53:38 the majority of my career in the health care space 53:41 and then working at ISIMS. And, 53:44 now that it's kind of a combination of that, 53:47 aviation and health care, the needs are 53:51 definitely different. 53:53 You know, we've got multiple brands, and so working through 53:57 some of those components. We're working on, 54:00 implementing some some new screening tools, interview tools, 54:05 heading down the the route of 54:09 signing on with recruitix 54:11 to manage some of our, you know, programmatic and how 54:14 we're doing things there. And so kind of this the 54:16 the standard stuff, but it's always, really unique. 54:20 That's really cool. Health care in the sky. With a 54:22 new company. Yeah. You know, when I think of health 54:24 care, health care in the sky didn't occur to me 54:26 as a as a sub sub industry niche. That's really 54:29 cool. Definitely. 54:31 Anything unique about, 54:34 this organization 54:35 as far as what that means for you as a 54:37 system administrator? 54:41 You know, nothing 54:45 nothing more than, 54:47 I think what others experience when you experience when you 54:48 have brands and and sub brands. Yeah. So this company 54:52 specifically does emergency flight medevac, but they're known, as different 54:57 company names 54:58 based on the hubs that we have throughout the country, 55:01 as well as having a separate brand that, like, does, 55:05 retrofitting 55:07 aircraft for, like, government contracts and things like that, and 55:10 then a tourism division in Hawaii. 55:13 Okay. So, you know, a lot of, 55:15 thinking about branding and what that looks like in in 55:18 various spaces. But, 55:22 you know, the needs are are similar 55:24 because a lot of our roles 55:27 amongst all of the brands, 55:29 there's a lot of crossover in there. We still need 55:31 mechanics regardless of, you know, whether it's it's retrofitting an 55:35 aircraft or maintaining 55:36 an aircraft at a, you know, hospital or, you know, 55:40 for a tourism aircraft. So 55:43 Got it. That is fascinating. Well, good to see you. 55:45 Thanks for joining today. Yeah. Thanks for for opening these 55:48 back up again. There's always so much great content in 55:50 here, so I always appreciate it. Absolutely. 55:54 Alright. Who else has a question today? We have another 55:56 5 minutes. Anybody can ask a question. 56:00 I do have a just a quick question because I 56:02 hopped on late. 56:03 I caught the tail end of the ISIMS developer community. 56:06 Is, 56:07 I missed the part of how to access that. 56:11 Can I I didn't Drop the link in the chat? 56:13 Oh. And on the the link in the chat, go 56:16 to, 56:17 new member request. 56:18 So if you have to actually ask them to create 56:21 a username and password for you, but they don't they're 56:24 they're not really that strict about who gets 1. So 56:26 you just have to sign up and, ask them to 56:29 send you a username and password, and then they'll keep 56:31 it as part of your logins. It does expire every 56:34 6 months too. So you go in, and it's like, 56:36 it doesn't work anymore. It's because you have to reinitial 56:39 it. Okay. Change your password. And you said this was 56:42 kinda set up to kinda help guide us for with 56:44 any questions that we can kinda search here for before 56:46 submitting, like, a ticket? 56:48 Yep. It's a great resource. 56:50 It's a little hard to navigate. 56:52 So stay tuned for the next couple of weeks because 56:54 I'm gonna be going through it, like, page by page 56:56 to give you some more guidance on how to navigate 56:58 it. But you're welcome to go in there and and 57:01 look through it on your own because pretty much every 57:03 integration they have is documented on there somewhere. 57:06 Awesome. Okay. Thank you so much. 57:09 Thank you, Kathy. Mhmm. 57:11 Alright. I have a few more minutes. Time for 1 57:13 more quick question. 57:23 Going once. 57:25 Going twice. 57:28 Well, Vivian, thank you so much for bringing the the 57:31 wisdom and the value today. Caitlin, thank you so much 57:34 for your help with the polls. 57:36 So glad that folks are able to, 57:38 get on this successfully. Screen sharing, there were some resolution 57:41 issues, but I figured out how to zoom it. 57:43 So I think we're good to go. We're gonna keep 57:45 doing these in circle for the rest of this month. 57:48 Thank you everybody once again for joining system admin insights. 57:51 It's always so great to see you here. Hope you 57:53 have a restful and restored weekend. Take care.