When talking about generic approaches for integration Zammad with external systems (e.g. Asset Management, DMS, etc.) it would be great to have a generic approach beyond the REST API. To enable the Community for contributing and conceptioning new integrations, a generic attribute type “JAVA Script” could be a game changer.
Example:
When trying to implement a CMDB database solution in Zammad, the current product capabilities only offer limited integration depth by using the object attribute format “external data source” and for content syncronizations there is only Webhook/API or Email available. CMDB databases usually have a quite generic solution and database design but the process details in combination of CMDB and Zammad often have the requirements of:
- Enabling search and assignment functionalities beond “user<->asset”
- Enabling change process logics and ticket<->CMDB synchronisations
For this pupose the solution could be:
- providing a dedicated “JAVA Script” (text input field), that simply execute/submit the entered code on foreseen destination to modify the screen/results delivered in the UI in Zammad
This general approach may have positive sideeffects in the Community, where all “integration codes” can be published and shared easily the the community contribution is enhances. Thinking this to an end, Zammad could generate a public library of easy custom integrations to 3rd party solution.
Possible benefits:
The CMDB database integration in Zammad in the logics/designs of the “idoit” integration can be easily adapted and re-used for all other CMDB databases (Snipe IT, Baramundi, etc) by simply utilizing the “external database” and “Java Script” attribute formats in individual combinations.
OS: any
Size of implementation: any
Use Cases: any
verticals: any