--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Question change history # Question change history {#ariaid-title1} Release version: Australia Updated September 3, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Question change history Question change history enables you to review a detailed log of every modification made to a question's response, justification, and flag state throughout an assessment's lifecycle. This tracking applies regardless of whether the assessment is open, closed, or cancelled. Each change entry includes the timestamp, the user who made the change, what was altered, and the previous and new values. Show full answer Show less This feature is available starting with the Australia Patch 2 release. You can access it via a change history icon on each question card, which opens the Change history panel showing the latest logged changes for that question. ## Key Features * **Comprehensive Tracking:** Monitors changes to response, justification, and flag state across the entire assessment lifecycle. * **Automatic Updates:** When the panel is open, you can refresh to load the most recent changes for the current question. * **Change Grouping:** Consecutive edits by the same user on the same field within 300 seconds are merged into a single entry to reduce noise. This window is configurable by an admin. * **Flag State Logging:** Each flag state change (Unflagged, Flagged, Resolved) is always logged as a separate entry, reflecting its significance. * **AI-assisted Changes:** Changes from AI suggestions follow the same merge rules as manual changes but do not merge across manual and AI-assisted edits. * **Actor Attribution:** Changes are attributed either to the user who made them or to "System" for automated, non-editable responses and system-initiated operations. * **Question Type Display:** Before and after values are formatted appropriately for question types (e.g., multi-select values shown comma-separated). * **Justification Handling:** Justification changes are tracked similarly to responses. If a justification is no longer required and cleared upon submission, this is recorded as a submission action attributed to the submitting user. ## Important Considerations * Attachment changes are not tracked in this history for attachment-type questions or questions with the "ask for attachment" option enabled. * Change history only logs activity from when the feature was enabled on your instance; earlier changes remain only in the platform's System Audit table. * Admins can adjust the merge window duration via the **snsmartasmt.activitymergewindowinseconds** system property to control the granularity of logged changes. ## Practical Benefits for ServiceNow Customers This change history feature provides transparency and accountability by allowing you to audit how question responses evolve during assessments. It helps ensure data integrity, supports collaboration by clearly showing who made what changes and when, and improves troubleshooting by preserving a clear change trail. The configurable merge window lets you balance detail with readability according to your organization's needs. Review a log of every response, justification, and flag state change made to a question throughout the lifecycle of an assessment. ## Change history overview {#sae-question-change-history__section_chov_r1x_9qc} Question change history tracks changes to a question's response, justification, and flag state. Changes are tracked regardless of whether the assessment is open, closed, or cancelled. Each entry records a timestamp, who made the change, what changed, and the previous and new values. Note: This feature is available starting with Australia Patch 2. Each question card includes a change history icon. Selecting it opens the Change history panel. The panel logs changes to three parts of a question: the response, the justification, and the flag state. Changes are tracked for the entire lifecycle of the assessment. When you first open the change history panel, or move to a different question, it automatically shows the latest changes for that question. If a change is made to the current question while the panel remains open, select the refresh icon in the panel header to load the latest entries. Note: * The change history panel logs activity starting from when this feature became available on your instance. Responses, justifications, and flag changes made before that aren't migrated into the change history; that data remains in the platform's System Audit \[sys_audit\] table. * Attachment-type questions, and any question with the ask for attachment option enabled, don't have their attachment changes tracked. {#sae-question-change-history__ul_jhz_hw5_ckc} ## How changes are grouped {#sae-question-change-history__section_chco_u3z_7sc} To avoid logging every intermediate keystroke, the system merges consecutive response and justification changes made by the same user into a single entry when the changes occur within 300 seconds by default: * If the same user changes the same field within the window, the entry updates instead of creating a new one, and its timestamp updates to the latest change. * The system merges changes only when both the field and source match the most recent entry. Sources include manual, automated, and AI-assisted. If you change a different field or use a different source on the same question, the merge stops and a new entry begins, even within the merge window. * If a different user changes the same field during that window, a separate entry is created. Changes made by different users are never merged, regardless of the time between them. * If a user reverts a field to its pre-edit value within the window, the entries covering that back-and-forth are removed, since they represent no net change. {#sae-question-change-history__ul_ch_coalesce_g4h} Flag state changes are never merged, even when the same user makes multiple flag changes seconds apart. Every flag transition is logged as its own entry because each state --- Unflagged, Flagged, and Resolved --- is meaningful on its own. For more information about flag states, see [Collaboration in assessments](https://www.servicenow.com/docs/yIaHj6w8llDRrZ8Pxb1rBQ "Collaboration in Smart Assessment Engine enables you to add multiple contributors to an assessment and support live collaboration with real-time updates. It also displays presence indicators to show who is active on the assessment."). AI assisted response changes follow the same merge rule as manual changes. Consecutive AI assisted changes to the same field by the same user are coalesced into a single entry within the merge window. For example, trying several AI-suggested responses before settling on one produces one entry. Manual and AI assisted changes never merge with each other. Switching between them starts a new entry, regardless of timing. Note: * The default merge window is 300 seconds. An Assessment admin can change this value in the `sn_smart_asmt.activity_merge_window_in_seconds` system property. * Reducing the value produces more granular history; increasing it produces fewer, larger entries. A change to this property applies only to activity recorded after the change is made. {#sae-question-change-history__ul_pm3_s55_ckc} ## Who made the change {#sae-question-change-history__section_chac_v4a_6tc} The actor on an entry identifies who made the change: User : The username of the person who made the change. System : Attributed to System for the following cases: * Automated and non-editable response: each change to a question whose response is automated and non-editable is attributed to System. These questions display a Last responded by System indicator. * Automated and editable response: the default automated response set when the assessment instance is created is attributed to System. Any subsequent change made by a user is attributed to that user. * Changes made through asynchronous or system-initiated operations, such as the Copy Response API, are also attributed to System {#sae-question-change-history__dl_ch_actors_c2d} ## Question type display {#sae-question-change-history__section_chqt_w5b_5uc} Before and after values are shown in a format suited to the question type: for example, comma-separated values for multi-select questions, or the configured display field value for reference questions. Justification changes are tracked the same way as text responses. If a response is changed so that a justification is no longer required for the question, the justification value is cleared at the time the assessment is submitted. Until submission, the value is preserved in the system and continues to appear in the change history. This change is attributed to the user who submits the assessment.