This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

One thing I like is the data table listing is now in single rows.  Previously, if you had a field of data that was long, it would expand the row in the data listing making it hard to find your entry.  The search at the top is also nice.  The Export Data icon is still wrong - should be down arrow.  I agree with the data entry, while it is supposed to be modern with the expandable boxes and all, it is not for me.  Minimalist to me says Mac of the 80's.

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

Robert, I am not seeing this. My Data Table views (both the list of tables and the individual table contents) still expands the rows 😑

One thing I like is the data table listing is now in single rows.  Previously, if you had a field of data that was long, it would expand the row in the data listing making it hard to find your entry.  The search at the top is also nice.  The Export Data icon is still wrong - should be down arrow.  I agree with the data entry, while it is supposed to be modern with the expandable boxes and all, it is not for me.  Minimalist to me says Mac of the 80's.

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

Robert, I am not seeing this. My Data Table views (both the list of tables and the individual table contents) still expands the rows 😑

One thing I like is the data table listing is now in single rows.  Previously, if you had a field of data that was long, it would expand the row in the data listing making it hard to find your entry.  The search at the top is also nice.  The Export Data icon is still wrong - should be down arrow.  I agree with the data entry, while it is supposed to be modern with the expandable boxes and all, it is not for me.  Minimalist to me says Mac of the 80's.

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

Got pulled out.  You can see why I don't like the old view:

Robert, I am not seeing this. My Data Table views (both the list of tables and the individual table contents) still expands the rows 😑

One thing I like is the data table listing is now in single rows.  Previously, if you had a field of data that was long, it would expand the row in the data listing making it hard to find your entry.  The search at the top is also nice.  The Export Data icon is still wrong - should be down arrow.  I agree with the data entry, while it is supposed to be modern with the expandable boxes and all, it is not for me.  Minimalist to me says Mac of the 80's.

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

What I would like to see is the ability to search / sort a Data Table by something other than the Key column.

I would also like to see the column data types expanded to include built-in Genesys ones (e.g. Skill, or Queue) Many people use Data Tables to dynamically program these things (no judgement here!) but you have to use a String and then use appropriate logic in Architect. Not only can / does this lead to typos, but it is also inefficiencies and can introduce errors down the line. For example, if you try to delete an object that is referenced, you get a warning, or an error, however if it's referenced by name in a Data Table, you don't (since the system has no way of knowing that the String contains, say, Queue names!) The dependency viewer also doesn't work for the same reason. I get that this is probably a bigger ask than just the UI 😉 - Ideas site here I come!

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------

Hey Everyone,

It would seem you aren't alone in wanting some improvements and I found this idea, Data Tables operations improvement, which you could vote on and add your input so that it can be considered for future updates (if you haven't already).

What I would like to see is the ability to search / sort a Data Table by something other than the Key column.

I would also like to see the column data types expanded to include built-in Genesys ones (e.g. Skill, or Queue) Many people use Data Tables to dynamically program these things (no judgement here!) but you have to use a String and then use appropriate logic in Architect. Not only can / does this lead to typos, but it is also inefficiencies and can introduce errors down the line. For example, if you try to delete an object that is referenced, you get a warning, or an error, however if it's referenced by name in a Data Table, you don't (since the system has no way of knowing that the String contains, say, Queue names!) The dependency viewer also doesn't work for the same reason. I get that this is probably a bigger ask than just the UI 😉 - Ideas site here I come!

This weeks release (10 Jan) included Architect data tables user interface updates - and I am not a fan of the new 'improved' layout. 

Previously the edit page would be full screen and could take advantage of the real estate. And the string field would by default take up 1 line, but could be easy expanded to see more content.

Now the new layout now squashes the row edit into about 1/3 of the space it uses to occupy with the font size about 20% smaller.

It also defaults the size (height) of the string field to about 4-5 lines and cannot be made smaller.

I don't know how this could be a more "more visually intuitive experience" - it just smaller text in a tinier window with endless scrolling :( Could at least make the pop-out edit window fit to width

Also to use on a mobile to quickly edit/update a data table row is even harder (yes I know a 'mobile' interface isn't expected/supported/optimal - but sometimes I just need to quickly update a value without access to a full desktop interface)

Before it would be usable in a pinch.


Now it's still possible, but it's even harder with half the field cut off and excessive margins / whitespace.

Don't know whether I'm being unreasonable - but I am not a fan of updates that prefer form over function.

If the edit row could be the same as the Flow Outcome edit page, that would still fit the newer UI look but retain similar function:

#Omni-Channel Desktop/User Interface
#PlatformAdministration
#SystemAdministration

------------------------------
Jeff
------------------------------