Genesys Cloud CX - Beta HQ

My thoughts so far:

1. It would be nice if the collapsing could be remembered.  I collapse 14 of 15 elements and click somewhere else and back to tool and they are all expanded again.
2. Why is there the need for two dividers as below and why does the divider move?  it does not move in the bot flows 
    
3. For the Set Attribute or Participant Data - it would be nice to see the attribute name in the title like does in the flow:
   
4. I don't see this functionality in a Switch tool

------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
------------------------------

My thoughts so far:

1. It would be nice if the collapsing could be remembered.  I collapse 14 of 15 elements and click somewhere else and back to tool and they are all expanded again.
2. Why is there the need for two dividers as below and why does the divider move?  it does not move in the bot flows 
    
3. For the Set Attribute or Participant Data - it would be nice to see the attribute name in the title like does in the flow:
   
4. I don't see this functionality in a Switch tool

@Amelie Wisniak - Just a few things at the moment:

1. I really like the ability to click and drag individual cards up/down (e.g. to rearrange the order of attributes, switch cases, etc.) So much better than having to click & chase the up/down arrow when rearranging the order.
2. It wasn't until I [accidentally] noticed the "tool tip" (that pops up when you hover over the drop-down arrow on the card) that you had to hold down the 'shift' key in order to expand more than one card at a time. Is that a requested usability feature? I ask because I would rather expand as many as I want without having to hold down the 'shift' key when doing so.
3. Piggybacking off the prior point, it would be helpful to have a "Expand/Collapse All [Cards]" option, especially since the variables/data is not visible until you do expand the card (e.g. Switch looks like this which is not as user-friendly when I'm trying to determine what to change.)
4. Also, as shown above (and to Robert's point--especially for Switch), it would be ideal to see a preview of the Expression/Literal Value assigned to the Case.

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology
------------------------------

Hi @Brian Jones,

Thank you for your thoughtful feedback. Just as a follow-up question to your points above, if we improved the type of information shown in the collapsed state (e.g. included the literal value, a preview of the expression, etc., along with some cue as to what the data type is) would that satisfy the need to have multiple cards open?

Or is there another use case that you can think of where you need to have multiple cards open in spite of having more information in the collapsed card?

Your point on the Switch action is a great one and has been noted by the team.

------------------------------
Colin Finnegan
Genesys - Employees
------------------------------


Original Message:
Sent: 05-21-2024 22:52
From: Brian Jones
Subject: Beta - Collapsible cards in Architect actions

@Amelie Wisniak - Just a few things at the moment:

1. I really like the ability to click and drag individual cards up/down (e.g. to rearrange the order of attributes, switch cases, etc.) So much better than having to click & chase the up/down arrow when rearranging the order.
2. It wasn't until I [accidentally] noticed the "tool tip" (that pops up when you hover over the drop-down arrow on the card) that you had to hold down the 'shift' key in order to expand more than one card at a time. Is that a requested usability feature? I ask because I would rather expand as many as I want without having to hold down the 'shift' key when doing so.
3. Piggybacking off the prior point, it would be helpful to have a "Expand/Collapse All [Cards]" option, especially since the variables/data is not visible until you do expand the card (e.g. Switch looks like this which is not as user-friendly when I'm trying to determine what to change.)
4. Also, as shown above (and to Robert's point--especially for Switch), it would be ideal to see a preview of the Expression/Literal Value assigned to the Case.

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology

Thanks for responding so quickly, @Colin Finnegan:

Q: If we improved the type of information shown in the collapsed state (e.g. included the literal value, a preview of the expression, etc., along with some cue as to what the data type is) would that satisfy the need to have multiple cards open? Or is there another use case that you can think of where you need to have multiple cards open in spite of having more information in the collapsed card?

A: I certainly don't want to speak for everyone else, but I believe that answer depends on the amount of detail contained within the collapsed card. In some cases a preview would be sufficient if it instantly helps me determine that's the card I need to expand and work on. In other cases, there could be multiple fields contained within a single card with lengthy entries, thus rendering a preview insufficient. Plus if you try to cram too much info in the preview, it almost defeats the purpose of a collapsed card [and likely increases your development time.] 

That said, I still believe an "Expand/Collapse All" option should be made available for those of us who want to get in (without hunting/pecking), expand everything, make our changes in the appropriate rows, collapse all, and move on. It's basically like allowing the user to choose if they want to see no detail (all collapsed), some detail (some expanded), or all detail (all expanded).

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology
------------------------------


Original Message:
Sent: 05-23-2024 07:30
From: Colin Finnegan
Subject: Beta - Collapsible cards in Architect actions

Hi @Brian Jones,

Thank you for your thoughtful feedback. Just as a follow-up question to your points above, if we improved the type of information shown in the collapsed state (e.g. included the literal value, a preview of the expression, etc., along with some cue as to what the data type is) would that satisfy the need to have multiple cards open?

Or is there another use case that you can think of where you need to have multiple cards open in spite of having more information in the collapsed card?

Your point on the Switch action is a great one and has been noted by the team.

------------------------------
Colin Finnegan
Genesys - Employees


Original Message:
Sent: 05-21-2024 22:52
From: Brian Jones
Subject: Beta - Collapsible cards in Architect actions

@Amelie Wisniak - Just a few things at the moment:

1. I really like the ability to click and drag individual cards up/down (e.g. to rearrange the order of attributes, switch cases, etc.) So much better than having to click & chase the up/down arrow when rearranging the order.
2. It wasn't until I [accidentally] noticed the "tool tip" (that pops up when you hover over the drop-down arrow on the card) that you had to hold down the 'shift' key in order to expand more than one card at a time. Is that a requested usability feature? I ask because I would rather expand as many as I want without having to hold down the 'shift' key when doing so.
3. Piggybacking off the prior point, it would be helpful to have a "Expand/Collapse All [Cards]" option, especially since the variables/data is not visible until you do expand the card (e.g. Switch looks like this which is not as user-friendly when I'm trying to determine what to change.)
4. Also, as shown above (and to Robert's point--especially for Switch), it would be ideal to see a preview of the Expression/Literal Value assigned to the Case.

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology

Hi Community!

I just joined the Beta so I haven't been able to try it out yet, but I think it would be nice if the number next to "Update Statement" still appeared on the cards.

I use the number to compare between flows and know if they have the same number of elements.

Thanks.

Hi @Marcelino Santos,

Thank you for taking the time to provide feedback. You raise an interesting point.

Just so I can understand your use case a bit more, can you tell me was the numbering useful by giving you context on the total number of elements contained in the Update Statement or did the individual numbers next to each element support you in another way?

Thanks again and looking forward to hearing more.

Hi Community!

I just joined the Beta so I haven't been able to try it out yet, but I think it would be nice if the number next to "Update Statement" still appeared on the cards.

I use the number to compare between flows and know if they have the same number of elements.

Thanks.

Hi @Colin Finnegan,

My post was actually related to your "individual numbers next to each element support me in another way".

I've seen that when a card is opened, a number appears next to Variable Name and to Value to Assign. This number changes when the card is moved to another position. What I was talking about is to show that number of the card even when the card is collapsed. You can know inmediately the position of the card and, as before, this number changes when this card is moved up or down. This way you can know if the number of data is the same and they are ordered in the same way, when you compare flows from different organizations (environments).

However the other part of you post is also interesting. It would be nice to just select the Action (Update Data, for example) and know the total number of elements defined in the object, without having to go to the bottom of the list to see the highest number. It can save you time while you are developing flows.

Thanks in advance.

Hi @Marcelino Santos,

Thank you for taking the time to provide feedback. You raise an interesting point.

Just so I can understand your use case a bit more, can you tell me was the numbering useful by giving you context on the total number of elements contained in the Update Statement or did the individual numbers next to each element support you in another way?

Thanks again and looking forward to hearing more.

Hi Community!

I just joined the Beta so I haven't been able to try it out yet, but I think it would be nice if the number next to "Update Statement" still appeared on the cards.

I use the number to compare between flows and know if they have the same number of elements.

Thanks.

Hello Amelie and @Colin Finnegan,

These are the first things that come to mind after testing the new interface.

1. The need of an expand/collapse all button
   
   The current default view provides no information of the content, which is what I'm generally interested in.
   The new design will most likely result in me needing to open/close a lot of cards to get the information I need when editing or troubleshooting Architect flows which doesn't "simplifying the identification of crucial elements for focus".
   Especially in the example of a Switch the labels Case 1, Case 2 etc, tells me nothing of the content.
   
   
   
   
2. Placement of the delete/trash can symbol.
   
   Deleting doesn't require any confirmation and since I now have to open all values to see the content the risk seems higher that I would accidentally delete something since the expand button is next to the delete button.
   I realize it was like this before, but since everything was expanded as default I rarely had to press anything in that area.
   Generally I wouldn't wanna delete something that I don't see the content of, so it might make more sense to only show it when it's expanded
   
   
   
3. Placement of the move icon.
   
   The move icon appears and blocks part of the name each time I hover something.
   I don't feel it's needed since I don't have to hold the actual icon to move something, or it could be indicated in some other way.
   
   
   
4. The hide all "values" icon isn't needed, and could be used to something else.
   
   There's an option to show/hide all variables/cases etc in an action.
   I don't see a practical use for this as it hides everything, leaving me with no information, and if I press the plus sign to add a new value it shows everything again.
   
   Changing this to expand/collapse all would be a better use of the space.
   
   
   

These are my personal opinions, and I welcome everyone to share their feedback on the "issues" I've mentioned.
Maybe a poll or survey on topics brought up in this thread could give an indication of how many think a certain part should be redesigned.

Hi @Jan Heinonen,

This feedback is fantastic. Thank you for taking the time to consider the designs and sending this very considered response.

I will take this back to the team for review.

Hello Amelie and @Colin Finnegan,

These are the first things that come to mind after testing the new interface.

1. The need of an expand/collapse all button
   
   The current default view provides no information of the content, which is what I'm generally interested in.
   The new design will most likely result in me needing to open/close a lot of cards to get the information I need when editing or troubleshooting Architect flows which doesn't "simplifying the identification of crucial elements for focus".
   Especially in the example of a Switch the labels Case 1, Case 2 etc, tells me nothing of the content.
   
   
   
   
2. Placement of the delete/trash can symbol.
   
   Deleting doesn't require any confirmation and since I now have to open all values to see the content the risk seems higher that I would accidentally delete something since the expand button is next to the delete button.
   I realize it was like this before, but since everything was expanded as default I rarely had to press anything in that area.
   Generally I wouldn't wanna delete something that I don't see the content of, so it might make more sense to only show it when it's expanded
   
   
   
3. Placement of the move icon.
   
   The move icon appears and blocks part of the name each time I hover something.
   I don't feel it's needed since I don't have to hold the actual icon to move something, or it could be indicated in some other way.
   
   
   
4. The hide all "values" icon isn't needed, and could be used to something else.
   
   There's an option to show/hide all variables/cases etc in an action.
   I don't see a practical use for this as it hides everything, leaving me with no information, and if I press the plus sign to add a new value it shows everything again.
   
   Changing this to expand/collapse all would be a better use of the space.
   
   
   

These are my personal opinions, and I welcome everyone to share their feedback on the "issues" I've mentioned.
Maybe a poll or survey on topics brought up in this thread could give an indication of how many think a certain part should be redesigned.

Dear community,

We are excited to share that this feature will be going live next week, starting on Monday! 

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


Original Message:
Sent: 05-30-2024 05:32
From: Colin Finnegan
Subject: Beta - Collapsible cards in Architect actions

Hi @Jan Heinonen,

This feedback is fantastic. Thank you for taking the time to consider the designs and sending this very considered response.

I will take this back to the team for review.

------------------------------
Colin Finnegan
Genesys - Employees


Original Message:
Sent: 05-30-2024 05:22
From: Jan Heinonen
Subject: Beta - Collapsible cards in Architect actions

Hello Amelie and @Colin Finnegan,

These are the first things that come to mind after testing the new interface.

1. The need of an expand/collapse all button
   
   The current default view provides no information of the content, which is what I'm generally interested in.
   The new design will most likely result in me needing to open/close a lot of cards to get the information I need when editing or troubleshooting Architect flows which doesn't "simplifying the identification of crucial elements for focus".
   Especially in the example of a Switch the labels Case 1, Case 2 etc, tells me nothing of the content.
   
   
   
   
2. Placement of the delete/trash can symbol.
   
   Deleting doesn't require any confirmation and since I now have to open all values to see the content the risk seems higher that I would accidentally delete something since the expand button is next to the delete button.
   I realize it was like this before, but since everything was expanded as default I rarely had to press anything in that area.
   Generally I wouldn't wanna delete something that I don't see the content of, so it might make more sense to only show it when it's expanded
   
   
   
3. Placement of the move icon.
   
   The move icon appears and blocks part of the name each time I hover something.
   I don't feel it's needed since I don't have to hold the actual icon to move something, or it could be indicated in some other way.
   
   
   
4. The hide all "values" icon isn't needed, and could be used to something else.
   
   There's an option to show/hide all variables/cases etc in an action.
   I don't see a practical use for this as it hides everything, leaving me with no information, and if I press the plus sign to add a new value it shows everything again.
   
   Changing this to expand/collapse all would be a better use of the space.
   
   
   

These are my personal opinions, and I welcome everyone to share their feedback on the "issues" I've mentioned.
Maybe a poll or survey on topics brought up in this thread could give an indication of how many think a certain part should be redesigned.

------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB

Hi Amelie,

We're seeing this for the first time in GA today. 

If we look at a regular variable in an Update Data node, you can see the name of the variable and the value (or I think you can see the expression), and the icon indicates the type.

But if we look at a collection variable, e.g. String Collection, you can't see the name at all, just the type.

Is this intentional or is it a bug? It seems to be significantly less user-friendly this way. To see the name and maybe a count of the contents would be much more preferable.

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


Original Message:
Sent: 06-28-2024 12:51
From: Amelie Wisniak
Subject: Beta - Collapsible cards in Architect actions

Dear community,

We are excited to share that this feature will be going live next week, starting on Monday! 

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


Original Message:
Sent: 05-30-2024 05:32
From: Colin Finnegan
Subject: Beta - Collapsible cards in Architect actions

Hi @Jan Heinonen,

This feedback is fantastic. Thank you for taking the time to consider the designs and sending this very considered response.

I will take this back to the team for review.

------------------------------
Colin Finnegan
Genesys - Employees


Original Message:
Sent: 05-30-2024 05:22
From: Jan Heinonen
Subject: Beta - Collapsible cards in Architect actions

Hello Amelie and @Colin Finnegan,

These are the first things that come to mind after testing the new interface.

1. The need of an expand/collapse all button
   
   The current default view provides no information of the content, which is what I'm generally interested in.
   The new design will most likely result in me needing to open/close a lot of cards to get the information I need when editing or troubleshooting Architect flows which doesn't "simplifying the identification of crucial elements for focus".
   Especially in the example of a Switch the labels Case 1, Case 2 etc, tells me nothing of the content.
   
   
   
   
2. Placement of the delete/trash can symbol.
   
   Deleting doesn't require any confirmation and since I now have to open all values to see the content the risk seems higher that I would accidentally delete something since the expand button is next to the delete button.
   I realize it was like this before, but since everything was expanded as default I rarely had to press anything in that area.
   Generally I wouldn't wanna delete something that I don't see the content of, so it might make more sense to only show it when it's expanded
   
   
   
3. Placement of the move icon.
   
   The move icon appears and blocks part of the name each time I hover something.
   I don't feel it's needed since I don't have to hold the actual icon to move something, or it could be indicated in some other way.
   
   
   
4. The hide all "values" icon isn't needed, and could be used to something else.
   
   There's an option to show/hide all variables/cases etc in an action.
   I don't see a practical use for this as it hides everything, leaving me with no information, and if I press the plus sign to add a new value it shows everything again.
   
   Changing this to expand/collapse all would be a better use of the space.
   
   
   

These are my personal opinions, and I welcome everyone to share their feedback on the "issues" I've mentioned.
Maybe a poll or survey on topics brought up in this thread could give an indication of how many think a certain part should be redesigned.

------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB

@Jan Heinonen, just found another annoying thing.  If you have a string and string collection, the icon does not show the collection when collapsed and same for all others.  But when expanded, the collections have the original box around them in the variable field.  Makes it hard to pick out the collections unless you reach each one. 

:

Hi Amelie,

We're seeing this for the first time in GA today. 

If we look at a regular variable in an Update Data node, you can see the name of the variable and the value (or I think you can see the expression), and the icon indicates the type.

But if we look at a collection variable, e.g. String Collection, you can't see the name at all, just the type.

Is this intentional or is it a bug? It seems to be significantly less user-friendly this way. To see the name and maybe a count of the contents would be much more preferable.

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


Original Message:
Sent: 06-28-2024 12:51
From: Amelie Wisniak
Subject: Beta - Collapsible cards in Architect actions

Dear community,

We are excited to share that this feature will be going live next week, starting on Monday! 

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


Original Message:
Sent: 05-30-2024 05:32
From: Colin Finnegan
Subject: Beta - Collapsible cards in Architect actions

Hi @Jan Heinonen,

This feedback is fantastic. Thank you for taking the time to consider the designs and sending this very considered response.

I will take this back to the team for review.

------------------------------
Colin Finnegan
Genesys - Employees


Original Message:
Sent: 05-30-2024 05:22
From: Jan Heinonen
Subject: Beta - Collapsible cards in Architect actions

Hello Amelie and @Colin Finnegan,

These are the first things that come to mind after testing the new interface.

1. The need of an expand/collapse all button
   
   The current default view provides no information of the content, which is what I'm generally interested in.
   The new design will most likely result in me needing to open/close a lot of cards to get the information I need when editing or troubleshooting Architect flows which doesn't "simplifying the identification of crucial elements for focus".
   Especially in the example of a Switch the labels Case 1, Case 2 etc, tells me nothing of the content.
   
   
   
   
2. Placement of the delete/trash can symbol.
   
   Deleting doesn't require any confirmation and since I now have to open all values to see the content the risk seems higher that I would accidentally delete something since the expand button is next to the delete button.
   I realize it was like this before, but since everything was expanded as default I rarely had to press anything in that area.
   Generally I wouldn't wanna delete something that I don't see the content of, so it might make more sense to only show it when it's expanded
   
   
   
3. Placement of the move icon.
   
   The move icon appears and blocks part of the name each time I hover something.
   I don't feel it's needed since I don't have to hold the actual icon to move something, or it could be indicated in some other way.
   
   
   
4. The hide all "values" icon isn't needed, and could be used to something else.
   
   There's an option to show/hide all variables/cases etc in an action.
   I don't see a practical use for this as it hides everything, leaving me with no information, and if I press the plus sign to add a new value it shows everything again.
   
   Changing this to expand/collapse all would be a better use of the space.
   
   
   

These are my personal opinions, and I welcome everyone to share their feedback on the "issues" I've mentioned.
Maybe a poll or survey on topics brought up in this thread could give an indication of how many think a certain part should be redesigned.

------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB

Hi Amelie,

We're seeing this for the first time in GA today. 

If we look at a regular variable in an Update Data node, you can see the name of the variable and the value (or I think you can see the expression), and the icon indicates the type.

But if we look at a collection variable, e.g. String Collection, you can't see the name at all, just the type.

Is this intentional or is it a bug? It seems to be significantly less user-friendly this way. To see the name and maybe a count of the contents would be much more preferable.

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


Original Message:
Sent: 06-28-2024 12:51
From: Amelie Wisniak
Subject: Beta - Collapsible cards in Architect actions

Dear community,

We are excited to share that this feature will be going live next week, starting on Monday! 

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


Original Message:
Sent: 05-30-2024 05:32
From: Colin Finnegan
Subject: Beta - Collapsible cards in Architect actions

Hi @Jan Heinonen,

This feedback is fantastic. Thank you for taking the time to consider the designs and sending this very considered response.

I will take this back to the team for review.

------------------------------
Colin Finnegan
Genesys - Employees


Original Message:
Sent: 05-30-2024 05:22
From: Jan Heinonen
Subject: Beta - Collapsible cards in Architect actions

Hello Amelie and @Colin Finnegan,

These are the first things that come to mind after testing the new interface.

1. The need of an expand/collapse all button
   
   The current default view provides no information of the content, which is what I'm generally interested in.
   The new design will most likely result in me needing to open/close a lot of cards to get the information I need when editing or troubleshooting Architect flows which doesn't "simplifying the identification of crucial elements for focus".
   Especially in the example of a Switch the labels Case 1, Case 2 etc, tells me nothing of the content.
   
   
   
   
2. Placement of the delete/trash can symbol.
   
   Deleting doesn't require any confirmation and since I now have to open all values to see the content the risk seems higher that I would accidentally delete something since the expand button is next to the delete button.
   I realize it was like this before, but since everything was expanded as default I rarely had to press anything in that area.
   Generally I wouldn't wanna delete something that I don't see the content of, so it might make more sense to only show it when it's expanded
   
   
   
3. Placement of the move icon.
   
   The move icon appears and blocks part of the name each time I hover something.
   I don't feel it's needed since I don't have to hold the actual icon to move something, or it could be indicated in some other way.
   
   
   
4. The hide all "values" icon isn't needed, and could be used to something else.
   
   There's an option to show/hide all variables/cases etc in an action.
   I don't see a practical use for this as it hides everything, leaving me with no information, and if I press the plus sign to add a new value it shows everything again.
   
   Changing this to expand/collapse all would be a better use of the space.
   
   
   

These are my personal opinions, and I welcome everyone to share their feedback on the "issues" I've mentioned.
Maybe a poll or survey on topics brought up in this thread could give an indication of how many think a certain part should be redesigned.

------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB