Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 47 | -47 |
| 164 days of no change | ||
| 2025-11-13 | 46 | +1 |
| 42 days of no change | ||
| 2025-10-01 | 45 | +1 |
| 5 days of no change | ||
| 2025-09-25 | 44 | +1 |
| 69 days of no change | ||
| 2025-07-17 | 43 | +1 |
| 31 days of no change | ||
| 2025-06-15 | 42 | +1 |
| 40 days of no change | ||
| 2025-05-05 | 41 | +1 |
| 47 days of no change | ||
| 2025-03-18 | 40 | +1 |
| 9 days of no change | ||
| 2025-03-08 | 39 | +1 |
| 20 days of no change | ||
| 2025-02-15 | 38 | +1 |
| 28 days of no change | ||
| 2025-01-17 | 37 | +1 |
| 78 days of no change | ||
| 2024-10-30 | 36 | +1 |
About
The BMC Remedy Spoke provides a list of actions that wrap around the primary Remedy REST APIs. The Spoke provides the foundation to synchronize data from ServiceNow to Remedy, such as ticketing scenarios.
a) Sync incidents, changes, problems, and theoretically any records through Get, Create, and Update Record Actions
b) Create and update incidents from ServiceNow to Remedy.
Enterprises can have multiple ITSM systems to handle different incidents, changes, problems, and so on, for different departments. Sometimes, this can be set up to differentiate regionally or strategically. Irrespective of the reasons, the BMC Remedy Spoke synchronizes ServiceNow and BMC Remedy easily and conveniently so that the end-users can view and modify ITSM-related actions at one place only, instead of swivel chair from different places.
Key Features
Actions:
- Get Incident
- Create Incident
- Get Incident Form Fields
- Get All Objects
- Get Record Details
- Create Record
- Update Record
- Create Change
- Get Change Status
- Create Problem
- Get Problem Status