User scenarios and associated actions

Brokering TC1 - Create Brokered Incident [Monitor qualifying incidents in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for Incident Brokering]

1. Initialization step: Login to  BMC Helix ITSM  and Salesforce portal. 
2. Transaction steps:
   1. Create a new BMC Helix ITSM incident in BMC Helix ITSM using Service Cloud.
   2. Access this Incident and check if the HTTP response contains the string brokerVendorName with Cloud.

   3. If the response does not contain the expected string, repeat steps a and b for every 30 seconds interval.

      The validation process will go on for a maximum of 6 minutes.

      • If the validation process does not return the expected string, then it will mark the transaction as FAIL  and proceed with Step 1 for the next iteration.
      • If validation is successful, then it will get incident details using the BMC Helix Multi-Cloud Broker HTTP call. Transaction will be marked as PASS and proceed with Step 1 for the next iteration.

3. End step: Logout from BMC Helix ITSM  and Salesforce .

   Important

   This script creates a data file with a linked Salesforce case number and the BMC Helix ITSM incident number.

Brokering TC2 - Create Incident Activity Note with Author

1. Initialization step: Login to BMC Helix ITSM and the Salesforce portal. 
2. Transaction steps 
   1. Select a Random Incident number from the data file. [Data file contains 1000+ incident numbers  of BMC Helix ITSM and related case numbers of Salesforce]
   2. Do a global search in BMC Helix ITSM and fetch incident details.
   3. Add activity notes in a given incident with a unique string and timestamp in BMC Helix ITSM.  
   4. Search related case numbers in Salesforce.
   5. Access the case's notes section in Salesforce
   6. Check if the response in the notes contains a unique string. If the response does not contain the expected string then repeat step e and f for every 30 seconds interval. 
   7. The validation process will go on for a maximum of 6 mins, if it does not return the expected string then it will mark the transaction as FAIL and proceed with step a for the next iteration. 
   8. If validation is successful, then the transaction will be marked as PASS and proceed with step A for the next iteration.
3. End step
   1. Logout from BMC Helix ITSM and Salesforce. 

Brokering TC3 (Sync Service Cloud Case Comment )  and Brokering TC4 (Sync Service Cloud Case )

1. Initialization step: Login to BMC Helix ITSM and Salesforce portal. 
2. Transaction steps
   1. Select a random case number from the data file.
      The data file contains 1000+ BMC Helix ITSM incident numbers and related Salesforce case numbers.
   2. Search this case number in Salesforce and fetch its details.
   3. Add comments in the given case with a unique string and timestamp in Salesforce.
   4. Edit the Description of the given case with a unique string and timestamp in Salesforce. 
   5. Do a global search of related incident number in BMC Helix ITSM. 
   6. Access the comment section of the ITSM incident and Description from the BMC Helix Multi-Cloud Broker call in BMC Helix ITSM. 
   7. Check if the response in the comment section of BMC Helix ITSM and description from the mcsm call in BMC Helix ITSM contains a unique string. If the response does not contain the expected string then repeat steps f and g for every 30 seconds interval. 
   8. The validation process will go on for a maximum of 6 mins, if it does not return the expected string then it will mark the transaction as FAIL and proceed with step a for the next iteration. 
   9. If validation is successful, then the transaction will be marked as PASS and proceed with step A for the next iteration.
3. End step: Logout from BMC Helix ITSM and Salesforce.

Brokering TC5 - Create Brokered Incident [Monitor qualifying incidents in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker  for Incident Brokering]

1. Initialization step: Login to BMC Helix ITSM of the Customer ITSM portal. 
2. Transaction steps
   1. Create a new Incident in BMC Helix ITSM using " Email ".
   2. Access this incident and check whether the HTTP response contains the string " brokerVendorName " with "ITSM"
   3. If the response does not contain the expected string, repeat steps b and c for every 30 seconds interval. 
   4. The validation process will go on for a maximum of 6 mins, if it does not return the expected string then it will mark the transaction as FAIL and proceed with step a for the next iteration. 
   5. If validation is successful, then it will get incident details using mcsm HTTP call. Transaction will be marked as  PASS  and proceed with step A for the next iteration.

3. End step: Logout from Customer BMC Helix ITSM.

   Note

   This script creates a data file with a linked incident number from Vendor BMC Helix ITSM and the incident number from Customer BMC Helix ITSM.

