Introduction

This document describes how a robotjob (change) request can be created.

A Robotjob Ticket can be created via the following two options

• Automated: Out of an existing SD ticket (preferred)
• Manually: Via the Create button, via this way a ticket can directly be created for a RobotJob Change.
  (Only to be used if there is no ticket from where you need to record a robotjob change)

New Robotjob request out of an existing ticket

1. Open the ticket in the Yamaha Applications Support Desk
   
   
   
2. Select Workflow , then select Create Req Robotjob Approvalchange
   Image RemovedImage Added
3. It immediately creates a LINKED (implemented by) new ticket until status In Progress + the reporter and + assignee prefilled.
   Description will be copied from the original ticket.
   Press Create Robotjob Approval ticket.
   Image RemovedThe original ticket is updated to status: Image Added
   
   SD ticket status is updated to Pending linked Ticket Execution
   Image AddedAwaiting RobotJob approval.
   
   
   
4. Jump to the robotjob Robotjob ticket which can be found under Issue Links - Is implemented by section
   Image RemovedJump to the robotjob ticket
   Image RemovedImage Added
   
   
5. Complete the text in the description area 
   Image Removed Description area 
   Image Added
   
   
6. Make sure correct Solution group is set: 
   Business Applications (ITS Support) or Logistics Applications
   
   
7. Make sure correct Yamaha Team is set
   
   
8. Select correct Application- Module
   If module cannot be specified for SYS200/YLS this can be left blank
   Image Added
     Image Added
     Image Added
9. Press Req. SQL or RobotJob approval
   Image Added
   
   
10. Add a comment if needed, and press Req. SQL or Robotjob approval
    If a Robotjob change has already been applied then Retrospective approval? flag Yes need to be selected. Else this can be left empty. 
    Image Added
    
11. The original ticket is updated to status: Awaiting RobotJob approval.Press Req. SQL or RobotJob approval
    This invokes an approval request which is similar as an SQL approval, ticket status will be changed to Awaiting manager approval
    Image Added
    
    
    Image Added
    
    
12. Approver will see the approval
    Image Removedrequest via filter on dashboard:
    Image Added
    1. The approver should select
    : Approve RobotJob change to M42  The approval will be send to m42_AS400@yamaha-motor.nl^{Image Removed} having subject starting with [RBTJ]
    Image Removed
13. AS400 support reports back the results manually in the ticket by leaving a comment.
    Image Removed
14. 1. Approve Robot Job  if approved
       Image Added
       1. If Retrospective approval has been requested the flag will be set:
          Image Added
          
          
    2. If not approved, the approver adds a comment to the ticket, selects Workflow and Back in Progress
       Assignee repeats from step 5 or closes the issue with resolution Canceled.
       Image Added
15. 1. For Normal approval the ticket changes to status Awaiting Execution
       Image Added
       Automatically the following comment is added:
       Image Added
       
       
    2. For Retrospective approval the ticket will automatically closed and Step 14 and 15 will be skipped
       Image Added
       
       Automatically the following comment is added including the approvers name:
       Image Added
16. Ticket will appear in filter results
    1. For Ympact: on Infra AS400 dashboard: Infra Robotjob Change requests waiting for execution
       Image Added
    2. for YLS/SYS2000 on Project management Logistics dashboard: Logistics Applications Robotjob Change requests waiting for execution
       Image Added
       
       
17.  When done, AS400 support will close the ticket via the Resolve button, select resolution Done- Robotjob changes 
    Image Removed
    Image Removedand then Resolve
    For Ympact this is done by INFRA AS-400 support for Logistics applications support is is done by the person who has completed the RobotJob Change request.
    Image Added
    
    Image Added
    
    Image Added
    
    
18. Automatically the original (source) ticket is updated to status in progress + commented that the robotjob has been done.Progress , via Issue links it is visible that the linked ticket is closed.Image Added

New Robotjob ticket via Create button (non-preferred)

