Oh :)
Then I suppose his option is to use a switch action in the Architect flow or maybe set wrap-up through APIs?
------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB
------------------------------
Original Message:
Sent: 05-08-2023 09:39
From: Melissa Bailey
Subject: Dynamic system wrap-up codes
I wasn't kidding when I said the ToWrapupCode function was useless. You can give it an existing WrapupCode object which means nothing changes, or NOT_SET to create a NOT_SET WrapupCode object. Several of the ToX functions are like that. Going from a string value to a WrapupCode object would require a FindX function, which we don't have.

------------------------------
Melissa Bailey
Genesys - Employees
------------------------------
Original Message:
Sent: 05-07-2023 06:43
From: Jan Heinonen
Subject: Dynamic system wrap-up codes
As I understand the OP he wants to set wrap-up code in flow to apply different recording policies based on DNIS.
Haven't tested the ToWrapupCode() function but if it requires the ID of the wrap-up code on way to solve it would be to have a Data Table with DNIS and the wrap-up code ID that you can lookup in the Inbound Flow.
------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB
Original Message:
Sent: 05-05-2023 16:46
From: Melissa Bailey
Subject: Dynamic system wrap-up codes
Correct there is no FindWrapupCode function or action. There is an idea for it you can vote for: https://genesyscloud.aha.io/ideas/ideas/ANLS-I-1340.
Ignore the ToWrapupCode function, it's one of our more useless ones.
However as Robert pointed out, you wouldn't want to do that anyways b/c you would have to go create tons of wrap up codes first. Using external tags or the existing dnis reports is a better idea.
------------------------------
Melissa Bailey
Genesys - Employees