The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Thanks @Amelie Wisniak

Would be good to have this for GA release.

Is there any guidance you can give though, like in general, on average, ball park figure for each level of data how much storage would be used for low /  middle / high flow sizes (which is a measure of number of actions)?

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Does this beta include a quicker way to get into the historical debugger other than (get ID manually, go into Architect, wait, manually search by ID, select it, wait more), like, a link in the Interaction view?

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Hi,

Last week I filled in the enrollment form to participate the beta. But I see no Execution Data item in the menu in Architect. Is the beta not active in my Org? Or is there a permission tied to this feature?

Thanks,

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

We joined the beta today. Finding it really useful, already helped solve a few bugs. It's not been seamless but definitely very good.

Immediate ask: can we get more information in the Execution History page when you click the Execution History button in a flow? Even just ConversationId (if not things like ANI, DNIS, ...) to help identify the interaction we want to review (without having to get the ID, search for it etc).

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

We joined the beta today. Finding it really useful, already helped solve a few bugs. It's not been seamless but definitely very good.

Immediate ask: can we get more information in the Execution History page when you click the Execution History button in a flow? Even just ConversationId (if not things like ANI, DNIS, ...) to help identify the interaction we want to review (without having to get the ID, search for it etc).

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@James Dunn @Edward Wit @Paul McGurn You should now all have access to the beta! 

We joined the beta today. Finding it really useful, already helped solve a few bugs. It's not been seamless but definitely very good.

Immediate ask: can we get more information in the Execution History page when you click the Execution History button in a flow? Even just ConversationId (if not things like ANI, DNIS, ...) to help identify the interaction we want to review (without having to get the ID, search for it etc).

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

We joined the beta today. Finding it really useful, already helped solve a few bugs. It's not been seamless but definitely very good.

Immediate ask: can we get more information in the Execution History page when you click the Execution History button in a flow? Even just ConversationId (if not things like ANI, DNIS, ...) to help identify the interaction we want to review (without having to get the ID, search for it etc).

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Really enjoying this feature. I've only had a little play with it so far but wanted to give some initial feedback.

Couple of things, first can we please get the keyboard shortcuts for all flows. pressing e then h to bring up expression helper, would be so handy in a normal flow. Same with the ctrl g to jump to location, ctrl s to save, ctrl i to hide the number ids etc.

When pinning a variable and setting it to a breakpoint, honestly first time i did it by accident and couldn't figure out why the variable disappeared from Data and where to find it. It was just at the top. But also while hovering over the symbol before the variable (not system) it gives 2 tooltips that overlap, add break point and the data type, eg

Seeing the error values even though I haven't added the outputs as variables, is awesome

Being able to click on go to next update on a variable, very helpful.

I like that I can click on a date to change it's format, just wish there was some localization applied, ie not American date format.

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Amelie Wisniak Can you please confirm if my org is on the list as I don't see the new permissions yet? We were using the old beta and signed up to this one. I have some queries about data size but want to make sure I'm on the right beta first.

Really enjoying this feature. I've only had a little play with it so far but wanted to give some initial feedback.

Couple of things, first can we please get the keyboard shortcuts for all flows. pressing e then h to bring up expression helper, would be so handy in a normal flow. Same with the ctrl g to jump to location, ctrl s to save, ctrl i to hide the number ids etc.

When pinning a variable and setting it to a breakpoint, honestly first time i did it by accident and couldn't figure out why the variable disappeared from Data and where to find it. It was just at the top. But also while hovering over the symbol before the variable (not system) it gives 2 tooltips that overlap, add break point and the data type, eg

Seeing the error values even though I haven't added the outputs as variables, is awesome

Being able to click on go to next update on a variable, very helpful.

I like that I can click on a date to change it's format, just wish there was some localization applied, ie not American date format.

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Richard Chandler Your org is now part of the beta. You must enable execution data storage and republish flows to track execution data. We are looking forward to your feedback. 

@Amelie Wisniak Can you please confirm if my org is on the list as I don't see the new permissions yet? We were using the old beta and signed up to this one. I have some queries about data size but want to make sure I'm on the right beta first.

Really enjoying this feature. I've only had a little play with it so far but wanted to give some initial feedback.

Couple of things, first can we please get the keyboard shortcuts for all flows. pressing e then h to bring up expression helper, would be so handy in a normal flow. Same with the ctrl g to jump to location, ctrl s to save, ctrl i to hide the number ids etc.

When pinning a variable and setting it to a breakpoint, honestly first time i did it by accident and couldn't figure out why the variable disappeared from Data and where to find it. It was just at the top. But also while hovering over the symbol before the variable (not system) it gives 2 tooltips that overlap, add break point and the data type, eg

Seeing the error values even though I haven't added the outputs as variables, is awesome

Being able to click on go to next update on a variable, very helpful.

