I-Lab v3.1 March -- CSDM life cycle migration agentic workflow

CSDM life cycle migration agentic workflow

시작하기 전에

Role required: cmdb_inst_admin

이 태스크 정보

1. Scan job and supporting data structures to identify life cycle-related metadata (scripts, business rules, etc.) that interact with legacy life-cycle fields.
2. Legacy life-cycle fields of interest include operational_status, install_status, hardware_status
3. Motivation is to help customer better understand the current state of their legacy life-cycle fields, to enable them to migrate to CSDM life cycle
4. Target is for Innovation Labs release of new store app in Q1
5. Discussion on processing for detecting use in script includes. Proposing team acknowledges some serious limitations to the current approach, including that the scanning code cannot identify/track use of constants, unless the constant is coincidentally the same name as the field of interest
6. There are also limitations on what will currently be scanned. For example, this will not scan flows.
7. Will this differentiate legacy field use due to OOTB usages vs customer custom usage? For IL version, no, but proposing team to consider as additional capability.
8. This has internal uses too. "We do not know where all the status fields are being touched”
9. Observation that there is existing platform feature to search for a string in all applications in Studio. Action item for proposing team to reach out to Platform team owner of Studio Code Search to see if there is a good option to leverage and/or Better Together opportunity

The AI Agent associated with EPIC1152657 relies on a nightly job that scans for usage of lifecycle fields in all metadata types (scripts, business rules, UI actions, etc) so that the NA agentic conversation can inform end users about where they have updates and dependencies happening around CMDB lifecycle. Need FARB review on the data model of the stored findings, our approach to collecting new scan data based on metadata table "updated" timestamp, and the use of our CMDB Context Job pattern to prevent initial or large scans from causing problems with history list length or long running jobs.This work is targeted to the ILabs 3.1 release, dev complete is Feb 7.

FARB: https://buildtools1.service-now.com/x_snc_review_board_farb_review.do?sys_id=ee0c48d4936a729c5093f5c56aba107c&sysparm_record_target=x_snc_review_board_farb_review&sysparm_record_row=1&sysparm_record_rows=2&sysparm_record_list=review_schedule_slotss%3D38ecc8bcc385761034e25773e4013131%5EORDERBYDESCnumber.

This procedure describes how you can manually access the skill in Core UI or in the CMDB Workspace. In addition, any agentic workflow can use the skill.

To learn more about using the Now Assist panel, see Working in the Now Assist panel.

프로시저

1. Select a CI from the workspace or from any list view.

   For example, select All and enter cmdb_ci.list in the search filter. Select a CI to open its CI form.

2. Zzz what next.
3. 옵션: Provide feedback, copy the response text to the clipboard, or refresh the response.

   Option	Procedure
   Provide feedback for the summary	If you think that the response was helpful, select thumbs-up . If you think that it wasn’t helpful, select thumbs-down . This feedback improves the Agentic AI model and can help to improve the future versions of this skill. The system gathers the feedback on each generated response and stores it in the Agentic AI logs (sys_generative_ai_log_list.do).
   Copy the summary	Select the copy to clipboard icon to use the response information for another purpose, such as pasting into an email.
   Refresh the summary	If you think that data might have changed after you viewed the response, select the redo icon to refresh the response information.