- What is your original issue/pain point you want to solve?
It’s a bit tricky, but my pain comes from the specific domain we are in: RealEstateAdministration-Outsourcing. We have clients (Zammad Orgs) and they have customers (Zammad Users). But those users can be related to different RealEstates. Hence User Klaus calls for organization HV GmbH and wants a problem be solveld for his house in Finkenweg 3 (He also owns Adlerstraße 9). So I need to capture this in a ticket.
The external data endpoint currently only allows me to provide a limiting search-param (which is good). But it would be ideal (and from GDPR-perspective necessary) to have for Klaus only a dropdown with his two assets. This could be “easily” achived, if the endpoint in the FE would also “interpret” other form-fields like #{customer.myId} allowing endpoint likemyserver.de/api/v1/assets/#{customer.myId}?search=#{search.term}
- Which are one or two concrete situations where this problem hurts the most?
The mentioned problem is critical for us and probably for everyone, who needs to differentiate fields in a ticket based on other fields. - Why is it not solvable with the Zammad standard?
It is the way the FE interprets currently the URL. This “interpretation” should find/replace fields with current values once the endpoint is called. This happens already for search, but not for other parameters - What is your expectation/what do you want to achieve?
I need to ensure only customers, who are entitled to se asset A can see it. This is not possible withouth more customizable Ajax-Calls
If there is any more useful information, feel free to share it all (e.g.: mockup screenshots, if something is UI related, or the API URL/documentation URL for a service you need a connection to).
Your Zammad environment:
- Average concurrent agent count: 50
- Average tickets a day: 20-100
- What roles/people are involved: Accounting, General Services, Management - we are a full-service outsourcer of services for “Hausverwaltungen”, hence our people have technical and/or accounting skills
Anything else which you think is useful to understand your use case:
Thank you and have fun.