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
------------------------------

@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
------------------------------