JavieR | 2023-03-13 16:03:44 UTC | #1
Hello colleagues,
I am massively creating queues with Terraform, with the help of a .csv file. When filling the "acwwrapupprompt" field, for example, with the value "MANDATORYFORCEDTIMEOUT", I can fill the "acwtimeoutms" field without problems.
When I fill the field "acwwrapupprompt", with the value, "MANDATORY", it does not make sense to give a value to the field "acwtimeoutms". And here is my problem, I can't set the value to "0", because it forces you to indicate a numeric value, starting from "1000".
If I indicate a "correct" value, the creation of the queue objects is done correctly, but... in the command line I never get the OK.
I don't know if I have managed to explain my problem... thanks in advance!!!
 |
 |
 |
 |
 |
John_Carnell | 2023-03-13 17:34:58 UTC | #2
Hi Javier,
I am going to dig into the expected behavior for MANDATORY vs. MANDATORYFORCEDTIMEOUT and see exactly what the behavior. In reviewing the code, we are using a validation function that is checking to see if the value is between 1000-84600 milliseconds (I think that is the right time unit), but it is not trying to do any cross-validation to see if there is a difference if value is MANDATORY vs. MANDATORYFORCEDTIME. When I get a chance to talk with the dev team, that will give me a better idea of behavior.
Could you please provide more detail:
If I indicate a "correct" value, the creation of the queue objects is done correctly, but...
in the command line I never get the OK.
Could you help me understand the statement. Is the queue getting created? Is Terraform hanging??? Any more comments would be greatly appreciated.
Thanks, John Carnell Director, Developer Engagement
John_Carnell | 2023-03-13 18:11:52 UTC | #3
Hi Javier,
I was able to reproduce the problem in our lab. MANDATORY should not have a timeout value with it and our constraint shows a minimum of 1000 - 84600 ms. This constraint should be 0-84600. I am going to write a ticket on this, fix the constraint, and update the documentation in the CX as a Code resource provider.
This should be a relatively simple fix to make so I should be able to have it out before the next release.
Thanks, John Carnell Director, Developer Engagement
JavieR | 2023-03-13 18:34:42 UTC | #4
Hi John,
thanks for your response.
What is the estimated date for the next update?
John_Carnell | 2023-03-13 20:35:08 UTC | #5
Hi Javier,
It is up for PR now and I dropped a message to my engineer in Ireland that I would like to get a release done sometime this week if possible. So barring any other issues, I am hoping this week or early next week.
Thanks, John Carnell Manager, Developer Engagement
JavieR | 2023-03-14 08:52:44 UTC | #6
Hi,
ok John, we await!!
Thanks.
John_Carnell | 2023-03-15 16:39:12 UTC | #7
Hi Javier,
The fix should be out in the https://github.com/MyPureCloud/terraform-provider-genesyscloud/releases/tag/v1.13.0 release. You can now set the value to zero for a MANDATORY item.
Thanks, John Carnell Director, Developer Engagement
This post was migrated from the old Developer Forum.
ref: 18861