Thank you so much @James Chun  I have spent many hours trying to get it to work, but still I couldn't.  That is because I am lack of programming skill.  Please let me know what is this means "  and what programming language is this.  Thank you  

Hi @AG - LearnNGrow    It may or may not. Reason begin, it depends on which table and what time is running. ==>   1. will schedule jobs trigerring/scheduled at same time hamper performance of system Atul: It may or may not. Reason begin, it depends on which table and what time is running. EX: I have 7 to 10 jobs scheduled at same time say at  6 Am  2. can we club all the jobs running at same time and execute one after another? Atul: What do you mean by club here?  The jobs which are running at same time wait for one to complete and start the next one instead of concurently triggering  

Hardware Life Cycle Process Alignment   The lifelong argument of asset vs. ci can be elevated to the Service level. It is at the Service Portfolio that these technical and strategic requirements are aligned with ServiceNow functionality. The Service Portfolio manager is overall accountable to define these, although they will usually require extensive guidance from each of the ServiceNow disciplines to ensure the correct alignment to Service(ITSM&CMDB)/Service Offering(ITSM&CMDB)/Category(ITSM&CMDB)/ Subcategory(ITSM&CMDB)/ Model Category(Source-to-pay&ITAM&CMDB)/ Model ID/ Managed By Group / Support Group / etc. are created for the onboarding Assets and CIs.   The discussion "when should we make an asset or ci" can be consolidated into one flow for the entire organization. The below image represents the Hardware Life Cycle Process for the CSDM 4.0   Blue check marks designate when a record is in its CI dominate stage. This means that updates from the designated discovery tool take priority on *any updated status field. Red check marks designate when a record is in its Asset dominate stage. Often times these are manual processes complete by various teams across the enterprise. Reports from the asset will always be retrospective until integrations with inventory/warehouse management tools are available and configured.  Purple check marks designate when a record is in its Procurement dominate phase. When a new/additional service is being added, new devices are often required to support it. Procurement processes the evaluation criteria and extends proposals to multiple Vendors. Vendors present a solution with one or more device types that correspond to model categories and ci classes. Pink check marks designate when a record is in its Supplier management lifecycle phase. After procurement has selected a vendor and proposed solution, the organization either uses an internal partner to purchase from or outsources to a supplier.   What does this have to do with records and their Life Cycle Control? Great question. Although the legacy Status and Operational Status were "left up to the organization to maintain the design" and pick one, it was the misunderstanding that at least two were required for this data model to work. Meaning organization would have to configure the legacy "Status" and "Operational Status" like ServiceNow is doing with Life Cycle Control(essentially the same thing when we create the life_cycle_mappings).   Let me put it to you this way - Just like how Discovery requires that Integrations and/or subnet scans adequately update the CI Status when it is on the "Network"; Procurement, Supplier, and Asset tools should adequately update the status of "Assets" as they move through the beginning stages of their life cycle. Once they hit the network, Discovery architecture will take over. Once they leave the network, Asset tools take precedence.    My organization needs a new video teleconferencing solution. The current laptop for each conference room creates unique challenges that we would like to provide a wholistic solution to. My organization requires that there be minimal devices with the added capability of sound quality, video communication and focus on the person talking, ease of use. Laptops often fall under a different support structure than video communication equipment, therefor the new solution would need to be communicated with the incumbent stakeholder who will be supporting it if it changes. Multiple vendors show up the next day, ready to present their solution and devices that support it. During the selection process, a new vendor and solution was designated for implementation. This solution consisted of a centralized device that sat on the conference room table with 360 cameras focused on the entire room with microphones attached. When a person in the conference room was speaking, the camera would enlarge their picture to show who was talking to everyone connected virtually. This solution implements different technology and network architecture requirements than the previous solution and requires a defined Service, for this example we would categorize this under Infrastructure->Network->Video/Phone Communication responsibilities vs. End-User->Workstation. This team, Video/Phone Communication would be the technical service supporting this solution and be designated as the Managed By Group. Once a list of device types are approved, supplier management takes over. An internal or external supplier is selected, with designated sla's for device availability etc. Usually procurement has a finance component that is then reimbursed once the Asset has been purchased, sent to the warehouse, then put onto the network and into operation. When the device is on the network, it can be reached by the defined Discovery tool which updates the record for its entire time on the network. Once the device is in operation does the organization submit a list to Accounting and accounts payable to reconcile source-to-pay operations. When the device is submitted for retirement, or the next stage in its life cycle, that process (likely ITAM, will take over and update the record).   ezpz

@Arka Banerjee  That does'nt seems to be valid JSON but you can try with below   var jsonObject = { "a:b:c:d": { "xyz": "abc" } }; var valueOfXYZ = jsonObject["a:b:c:d"]["xyz"]; gs.info("Value of 'xyz': " + valueOfXYZ);   Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.   Thanks

