Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.
  • 1.  CurrentTimestamp variable as a value of a call rule condition

    Posted 05-23-2017 13:02
    No replies, thread closed.

    Hi there,

     

    Context : 

    Outbound Dialing / Call rule condition for contact list and outbound campaign.

     

    Problem :

    I am wondering if it is possible to set the CurrentTimestamp as a value of the call rule condition that use numeric comparator.

    In the call rule administration, it seems that we can compare a date using both comparator methods :

    - Relative time comparator : can compare a timestamp according to a fixed hour or week (1 hour, 2 hour...). In this case, I cannot specify a precise time, for instance 15 minutes.

    - Numeric comparator : this allows me to set a fix timestamp on which I can compare the date within my contact list, but I cannot compare according to a period, because I do not find a way to set the current timestamp variable as the value of this condition. If I can set it, I would do this :

    LastAttemptTimestamp Is Less Than CurrentTimestamp - 900000

     

    Question : 

    How can we set the CurrentTimestamp as a value of a call rule condition ?

     

    Thanks a lot for your help.

     

    Baptiste.

     



  • 2.  RE: CurrentTimestamp variable as a value of a call rule condition

    Posted 05-23-2017 17:58
    No replies, thread closed.

    I don't know if you have more options available by creating a rule through the API:

    https://developer.mypurecloud.com/api/rest/v2/outbound/index.html#postOutboundCampaignrules

     

    I suggest you post on developer.mypurecloud.com asking if that would be possible/feasible.



  • 3.  RE: CurrentTimestamp variable as a value of a call rule condition

    Posted 05-24-2017 09:17
    No replies, thread closed.

    Thanks a lot George for your answer.

    We can do it using the API and it works. I configured it using this :

     

    (ruleset.PNG attachment)

     

    The major problem with this method using the API blocks the ability to update the ruleset afterwards. Once a ruleset is modified using the API, we have blocking message if we try to change it from the Administration screen.

     

    It would be good if either we can use such a variable like CurrentTimestamp, or if relative time can have more available values (15 minutes, 30 minutes, 45 minutes for instance).

     

    How can we ask the developers from Purecloud to develop this. It should be a quick change, but with a major business value.

     

    Again thanks for your help!

     

    Baptiste.



  • 4.  RE: CurrentTimestamp variable as a value of a call rule condition

    Posted 05-24-2017 13:22
    No replies, thread closed.

    I'm glad to hear it worked, Baptiste.

     

    You can submit an enhancement request by contacting Support, to make sure it gets entered in the system.

     

    Until then, I guess you will need to use the PUT to update your rule:

    https://developer.mypurecloud.com/api/rest/v2/outbound/index.html#putOutboundCampaignrulesCampaignruleId

     



  • 5.  RE: CurrentTimestamp variable as a value of a call rule condition

    Posted 05-24-2017 13:48
    No replies, thread closed.

    Thanks George, I have created the request : 0001982401

     

    Best regards,

    Baptiste.