Nick Ashcroft 2/15/2021 4:31:30 AM
thanks for the suggestion. Its not quite what I am after but shows how 'creative thinking' get get around some of the limitations of TeamDesk when trying to use it in an unconvetional way !
My goal is to set some default values/filtering of records based on some session based parameters.
example fictive scenario is a salesman who can sell both 'cars' and 'trucks'. The clients, services, products (cars or trucks) are often (but not always) different according to cars or trucks. Sales Person could be in teamdesk in one 'session' with his 'car selling hat' on and another in his 'truck selling hat'. In each session, the information should be based on which 'hat' he is wearing on that moment. Problem is that the choice of cars and trucks could easily be extended to planes, boats, submarines and more in future so 'hard coding' is to be avoided. I need to be able to, for example, analyse which clients take only cars, only trucks or both.
In user parameters I could indicate which 'hat' the user is wearing but he needs to actually have 2 hats on at the same time (different sessions) to easily alternate between them and have them isolated in different sessions. I could create multiple users but that would become costly in licensing !