Sarah Hartmann
My feedback
14 results found
-
33 votesSarah Hartmann shared this idea ·
-
6 votesSarah Hartmann shared this idea ·
-
3 votesSarah Hartmann shared this idea ·
-
3 votesSarah Hartmann shared this idea ·
-
60 votesSarah Hartmann supported this idea ·
-
515 votesSarah Hartmann supported this idea ·
-
21 votesSarah Hartmann shared this idea ·
-
154 votesSarah Hartmann supported this idea ·
-
5 votesSarah Hartmann supported this idea ·
-
55 votesSarah Hartmann shared this idea ·
-
44 votes
An error occurred while saving the comment Sarah Hartmann supported this idea · -
167 votes
Hi all,
This is planned to be handled in the Primo Next Discovery Experience User Interface.
More details on the new interface planning can be found here -
Best regards,
Yael.
An error occurred while saving the comment Sarah Hartmann commentedAgreed! The current behaviour is very strange and not user friendly. And I don't think a tooltip would contribute much to a better user experience. Functions should only be displayed where they can be used, and it's confusing that Primo VE just changes the field selector when you choose the search type "starts with".
Sarah Hartmann supported this idea · -
73 votesSarah Hartmann supported this idea ·
-
197 votes
The Purchase Request library will be supported vi SIS/API and user update job, just as the Resoruce Sharing library is.
We’ll also look into making the Purchase Request and the Resoruce Sharing library be searchable in the users advanced search option.
Sarah Hartmann supported this idea ·
We would greatly appreciate the possibility to configure what data is being prepopulated.