For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Getting Started
    • Welcome to Moveworks
    • Roadmap & Release Notes
    • Moveworks Best Practices
    • Labs
    • Professional Services
    • Support
  • AI Assistant
    • AI Assistant Overview
    • Capabilities
    • Web Experiences
    • Analytics & Performance
  • Enterprise Search
    • Overview
    • Agentic RAG Overview
    • Content Ingestion Platform
    • Profile Boosting
    • Retrieval
    • Permissions Platform
    • Built-in Content Connectors
      • Axero
      • Brainstorm QuickHelp
      • Atlassian Confluence
      • Freshservice
      • GitHub
      • Google Drive
      • Interact
      • LumApps
      • ManageEngine
      • Notion
      • Salesforce
      • ServiceNow
        • ServiceNow Permission Mirroring
        • Permission Mirroring - Update Set Modules
        • Moveworks-Ready Knowledge Blocks
      • Microsoft Sharepoint
      • Slack
      • Staffbase
      • Unily
      • WordPress
      • Workday
    • Build your own Content Connectors
    • Configure Search
    • Configure Enterprise Search
    • Vetted Content
    • Writing AI-Ready KB Articles
    • Document Chunking and Snippetization Overview
  • Productivity Boost
    • Overview
    • Configure Productivity Boost
    • Quick GPT
    • Calendar Management
    • Brief Me
DeveloperAcademyCommunityStatus
On this page
  • Overview
  • Installing an Update Set Module
  • Updating an Update Set Module
  • Base (base)
  • What’s Inside?
  • User Role
  • System Properties
  • Scripted REST API
  • Scripted REST Resources
  • Script Includes
  • Security ACLs
  • Forms & KBs: UserCriteria & Roles (acl)
  • What’s Inside?
  • System Properties
  • Scripted REST Resources
  • Data Extracted
  • FAQ
  • Q: What security measures are in place to restrict access to this custom endpoint?
  • Q: How can I review the contents of an Update Set Module?
  • Q: If I ever need to revert changes from an Update Set Module, can I?
  • Q: Does the Moveworks Update Set support HR User Criteria?
Enterprise SearchBuilt-in Content ConnectorsServiceNow

Permission Mirroring - Update Set Modules

To further enhance your Moveworks experience, Moveworks provides plugins that are installed through Update Sets for advanced ServiceNow functionality
||View as Markdown|
Was this page helpful?
Edit this page
Previous

Moveworks-Ready Knowledge Blocks

Next
Built with

Overview

Moveworks Update Set Modules were designed to be modular and bite-sized. Rather than shipping one giant update set, we chose to ship our updates as “Modules.” There are a couple of key benefits to this approach.

  1. Feature Selection: Think of our list of Modules as a menu: order what you want, and remove what you don’t. It’s customized to your needs and feature requests.
  2. Easier Updating: When we push out updates to our modules, we want to minimize the number of merge conflicts ServiceNow identifies. Keeping Modules small lets us only update what’s required, rather than having to do a clean install each time.

Installing an Update Set Module

To install a Module, you can follow the three steps below, or watch this video.

  • Download the Update Set Module (XML) files here.
  • Import these under “Retrieved Update Sets” in your ServiceNow instance.
  • Commit the changes and the app will show up in “My Company Applications”.

Updating an Update Set Module

To update a Module, you will follow the same steps as above. There may be some merge conflicts when installing. If you’re having trouble resolving these, reach out to Moveworks Support for assistance.

In general, it is safer to accept the remote update and then ask Moveworks to run any configuration scripts for that module.

Base (base)

Provides Core Functionality to Support Our Modules

What’s Inside?

User Role

The moveworks_user role must be granted to our service account for our Update Set Modules to function properly. It also is how we restrict access to custom APIs and Tables.

System Properties

System Properties help our GlideScripts access the right constants (values) for your instance. For example, we might need to look up our bot’s sys_id, or change an email color to match your corporate theme. We also keep these for internal reporting and validation. Since, in this case, Moveworks’ code lives in an external system, our engineers need visibility into versioning, as well as the ability to validate expected results/contracts when our services start up. These attributes are exposed over the /version endpoint and we maintain them for audit purposes.

  • moveworks.base.version - identifies the version of this Update Set Module.
  • moveworks.base.api.sys_id - identifies the sys_id of the Scripted REST API that we install in order to interact with your system.

Scripted REST API

The Scripted Rest API handles authentication for our custom endpoints to make sure only our user has the ability to send requests to that endpoint. It also serves as the parent for all endpoints in future modules.

Scripted REST Resources

We have one Scripted REST Resource that ships with the base module.

GET moveworks/base/version - this endpoint lets our CS team know what version you have for each Update Set Module.

Example Request

$**curl** *{{snow_url}}/api/488834/moveworks/base/version*
$**-H** Authorization {auth header}

Example Response

