Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.
  • 1.  Media Type = email, changes ConversationEndDate for each Interaction

    Posted 02-20-2023 09:06
    No replies, thread closed.

    We have a Rest API POST framework in place which pulls the data from Conversation Detail API in Incremental way. Means takes max(ConversationStart) and queries PureCloud API with Dates after that.

    But, for Email MediaType whenever a new email message arrives for same Conversation, the ConversationStart Date remains same for the new Segments/Sessions but the ConversationEnd Changes for the entire conversation. So, in our scenario we miss the details of messages.

    Is there a way to load the ConversationDetail for MediaType=email in incremental way based on any other date field in the filters. Instead of ConversationStart & ConversationEnd (Interval) Date filter in the query.

    Current Query:

    {
     "interval": "2022-12-26T05:00:00.000Z/2022-12-31T05:00:00.000Z",
     "order": "asc",
     "orderBy": "conversationStart",
     "paging": {
      "pageSize": 25,
      "pageNumber": 1
     },
     "segmentFilters": [
      {
       "type": "or",
       "predicates": [
        {
         "type": "dimension",
         "dimension": "mediaType",
         "operator": "matches",
         "value": "email"
        }
       ]
      }
     ]
    }
    

    Thanks,
    Rahul


    #Reporting/Analytics

    ------------------------------
    Rahul Yadav
    Allscripts Healthcare Solutions Inc.
    ------------------------------


  • 2.  RE: Media Type = email, changes ConversationEndDate for each Interaction

    Posted 02-20-2023 15:49
    No replies, thread closed.

    Give this a go and see if it maybe helps:

    {
     "interval": "2022-12-22T05:00:00.000Z/2022-12-31T05:00:00.000Z",
     "order": "asc",
     "orderBy": "conversationStart",
     "paging": {
      "pageSize": 25,
      "pageNumber": 1
     },
     "segmentFilters": [
      {
       "type": "and",
       "predicates": [
        {
         "type": "dimension",
         "dimension": "mediaType",
         "operator": "matches",
         "value": "email"
        },
        {
         "type": "dimension",
         "dimension": "purpose",
         "operator": "matches",
         "value": "customer"
        }
       ]
      }
     ]
    }



    ------------------------------
    Dewald Smit
    Altron Systems Integration a Division of Altron TMT (Pty) Ltd
    ------------------------------



  • 3.  RE: Media Type = email, changes ConversationEndDate for each Interaction

    Posted 02-24-2023 06:47
    No replies, thread closed.

    Hi Dewald,

    Is there a way to read data based on Conversation End date instead of Conversation Start Date? 

    e.g. we have a Conversation which started on 27-Dec-2022 and Ended on 29-Dec-2022. When our API ran on 27-Dec-2022 it returned data for this Conversation. But, when we ran for 29-Dec-2022 it did not return this conversation as the Conversation started on 27th. so, we are missing the Segments after start date.

    We are running the API's for the interval of the current date only, as we are doing Incremental Loads in our Datawarehouse. 

    Thanks,

    Rahul



    ------------------------------
    Rahul Yadav
    Allscripts Healthcare Solutions Inc.
    ------------------------------



  • 4.  RE: Media Type = email, changes ConversationEndDate for each Interaction

    Posted 02-24-2023 07:00
    No replies, thread closed.

    HI Rahul,

    I am not sure if and how that would work for you.

    But you can add End date as a filter.

     "conversationFilters": [
      {
       "type": "or",
       "predicates": [
        {
         "type": "dimension",
         "dimension": "conversationEnd",
         "operator": "matches",
         "value": "2023-02-23" - im not 100% sure about this value structure.
    }


    ------------------------------
    Dewald Smit
    Altron Systems Integration a Division of Altron TMT (Pty) Ltd
    ------------------------------