YPM-105 - Getting issue details... STATUS

YPM-105 Onboarding flow Successfactors - AD

SD-47281 - Getting issue details... STATUS

SD-47284 - Getting issue details... STATUS

Onboarding

Onboarding procedure in Jira

1. Onboarding ticket is created by HR, reporter = HR-Jira@yamaha-motor.eu [YME HR]
2. After creation ticket will be transitioned to status Awaiting assignment
3. SD-agent allocates ticket via button to him/herself
4. SD-agent set issue to  
   After transitioning the Onboarding ticket to status In Progress the Onboarding form will automatically being attached.
   Please make sure you have the Forms tab open to view the form
   
   
   The form is directly visible in the custor portal.
   
   
5. SD-agent adds Manager of the new user as Requested participant
   1. Add in the comment section a canned response and adjust the information between brackets[ ]
   2. Then click on Share with Customer to send the message.
      
      
      
      
6. Manager receives a notification via e-mail.
   For the manager it will look like below in the Customer portal:
   
7. Manager action:
   1. Manager saves and submit form in customer portal
      
      The form will be locked for editing. Printscreen from original onboarding ticket
      
   2. Form will be attached as PDF. This PDF file is not visible in the customer portal, only in the original ticket for SD-agents.
      
8. Sub-task and Onboarding can be requested according to selection made in the Onboarding Form.
9. After all linked Sub-task and tasks are completed the Onboarding ticket can be closed by the SD-Agent.
   1. Use a canned response:

Sub-Tasks

For internal action by IT department(s) a Sub-Task can be created via the original Onboarding ticket. This is automatically done by selecting the appropriate transition.

       Status:                                                     Transition:

Transitions are visible in the Onboarding ticket via the  (workflow)buttons

After a Subtask transition is triggered in the original Onboarding ticket the status is changed to Onboarding XXXXXXX
This status change is visible in the Customer Portal:
Example:

After the Sub-Task creation the original SD ticket automatically transitions back to In Progress.
This status change also reflects in the customer portal:
Example:

All requested Sub-Tasks can be found under Sub-Task section in the original Onboarding ticket

Status of Sub-Task can easily being tracked in original  Onboarding ticket.
If a Sub-Task is completed it will look as follow in the original ticket.

Sub- Task workflow and procedure

1. Status To Do: SD-Agent assigns ticket to himself/herself
2. Requested action is being executed by SD- agent
3. Request is closed, comment screen will pop up for final comment
   1. Approval: add approved comment
   2. Execution granting rights or Ympact : add screenshots for evidence collection J-sox, see .......

No action needed, select canceled and provide reason for cancelation.

A Sub-Task ticket is a internal task which is not visible in the Customer portal. For this reason there is no match with the (customer) request type in the customer portal.

Onboarding Ympact - Req. Ympact

1. Select Internal comment
2. Type comment: Ympact: copy [ example user ]to [ New user]  
3. Select Req. Ympact

Status of Onboarding ticket temporary changes to After ticket is created it will automatically transitions back to

This option triggers a subtask


All attachments and onboarding form from original ticket are copied to the subtask:

Description:
Please grand the new AS400 user the requested BPCS environment(s) authorization.

Added directly from last comment original Onboarding ticket
Ympact: YMETST to YMETSTNEW1

Task 

For non-internal action by divisions/departments other than Information Systems a Task can be created via the original Onboarding ticket. This is automatically done by selecting the appropriate transition.

Status:                                                     Transition:

Transitions are visible in the Onboarding ticket via the  (workflow)buttons

Req. Facility

After a Subtask transition is triggered in the original Onboarding ticket the status is changed to Onboarding XXXXXXX

This status change is visible in the Customer Portal:

After the Sub-Task creation the original SD ticket automatically transitions back to In Progress.
This status change also reflects in the customer portal:
Example:

All requested Tasks can be found under Issue Links section in the original Onboarding ticket

Task workflow and procedure

1. Status To Do: Assignee is automatically set , same as person who takes care of Original Onboarding ticket.
2. Facility/Reception informs via comment in customer portal what action has been taken: Provided Batch, Keys, Desk
3. Assignee received comment notification via e-mail
4. SD-Agent closes ticket via Done

No action needed, select canceled and provide reason for cancelation.

A Task is visible in the Customer portal 

Onboarding Form

The Onboarding form has been setup in Pro Forma Forms. If it is not working properly please reach out to Bregje Mank, Daan Libeton, Jira administrator.

A open form always needs to be saved and submitted.

After Save and Submit or pressing Submit button in the form a Confirm screen will pop up.
Select Submit to finalize the Onboarding Form.

Automatically the form is being attached to the Ticket.

Form will also being attached as PDF. This PDF file is not visible in the customer portal, only in the original ticket for SD-agents.

Re-open locked form

If needed form can be re-opened by SD-agents.

1. Select Reopen
   
2. Confirm Reopen
   
3. Form can be adjusted by reporter and requested participants or by SD-agent.
4. Save changes by pressing submit
5. Confirm submit
   
6. A new PDF file will be attached with the form. See date/time stamp for form version. This PDF file is not visible in the customer portal.