Skip to content

Issue with UI Action Implementation for Incident Cancellation #2299

Description

@Sriharsha19

Problem:

I found that the incident cancellation UI Action implementation at Cancel Incident UI Action using a GlideModal confirmation introduces unnecessary complexity and reduces maintainability. A simpler approach using a standard browser confirmation dialog combined with clear server-side logic for setting the incident state to "Cancelled," adding work notes for traceability, and redirecting the user is more readable and easier to maintain.

Proposed Enhancement:

Simplify the incident cancellation UI Action by removing the GlideModal confirmation and replacing it with a straightforward alert prompt. The revised UI Action should:

  • Use a simple confirmation dialog for user acknowledgment
  • Clearly log cancellation in work notes for traceability
  • Update the incident state to "Cancelled" (state = 8)
  • Redirect the user appropriately after cancellation
  • Follow ServiceNow best practices by clearly separating client-side confirmation and server-side business logic

Goal:

To improve code simplicity, maintainability, and user experience by refactoring the incident cancellation UI Action following ServiceNow client-server scripting best practices.

Assign to Me:

I would like this issue assigned to me to proceed with implementation and validation of the improved UI Action.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions