Recognize
DLH.io documentation for Recognize
Recognize is an employee recognition and rewards platform. Replicating it into your data cloud lets people analytics teams measure recognition activity, badges, teams and reward redemptions alongside HR and engagement data.
Setup Instructions
Follow the setup steps guide for configuring your Recognize connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Recent recognitions are re-read |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | Not captured automatically (use a historical re-sync) | |
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
This connection is read only and never writes data back to Recognize. Be sure to also check the change log and notes page from time to time for any changes.
- Recognize offers no way to ask only for changed records, so users, teams, badges, announcements, tasks, catalogs and redemptions are read in full on every run.
- Recognitions are read newest first. The first synchronization reads the full history (or starts at the Historical Start Date if set), and later runs read back to four days before the previous run, which also picks up comments and likes added in that time.
- A comment or like added to an older recognition, and anything deleted in Recognize, is picked up by a historical re-sync.
- Disabled users are not returned by Recognize.
- DLH.io reads data as the company admin whose email you enter, so private recognitions are included only when that admin can see them.
Issue Handling
If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.
Replicated Entities
The following 12 entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:
USERSUSER_TEAMSTEAMSRECOGNITIONSRECOGNITION_RECIPIENTSRECOGNITION_COMMENTSRECOGNITION_APPROVALSBADGESANNOUNCEMENTSTASKSCATALOGSREDEMPTIONS
Schema Details (ER Diagram)
This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.