Approvals experience reference

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read
  • Summarize
    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 Approvals Experience Reference

    This document outlines the configuration and integration options for the approvals experience in ServiceNow, focusing on enhancing user engagement and ensuring seamless task management within the Employee Center. It discusses default task configurations, role requirements, and the integration of third-party services such as SAP Concur and Workday.

    Show full answer Show less

    Key Features

    • Default Task Configurations: Standard configurations are provided for handling approval requests related to screquest and screqitem. Customization of these configurations is encouraged to meet specific business needs.
    • Role Requirements: Users must have the approvaluser or businessstakeholder roles to access and manage approval tasks successfully. This is essential for viewing approval to-dos in the system.
    • Fallback Mechanism: If child tables lack specific task configurations, the system will revert to the parent table's settings, ensuring continuity in the approval workflow.
    • SAP Concur Integration: Scheduled jobs sync reports between ServiceNow and Concur, ensuring that the latest data is available for approvals.
    • Workday Integration: Utilizes RAAS reports for data transfer, with a focus on protecting sensitive information through Integration System Users (ISUs).
    • Mobile Support: Approvals are accessible via mobile for tasks in the sysapprovalapprover table, enhancing on-the-go management.
    • Out-of-the-Box Action Groups: Utilize the built-in Approvals action group to streamline approval and rejection processes.

    Key Outcomes

    By implementing these configurations, ServiceNow customers can expect a more efficient approval process that is flexible and secure. Role-based access ensures that only authorized personnel manage sensitive data, while integrations with SAP Concur and Workday facilitate comprehensive task management. The fallback feature for task configurations minimizes disruptions, promoting a smooth user experience when dealing with approval processes.

    Use the following reference information for better approval experience.

    Default task configurations

    Use the following default task configurations available for approvals.
    • Request with sysapproval as reference column and sc_request as reference table.
    • Requested item with sysapproval as reference column and sc_req_item as reference table.
    You can customize the task configurations to suit your requirements. The data model is an extension to the Employee Center To-do configuration as a related list. Follow the instructions Enable task configuration for approvals about configuring the approval experience. For more information on how to configure approvals, see Approvals hub.
    Note:
    A user must have the approval_user or business_stakeholder role to approve IT requests (not applicable to other requests such as HR approvals) on Employee Centre. Role validation has not been implemented in Core UI16 because modifying ACLs in UI16 might have broader implications at the NowPlatform level.

    Unable to see Approval todos

    Ensure you have the approver_user or business_stakeholder roles to see the approval todos for the sc_request or sc_req_item items. In the _getClosureFunction() method of Script Include todoPageUtils:
    if (tableName == 'sysapproval_approver') { 
     if (!(gs.getUser().hasRole('approver_user') || gs.getUser().hasRole('business_stakeholder'))) { 
      var queryString = "sysapproval.sys_class_name!=sc_request^sysapproval.sys_class_name!=sc_req_item^NQsysapprovalISEMPTY"; 
      grTask.addEncodedQuery(queryString); 
     } 
    } 

    Fallback to parent table configuration

    When the child table does not have task configuration, fallback is one level above its hierarchy and picks the task configuration of the parent table. When the task parent is not available, fallback is to the default configuration.

    SAP Concur reference info

    Use the following information for SAP Concur integration.
    • All Concur actions are present in SAP Concur Spoke (sn_sap_concur_spok) plugin.
    • Scheduled job Pull concur reports (sysauto_script) is triggered daily. This scheduled job internally calls the Concur Integration record from the Integration Source table (sn_hr_integr_fw_source) of the ESM framework.
    • Schedule job runs and updates the record in the Concur Sync Details table (sn_ex_cnc_concur_sync_details) with latest timestamp.
    • Concur reports from ServiceNow are synced in the Concur Expense Report Staging table (sn_ex_cnc_concur_report_staging).
    • Reports from the Staging table are transformed in the Concur Expense Report table (sn_ex_cnc_concur_report) by the ESM framework. Use the transformation map Concur Report Transform Map in the Table Transform Map table (sys_transform_map).
    • Approval record is created in the Pulled Integration To-do table (sn_hr_integr_fw_todo_inbound) based on the Approver field in the Concur Expense Report table.

    Workday reference info

    Use the following information for Workday integration.
    • Workday uses RAAS reports to send data to external system. For more information on RAAS and field-level info about leaves, timesheets, compensation, job change, job requisition, or leave of absence, see Workday HR Spoke.
    • Only the open requests are displayed on the approvers My tasks page.
    • Approval and rejection actions are performed using an Integration System User (ISU). ISU is a virtual user (and not an actual user) which helps in the safe-keeping of approver credentials. With the use of ISU, approval and rejection records protect the sensitive data according to your configuration in Workday. For example,
      • When John Doe, the approver enters time sheet approved as comment, the comment shown as John Doe(john.doe@acme.com): Time sheet approved.
      • When John Doe performs the action Approve, a comment is added in Workday as John Doe (john.doe@acme.com): Action – Approve.
      • When John Doe performs the action Reject, a comment is added in Workday as John Doe john.doe@acme.com): Action – Reject.
      • When John Doe performs the action Reject with a comment-Request is not in compliance with company policy, two comments are added John Doe (john.doe@acme.com): Action–Reject John Doe(john.doe@acme.com): Request is not in compliance with company policy.
    • Approve or reject actions are shipped out-of-the-box for all use cases.
    • When an approval is delegated from one approver to another in Workday; report data source is not able to handle the delegation change such as delegated task and other delegation details.
    • When a request requires a multi-level approval with level 1 approved in Workday and ServiceNow, you may see two entries for the same approval. This is a limitation with the ISU use.
    • Attachments support a max limit of 12 MB. Ensure the attachment size is below 12 MB.
    • Use the following scripts:
      • WorkdayApprovalToDosClientUtilSNC: Retrieves records for the purge process in Workday approvals.
      • WorkdayApprovalToDosHelperSNC: Contains constants related to Workday approvals.
      • WorkdayApprovalToDosClientUtil: Extends WorkdayApprovalToDosClientUtilSNC and allows users to define custom code.
      • WorkdayApprovalToDosHelperUtils: Extends WorkdayApprovalToDosHelperUtilsSNC and enables users to define custom code.
      • WorkdayApprovalToDosHelperUtilsSNC: Provides functions for Workday approvals.
    • Ensure you configure the right user controls and privileges for Compensation Change and Spend Authorization use cases. Only the authorized users can view the sensitive records and data from Workday.
    • For data protection, use the default purge policy to delete data more often. By default, data purge happens after in 30 days.
    • Ensure only the HR administrator [sn_hr_core.admin] has access to the sensitive information as explained in Remove HR Administrator role from IT System Administrators.
    For more information on how to configure approvals, see Approvals hub.

    Approvals on mobile

    Only approvals that are in sysapproval_approver table are shown using the generic card in Now Mobile.

    To disable the feature change the value of this sys_property: sn_me_todos.all_approvals_mobile_enabled to false​.

    OOTB action group use

    Use the out-of-the-box Approvals action group to display the actions such as Approve and Reject. For more information, see Action framework.
    Note:
    For actions to appear in my items widget, you can add the OOTB Approvals action group from All > Employee Center > Administration > To-dos Configurations, click an existing to-dos configuration, navigate to the To-do Configuration Details record, and use the OOTB action group under Fields Mapping.

    Additional information

    • Click the URLs for additional information and context.
    • Allow BUs to add non-task tables easily to the list in the To-dos or Task configuration reference tables by passing non-task tables as an array in the Scripted Extension Points. sn_hr_sp.TodoNonTaskTables, and sn_ex_sp.RefNonTaskTables.