Workspace-is a user able to amend their 'rows per page', so it doesn't keep reverting to default 20

gaynor_tpp
Tera Contributor

When in  the main UI, one can select 'Show' and amend the number of records to view / row per page from the system default to their preference and it remembers the selection when logging out / navigating elsewhere

However in Workspace e.g. one that displays HR Cases and records relating to HR, the rows per page is set to 20, the user is able to amend to 100, but when the log out or navigate away from Workspace, it changes their selection back to the default of 20. Is this by design to prevent loading records straight away on viewing? Is this to prevent the system from slowing? Is there a way to allow the users say to up it to 100 rows per pqge and remains at the number seelct e.g. 100

1 ACCEPTED SOLUTION

Martin iTSM
Tera Guru

Hey there,

i don`t have a solution for this - but i could reproduce what you describe in a client`s tokyo instance - after logging out the rows are reset to 20 in workspace although the rowcount in sys_user_preference is still 100.

On my PDI with Washington DC this seems to be working as expected as it is still showing 100 rows after relogging.

So depending on how much of an issue this is for your client/users maybe you can just wait for the upgrade (maybe it was even fixed before Washington - but i don`t have Utah or Vancouver instances available right now) instead of putting efforts to fix it (if possible) with a temporary solution.

Cheers!

Martin


View solution in original post

2 REPLIES 2

Martin iTSM
Tera Guru

Hey there,

i don`t have a solution for this - but i could reproduce what you describe in a client`s tokyo instance - after logging out the rows are reset to 20 in workspace although the rowcount in sys_user_preference is still 100.

On my PDI with Washington DC this seems to be working as expected as it is still showing 100 rows after relogging.

So depending on how much of an issue this is for your client/users maybe you can just wait for the upgrade (maybe it was even fixed before Washington - but i don`t have Utah or Vancouver instances available right now) instead of putting efforts to fix it (if possible) with a temporary solution.

Cheers!

Martin


Zmud1
Tera Contributor

Hi, does anybody have solution for this?