SAP Knowledge Base Article - Public

2076141 - Launching Forms - Testing a new or updated Performance Form template - Performance Management

Symptom

  • This article provides a testing strategy when adding or updating a Performance Form template.
  • What testing should I conduct when modifying or creating a Performance Form template?

Environment

  • Performance Management

 

Resolution

  • These are common test scenarios to help ensure your Performance form is configured as expected.  For each item, are the results what you intended?  If not, adjustments may be needed. While not all of these scenarios may apply to your process, evaluating each item will help ensure your users do not have unexpected access or limitations.
  • Please also see our main Admin Guide to Testing a New Process 101

 

General Form Testing:

  1. Create a form for a test user via Admin Tools > Performance Management > Launch Form.
  2. Launch it to a test user with complete hierarchy a.k.a. has a user for each role in the route map thus creating the first requirement:
    1. copy template named ______, rename the copy to be ______ and make changes on the copy
  3. Proxy as the test user who currently has the form in their Inbox.
  4. Fill out the form and then click Save & Close. Did the form behave the way you want it to?
  5. Send the form to the next recipient.  Have you set any required fields in the form?  If so, try sending the form to the next step without meeting the requirements.  Do you receive a warning as designed?
  6. Once the form has been sent to the next recipient, Proxy as that user.
  7. Fill out the form and then click Save & Close. Did the form behave the way you want it to?
  8. Proxy as the first test user again.  Open the form from the En Route folder.  Can you see what is intended and not see additional information you don’t want visible from the En Route folder?
  9. Proxy again as the second recipient and send the form forward.  Repeat these steps through the planned routing of the form to ensure the form behaves as expected at each step.
  10. Once the form is completed, find the form in the completed folder for each user who receives it. Can each role see what is expected?
  11. While sending the form from user to user, take thorough notes on what needs to be changed using this format:
    1. on template named _____, in section named ______, _which role(s)_ should/should not be able to __do what?__
  12. If you have any downstream processes that rely on the ratings and information in the form, ensure that this information, particularly ratings, flows to those areas properly, such as Calibration, Compensation, Employee Profile and Reports.  Is the information accurate?
  13. If your testing has occurred in a test/staging instance, be sure to test again thoroughly in your Production instance.  Form Template Settings and Route Maps and Competency Libraries may differ between instances which can lead to different results.

 

 

Specific Elements to Test

1. Competencies

If competencies are populated by job code, make sure different roles have forms that look different. For example, engineer competencies should appear on an engineer's form and administrator competencies should appear on an administrator's form.  If you have any new Job Codes, be sure to map competencies to these roles prior to launching the forms.

If your competencies are hard-coded onto the form, ensure none of those competencies have been deleted from your Competency Library.  Invalid competency IDs in the form can cause an error when launching.

 

2. Goals/Objectives:

Add goals to the form, whether through the goal plan or directly to the form.  Do all of the desired fields appear on the form?  Is the goal information accurately reflected in the form and in the goal plan?  If you’ve copied the form template from a previous year, check that the goals on the new form are from the correct goal plan and not an old goal plan.

 

3. Button and Form Labels:

Ensure that the labels are what you expect for the form fields and buttons as well as the information displayed as you route a form.

 

4. Route Maps:

If your only changes are to route maps (reusing a previous form template), ensure that the form’s permissions allow for the desired view and edit access at the new route steps.  The steps outlined above for general testing should identify any issues with permissions.

 

5. Languages:

If your forms are multi-lingual (users with different languages see translated versions of the form), test the forms for each language to ensure the translated view is correct.  This can be especially important if you’ve added new fields or sections to your form template

 

 

Tips to Ensure Form Launches Go Well:

  1. Do not launch forms to real users until you have thoroughly tested.
  2. Avoid launching forms with known configuration issues while assuming that you can fix those issues later.  It is best to delay the launch until the configuration issues are addressed.
  3. Do not add steps to your route map and assume forms will work the same.
  4. Do not delete competencies from your Competency Library without reviewing the form template.  Otherwise, your forms may not launch at all.
  5. Testing cannot be done in 5 minutes! Proper testing should take a few days and should include more than one tester.  Include someone who didn’t participate in the form design, they often catch errors that an administrator might miss.
  6. A test template cannot be put into production as the dependencies (competency ids, rating scale names, ...) are typically different from instance to instance.
  7. Don't go from your memory regarding last year's forms.
  8. Make sure to run your reports that will be created after going live.
  9. Route the forms to completion.
  10. It is safe to launch dummy forms in production as long as you launch to test users such as the alphabet people.
  11. Don't wait until the last minute to create your case.
  12. Changing requirements after work has started will lengthen the process.
  13. It is best to submit all (thorough) requirements at the start of the case.
  14. If there are route step changes, please create a new route map and link it to the template.
  15. When copying last year's form to create this year's form, last year's goal plan and/or dev plan will need to be swapped out for this year's goal plan and/or dev plan if there is a goal plan/dev plan section.

 

Downloadable Guide:

How to Test a New Form. Please feel free to download this guide. This document describes common elements of a new form template, and how a client can QA that form using test users before launching it to end users. How To QA Form Templates.docx

Keywords

KBA , LOD-SF-PM , Performance Management , How To

Product

SAP SuccessFactors HCM Core all versions

Attachments

How_To_QA_Form_Templates.docx