1. Via  Create button, select Issue Type RobotJob Change
   Note: This option is only available for users who are member of licensed group:  YMEUACJiraServiceDeskUsers.
   Image Modified
2. A new screen will be opened where you can enter the ticket details:
   a.
   1. Add text to the Summary, Description fields
   b.
   1. Select Solution group: Business Applications (ITS Support) or Logistics support
   c.
   1. Select Application Module:
   YMPACT
   d.
   1.   
      Image Added
        Image Added
        Image Added
   2. Select correct Team Yamaha
   3. If available include screenshots/attachments to the ticket
   e.
   1. Press Create button
      
   Image Removed
   1.   Image Added  Image Added
      
      
   1. The requester will receive a notification per mail with the ticket number or check the Queue for open tickets.
      Open the newly created for Type Robot Job Change ticket 
      Image Modified
      
      
   2. Allocate the ticket to yourself
      a. select assign
      
      1. Click on the Allocate button
         Image Added
      2. select Assign to me
         
      Image Removed
      1. Image Added 
         
         b. Click on the  Allocate button in the Allocate screen
         Image Modified
         
         
   3. Click on Start Progress
      Image Modified
      
      
   4. Complete the text in the Description area. Describe manually the change required for the RobotJob. There is no template text available when creating a ticket manually.
      Below text can be  used to copy-paste it in the description field. 
      
      

      ACTION:
      Change, Create, Remove, Hold, Release (choose the correct action) 

      Environment / Distributor (P=Process, N=No change)
      YBE : N YCZ : N YDE : N YES : N YFI : N YFR : N
      YHU : N YIT : N YLU : N YMA : N YME : N YNL : N
      YPL : N YPT : N YSC : N YSK : N YTR : N YUK : N

      JOB NAME:
      What should be the job name, which jobname does it concern?

      PROGRAM to be called:

      DEPENDENCIES:
      Indicate possible dependencies and inform how to mitigate them

      TIMING:
      Select the correct timing (SOD, EOD, EOM, SOM, special runtimes etc)
      
      

   5. Press Req. SQL or RobotJob approval
      Image Added
      
      
   6. Add a comment if needed, and press Req. SQL or Robotjob approval
      If a Robotjob change has already been applied then Retrospective approval? flag Yes need to be selected. Else this can be left empty. 
      Image Added
      
   7. The original ticket is updated to status: Awaiting RobotJob approval.
      
   8. Approver approves the Robotjob to M42
   9. This invokes an approval request which is similar as an SQL approval, ticket status will be changed to Awaiting manager approval
      Image Added
      
      
      Image Added
      
      
   10. Approver will see the approval request via filter on dashboard:
       Image Added
       1. The approver should select Approve Robot Job  if approved
          Image Added
          1. If Retrospective approval has been requested the flag will be set:
             Image Added
             
             
       2. If not approved, the approver adds a comment to the ticket, selects Workflow and Back in Progress
          Assignee repeats from step 5 or closes the issue with resolution Canceled.
          Image Added
          
          
   11. 1. For Normal approval the ticket changes to status Awaiting Execution
          Image Added
          Automatically the following comment is added:
          Image Added
          
          
       2. For Retrospective approval the ticket will automatically closed and Step 12 and 13 will be skipped
          Image Added
          
          Automatically the following comment is added including the approvers name:
          Image Added
          
          
          
   12. Ticket will appear in filter results
       1. For Ympact: on Infra AS400 dashboard: Infra Robotjob Change requests waiting for execution
          Image Added
       2. for YLS/SYS2000 on Project management Logistics dashboard: Logistics Applications Robotjob Change requests waiting for execution
          Image Added
          
          
   13.  When done, close the ticket via the Resolve button, select resolution Done- Robotjob changes  and then Resolve
       For Ympact this is done by INFRA AS-400 support for Logistics applications support is is done by the person who has completed the RobotJob Change request.
       Image Added
       
       Image Added
       
       Image AddedAS400 support resolves the ticket by entering the results and selecting the robotjob closure reason.