Settings and activity
12 results found
-
3 votes
Brian Horrocks
shared this idea
·
An error occurred while saving the comment -
62 votesBrian Horrocks
supported this idea
·
-
96 votesBrian Horrocks
supported this idea
·
-
96 votesBrian Horrocks
supported this idea
·
-
93 votesBrian Horrocks
supported this idea
·
-
111 votesBrian Horrocks
supported this idea
·
-
115 votesBrian Horrocks
supported this idea
·
-
17 votesBrian Horrocks
supported this idea
·
-
20 votesBrian Horrocks
supported this idea
·
An error occurred while saving the comment Brian Horrocks
commented
We would also like to be able to auto-delete expired patrons. Additional parameters would be nice to have as well like PatronCodeID.
-
24 votes
An error occurred while saving the comment Brian Horrocks
commented
When checking out in LEAP, staff would like it to be more obvious when a patron has blocks on their account. Especially when the blocks would stop the patron from checking out items. Currently, from the patron checkout page, there is a small padlock and "BLOCKS" in red text, which is too subtle for some staff.
This can be inconvenient for staff and the patron because they scan several items only to realize the patron is blocked after scanning all the items.
Staff would like the block indicator to be more obvious, something like setting the Patron header div to have a light-red background color. See attached image with added css style:
<div class="patron-info row workform-heading" id="patron-info-pid123456" style="padding: 0px; background-color:pink ">
Brian Horrocks
supported this idea
·
-
49 votesBrian Horrocks
supported this idea
·
-
60 votesBrian Horrocks
supported this idea
·
Requested Change:
We would like to be able to configure Leap to match the Polaris Desktop Client's login behavior with regard to session branch selection.
Desktop Client:
When logging into the Polaris Desktop Client, the "Please select a branch for this session" dialog dropdown menu defaults to the Workstation's branch.
Leap:
When logging into Leap, the "Select your Branch and Workstation" branch dropdown defaults to the User's assigned branch.
Why:
At our organization, most staff are transacting in Leap on a desktop computer that is installed at a particular location and will only be used at that location. With very few exceptions, these computers will be signing into Leap using the branch where the computer is installed, independent of the staff user's default assigned branch.
We have staff who work at multiple branches and have noticed they accidentally sign into their staff user's default branch, even when they are working at a different location.
Solution idea:
Add a LEAP setting that will allow organizations to select which default branch is presented at login (workstation vs. user). In our case, we would want a global setting for LEAP workstations that always defaults to the workstation's branch. But some organizations might want a user-specific or workstation-specific setting that would override the global setting. There could be unique use cases where a user travels with a laptop and you might want to force a manual selection each time for that particular user or workstation (no default).