Repository navigation
Idea for Forms Lookup's #330
Replies: 3 comments
|
Hi @Shadowtech87 - thanks for the detailed write-up. Some of this is in 5.4.0 already, and the rest is planned in a way that builds on it. In 5.4.0
How it works today: Equipment, Infrastructure and Location lookups do work on the portal once you tick Customers can use this on the portal on the field, and a customer only ever sees their own company's records. The People lookup is staff-only on purpose, because it's your staff directory. Next, building on the same setting:
Both will be added alongside the class option rather than replacing it, so nothing you set up now will need redoing. |
|
ok the lookup for people makes sense from an ITSM / MSP view. I was looking at this from an internal companies IT department. So the initial limitation makes sense now. Would almost have to have an exclude from lookup or something. |
|
Thanks @Shadowtech87 - that's a really useful distinction, and it's the one that decides how this gets built. For an MSP, letting customers search the staff list is a no; for an internal IT department, employees looking each other up is normal. So when People lookups come to the portal, it'll be something you switch on, not a default:
I've noted the internal-IT case on the plan so it's designed for, not bolted on later. |
Uh oh!
There was an error while loading. Please reload this page.
Is it possible to allow end users in a specific group to have lookup permissions. Such as I'm creating forms for employee change or offboarding. The lookup and people option is there but it only functions inside the analyst view. If i could allow specific portal users that are part a specified group access that would be useful.
In addition to this if there were also ways to say limit the scope so lets say I give access to lookup a CMDB item, I don't want them to be able to look up everything so if there were ways to filter what they could/couldn't see. Another option would be a more advanced query builder but not sure how that would play out.
The idea I'm working on for this is for say creating a list of Job Positions. I could create them in the CMDB and then do a CMDB lookup that only returns the Names perhaps. That way I could build my list of positions and maintain it in one place rather than having to have the list of positions in the Onboarding ticket, position change ticket, etc.
With the forms "Only show this when" condition logic we could also possibly build something where they have a selection of the department first and that might be a lookup of its own. Then the Position drop down would only show job titles for the appropriate department.
All reactions