DevOps TC1 - Create Change  - JIRA to BMC Helix ITSM [Create a change in BMC Helix ITSM when BMC Helix Multi-Cloud Broker has received a qualifying Issue from Dev Tool]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps
   1. Create New issue with type " Story " in JIRA with " Highest "  priority.  
   2.  Access this issue and check whether HTTP response contains label with string "CRQ".  "CRQ"  indicates this corresponding change request is created inBMC Helix ITSM. 
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteratoin. 
   5. validation is successful , then it will do a global search in Smart IT with CRQ number and fetch details of change request. Also fetch change request details using mcsm HTTP call . Transaction will be marked as  PASS  and proceed with step a for next iteration.

3. End step: Logout from BMC Helix ITSM and JIRA portal.  

   Note

   This script creates a data file with linked issue number from JIRA and Change Request number from BMC Helix ITSM.

DevOps TC2 - Create Change Activity Note with Author [Monitor qualifying activity notes (worklogs) on change records in

BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps 
   1. Select Random Change Request number from data file. [ Data file contains 1000 Change Request numbers  of BMC Helix ITSM and related Issue number of JIRA ]
   2. Do a global search in BMC Helix ITSM and fetch Change Request details.
   3. Add activity notes in given Change with unique string and timestamp in BMC Helix ITSM.  
   4. Search related Issue number in JIRA.
   5. Access Issue details in JIRA
   6. Check if response in notes contains unique string. If response does not contain expected string  then repeat  step e and f for every 30 seconds interval. 
   7. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   8. If validation is successful , then transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA. 

DevOps TC3 (Sync JIRA Issue Comment)  and DevOpsTC4 (Sync JIRA Issue )

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps 
   1. Select Random Case number from data file. [ Data file contains 1000 Change Request numbers  of BMC Helix ITSM and related Issue number of JIRA]
   2. Search this Issue number in JIRA and fetch its details.
   3. Add comments in given issue with unique string and timestamp in JIRA.
   4. Also Edit Description of given issue with unique string and timestamp in JIRA. 
   5. Do a global search of related change request number in BMC Helix ITSM. 
   6. Access comment section of change request in BMC Helix ITSM and description from mcsm call in BMC Helix ITSM. 
   7. Check if response in comment section of Smart IT and description from mcsm call in BMC Helix ITSM contains unique string. If response does not contain expected string  then repeat  step f and g for every 30 seconds interval. 
   8. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   9. If validation is successful , then transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA.

DevOps TC5 - Create DevOps Incident [Monitor qualifying incidents in ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps
   1. Create New Incident in BMC Helix ITSM and mark its status as " Resolved "  with reason " Future Enhancement " along with resolving operation category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains the string " brokerVendorName " with " JIRA "
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   5. If validation is successful , then it will get incident details using mcsm HTTP call . Transaction will be marked as  PASS  and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA.

DevOps TC6 - Create DevOps Change [Monitor qualifying Change Records in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps
   1. Create New Change in BMC Helix ITSM and Low Priority with   operation category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains the string " brokerVendorName " with " JIRA "
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   5. If validation is successful , then it will get Change details using mcsm HTTP call . Transaction will be marked as  PASS  and proceed with step A for the next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA.

DevOps TC7- Create Incident- JIRA to BMC Helix ITSM [Create a Incident in BMC Helix ITSM when BMC Helix Multi-Cloud Broker has received a qualifying Issue from Dev Tool]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps 
   1. Create a New issue with type " Bug " in JIRA with " Medium "  priority.  
   2.  Access this issue and check whether HTTP response contains label with string "INC".  "INC"  indicates this corresponding change request is created in BMC Helix ITSM. 
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteratoin. 
   5. Validation is successful, then it will do a global search in BMC Helix ITSM with INC number and fetch details of Incident number. Also fetch incident number details using mcsm HTTP call . Transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA portal.  

DevOps TC8 - Create DevOps Problem [Monitor qualifying Problem Records in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps
   1. Create New Problem in BMC Helix ITSM and Low Priority with  operational category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains the string " brokerVendorName " with " JIRA "
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   5. If validation is successful, then it will get problem details using mcsm HTTP call . Transaction will be marked as  PASS  and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA.

DevOps TC9 - Create Problem Activity Note with Author [Monitor qualifying activity notes (worklogs) on problem records in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps 
   1. Select Random Problem number from data file. [ Data file contains 1000 Problem numbers  of Smart IT and related Issue number of JIRA ]
   2. Do a global search in BMC Helix ITSM and fetch Problem details.
   3. Add activity notes in given Problem with unique string and timestamp in BMC Helix ITSM.  
   4. Search related Issue number in JIRA.
   5. Access Issue details in JIRA
   6. Check if response in notes contains unique string. If response does not contain expected string  then repeat  step e and f for every 30 seconds interval. 
   7. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   8. If validation is successful , then transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA. 

DevOps TC10 - Create DevOps WorkOrder [Monitor qualifying WorkOrder Records in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps
   1. Create New WorkOrder in BMC Helix ITSM and Low Priority with  operational category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains the string " brokerVendorName " with " JIRA "
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteratoin. 
   5. If validation is successful , then it will get WorkOrder details using mcsm HTTP call . Transaction will be marked as  PASS  and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA.

DevOps TC11 - Create Work Order Activity Note with Author [Monitor qualifying activity notes (worklogs) on WorkOrder records in BMC Helix ITSM and create in BMC Helix Multi-Cloud Broker for DevOps Integration]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps 
   1. Select Random WorkOrder number from data file. [ Data file contains 1000 WorkOrder numbers  of Smart IT and related Issue number of JIRA ]
   2. Do a global search in BMC Helix ITSM and fetch WorkOrder details.
   3. Add activity notes in given WorkOrder with unique string and timestamp in BMC Helix ITSM.  
   4. Search related Issue number in JIRA.
   5. Access Issue details in JIRA
   6. Check if response in notes contains unique string. If response does not contain expected string  then repeat  step e and f for every 30 seconds interval. 
   7. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   8. If validation is successful , then transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA. 

DevOps TC12 - Create WorkOrder  - JIRA to Smart IT [Create a WorkOrder in BMC Helix ITSM when BMC Helix Multi-Cloud Broker has received a qualifying Issue from Dev Tool]

1. Initialization step: Login to BMC Helix ITSM and JIRA portal. 
2. Transaction steps
   1. Create New issue with type " bug " in JIRA with " Low "  priority.  
   2.  Access this issue and check whether HTTP response contains label with string "WO".  "WO"  indicates this corresponding WorkOrder is created in BMC Helix ITSM. 
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   5. Validation is successful, then it will do a global search in BMC Helix ITSM with WO number and fetch details of change request. Also fetch change request details using mcsm HTTP call . Transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM and JIRA portal. 

Ticket Consolidation TC1 - Create Incident from Vendor BMC Helix ITSM -  [Create an Incident in Customer BMC Helix ITSM when BMC Helix Multi-Cloud Broker has received a qualifying incident from Vendor BMC Helix ITSM ]

1. Initialization step: Login to Vendor and Customer BMC Helix ITSM portal. 
2. Transaction steps 
   1.  Create New Incident in BMC Helix ITSM of Vendor BMC Helix ITSM along with operation category as Request → ITSM → Incident 
   2.  Access this incident and check whether HTTP response contains a label with the string " vendorTicketNumber ".  " vendorTicketNumber "  indicates this corresponding incident is created in customer BMC Helix ITSM. 
   3. If response does not contains expected string, repeat step b and c for every 30 seconds interval. 
   4. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL  and proceed with step a for next iteration. 
   5. Validation is successful , then transaction will be marked as  PASS and proceed with step a for next iteration.
3. End step: Logout from BMC Helix ITSM of vendor and customer portal.  

Ticket Consolidation TC3 (Sync Vendor BMC Helix ITSM Incident Worklog )  and Ticket Consolidation TC4 (Sync Vendor BMC Helix ITSM Incident )

1. Initialization step: Login to Vendor and Customer BMC Helix ITSM portal. 
2. Transaction steps 
   1. Select Random Incident number from data file. [ Data file contains 1000 Incident numbers  of Vendor BMC Helix ITSM and related incident number of Customer BMC Helix ITSM]
   2. Search this Incident number in BMC Helix ITSM and fetch its details.
   3. Add comments in given Incident with unique string and timestamp in Vendor BMC Helix ITSM.
   4. Also Edit Description of given Incident with unique string and timestamp in Vendor BMC Helix ITSM. 
   5. Do a global search of related Incident number in Customer BMC Helix ITSM. 
   6. Access comment section of Incident number in Customer BMC Helix ITSM and description from mcsm call in Customer BMC Helix ITSM. 
   7. Check if response in comment section of BMC Helix ITSM and description from mcsm call in BMC Helix ITSM contains unique string. If response does not contain expected string  then repeat  step f and g for every 30 seconds interval. 
   8. Validation process will go on for maximum 6 mins , if it does not return expected string then it will mark the transaction as  FAIL and proceed with step a for next iteration. 
   9. If validation is successful, then the transaction will be marked as  PASS  and proceed with step A for the next iteration.
3. End step: Logout from BMC Helix ITSM of vendor and customer portal.