I like that I can click on a date to change it's format, just wish there was some localization applied, ie not American date format.

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Amelie Wisniak Can you please confirm if my org is on the list as I don't see the new permissions yet? We were using the old beta and signed up to this one. I have some queries about data size but want to make sure I'm on the right beta first.

Really enjoying this feature. I've only had a little play with it so far but wanted to give some initial feedback.

Couple of things, first can we please get the keyboard shortcuts for all flows. pressing e then h to bring up expression helper, would be so handy in a normal flow. Same with the ctrl g to jump to location, ctrl s to save, ctrl i to hide the number ids etc.

When pinning a variable and setting it to a breakpoint, honestly first time i did it by accident and couldn't figure out why the variable disappeared from Data and where to find it. It was just at the top. But also while hovering over the symbol before the variable (not system) it gives 2 tooltips that overlap, add break point and the data type, eg

Seeing the error values even though I haven't added the outputs as variables, is awesome

Being able to click on go to next update on a variable, very helpful.

I like that I can click on a date to change it's format, just wish there was some localization applied, ie not American date format.

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Hi Amelie,

we are trying to consume the Execution Data History via Event Bridge but what we saw is that the log level on Notification is set to base that is already something but not helpful for debugging outside of Architect. Do you know if this log level can be changed? The level "Notes" should help for our use case. 

The idea behind is consuming these events and keep trace for longer troubleshooting via Splunk to trace the history longer then 10 days.

As additional info also on the Common Module at the moment it's not enable the Execution Data & reply.do you have any idea if it will be added ? 

Thanks and let me know

Gianpaolo

------------------------------
Gianpaolo Butera
Genesys - Employees

Original Message:
Sent: 05-09-2024 17:50
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Hi,

Very happy with this feature. Normally we added several logging steps in Architect flows and write that into Participant Data. This tool really will help to get rid of that. Maybe some suggestions to make it even better:

• It is mentioned earlier in this thread, the storage. Maybe it is an idea to give a possibility to delete execution data manually, e.g. the result of a particular query. Or a period or simply all. I also think it would be wise that you can delete a single conversation for GDPR purposes.
• The Flow Level is a global setting. When building and tracing a flow you normally need a higher log level for only that flow and not for all. Is there a way to overwrite the global log level for a single flow?
• The Query Builder in the result pane only supports in criteria.When you have tons of conversations and you need some from yesterday then finding the right one is now doable. So additional criteria would really help, like Time, DNIS, ANI, etc. Or add some link in the Interaction view on conversation to view the execution data. As mentioned earlier in this thread. 

I also have a question when logging will start. Yesterday I enable this feature and didn't see any logs appearing on the flow. I republished one flow and from that moment I saw the logs coming in for that flow. But till now I don't see the logs on other flows. So do we have to publish a flow first so it will store the execution data?

And this morning I changed the log level from Base to Notes and it took a couple of minutes before that change had effect on the flow I republished yesterday. So is there a delay and how long is that delay? On the other flows I still have no execution data.

Thanks,

------------------------------
Edward de Wit
Cloudoe BV

Original Message:
Sent: 05-09-2024 17:50
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Edward Wit

You can set the log level for an individual flow. If you go to the Architect flow list (the front page for Architect) and search for the flow, there is an Execution Data option where you can change the flow level.



Yes you do seemingly have to republish every single flow to start capturing logs for that flow. Until you republish you don't get anything for that flow, which is a bit of a pain.

I have also had on occasion flows that were republished seemingly stop capturing logs after a later publish, and having to be published again.

------------------------------
James Dunn
Pitney Bowes Inc.

Original Message:
Sent: 05-16-2024 03:11
From: Edward Wit
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Hi,

Very happy with this feature. Normally we added several logging steps in Architect flows and write that into Participant Data. This tool really will help to get rid of that. Maybe some suggestions to make it even better:

• It is mentioned earlier in this thread, the storage. Maybe it is an idea to give a possibility to delete execution data manually, e.g. the result of a particular query. Or a period or simply all. I also think it would be wise that you can delete a single conversation for GDPR purposes.
• The Flow Level is a global setting. When building and tracing a flow you normally need a higher log level for only that flow and not for all. Is there a way to overwrite the global log level for a single flow?
• The Query Builder in the result pane only supports in criteria.When you have tons of conversations and you need some from yesterday then finding the right one is now doable. So additional criteria would really help, like Time, DNIS, ANI, etc. Or add some link in the Interaction view on conversation to view the execution data. As mentioned earlier in this thread. 

I also have a question when logging will start. Yesterday I enable this feature and didn't see any logs appearing on the flow. I republished one flow and from that moment I saw the logs coming in for that flow. But till now I don't see the logs on other flows. So do we have to publish a flow first so it will store the execution data?

And this morning I changed the log level from Base to Notes and it took a couple of minutes before that change had effect on the flow I republished yesterday. So is there a delay and how long is that delay? On the other flows I still have no execution data.

Thanks,

------------------------------
Edward de Wit
Cloudoe BV

Original Message:
Sent: 05-09-2024 17:50
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------