Service Manager is Micro Focus’s enterprise service management solution. Its integrated applications are designed for out-of-box implementation, with best-practice workflows that help organizations support their infrastructure and drive competitive advantage in their core businesses. Service Manager enables companies to manage their service and support operations. It provides the tools and workflows needed to manage corporate assets: the people, knowledge, information, processes, equipment, documentation, software, and all tangible resources collectively known as infrastructure.
This document provides information about the Micro Focus Service Manager connector, which facilitates automated interactions, with a Micro Focus Service Manager server using FortiSOAR™ playbooks. Add the Micro Focus Service Manager connector as a step in FortiSOAR™ playbooks and perform automated operations, such as creating and updating incidents on Micro Focus Service Manager and retrieving a list of incidents from Micro Focus Service Manager based on the filter query that you have specified.
Connector Version: 1.4.0
Authored By: Fortinet
Certified: No
Following enhancements have been made to the Micro Focus Service Manager Connector in version 1.4.0:
Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.
You can also use the yum command as a root user to install the connector:
yum install cyops-connector-micro-focus-service-manager
For the procedure to configure a connector, click here.
In FortiSOAR™, on the Connectors page, click the Micro Focus Service Manager connector row (if you are in the Grid view on the Connectors page) and in the Configurations tab enter the required configuration details:
| Parameter | Description |
|---|---|
| Server URL | Host or domain name on which the service is available. |
| Initial Path | Initial path, i.e., the path of URI for a given deployment. This value should start with /SM/9/rest |
| Username | Username used to connect to the Micro Focus Service Manager server to which you will connect and perform automated operations. |
| Password | Password used to connect to the Micro Focus Service Manager server to which you will connect and perform automated operations. |
| Port | TCP port number on which service is available. |
| Verify SSL | Specifies whether the SSL certificate for the server is to be verified or not. By default, this option is set as True. |
The following automated operations can be included in playbooks, and you can also use the annotations to access operations:
| Function | Description | Annotation and Category |
|---|---|---|
| Create Incident | Creates a new incident on the Micro Focus Service Manager server, based on the input parameters you have specified. | create_incident Investigation |
| Get Incident List | Retrieves a list of incidents from the Micro Focus Service Manager server, based on the query and other input parameters you have specified. | get_incidents Investigation |
| Get Incident | Retrieves details for a specific incident from the Micro Focus Service Manager server, based on the incident ID you have specified. | get_incidents Investigation |
| Update Incident | Updates an existing incident on the Micro Focus Service Manager server, based on the input parameters you have specified. | update_incident Investigation |
| Get Device List | Retrieves a list of devices from the Micro Focus Service Manager server, based on the query and other input parameters you have specified. | get_devices Investigation |
| Get Device | Retrieves details for a specific device from the Micro Focus Service Manager server, based on the configuration item you have specified. | get_devices Investigation |
| Create Change | Creates a new change request on the Service Manager server, based on the title, category, primary affected service, and other input parameters you have specified. | create_change Investigation |
| Get Change List | Retrieves a list of all change requests or specific change requests from the Service Manager server, based on the query and other input parameters you have specified. | get_changes Investigation |
| Get Change Request | Retrieves details for a specific change request from the Service Manager server, based on the change request ID you have specified. | get_changes Investigation |
| Update Change | Updates an existing change for closure in Service Manager based on the change ID, closure code, phase, and other input parameters you have specified. | update_change Investigation |
| Create RF - Request Fulfillment Ticket | Creates a new RF - Request Fulfillment Ticket on the MFSM/HPSM Manager server, based on the title, description, category, priority, etc., and other input parameters you have specified. | create_rf Investigation |
| Get RF - Request Fulfillment Ticket | Retrieves details for a specific RF-Request Fulfillment Ticket from the MFSM/HPSM server, based on the RF ID you have specified. | get_rf Investigation |
| Update RF - Request Fulfillment Ticket for an attachment | Updates an existing RF-Request Fulfillment Ticket to upload (add) an attachment to that RF in Service Manager based on the RF ID, attachment name, and message body you have specified. | update_rf_attachment Investigation |
| Retrieve Attachment Information | Retrieves information on the resource attachment collection of an incident based on the incident ID that you have specified. | retrieve_attachment_information Investigation |
| Download Attachment | Downloads an attachment associated with an incident based on the attachment ID and the incident ID that you have specified. | download_an_attachment Investigation |
| Delete Attachment | Deletes an attachment associated with an incident based on the attachment ID and the incident ID that you have specified. | delete_an_attachment Investigation |
| Parameter | Description |
|---|---|
| Title | Title of the incident that you want to create on the Micro Focus Service Manager server. |
| Description | Description of the incident that you want to create on the Micro Focus Service Manager server. |
| Impact | Impact value to be assigned to the incident that you want to create on the Micro Focus Service Manager server. You can choose from the following options: Enterprises, Site/Dept, Multiple Users, or User. By default, this is set as User. |
| Urgency | Urgency value to be assigned to the incident that you want to create on the Micro Focus Service Manager server. You can choose from the following options: Critical, High, Average, or Low. By default, this is set as Low. |
| Category | Category to be assigned to the incident that you want to create on the Micro Focus Service Manager server. For example, Incident, Complaint, etc. Note: Category values can be added in lowercase. |
| Primary Affected Service | The ID of the primary service that has been affected by the incident that you want to create on the Micro Focus Service Manager server. For example, CI1001020 |
| Affected CI | (Optional) The ID of the service component(s) that have been affected by the incident that you want to create on the Micro Focus Service Manager server. For example, CI1000783 |
| Subcategory | (Optional) Subcategory to be assigned to the incident that you want to create on the Micro Focus Service Manager server. |
| Area | (Optional) Area to be assigned to the incident that you want to create on the Micro Focus Service Manager server. For example, performance, failure, hardware, access, etc. |
| Assignment Group | (Optional) Assignment Group to whom the incident that you want to create on the Micro Focus Service Manager server should be assigned. For example, Office Supplies (North America). |
| Source | (Optional) Source of the incident that you want to create on the Micro Focus Service Manager server. You can choose from the following options: User, Group, Event, Chat, E-mail, or Telephone. By default, this is set as User. |
| Contact Person | (Optional) Name of the person to contact for information about the incident that you want to create on the Micro Focus Service Manager server. |
| Outage Start Time | (Optional) Start time of the outage due to the incident that you want to create on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 03:30:00. |
| Outage End Time | (Optional) End time of the outage due to the incident that you want to create on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 05:30:00. |
| Assignee | (Optional) Name of the assignee of the incident that you want to create on the Micro Focus Service Manager server. |
| Service Recipient | (Optional) Name of the service recipient of the incident that you want to create on the Micro Focus Service Manager server. |
| Location | (Optional) The location where the incident occurred that you want to create on the Micro Focus Service Manager server. For example, Africa, Asia, Europe, etc. |
| Solution | (Optional) Solution (if available) to the incident that occurred and that you want to create on the Micro Focus Service Manager server. |
| Additional Fields | (Optional) Additional fields that you want to add to the incident record that you want to create on the Micro Focus Service Manager server. You must add the additional fields in the JSON Dictionary format. |
The output contains the following populated JSON schema:
{
"Messages": [],
"ReturnCode": "",
"Incident": {
"AssignmentGroup": "",
"Title": "",
"Service": "",
"UpdatedBy": "",
"OpenedBy": "",
"Category": "",
"Assignee": "",
"Urgency": "",
"Phase": "",
"Description": [],
"UpdatedTime": "",
"IncidentID": "",
"Status": "",
"Impact": "",
"OpenTime": ""
}
}
| Parameter | Description |
|---|---|
| Incident ID | The ID of the incident that you want to update on the Micro Focus Service Manager server. |
| Title | (Optional) Title of the incident that you want to update on the Micro Focus Service Manager server. |
| Description | (Optional) Description of the incident that you want to update on the Micro Focus Service Manager server. |
| Impact | (Optional) Impact value to be assigned to the incident that you want to update on the Micro Focus Service Manager server. You can choose from the following options: Enterprises, Site/Dept, Multiple Users, or User. By default, this is set as User. |
| Urgency | (Optional) Urgency value to be assigned to the incident that you want to update on the Micro Focus Service Manager server. You can choose from the following options: Critical, High, Average, or Low. By default, this is set as Low. |
| Category | (Optional) Category to be assigned to the incident that you want to update on the Micro Focus Service Manager server. For example, Incident, Complaint, etc. Note: Category values can be added in lowercase. |
| Primary Affected Service | (Optional) The ID of the primary service that has been affected by the incident that you want to update on the Micro Focus Service Manager server. For example, CI1001020 |
| Affected CI | (Optional) The ID of the service component(s) that have been affected by the incident that you want to update on the Micro Focus Service Manager server. For example, CI1000783 |
| Subcategory | (Optional) Subcategory to be assigned to the incident that you want to update on the Micro Focus Service Manager server. |
| Area | (Optional) Area to be assigned to the incident that you want to update on the Micro Focus Service Manager server. For example, performance, failure, hardware, access, etc. |
| Assignment Group | (Optional) Assignment Group to whom the incident that you want to update on the Micro Focus Service Manager server should be assigned. For example, Office Supplies (North America). |
| Source | (Optional) Source of the incident that you want to update on the Micro Focus Service Manager server. You can choose from the following options: User, Group, Event, Chat, E-mail, or Telephone. By default, this is set as User. |
| Contact Person | (Optional) Name of the person to contact for information about the incident that you want to update on the Micro Focus Service Manager server. |
| Outage Start Time | (Optional) Start time of the outage due to the incident that you want to update on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 03:30:00. |
| Outage End Time | (Optional) End time of the outage due to the incident that you want to update on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 05:30:00. |
| Assignee | (Optional) Name of the assignee of the incident that you want to update on the Micro Focus Service Manager server. |
| Service Recipient | (Optional) Name of the service recipient of the incident that you want to update on the Micro Focus Service Manager server. |
| Location | (Optional) The location where the incident occurred that you want to update on the Micro Focus Service Manager server. For example, Africa, Asia, Europe, etc. |
| Solution | (Optional) Solution (if available) to the incident that occurred and that you want to update on the Micro Focus Service Manager server. |
| Additional Fields | (Optional) Additional fields that you want to add to the incident record that you want to update on the Micro Focus Service Manager server. You must add the additional fields in the JSON Dictionary format. |
The output contains the following populated JSON schema:
{
"Incident": {
"Area": "",
"Assignee": "",
"AssignmentGroup": "",
"Category": "",
"Company": "",
"Contact": "",
"Description": [],
"Impact": "",
"IncidentID": "",
"OpenTime": "",
"OpenedBy": "",
"Phase": "",
"Service": "",
"Solution": [],
"Status": "",
"Subarea": "",
"Title": "",
"UpdatedBy": "",
"UpdatedTime": "",
"Urgency": ""
},
"Messages": [],
"ReturnCode": ""
}
Note: All the input parameters are optional. However, if you do not specify any parameter, then no filter criterion is applied, and an unfiltered list (of incidents) is returned.
| Parameter | Description |
|---|---|
| Query | Query (or filter) that you use to specify the search criteria, based on which you want to retrieve incidents from the Micro Focus Service Manager server. For example, Category = "incident", Title = "Desktop screen out of order" |
| Sort | Sorts the result of the operation, i.e., the list of incidents retrieved from the Micro Focus Service Manager server are sorted based on the sort fields you have specified. For example, Urgency:ascending,field2:descending |
| Start | Index of the member from which the collection response representation begins. |
| Count | The number of collection members to be returned by this operation. |
| View | View of the collection that is returned by this operation. You can choose from the following options: Summary, Condense, or Expand. By default, this is set as Expand. |
The output contains the following populated JSON schema:
{
"@count": "",
"@start": "",
"@totalcount": "",
"Messages": [],
"ResourceName": "",
"ReturnCode": "",
"content": [
{
"Incident": {
"Area": "",
"Assignee": "",
"AssignmentGroup": "",
"Category": "",
"ClosedBy": "",
"ClosedTime": "",
"ClosureCode": "",
"Company": "",
"Contact": "",
"Description": [],
"Impact": "",
"IncidentID": "",
"JournalUpdates": [],
"OpenTime": "",
"OpenedBy": "",
"Phase": "",
"Service": "",
"Solution": [],
"Status": "",
"Subarea": "",
"Title": "",
"UpdatedBy": "",
"UpdatedTime": "",
"Urgency": ""
}
}
]
}
| Parameter | Description |
|---|---|
| Incident ID | The ID of the incident whose details you want to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Messages": [],
"ReturnCode": 0,
"Incident": {
"UpdatedBy": "",
"Status": "",
"SLAAgreementID": "",
"Urgency": "",
"Area": "",
"OpenTime": "",
"Location": "",
"ClosedTime": "",
"Title": "",
"Subarea": "",
"Solution": [],
"ClosedBy": "",
"OpenedBy": "",
"IncidentID": "",
"Assignee": "",
"Company": "",
"Description": [],
"TicketOwner": "",
"ProblemType": "",
"AssignmentGroup": "",
"UpdatedTime": "",
"Service": "",
"Impact": "",
"ClosureCode": "",
"Category": "",
"AffectedCI": ""
}
}
Note: Note: All the input parameters are optional. However, if you do not specify any parameter, then no filter criterion is applied, and an unfiltered list (of devices) is returned.
| Parameter | Description |
|---|---|
| Query | Query (or filter) that you use to specify the search criteria, based on which you want to retrieve devices from the Micro Focus Service Manager server. For example, Status="Available" |
| Sort | Sorts the result of the operation, i.e., the list of devices retrieved from the Micro Focus Service Manager server are sorted based on the sort fields you have specified. For example, Urgency:ascending,field2:descending |
| Start | Index of the member from which the collection response representation begins. |
| Count | The number of collection members to be returned by this operation. |
| View | View of the collection that is returned by this operation. You can choose from the following options: Summary, Condense, or Expand. By default, this is set as Expand. |
The output contains the following populated JSON schema:
{
"@totalcount": "",
"Messages": [],
"ResourceName": "",
"content": [
{
"Device": {
"DisplayName": "",
"Status": "",
"UpdatedBy": "",
"AssignmentGroup": "",
"ConfigurationItem": "",
"Vendor": "",
"ConfigurationItemSubType": "",
"Company": "",
"ConfigurationItemType": ""
}
}
],
"@start": "",
"@count": "",
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Configuration Item | Configuration item of the device, i.e., the ID of the device, whose details you want to retrieve from the Micro Focus Service Manager server. For example, CI1000011 |
The output contains the following populated JSON schema:
{
"ReturnCode": "",
"Messages": [],
"Device": {
"DisplayName": "",
"Status": "",
"UpdatedBy": "",
"AssignmentGroup": "",
"ConfigurationItem": "",
"Vendor": "",
"ConfigurationItemSubType": "",
"Company": "",
"ConfigurationItemType": ""
}
}
| Parameter | Description |
|---|---|
| Title | Title of the change request that you want to create in the Micro Focus Service Manager server. |
| Description | Description of the change request that you want to create in the Micro Focus Service Manager server. |
| Category | Category to be assigned to the change request that you want to create in the Micro Focus Service Manager server. |
| Subcategory | Subcategory to be assigned to the change request that you want to create in the Micro Focus Service Manager server. |
| Initiated By | Name of the user who has initiated the change request that you want to create in the Micro Focus Service Manager server. |
| Primary Affected Service | The ID of the primary service that has been affected by the change request that you want to create in the Micro Focus Service Manager server. |
| Affected CI | (Optional) The ID of the service component(s) that have been affected by the change request that you want to create in the Micro Focus Service Manager server. |
| Change Originator | (Optional) Enter the value of the originator of the change for which you want to create a change request in the Micro Focus Service Manager server. |
| Change Coordinator | (Optional) Enter the value of the coordinator of the change for which you want to create a change request in the Micro Focus Service Manager server. |
| Reason For Change | (Optional) Enter the reason for which you want to create a change request in the Micro Focus Service Manager server. |
| Target Start Time | (Optional) Enter the target start DateTime for the change request that you want to create in the Micro Focus Service Manager server. |
| Target End Time | (Optional) Enter the target end DateTime for the change request that you want to create in the Micro Focus Service Manager server. |
| Additional Fields | (Optional) JSON dictionary using which you can add extra input parameters to the change request that you want to create in the Micro Focus Service Manager server. For example, {"AssignmentGroup": "cs"} |
The output contains the following populated JSON schema:
{
"Change": {
"close": {
"ClosureCode": ""
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": []
},
"ChangeOriginator": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Query | Query (or filter) that you use to specify the search criteria, based on which you want to retrieve change requests from the Micro Focus Service Manager server. |
| Sort | Sorts the result of the operation, i.e., the list of change requests retrieved from the Micro Focus Service Manager server are sorted based on the sort fields you have specified. For example, Urgency:ascending,field2:descending |
| Start | Index of the member from which the collection response representation begins. |
| Count | The number of collection members to be returned by this operation. |
| View | View of the collection that is returned by this operation. You can choose from the following options: Summary, Condense, or Expand. By default, this is set as Expand. |
The output contains the following populated JSON schema:
{
"@count": "",
"@start": "",
"content": [
{
"Change": {
"close": {
"ClosureCode": "",
"ClosingComments": []
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"Priority": "",
"CloseTime": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"BackoutDuration": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": []
},
"OoredooChangeOriginator": ""
}
}
],
"Messages": [],
"ReturnCode": "",
"@totalcount": "",
"ResourceName": ""
}
| Parameter | Description |
|---|---|
| Change Request Number | The ID of the change request whose details you want to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Change": {
"close": {
"ClosureCode": "",
"ClosingComments": []
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"Priority": "",
"CloseTime": "",
"AssignedTo": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"BackoutDuration": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": [],
"BackoutMethod": []
},
"ChangeOriginator": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Change ID | Specify the ID of the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Closure Code | Specify the closure code that you want to apply to the change request that you want to update for closure in the Micro Focus Service Manager server. |
| SubClosure Code | Specify the sub-closure code that you want to apply to the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Closing Comments | Specify the closing comments that you want to add to the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Phase | Specify the phase of the change request that you want to update for closure in the Micro Focus Service Manager server. You can specify phases such as logging, approve, close, etc. |
| Actual Start Time | (Optional) Select the actual start DateTime of the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Actual End Time | (Optional) Enter the actual end DateTime of the change request that you want to update for closure in the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"SubClosureCode": "",
"Change": {
"close": {
"ClosureCode": "",
"ClosingComments": []
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"CloseTime": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": []
},
"OoredooChangeOriginator": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Title or Brief Description | Title or brief description of the Request Fulfillment Ticket (RF) that you want to create on the Micro Focus Service Manager server. |
| Description | Description of the Request Fulfillment Ticket (RF) that you want to create on the Micro Focus Service Manager server. |
| Category | Category to be assigned to the RF that you want to create on the Micro Focus Service Manager server. |
| Subcategory | Subcategory to be assigned to the RF that you want to create on the Micro Focus Service Manager server. |
| Assigned To | Name of the user to whom you want to assign the RF that you want to create on the Micro Focus Service Manager server. |
| Assigned Group | The ID of the group to which you want to assign the RF that you want to create on the Micro Focus Service Manager server |
| Impact | Impact number to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, 4 is 'No Service Impact'. |
| Priority | Priority value to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, 4 is 'Low'. |
| Urgency | Urgency value to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, 4 is 'Low'. |
| Product Type | Product Type to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, other. |
| Requester Name | Name of the Requester, who has raised the RF that you want to create on the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Request": {
"Open": "",
"Impact": "",
"Number": "",
"Status": "",
"Urgency": "",
"Category": "",
"Priority": "",
"SlaBreach": "",
"AssignedTo": "",
"SubmitDate": "",
"UpdateDate": "",
"CustVisible": "",
"Description": [],
"ProductType": "",
"Subcategory": "",
"AgreementIds": [],
"CurrentPhase": "",
"DeliveryDate": "",
"AssignedGroup": "",
"RequestorName": "",
"ApprovalStatus": "",
"BriefDescription": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| RF - Request Fulfillment Ticket Number | The ID of the Request Fulfillment Ticket whose details you want to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Request": {
"Open": "",
"Impact": "",
"Number": "",
"Status": "",
"Urgency": "",
"Category": "",
"Priority": "",
"SlaBreach": "",
"AssignedTo": "",
"SubmitDate": "",
"UpdateDate": "",
"CustVisible": "",
"Description": [],
"ProductType": "",
"Subcategory": "",
"AgreementIds": [],
"CurrentPhase": "",
"DeliveryDate": "",
"AssignedGroup": "",
"RequestorName": "",
"ApprovalStatus": "",
"BriefDescription": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| RF-Request Fulfillment Ticket ID | The ID of the Request Fulfillment Ticket to which you want to add the attachment in the Micro Focus Service Manager server. |
| Attachment Name | The name of the attachment name that you want to add to the specified RF in the Micro Focus Service Manager server. |
| Message Body | The content of the file to be uploaded to the specified RF in the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Messages": [],
"ReturnCode": "",
"ResourceName": "",
"content": []
}
| Parameter | Description |
|---|---|
| Incident ID | Specify the incident ID whose details to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"@count": "",
"@start": "",
"@totalcount": "",
"Messages": [],
"ResourceName": "",
"ReturnCode": "",
"content": []
}
| Parameter | Description |
|---|---|
| Incident ID | Specify the incident ID associated with the attachment to download from the Micro Focus Service Manager server. |
| Attachment ID | Specify the attachment ID associated with the attachment to download from the Micro Focus Service Manager server. |
No output schema is available at this time.
| Parameter | Description |
|---|---|
| Incident ID | Specify the incident ID associated with the attachment to delete from the Micro Focus Service Manager server. |
| Attachment ID | Specify the attachment ID associated with the attachment to delete from the Micro Focus Service Manager server. |
No output schema is available at this time.
The Sample - Micro Focus Service Manager - 1.4.0 playbook collection comes bundled with the Micro Focus Service Manager connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Micro Focus Service Manager connector.
Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during the connector upgrade and delete.
Service Manager is Micro Focus’s enterprise service management solution. Its integrated applications are designed for out-of-box implementation, with best-practice workflows that help organizations support their infrastructure and drive competitive advantage in their core businesses. Service Manager enables companies to manage their service and support operations. It provides the tools and workflows needed to manage corporate assets: the people, knowledge, information, processes, equipment, documentation, software, and all tangible resources collectively known as infrastructure.
This document provides information about the Micro Focus Service Manager connector, which facilitates automated interactions, with a Micro Focus Service Manager server using FortiSOAR™ playbooks. Add the Micro Focus Service Manager connector as a step in FortiSOAR™ playbooks and perform automated operations, such as creating and updating incidents on Micro Focus Service Manager and retrieving a list of incidents from Micro Focus Service Manager based on the filter query that you have specified.
Connector Version: 1.4.0
Authored By: Fortinet
Certified: No
Following enhancements have been made to the Micro Focus Service Manager Connector in version 1.4.0:
Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.
You can also use the yum command as a root user to install the connector:
yum install cyops-connector-micro-focus-service-manager
For the procedure to configure a connector, click here.
In FortiSOAR™, on the Connectors page, click the Micro Focus Service Manager connector row (if you are in the Grid view on the Connectors page) and in the Configurations tab enter the required configuration details:
| Parameter | Description |
|---|---|
| Server URL | Host or domain name on which the service is available. |
| Initial Path | Initial path, i.e., the path of URI for a given deployment. This value should start with /SM/9/rest |
| Username | Username used to connect to the Micro Focus Service Manager server to which you will connect and perform automated operations. |
| Password | Password used to connect to the Micro Focus Service Manager server to which you will connect and perform automated operations. |
| Port | TCP port number on which service is available. |
| Verify SSL | Specifies whether the SSL certificate for the server is to be verified or not. By default, this option is set as True. |
The following automated operations can be included in playbooks, and you can also use the annotations to access operations:
| Function | Description | Annotation and Category |
|---|---|---|
| Create Incident | Creates a new incident on the Micro Focus Service Manager server, based on the input parameters you have specified. | create_incident Investigation |
| Get Incident List | Retrieves a list of incidents from the Micro Focus Service Manager server, based on the query and other input parameters you have specified. | get_incidents Investigation |
| Get Incident | Retrieves details for a specific incident from the Micro Focus Service Manager server, based on the incident ID you have specified. | get_incidents Investigation |
| Update Incident | Updates an existing incident on the Micro Focus Service Manager server, based on the input parameters you have specified. | update_incident Investigation |
| Get Device List | Retrieves a list of devices from the Micro Focus Service Manager server, based on the query and other input parameters you have specified. | get_devices Investigation |
| Get Device | Retrieves details for a specific device from the Micro Focus Service Manager server, based on the configuration item you have specified. | get_devices Investigation |
| Create Change | Creates a new change request on the Service Manager server, based on the title, category, primary affected service, and other input parameters you have specified. | create_change Investigation |
| Get Change List | Retrieves a list of all change requests or specific change requests from the Service Manager server, based on the query and other input parameters you have specified. | get_changes Investigation |
| Get Change Request | Retrieves details for a specific change request from the Service Manager server, based on the change request ID you have specified. | get_changes Investigation |
| Update Change | Updates an existing change for closure in Service Manager based on the change ID, closure code, phase, and other input parameters you have specified. | update_change Investigation |
| Create RF - Request Fulfillment Ticket | Creates a new RF - Request Fulfillment Ticket on the MFSM/HPSM Manager server, based on the title, description, category, priority, etc., and other input parameters you have specified. | create_rf Investigation |
| Get RF - Request Fulfillment Ticket | Retrieves details for a specific RF-Request Fulfillment Ticket from the MFSM/HPSM server, based on the RF ID you have specified. | get_rf Investigation |
| Update RF - Request Fulfillment Ticket for an attachment | Updates an existing RF-Request Fulfillment Ticket to upload (add) an attachment to that RF in Service Manager based on the RF ID, attachment name, and message body you have specified. | update_rf_attachment Investigation |
| Retrieve Attachment Information | Retrieves information on the resource attachment collection of an incident based on the incident ID that you have specified. | retrieve_attachment_information Investigation |
| Download Attachment | Downloads an attachment associated with an incident based on the attachment ID and the incident ID that you have specified. | download_an_attachment Investigation |
| Delete Attachment | Deletes an attachment associated with an incident based on the attachment ID and the incident ID that you have specified. | delete_an_attachment Investigation |
| Parameter | Description |
|---|---|
| Title | Title of the incident that you want to create on the Micro Focus Service Manager server. |
| Description | Description of the incident that you want to create on the Micro Focus Service Manager server. |
| Impact | Impact value to be assigned to the incident that you want to create on the Micro Focus Service Manager server. You can choose from the following options: Enterprises, Site/Dept, Multiple Users, or User. By default, this is set as User. |
| Urgency | Urgency value to be assigned to the incident that you want to create on the Micro Focus Service Manager server. You can choose from the following options: Critical, High, Average, or Low. By default, this is set as Low. |
| Category | Category to be assigned to the incident that you want to create on the Micro Focus Service Manager server. For example, Incident, Complaint, etc. Note: Category values can be added in lowercase. |
| Primary Affected Service | The ID of the primary service that has been affected by the incident that you want to create on the Micro Focus Service Manager server. For example, CI1001020 |
| Affected CI | (Optional) The ID of the service component(s) that have been affected by the incident that you want to create on the Micro Focus Service Manager server. For example, CI1000783 |
| Subcategory | (Optional) Subcategory to be assigned to the incident that you want to create on the Micro Focus Service Manager server. |
| Area | (Optional) Area to be assigned to the incident that you want to create on the Micro Focus Service Manager server. For example, performance, failure, hardware, access, etc. |
| Assignment Group | (Optional) Assignment Group to whom the incident that you want to create on the Micro Focus Service Manager server should be assigned. For example, Office Supplies (North America). |
| Source | (Optional) Source of the incident that you want to create on the Micro Focus Service Manager server. You can choose from the following options: User, Group, Event, Chat, E-mail, or Telephone. By default, this is set as User. |
| Contact Person | (Optional) Name of the person to contact for information about the incident that you want to create on the Micro Focus Service Manager server. |
| Outage Start Time | (Optional) Start time of the outage due to the incident that you want to create on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 03:30:00. |
| Outage End Time | (Optional) End time of the outage due to the incident that you want to create on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 05:30:00. |
| Assignee | (Optional) Name of the assignee of the incident that you want to create on the Micro Focus Service Manager server. |
| Service Recipient | (Optional) Name of the service recipient of the incident that you want to create on the Micro Focus Service Manager server. |
| Location | (Optional) The location where the incident occurred that you want to create on the Micro Focus Service Manager server. For example, Africa, Asia, Europe, etc. |
| Solution | (Optional) Solution (if available) to the incident that occurred and that you want to create on the Micro Focus Service Manager server. |
| Additional Fields | (Optional) Additional fields that you want to add to the incident record that you want to create on the Micro Focus Service Manager server. You must add the additional fields in the JSON Dictionary format. |
The output contains the following populated JSON schema:
{
"Messages": [],
"ReturnCode": "",
"Incident": {
"AssignmentGroup": "",
"Title": "",
"Service": "",
"UpdatedBy": "",
"OpenedBy": "",
"Category": "",
"Assignee": "",
"Urgency": "",
"Phase": "",
"Description": [],
"UpdatedTime": "",
"IncidentID": "",
"Status": "",
"Impact": "",
"OpenTime": ""
}
}
| Parameter | Description |
|---|---|
| Incident ID | The ID of the incident that you want to update on the Micro Focus Service Manager server. |
| Title | (Optional) Title of the incident that you want to update on the Micro Focus Service Manager server. |
| Description | (Optional) Description of the incident that you want to update on the Micro Focus Service Manager server. |
| Impact | (Optional) Impact value to be assigned to the incident that you want to update on the Micro Focus Service Manager server. You can choose from the following options: Enterprises, Site/Dept, Multiple Users, or User. By default, this is set as User. |
| Urgency | (Optional) Urgency value to be assigned to the incident that you want to update on the Micro Focus Service Manager server. You can choose from the following options: Critical, High, Average, or Low. By default, this is set as Low. |
| Category | (Optional) Category to be assigned to the incident that you want to update on the Micro Focus Service Manager server. For example, Incident, Complaint, etc. Note: Category values can be added in lowercase. |
| Primary Affected Service | (Optional) The ID of the primary service that has been affected by the incident that you want to update on the Micro Focus Service Manager server. For example, CI1001020 |
| Affected CI | (Optional) The ID of the service component(s) that have been affected by the incident that you want to update on the Micro Focus Service Manager server. For example, CI1000783 |
| Subcategory | (Optional) Subcategory to be assigned to the incident that you want to update on the Micro Focus Service Manager server. |
| Area | (Optional) Area to be assigned to the incident that you want to update on the Micro Focus Service Manager server. For example, performance, failure, hardware, access, etc. |
| Assignment Group | (Optional) Assignment Group to whom the incident that you want to update on the Micro Focus Service Manager server should be assigned. For example, Office Supplies (North America). |
| Source | (Optional) Source of the incident that you want to update on the Micro Focus Service Manager server. You can choose from the following options: User, Group, Event, Chat, E-mail, or Telephone. By default, this is set as User. |
| Contact Person | (Optional) Name of the person to contact for information about the incident that you want to update on the Micro Focus Service Manager server. |
| Outage Start Time | (Optional) Start time of the outage due to the incident that you want to update on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 03:30:00. |
| Outage End Time | (Optional) End time of the outage due to the incident that you want to update on the Micro Focus Service Manager server. You must enter the time in the format MM/DD/YY HH:MM:SSFor example, 08/24/18 05:30:00. |
| Assignee | (Optional) Name of the assignee of the incident that you want to update on the Micro Focus Service Manager server. |
| Service Recipient | (Optional) Name of the service recipient of the incident that you want to update on the Micro Focus Service Manager server. |
| Location | (Optional) The location where the incident occurred that you want to update on the Micro Focus Service Manager server. For example, Africa, Asia, Europe, etc. |
| Solution | (Optional) Solution (if available) to the incident that occurred and that you want to update on the Micro Focus Service Manager server. |
| Additional Fields | (Optional) Additional fields that you want to add to the incident record that you want to update on the Micro Focus Service Manager server. You must add the additional fields in the JSON Dictionary format. |
The output contains the following populated JSON schema:
{
"Incident": {
"Area": "",
"Assignee": "",
"AssignmentGroup": "",
"Category": "",
"Company": "",
"Contact": "",
"Description": [],
"Impact": "",
"IncidentID": "",
"OpenTime": "",
"OpenedBy": "",
"Phase": "",
"Service": "",
"Solution": [],
"Status": "",
"Subarea": "",
"Title": "",
"UpdatedBy": "",
"UpdatedTime": "",
"Urgency": ""
},
"Messages": [],
"ReturnCode": ""
}
Note: All the input parameters are optional. However, if you do not specify any parameter, then no filter criterion is applied, and an unfiltered list (of incidents) is returned.
| Parameter | Description |
|---|---|
| Query | Query (or filter) that you use to specify the search criteria, based on which you want to retrieve incidents from the Micro Focus Service Manager server. For example, Category = "incident", Title = "Desktop screen out of order" |
| Sort | Sorts the result of the operation, i.e., the list of incidents retrieved from the Micro Focus Service Manager server are sorted based on the sort fields you have specified. For example, Urgency:ascending,field2:descending |
| Start | Index of the member from which the collection response representation begins. |
| Count | The number of collection members to be returned by this operation. |
| View | View of the collection that is returned by this operation. You can choose from the following options: Summary, Condense, or Expand. By default, this is set as Expand. |
The output contains the following populated JSON schema:
{
"@count": "",
"@start": "",
"@totalcount": "",
"Messages": [],
"ResourceName": "",
"ReturnCode": "",
"content": [
{
"Incident": {
"Area": "",
"Assignee": "",
"AssignmentGroup": "",
"Category": "",
"ClosedBy": "",
"ClosedTime": "",
"ClosureCode": "",
"Company": "",
"Contact": "",
"Description": [],
"Impact": "",
"IncidentID": "",
"JournalUpdates": [],
"OpenTime": "",
"OpenedBy": "",
"Phase": "",
"Service": "",
"Solution": [],
"Status": "",
"Subarea": "",
"Title": "",
"UpdatedBy": "",
"UpdatedTime": "",
"Urgency": ""
}
}
]
}
| Parameter | Description |
|---|---|
| Incident ID | The ID of the incident whose details you want to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Messages": [],
"ReturnCode": 0,
"Incident": {
"UpdatedBy": "",
"Status": "",
"SLAAgreementID": "",
"Urgency": "",
"Area": "",
"OpenTime": "",
"Location": "",
"ClosedTime": "",
"Title": "",
"Subarea": "",
"Solution": [],
"ClosedBy": "",
"OpenedBy": "",
"IncidentID": "",
"Assignee": "",
"Company": "",
"Description": [],
"TicketOwner": "",
"ProblemType": "",
"AssignmentGroup": "",
"UpdatedTime": "",
"Service": "",
"Impact": "",
"ClosureCode": "",
"Category": "",
"AffectedCI": ""
}
}
Note: Note: All the input parameters are optional. However, if you do not specify any parameter, then no filter criterion is applied, and an unfiltered list (of devices) is returned.
| Parameter | Description |
|---|---|
| Query | Query (or filter) that you use to specify the search criteria, based on which you want to retrieve devices from the Micro Focus Service Manager server. For example, Status="Available" |
| Sort | Sorts the result of the operation, i.e., the list of devices retrieved from the Micro Focus Service Manager server are sorted based on the sort fields you have specified. For example, Urgency:ascending,field2:descending |
| Start | Index of the member from which the collection response representation begins. |
| Count | The number of collection members to be returned by this operation. |
| View | View of the collection that is returned by this operation. You can choose from the following options: Summary, Condense, or Expand. By default, this is set as Expand. |
The output contains the following populated JSON schema:
{
"@totalcount": "",
"Messages": [],
"ResourceName": "",
"content": [
{
"Device": {
"DisplayName": "",
"Status": "",
"UpdatedBy": "",
"AssignmentGroup": "",
"ConfigurationItem": "",
"Vendor": "",
"ConfigurationItemSubType": "",
"Company": "",
"ConfigurationItemType": ""
}
}
],
"@start": "",
"@count": "",
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Configuration Item | Configuration item of the device, i.e., the ID of the device, whose details you want to retrieve from the Micro Focus Service Manager server. For example, CI1000011 |
The output contains the following populated JSON schema:
{
"ReturnCode": "",
"Messages": [],
"Device": {
"DisplayName": "",
"Status": "",
"UpdatedBy": "",
"AssignmentGroup": "",
"ConfigurationItem": "",
"Vendor": "",
"ConfigurationItemSubType": "",
"Company": "",
"ConfigurationItemType": ""
}
}
| Parameter | Description |
|---|---|
| Title | Title of the change request that you want to create in the Micro Focus Service Manager server. |
| Description | Description of the change request that you want to create in the Micro Focus Service Manager server. |
| Category | Category to be assigned to the change request that you want to create in the Micro Focus Service Manager server. |
| Subcategory | Subcategory to be assigned to the change request that you want to create in the Micro Focus Service Manager server. |
| Initiated By | Name of the user who has initiated the change request that you want to create in the Micro Focus Service Manager server. |
| Primary Affected Service | The ID of the primary service that has been affected by the change request that you want to create in the Micro Focus Service Manager server. |
| Affected CI | (Optional) The ID of the service component(s) that have been affected by the change request that you want to create in the Micro Focus Service Manager server. |
| Change Originator | (Optional) Enter the value of the originator of the change for which you want to create a change request in the Micro Focus Service Manager server. |
| Change Coordinator | (Optional) Enter the value of the coordinator of the change for which you want to create a change request in the Micro Focus Service Manager server. |
| Reason For Change | (Optional) Enter the reason for which you want to create a change request in the Micro Focus Service Manager server. |
| Target Start Time | (Optional) Enter the target start DateTime for the change request that you want to create in the Micro Focus Service Manager server. |
| Target End Time | (Optional) Enter the target end DateTime for the change request that you want to create in the Micro Focus Service Manager server. |
| Additional Fields | (Optional) JSON dictionary using which you can add extra input parameters to the change request that you want to create in the Micro Focus Service Manager server. For example, {"AssignmentGroup": "cs"} |
The output contains the following populated JSON schema:
{
"Change": {
"close": {
"ClosureCode": ""
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": []
},
"ChangeOriginator": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Query | Query (or filter) that you use to specify the search criteria, based on which you want to retrieve change requests from the Micro Focus Service Manager server. |
| Sort | Sorts the result of the operation, i.e., the list of change requests retrieved from the Micro Focus Service Manager server are sorted based on the sort fields you have specified. For example, Urgency:ascending,field2:descending |
| Start | Index of the member from which the collection response representation begins. |
| Count | The number of collection members to be returned by this operation. |
| View | View of the collection that is returned by this operation. You can choose from the following options: Summary, Condense, or Expand. By default, this is set as Expand. |
The output contains the following populated JSON schema:
{
"@count": "",
"@start": "",
"content": [
{
"Change": {
"close": {
"ClosureCode": "",
"ClosingComments": []
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"Priority": "",
"CloseTime": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"BackoutDuration": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": []
},
"OoredooChangeOriginator": ""
}
}
],
"Messages": [],
"ReturnCode": "",
"@totalcount": "",
"ResourceName": ""
}
| Parameter | Description |
|---|---|
| Change Request Number | The ID of the change request whose details you want to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Change": {
"close": {
"ClosureCode": "",
"ClosingComments": []
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"Priority": "",
"CloseTime": "",
"AssignedTo": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"BackoutDuration": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": [],
"BackoutMethod": []
},
"ChangeOriginator": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Change ID | Specify the ID of the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Closure Code | Specify the closure code that you want to apply to the change request that you want to update for closure in the Micro Focus Service Manager server. |
| SubClosure Code | Specify the sub-closure code that you want to apply to the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Closing Comments | Specify the closing comments that you want to add to the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Phase | Specify the phase of the change request that you want to update for closure in the Micro Focus Service Manager server. You can specify phases such as logging, approve, close, etc. |
| Actual Start Time | (Optional) Select the actual start DateTime of the change request that you want to update for closure in the Micro Focus Service Manager server. |
| Actual End Time | (Optional) Enter the actual end DateTime of the change request that you want to update for closure in the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"SubClosureCode": "",
"Change": {
"close": {
"ClosureCode": "",
"ClosingComments": []
},
"header": {
"Open": "",
"Phase": "",
"Title": "",
"Reason": "",
"Status": "",
"Company": "",
"Category": "",
"ChangeID": "",
"CloseTime": "",
"PlannedEnd": "",
"ChangeModel": "",
"DateEntered": "",
"InitiatedBy": "",
"Subcategory": "",
"PlannedStart": "",
"ApprovalStatus": "",
"AssignmentGroup": "",
"ChangeCoordinator": ""
},
"middle": {},
"Service": "",
"CustomerVisible": "",
"description.structure": {
"Description": []
},
"OoredooChangeOriginator": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| Title or Brief Description | Title or brief description of the Request Fulfillment Ticket (RF) that you want to create on the Micro Focus Service Manager server. |
| Description | Description of the Request Fulfillment Ticket (RF) that you want to create on the Micro Focus Service Manager server. |
| Category | Category to be assigned to the RF that you want to create on the Micro Focus Service Manager server. |
| Subcategory | Subcategory to be assigned to the RF that you want to create on the Micro Focus Service Manager server. |
| Assigned To | Name of the user to whom you want to assign the RF that you want to create on the Micro Focus Service Manager server. |
| Assigned Group | The ID of the group to which you want to assign the RF that you want to create on the Micro Focus Service Manager server |
| Impact | Impact number to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, 4 is 'No Service Impact'. |
| Priority | Priority value to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, 4 is 'Low'. |
| Urgency | Urgency value to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, 4 is 'Low'. |
| Product Type | Product Type to be assigned to the RF that you want to create on the Micro Focus Service Manager server. For example, other. |
| Requester Name | Name of the Requester, who has raised the RF that you want to create on the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Request": {
"Open": "",
"Impact": "",
"Number": "",
"Status": "",
"Urgency": "",
"Category": "",
"Priority": "",
"SlaBreach": "",
"AssignedTo": "",
"SubmitDate": "",
"UpdateDate": "",
"CustVisible": "",
"Description": [],
"ProductType": "",
"Subcategory": "",
"AgreementIds": [],
"CurrentPhase": "",
"DeliveryDate": "",
"AssignedGroup": "",
"RequestorName": "",
"ApprovalStatus": "",
"BriefDescription": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| RF - Request Fulfillment Ticket Number | The ID of the Request Fulfillment Ticket whose details you want to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Request": {
"Open": "",
"Impact": "",
"Number": "",
"Status": "",
"Urgency": "",
"Category": "",
"Priority": "",
"SlaBreach": "",
"AssignedTo": "",
"SubmitDate": "",
"UpdateDate": "",
"CustVisible": "",
"Description": [],
"ProductType": "",
"Subcategory": "",
"AgreementIds": [],
"CurrentPhase": "",
"DeliveryDate": "",
"AssignedGroup": "",
"RequestorName": "",
"ApprovalStatus": "",
"BriefDescription": ""
},
"Messages": [],
"ReturnCode": ""
}
| Parameter | Description |
|---|---|
| RF-Request Fulfillment Ticket ID | The ID of the Request Fulfillment Ticket to which you want to add the attachment in the Micro Focus Service Manager server. |
| Attachment Name | The name of the attachment name that you want to add to the specified RF in the Micro Focus Service Manager server. |
| Message Body | The content of the file to be uploaded to the specified RF in the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"Messages": [],
"ReturnCode": "",
"ResourceName": "",
"content": []
}
| Parameter | Description |
|---|---|
| Incident ID | Specify the incident ID whose details to retrieve from the Micro Focus Service Manager server. |
The output contains the following populated JSON schema:
{
"@count": "",
"@start": "",
"@totalcount": "",
"Messages": [],
"ResourceName": "",
"ReturnCode": "",
"content": []
}
| Parameter | Description |
|---|---|
| Incident ID | Specify the incident ID associated with the attachment to download from the Micro Focus Service Manager server. |
| Attachment ID | Specify the attachment ID associated with the attachment to download from the Micro Focus Service Manager server. |
No output schema is available at this time.
| Parameter | Description |
|---|---|
| Incident ID | Specify the incident ID associated with the attachment to delete from the Micro Focus Service Manager server. |
| Attachment ID | Specify the attachment ID associated with the attachment to delete from the Micro Focus Service Manager server. |
No output schema is available at this time.
The Sample - Micro Focus Service Manager - 1.4.0 playbook collection comes bundled with the Micro Focus Service Manager connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Micro Focus Service Manager connector.
Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during the connector upgrade and delete.