REST API Create incident - urgency

[Chris Bampton]

I use the table API to create a new incident:

https://dev77859.service-now.com/api/now/table/incident

{

    "state": 1,

    "active": "true",

    "short_description": "Test incident",

    "description": "This is a test POST request to create a new incident",

    "urgency": 1,

    "impact": 1,

    "severity": 1

}

However, the resulting incident seems to ignore the 'urgency' field and always set it to 3:

Any ideas?

Thanks

Chris

{

    "result": {

        "parent": "",

        "made_sla": "true",

        "caused_by": "",

        "watch_list": "",

        "upon_reject": "cancel",

        "sys_updated_on": "2022-02-01 15:47:26",

        "child_incidents": "0",

        "hold_reason": "",

        "task_effective_number": "INC0010100",

        "approval_history": "",

        "skills": "",

        "number": "INC0010100",

        "sn_ind_tsm_core_incident": "false",

        "resolved_by": "",

        "sys_updated_by": "import_sa",

        "opened_by": {

            "link": "https://dev77859.service-now.com/api/now/table/sys_user/f5f6434d2f150110a6fdde1a2799b6e3",

            "value": "f5f6434d2f150110a6fdde1a2799b6e3"

        },

        "user_input": "",

        "sys_created_on": "2022-02-01 15:47:26",

        "sys_domain": {

            "link": "https://dev77859.service-now.com/api/now/table/sys_user_group/global",

            "value": "global"

        },

        "state": "1",

        "route_reason": "",

        "sys_created_by": "import_sa",

        "knowledge": "false",

        "order": "",

        "calendar_stc": "",

        "closed_at": "",

        "contract": "",

        "impact": "1",

        "active": "true",

        "priority": "3",

        "sys_domain_path": "/",

        "rfc": "",

        "time_worked": "",

        "expected_start": "",

        "opened_at": "2022-02-01 15:47:26",

        "business_duration": "",

        "group_list": "",

        "work_end": "",

        "caller_id": {

            "link": "https://dev77859.service-now.com/api/now/table/sys_user/f5f6434d2f150110a6fdde1a2799b6e3",

            "value": "f5f6434d2f150110a6fdde1a2799b6e3"

        },

        "reopened_time": "",

        "resolved_at": "",

        "subcategory": "",

        "universal_request": "",

        "short_description": "Test incident",

        "close_code": "",

        "correlation_display": "",

        "work_start": "",

        "assignment_group": "",

        "additional_assignee_list": "",

        "business_stc": "",

        "description": "",

        "calendar_duration": "",

        "close_notes": "",

        "notify": "1",

        "sys_class_name": "incident",

        "closed_by": "",

        "follow_up": "",

        "parent_incident": "",

        "sys_id": "5026475f2fd10110a6fdde1a2799b6b0",

        "contact_type": "",

        "reopened_by": "",

        "incident_state": "1",

        "sn_ind_tsm_core_stage": "",

        "urgency": "3",

        "problem_id": "",

        "reassignment_count": "0",

        "activity_due": "",

        "assigned_to": "",

        "severity": "1",

        "comments": "",

        "approval": "not requested",

        "sla_due": "",

        "due_date": "",

        "sys_mod_count": "0",

        "reopen_count": "0",

        "sys_tags": "",

        "escalation": "0",

        "upon_approval": "proceed",

        "correlation_id": "",

        "location": "",

        "category": "inquiry"

    }

}

[Geoff_T · Accepted solution]

Hello,

EDIT: Ensure the user has ITIL role since there is an ACL on incident.urgency field that requires sn_incident_write role (ITIL role contains this).

Geoff

[Chris Bampton]

That did it!

Thanks