BMC Helix Remedyforce integration requires a user setup in Salesforce Lightning Platform and subscription to BMC Helix Remedyforce app. FlexDeploy uses OAuth to integrate with the Lightining Platform to create Change or Incident in BMC Helix Remedyforce application.
...
Creating an Incident in BMC Helix requires category id (Foreign Key value) to be setup
You need to setup/add Category for the type of Incident going to be created from FlexDeploy. Once the Catgegory is defined, you can use the Lightning Platform Rest for SObject Relationships to get the id.
For category, you can use https://<Salesforce instance name>/services/data/<version>/sobjects/BMCServiceDesk__Category__c. Below is a sample response, you should use the id field value for Category Id when you setup the BMC instance in Topology
...
Field Code | Display Name | Description | Data Type | Required |
|---|---|---|---|---|
BMCServiceDesk__Change_Description__c | Change Description | A description for the change ticket | String | No |
BMCServiceDesk__Reason_for_Change_Details__c | Change Details |
Configure Folder for Change Management Approvals
Configure BMC Remedyforce Change Management Instance on your parent folder. Change management configurations are inherited by sub-folder and projects. This configuration will allow you to integrate BMC Remedyforce tickets with your FlexDeploy deployment. See Configure Change Management on Folders for more details.
Linking Jira ITSM with FlexDeploy Deployments
If Auto Create Ticket, is not enabled, then user must specific the change ticket number on the deployment request. See https://flexagon.atlassian.net/wiki/spaces/FD65/pages/10125813121/Link+Change+Ticket+s+with+Deployments . Otherwise, Change Ticket field will be required in the deployment request form. When change ticket number is passed the ticket number is validated on the external application.