User scenarios and associated actions

Brokering TC1 - Create Brokered Incident [Monitor qualifying incidents in ITSM and create in Multi-cloud for Incident Brokering]

1. Initialization step
   1. Login to Smart IT and Salesforce portal. 
2. Transaction steps
   1. Create New Incident in Smart IT using Service Cloud.
   2. Access this Incident and check whether HTTP response contains string brokerVendorName with Cloud.
   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 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

   1. Logout from Smart IT and Salesforce .

      Note

      This script creates a data file with linked case number from Salesforce and the incident number from Smart IT.

Brokering TC2 - Create Incident Activity Note with Author

1. Initialization step
   1. Login to Smart IT and the Salesforce portal. 
2. Transaction steps 
   1. Select Random Incident number from data file. [ Data file contains 1000+ incident numbers  of Smart IT and related case number of Salesforce ]
   2. Do a global search in Smart IT and fetch incident details.
   3. Add activity notes in given incident with unique string and timestamp in Smart IT.  
   4. Search related case number in Salesforce.
   5. Access case's notes section in salesforce
   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 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
   1. Logout from Smart IT and Salesforce. 

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

1. Initialization step
   1. Login to Smart IT and Salesforce portal. 
2. Transaction steps
   1. Select Random Case number from data file. [ Data file contains 1000 incident numbers  of Smart IT and related case number of Salesforce ]
   2. Search this case number in Salesforce and fetch its details.
   3. Add comments in given case with unique string and timestamp in Salesforce.
   4. Also Edit Description of given case with unique string and timestamp in Salesforce. 
   5. Do a global search of related incident number in Smart IT. 
   6. Access comment section of incident in Smart IT and description from mcsm call in Smart IT. 
   7. Check if response in comment section of Smart IT and description from mcsm call in Smart IT 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 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 Smart IT and Salesforce.

Brokering TC5 - Create Brokered Incident [Monitor qualifying incidents in ITSM and create in Multi-cloud for Incident Brokering]

1. Initialization step: Login to Smart IT of Customer ITSM portal. 
2. Transaction steps
   1. Create New Incident in Smart IT using " Email "  
   2. Access this Incident and check whether HTTP response contains string "brokerVendorName" with "ITSM"
   3. If response does not contain 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 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 Customer Smart IT.

   Note

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

DevOps TC1 - Create Change  - JIRA to Smart IT [Create a change in ITSM when Multi-cloud has received a qualifying Issue from Dev Tool]

1. Initialization step: Login to Smart IT 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 inSmart IT. 
   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 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 Smart IT and JIRA portal.  

   Note

   This script creates a data file with linked issue number from JIRA and Change Request number from Smart IT.

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

ITSM and create in Multi-Cloud for DevOps Integration]

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps 
   1. Select Random Change Request number from data file. [ Data file contains 1000 Change Request numbers  of Smart IT and related Issue number of JIRA ]
   2. Do a global search in Smart IT and fetch Change Request details.
   3. Add activity notes in given Change with unique string and timestamp in Smart IT.  
   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 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 Smart IT and JIRA. 

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

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps 
   1. Select Random Case number from data file. [ Data file contains 1000 Change Request numbers  of Smart IT 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 Smart IT. 
   6. Access comment section of change request in Smart IT and description from mcsm call in Smart IT. 
   7. Check if response in comment section of Smart IT and description from mcsm call in Smart IT 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 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 Smart IT and JIRA.

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

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps
   1. Create New Incident in Smart IT 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 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 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 Smart IT and JIRA.

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

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps
   1. Create New Change in Smart IT and Low Priority with   operation category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains 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 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 next iteration.
3. End step: Logout from Smart IT and JIRA.

DevOps TC7- Create Incident- JIRA to Smart IT [Create a Incident in ITSM when Multi-cloud has received a qualifying Issue from Dev Tool]

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps 
   1. Create 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 Smart IT. 
   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 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 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 Smart IT and JIRA portal.  

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

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps
   1. Create New Problem in Smart IT and Low Priority with  operational category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains 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 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 Smart IT and JIRA.

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

1. Initialization step: Login to Smart IT 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 Smart IT and fetch Problem details.
   3. Add activity notes in given Problem with unique string and timestamp in Smart IT.  
   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 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 Smart IT and JIRA. 

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

1. Initialization step: Login to Smart IT and JIRA portal. 
2. Transaction steps
   1. Create New WorkOrder in Smart IT and Low Priority with  operational category as Request → JIRA → Story
   2. Access this Incident and check whether HTTP response contains 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 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 Smart IT and JIRA.

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

1. Initialization step: Login to Smart IT 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 Smart IT and fetch WorkOrder details.
   3. Add activity notes in given WorkOrder with unique string and timestamp in Smart IT.  
   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 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 Smart IT and JIRA. 

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

1. Initialization step: Login to Smart IT 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 Smart IT. 
   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 transaction as FAIL and proceed with step a for next iteration. 
   5. Validation is successful, then it will do a global search in Smart IT 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 Smart IT and JIRA portal. 

Ticket Consolidation TC1 - Create Incident from Vendor ITSM -  [Create a Incident in Customer ITSM when Multi-cloud has received a qualifying incident from Vendor ITSM ]

1. Initialization step: Login to Vendor & Customer Smart IT portal. 
2. Transaction steps 
   1.  Create New Incident in Smart IT of Vendor ITSM along with operation category as Request → ITSM → Incident 
   2.  Access this incident and check whether HTTP response contains label with string "vendorTicketNumber".  "vendorTicketNumber"  indicates this corresponding incident is created in customer Smart IT. 
   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 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 Smart IT of vendor & customer portal.  

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

1. Initialization step: Login to Vendor and Customer Smart IT portal. 
2. Transaction steps 
   1. Select Random Incident number from data file. [ Data file contains 1000 Incident numbers  of Vendor Smart IT and related incident number of Customer ITSM]
   2. Search this Incident number in Smart IT and fetch its details.
   3. Add comments in given Incident with unique string and timestamp in Vendor Smart IT.
   4. Also Edit Description of given Incident with unique string and timestamp in Vendor Smart IT. 
   5. Do a global search of related Incident number in Customer Smart IT. 
   6. Access comment section of Incident number in Customer Smart IT and description from mcsm call in Customer Smart IT. 
   7. Check if response in comment section of Smart IT and description from mcsm call in Smart IT 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 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 Smart IT of vendor & customer portal.