The bidirectional mapping works but has caused us some issues that we have had to work around. Our issues are due to two main problems with the mapping functionality: You can only map a legacy field value to a single new Life Cycle Stage/Status value, and there are many more new Life Cycle Stage/Status values than legacy values (for the OOB legacy fields we care about). We are doing bidirectional mapping between either Install status or Operational status (which one depends on the class), and we had not customized the values of those fields. We care about those fields, because discovery will maintain them in certain situations, so we want those fields and the new fields to stay in sync. The business rule that does the forward mapping (legacy field -> life cycle fields) fires upon any change to the CI - not just when the field being mapped forward changes. Note that if the legacy field you care about has legacy values corresponding to every new life cycle value (that is, every new life cycle value can be reverse mapped to a legacy value), this issue will not affect you.   This affected us in a couple different ways. The first issue means that if a user selects a new life cycle value that does not have a reverse mapping for it (because there aren't enough legacy values to reverse map to), the legacy field value does not change, and effectively becomes out of sync with the new fields.   For example, on a server, Install status only has 2 values that correspond to a server that is deployed and in use or retired: Installed and Retired - Installed corresponds to Operational, and Retired corresponds to End of Life.  However, Life Cycle Stage Status has 3 values for the Operational stage, and many more for the End of Life stage. By default Installed forward maps to Operational/In Use, and Retired forward maps to End of Life/Retired.   The issue occurs when, for example, you move an Operational/In Use server to, say, End of Life/Pending Disposal. That server is clearly retired based on the new field values, but because there is no reverse mapping that tells the system that Install status should now be set to Retired instead of Installed, it stays set to Installed and becomes out of sync.   This is where the second issue comes in. So, the legacy and new fields are out of sync, and the business rule that performs the forward mapping (from the legacy to the new fields) fires on update, but without qualification, so it runs on all updates. When it runs, it compares the legacy field with the new fields, and if they're out of sync according to the mapping definitions, it forward maps the legacy field to the new fields. So, in the example above, our retired server gets updated so that Life Cycle Stage and Life Cycle Stage Status match the value in the Install status field (Installed), and sets it back to Operational/In Use.   This specific scenario bit us on a large number of servers, and has affected us with other classes as well. There is a work around, but it also has its issues in this specific scenario.   The workaround is to define custom legacy values for each of the additional new values that you want to use. So, for our server case, that means adding a new custom value to Install status that we can map to End of Life/Pending Disposal. This "fixes" the out of sync issue but introduces a new issue. OOB, when a retired server (Install status = Retired) is discovered, it will set Install status back to Installed. We want this to happen. However, now that we have to set Install status to a custom value for our retired server, the code that sets a discovered server that was Retired back to Installed no longer works. So, we've traded one issue for another in implementing the workaround.

I found an example in another post of an inline script provided by nagydan2 for the To field. It worked! 🙂       //Get email addresses of SAM group members //"SAM" groups SysID is: "8111195edb5333300b79d44444b961998"". var samARR = []; var groupGR = new GlideRecord('sys_user_grmember'); groupGR.addQuery("group", "8111195edb5333300b79d44444b961998"); groupGR.query(); while(groupGR.next()) { samARR.push(groupGR.user.email); } var SAMstr = samARR.join(','); return SAMstr;​      

I recently ran into the same issue when trying to use the IntegrationHub ETL to test some minor customisations to the SCCM Computer Identity transform mappings, and this is the solution that I was able to figure out:   Make sure you're in the "Service Graph Connector for Microsoft SCCM" Application Scope. Navigate to 'System Import Sets > Administration > Robust Import Set Transformers' (or direct navigate to sys_robust_import_set_transformer.list).  Locate and open "SCCM Computer Identity", or whichever ETL Transform Map is causing the issue; in the original example this would be a custom duplicate of the OOB SCCM Computer Identity. Open the referenced Transformer definition record ("SG-SCCM Computer Identity" for OOB SG-SCCM). Update the Data Source reference field in the CMDB Integration Studio Application Data Source record to your preferred SCCM Computer Identity data source record; you can find the list under 'Service Graph Connectors > SCCM > Data Sources'.  You should then be able to return to the IntegrationHub ETL and have the Data Source you need in the ETL Transform Map setup.   I hope this helps anyone else running into this issue.

This is the attached KB article for your reference: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1584548 I think the comm record is not the same for everyone but it is also stated in this ServiceNow documentation https://docs.servicenow.com/bundle/washingtondc-it-service-management/page/product/asset-management/concept/c_AssetManagement.html  

Hi @KellyLewins,   I think you will need to make a variant/copy of the page and modify the component layout. Open the UI Builder Open Service Operations Workspace record Open Knowledge View SNC variant (/kb_view) Select 'Duplicant variant' on top of the screen to create a new variant of the page In the component navigator, select 'Right rail' component In the right pane, select the 'Styles' tab and select the ellipsis icon next to 'Direction'. Select the 'Reverse' checkbox under the 'Advanced direction' pop up box   Now, you will need to modify the 'order' of the page to ensure it overrides the OOB one. Go to 'Settings' and set the Order to any value less than 100.     That should do it, cheers