Build Agent checkpoints and conversation change log
Summarize
Summary of Build Agent checkpoints and conversation change log
The conversation change log in ServiceNow Studio automatically records every modification made by Build Agent to your application. This integrated feature enables you to track changes, revert to previous states, and manage deployments efficiently through update sets. It is designed to enhance control and visibility over your application development process within the ServiceNow environment.
Show less
Key Features
- Change Tracking: View all changes made since the last checkpoint, organized by file categories matching the Studio Navigator panel.
- Checkpoints: Automatic grouping of changes after task plan approval, allowing easy rollback to earlier application states during your Build Agent conversation.
- Update Sets Integration: Changes from each checkpoint are bundled into update sets accessible in the Deployment tab of ServiceNow Studio, supporting streamlined deployment.
- Checkpoint Management: Checkpoint 0 serves as an initial state placeholder (from Australia Patch 4 onward), while Checkpoint 1 acts as the base update set. All update sets exist in the same application scope to facilitate merging and environment transfers.
- Manual Edit Update Sets: Build Agent detects changes in manual edit update sets, completing or removing them as needed, with direct access via the checkpoints panel.
- Conversation Panel Access: Within the chat panel, you can open relevant update sets in new tabs and view all updates created by Build Agent.
Practical Benefits
- Improved Change Visibility: Easily monitor and review all modifications Build Agent applies, enhancing transparency during application development.
- Safe Experimentation: Use checkpoints to revert unwanted changes quickly without losing progress, ensuring reliable application stability.
- Streamlined Deployment: Grouped update sets simplify moving changes between environments, reducing manual effort and deployment errors.
- Consistent Application Scope: By maintaining update sets within the same application scope, merging and managing updates becomes more efficient and less error-prone.
The conversation change log tracks every change Build Agent makes to your application. It appears automatically in an integrated tab in ServiceNow Studio and lets you view updates, roll back to a previous checkpoint, and deploy changes to an update set.
Conversation change log
- View the changes you have made since a checkpoint
- Roll back changes to the previous checkpoint
- Approve and deploy changes to an update set
- The Files list displays all the files that Build Agent updated during your conversation. The categories mirror the ones in the ServiceNow Studio Navigator panel.
- The menu at the top shows the current checkpoint. You can use the list at the end of the checkpoint name to select a different checkpoint to view. When there are multiple checkpoints, a Summary option appears, which shows changes from each checkpoint all together.
- The overview section shows the plan and actions Build Agent took based on the conversation.
- The action in the corner menu to pen the chat, Restore your app to a previous checkpoint, or open the app details page.
Changes from each checkpoint in the conversation are packaged together into an update set. You can find each update set on the Deployment tab on the ServiceNow Studio home page. For more information on deployment, see Deploying what you built with Build Agent.
Checkpoints
Checkpoints are groups of changes that you made to an application that you can revert to at any time during your conversation with Build Agent. Checkpoints are created automatically after you approve each task plan.
With Australia Patch 4 and later:
- Checkpoint 0 doesn't create an update set. Instead, it serves as a placeholder in the UI that you can use to restore your application to its initial state.
- Checkpoint 1 is the base update set for your application. The checkpoint 1 update set is the parent, or chain root, for all subsequent update sets created during the conversation. Because all update sets exist in the same application scope, you can merge them together when you're ready to move your changes to another environment. For information on update sets, see Update sets and Build Agent.
When Build Agent prepares to create the next checkpoint, it checks whether any changes exist in the manual edit update set. If no changes are present, Build Agent removes the update set. If changes exist, Build Agent completes the update set and renders it with the other update sets from your conversation. You can access manual edit update sets directly from the checkpoints panel in your Build Agent conversation.