1**{
2	"result": {
3		"apis": {
4			"GET /api/488834/moveworks/acl/get_access_info": "2021-02-23 04:56:42",
5			"PUT /api/488834/moveworks/acl/config": "2021-02-23 04:56:40",
6			"GET /api/488834/moveworks/base/version": "2021-02-23 04:49:37",
7			"POST /api/488834/moveworks/dev_essentials/bypass": "2021-02-23 04:35:25",
8			"PUT /api/488834/moveworks/dev_essentials/bypass": "2021-02-23 04:35:24"
9		},
10		"properties": {
11			"moveworks.acl.check_legacy_entitlements": "false",
12			"moveworks.acl.version": "1.0.0",
13			"moveworks.base.api.sys_id": "aaf4178a1b85d4105394fc88cc4bcbc8",
14			"moveworks.base.version": "1.0.0",
15			"moveworks.dev_essentials.version": "0.0.1",
16			"moveworks.logging.version": "1.0.0"
17		}
18	}
19}**

Script Includes

We ship a MoveworksBaseUtils sys_script_include with our base module to serve as system property accessors and improve our ability to work with GlideRecords.

Security ACLs

To prevent unauthorized access to the Scripted REST API, we have created an ACL (type = execute) and associated it with the moveworks_user role.

Forms & KBs: UserCriteria & Roles (acl)

Respect User Criteria & Roles When Serving Content In-Bot

What’s Inside?

System Properties

  • moveworks.acl.version - identifies the version of this Update Set Module. Maintained for the same reasons as in the base module.
  • moveworks.acl.check_legacy_entitlements - determines if we evaluate User Entitlements to determine access to forms. We need this flag to minimize the performance cost of running our script based on your instance’s configuration. When disabled, it reduces the number of GlideRecord lookups by roughly 8 lookups per record.

Scripted REST Resources

GET moveworks/acl/get_access_info - this is our production endpoint which returns information like User Criteria sys_ids so that we can support ServiceNow’s permission rules on our servers.

Example Request

$**curl** *{{snow_url}}/api/488834/moveworks/acl/get_access_info?table=sc_cat_item&record={sys_id}&user={sys_id}*
$**-H** Authorization {auth header}

Example Response

1**{
2	"result": {
3		"user": [
4			{
5				"roles": [],
6				"user_criteria": [
7					"4015ed49db1208d88228ecfc13961977",
8					"81cda580db6bd050d03dc25a1396196e",
9					"c0e466d24fd1ab80ead349cf0310c7c7"
10				]
11			}
12		],
13		"sc_cat_item": [
14			{
15				"roles": [
16					"snc_internal"
17				],
18				"available_for": [],
19				"not_available_for": []
20			}
21		]
22	}
23}**

PUT moveworks/acl/config - this endpoint configures our Update Set Module to ignore/evaluate User Entitlements by updating the system property moveworks.acl.check_legacy_entitlements to True or False accordingly. Whether this is set to True or False depends on the ServiceNow instance’s usage/configuration details.

Example Request

$**curl** *{{snow_url}}/api/488834/moveworks/acl/config ***\
>-X** POST **\
>-H** Authorization {auth header} **\
>-d** entitlements_enabled=false **\**

Example Response

1**{
2	"result": {
3		"entitlements_enabled": "false"
4	}
5}**

Data Extracted

We extract sys_ids wherever possible to protect the anonymity of user & resource constraints. These raw materials enable us to be accurate without sacrificing confidentiality. Moveworks considers all of the following for any modern ServiceNow implementation.

  • User:
    • A list of UserCriteria sys_ids that a user satisfies (UserCriteriaLoader).
    • A list of roles that a user has.
  • Knowledge Articles:
    • A list of Available UserCriteria sys_ids (can_read_user_criteria)
    • A list of Not Available UserCriteria sys_ids (cannot_read_user_criteria)
    • The sys_id of the knowledge base to which an article belongs (see below).
  • Knowledge Bases:
    • A list of “Available For” User Criteria (kb_uc_can_read_mtom).
    • A list of “Not Available For” User Criteria (kb_uc_cannot_read_mtom).
  • Catalog Items:
    • A list of roles that have access to this Catalog Item.
    • A list of “Available For” User Criteria (sc_cat_item_user_criteria_mtom).
    • A list of “Not Available For” User Criteria (sc_cat_item_user_criteria_no_mtom).

If your system is equipped with legacy User Entitlements, Moveworks will also ingest the following information.

  • User:
    • Company sys_id
    • Location sys_id
    • Department sys_id
    • Group sys_ids
  • User Criteria Records related to Catalog Items from the following tables
    • “sc_cat_item” +
    • “user”, “company”, “dept”, “location”, “group” +
    • “mtom”, “no_mtom”

FAQ

Q: What security measures are in place to restrict access to this custom endpoint?

We leverage ServiceNow’s Security ACLs to restrict usage of this endpoint to users with either the admin role or the moveworks_user role.

Q: How can I review the contents of an Update Set Module?

You can review changes under “My Company Applications” (search for “moveworks.”). We’ll also share some documentation on the contents of each of our modules.

Q: If I ever need to revert changes from an Update Set Module, can I?

If you ever need to revert changes you can do so easily with the click of a button. Simply find the update set under “Retrieved Update Sets” and select “Back Out”.

Q: Does the Moveworks Update Set support HR User Criteria?

Yes, the Moveworks Update Set does support ingestion of HR User Criteria such that it can be enforced in the bot, just like IT User Criteria. However, if you are leveraging the Human Resources: Core application to build out your HR knowledge in your ServiceNow instance, you will likely need to additionally install the HR_ACL_Patch update set due to a limit in cross-scope privileges on the Moveworks Platform Permissions REST API. Please reach out to Moveworks support for more information on this.