Processing and Setup Considerations

Review the following when configuring, awarding, and troubleshooting Digital Badges.

Note:

Digital Badges is supported beginning with PeopleTools 8.55. For administrators, the Recognition and Digital Badges tile on the Talent Administrator home page provides access to badge administration pages and related tasks. Employees can optionally add the View Digital Badges tile to the Employee Self Service home page to view their awarded badges.

To use the tiles and dashboard delivered for Digital Badges on the PeopleSoft landing page, PeopleTools 8.62 is required.

Awarding and processing behavior

  • Badges are awarded at the employee ID level, not the employee record level.
  • The "detected" recipient count shown when a badge award request is submitted on the Give a Badge page can differ from the final "awarded" count after the AE process completes, if the criteria type input includes duplicate employee IDs. Administrators can use the Process Scheduler logs (for example, View Log/Trace) or the View and Award Badges Page to confirm the final badge award results.

Badge status

  • Only active badges can be awarded.

  • A badge can still be awarded if its category or type is inactive, provided the badge itself is active.

    • If the current effective-dated type row is inactive, the badge appears only under All Badges on the View Digital Badges/Digital Badges page.
    • If the current effective-dated category row is inactive, the badge appears with no category.
  • Once a badge has been awarded, it remains visible to employees on the View Digital Badges page and administrators on the View and Award Badges page even if its status is later set to inactive. This ensures that earned badges continue to display for appreciation, regardless of subsequent status changes.

Badge visibility and deletion

  • Visibility: Administrators can view all unexpired badges on various view badge pages to which they have access. Non-administrator users in general can view all unexpired badges as well. The exception to this rule is when a badge is associated with a reported recognition that is hidden by an administrator.

  • Deletion: Administrators can remove badges using the View and Award Badges page.

    When a group badge is deleted, it will be deleted for all recipients.

    Deleting a badge does not remove an associated recognition. Deleting a recognition from Team Recognition removes both the recognition and any associated badge.

Badge setup

  • Avoid inactivating digital badge categories or types that are currently used in badge setup. Doing so can cause unexpected badge behavior (for example, awarding, filtering, or display issues).
  • Validate recipient populations. When preparing groups, queries, flat files, or application classes to determine recipients for badge assignment, ensure the results exclude employees who should not receive badges based on your company policy (for example, terminated employees or contingent workers).
  • If you wish to prevent administrators from manually awarding badges to contingent workers, configure the person selector for the Select Recipients criteria type on the Give a Badge page to exclude contingent workers (using Configure Simple Person Search). Similarly, use Direct Reports Transaction Configuration to control whether contingent workers are included as team members when managers award badges through Team Recognition.
  • Avoid unintended badge awards. When you write an application class to award a badge, include eligibility and duplicate-check logic that aligns to the badge's intended behavior. For badges intended to be awarded only once per recipient (for example, a 10-year service award), verify whether the recipient already has the badge and skip awarding it again on subsequent runs. For repeatable badges (for example, recognition or volunteer event badges), allow multiple awards only when a new, valid trigger occurs, and prevent duplicate awards for the same event or transaction.
  • Do not mix automatic and manual awards without a plan. For example, if you use event processing for automatic awards (for example, license or honor award badges), avoid also awarding the same badge manually using the Give a Badge page, except for controlled baseline scenarios (for example, initial license/certification population).
  • Use separate badge IDs for recurring programs. For badges awarded on a regular schedule (for example, annual compliance training), create a new badge ID for each award cycle instead of adding effective-dated rows. This approach supports cleaner implementation and simplifies troubleshooting.

User Interface

Page layout and visual appearance may vary slightly depending on the browser and browser version used.