Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  WFM Time-Off HRIS Integration Does Not Expose timeOffRequestId Needed for PTO Audit Trail

    Posted yesterday
    Edited by MANERI MANOJ yesterday

    Hello Genesys Community,

    We are working with the Genesys Cloud WFM Time-Off HRIS Integration and have encountered a challenge related to PTO auditing and compliance requirements.

    Genesys Support confirmed that the Time-Off Request Details API provides the information we need, including:

    • Submitted By
    • Submitted Date
    • Reviewed/Approved By
    • Modified By
    • Modified Date

    However, the API requires a timeOffRequestId:

    HTTP

    GET /api/v2/workforcemanagement/managementunits/{managementUnitId}/users/{userId}/timeoffrequests/{timeOffRequestId}

    Show more lines

    The Challenge

    Within the HRIS integration setup, we are only able to provide:

    • managementUnitId
    • userId

    These are static values associated with an agent and can be configured once.

    The missing piece is the timeOffRequestId, which is dynamically generated for every PTO request. Since this ID is not exposed within the integration workflow or payload, there is no way for downstream systems to call the Time-Off Request API and retrieve the audit information for the specific request being processed.

    Business Impact

    Although the audit information exists in Genesys Cloud, we cannot retrieve or persist:

    • Who submitted the PTO request
    • Who approved/reviewed the PTO request
    • Submission timestamp
    • Approval/review timestamp

    These fields are required for:

    • Compliance audits
    • Employee dispute resolution
    • Payroll investigations
    • Historical approval tracking

    Questions

    1. Is there any supported method to obtain the timeOffRequestId during HRIS integration processing?
    2. Is it available through data mappings, triggers, events, notifications, or another API?
    3. Has anyone implemented a workaround to associate a PTO transaction with its corresponding timeOffRequestId?
    4. Is there a roadmap item to expose timeOffRequestId within WFM HRIS integrations?


    #Architect
    #DataActions
    #Integrations
    #PlatformAPI

    ------------------------------
    MANERI MANOJ
    Software Engineer
    ------------------------------



  • 2.  RE: WFM Time-Off HRIS Integration Does Not Expose timeOffRequestId Needed for PTO Audit Trail

    Posted 13 hours ago

    Hello,

    Thanks for reaching out. If I understand your requirement correctly, you are looking for a API to be able to get mappings of Genesys time off request identifiers to HRIS system time off request identifiers. i.e for a given HRIS TOR id is you would like to know Genesys TOR id to use in Genesys APIs to get TOR details for audit purposes.

    Unfortunately we do not have an API that supports that requirement and there is nothing on the roadmap at the moment. But you are welcome to submit your thought in Genesys cloud aha ideas portal and we will certainly look into it. Feel free to reach out for any additional questions.



    ------------------------------
    Krishna Raghuraman
    Lead Software Engineer
    ------------------------------



  • 3.  RE: WFM Time-Off HRIS Integration Does Not Expose timeOffRequestId Needed for PTO Audit Trail

    Posted 3 hours ago

    Hi Krishna Raghuraman,

        Thanks for your response and you are correct, but I just want to let you know in detail that in current HRIS integration setup Genesys cloud is passing details in below table to workflows.

    Name Data Type Notes Mandatory
    Flow.agentId String External HRIS agent ID for whom the time-off request is being inserted Yes
    Flow.dates String Array Dates for the time-off request in YYYY-MM-DD format; includes all days spanning the request Yes
    Flow.startDateTimes String Array For partial-day time-off requests only; ISO datetime strings in YYYY-MM-DDTHH:mm:ss format No
    Flow.minDate String Earliest date of the request (in YYYY-MM-DD format) Yes
    Flow.maxDate String Latest date of the request (in YYYY-MM-DD format) Yes
    Flow.timeOffStatus String One of: APPROVED, PENDING Yes
    Flow.timeOffTypeId String External time-off type ID configured in the HRIS Yes
    Flow.payableMinutes String Array Payable minutes for each date in the request Yes
    Flow.notes String Optional notes attached to the request No

    We will be good if this integration can pass additional details like below which required to get required using existing platform API.
    • timeOffRequestId 
    • managementUnitId
    • userId       (genesys)

    Or it will be great if this Integration can pass all required fields to workflows so that we do not need to use any additional platform APIs.

    • Who submitted the PTO request
    • Who approved/reviewed the PTO request
    • Submission timestamp
    • Approval/review timestamp

    FYI,
    please see this blue print that we are using.
    wfm-hris-blueprint/blueprint/index.md at main · GenesysCloudBlueprints/wfm-hris-blueprint · GitHub


    AND I have submitted an Idea in Genesys AHA portal for this enhancement, please get this reviewed and provide your comments and vote for this idea if you can.
    Expose timeOffRequestId in the WFM | Genesys Cloud Ideas Portal

    Thanks a bunch again for looking into this. 



    ------------------------------
    MANERI MANOJ
    Software Engineer
    ------------------------------



  • 4.  RE: WFM Time-Off HRIS Integration Does Not Expose timeOffRequestId Needed for PTO Audit Trail

    Posted 3 hours ago

    Hello,

    Could you elaborate a little bit on the use case? Are you looking to send an information about who has submitted and who has approved the PTO to HRIS system and store it there? 

    This is available already in Genesys Cloud and can be audited and reviewed there for dispute resolution. 



    ------------------------------
    Vidas Placiakis
    Genesys
    ------------------------------



  • 5.  RE: WFM Time-Off HRIS Integration Does Not Expose timeOffRequestId Needed for PTO Audit Trail

    Posted an hour ago

    Hi Vidas Placiakis,
        You are correct our Payroll and HR team want this information to be passed to Workday real time with PTO requests.
        As workday being source system for payroll team they do want all information to be stored in workday itself so that payroll& HR teams can Audit and provide any clarifications related to payroll queries by agents. 
       they do not want to login and see in genesys cloud for these details.



    ------------------------------
    MANERI MANOJ
    Software Engineer
    ------------------------------