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
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
      • ServiceNow Access Requirements
      • ServiceNow for HR Access Requirements
      • Jira Service Desk Permission (On-Prem) Access Requirements
      • Moveworks Jira Application (for Jira Cloud)
      • Jira Service Management (Cloud) - Access Requirements
      • Zendesk Access Requirements
      • Freshservice Access Requirements
      • Freshdesk Access Requirements
      • Salesforce Access Requirements
      • BMC Remedy/Helix Access Requirements
      • BMC Remedyforce Access Requirements
      • Cherwell Access Requirements
      • Ivanti Service Manager Access Requirements
      • ManageEngine (Cloud) Access Requirements
      • ManageEngine (On-Prem) Access Requirements
      • SolarWinds Samange Access Requirements
      • Sysaid Access Requirements
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • What is this account used for:
Access RequirementsTicketing Systems & ITSMs Access

BMC Remedyforce Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Cherwell Access Requirements

Next
Built with

What is this account used for:

To integrate with BMC Remedyforce, Moveworks will need a dedicated service account along with its:

  1. Username
  2. Password
  3. Security Token
  4. Site URL

This is to enable the Moveworks bot to interact with the BMC Remedyforce System REST API. The Moveworks bot interacts with your BMC Remedyforce System to:

  • Monitor tickets for autonomous resolution
  • Reach out to an employee when a BMC Remedyforce ticket needs the employee’s attention
  • Create tickets to log issues the bot has resolved autonomously
  • Create tickets for issues that require an agent’s attention
  • Read the BMC Remedy user table so that the bot can log and assign issues appropriately.

Moveworks utilises the 58.0 version of the APIs to make Salesforce Object Query Language (SOQL) calls to

  1. Read Tickets
  2. Read Users

Additionally, Moveworks utilises the 58.0 version of the Salesforce Objects (sobjects) API to

  1. Create Tickets
  2. Update Tickets

Please create a service account that has the permissions to perform all the above actions, dedicated to Moveworks and then configure it within Moveworks Setup by following these steps:

  1. Select the connector - BMC Remedyforce
  2. Name the connection and select the “Common Base URL” option. Input your instance’s URL
  3. Select “Oauth2 Password Grant” under authentication type and input the values from above in the specified fields


  1. Click on save and your connector is now succesfully configured!