We provide a Bi-directional Integration over our KIMI middleware bridge or via Jitterbit between PagerDuty & Helix. Across any Helix/Remedy version supporting REST API.
– Incidents (including notes & status)
– Service Configuration & CMDB data sync
– People & Teams
– Priority Mapping
– Reassignment & Delegation
– Configurable Mapping
Manages Authentication, Configuration, Retries and Error Handling
Helix Segregation = Easier management of areas not traditionally core to Helix
Logging can be controlled outside of the Helix environment (when Helix is SAAS)
Helix integration: transactions and configurations held are in new forms, reducing changes to out-of-the-box forms
Minimises issues from PagerDuty or BMC during SAAS upgrades
Supports version upgrades and changes from both PagerDuty and KTSL
Reduces footprint on Helix ensuring support from BMC is not impacted
A layer between core forms and the PagerDuty integration means customer customisations are unaffected
