Hello Developers,
I am trying to integrate some javascript features into znuny, but I am struggeling to deal with the backend data in the frontend.
E.g. I would like to access the ticket details and article details in the AgentTicketZoom, but I did not find a common way.
Since I assume there is the issue already solved in js, where shall I take a look how to re-use existing js code?
I assume that the .tt Data Hash/Object is somehow already mapped to js, but did not find it.
Can someone show me a sample how to use it?
What would be the alternative? to re-call again the REST api of znuny and re-access the data, which was already loaded?
Javascript API to access ticket and articles in AgentTicketZoom
-
- Znuny wizard
- Posts: 343
- Joined: 16 Apr 2016, 08:55
- Znuny Version: see in post
- Real Name: Hans
- Contact:
Javascript API to access ticket and articles in AgentTicketZoom
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users
-
- Znuny wizard
- Posts: 343
- Joined: 16 Apr 2016, 08:55
- Znuny Version: see in post
- Real Name: Hans
- Contact:
Re: Javascript API to access ticket and articles in AgentTicketZoom
no hints here?
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users
-
- Moderator
- Posts: 425
- Joined: 30 Jan 2008, 02:26
- Znuny Version: All of them ^^
- Real Name: Hannes
- Company: Znuny|OTTERHUB
Re: Javascript API to access ticket and articles in AgentTicketZoom
Hi,
I would doubt that this is "already" solved.
The Ticket and article information are rendered on server side.
The async widgets also wont load JS (JSON), they return html content.
Regards
I would doubt that this is "already" solved.
The Ticket and article information are rendered on server side.
The async widgets also wont load JS (JSON), they return html content.
Regards
-
- Znuny wizard
- Posts: 343
- Joined: 16 Apr 2016, 08:55
- Znuny Version: see in post
- Real Name: Hans
- Contact:
Re: Javascript API to access ticket and articles in AgentTicketZoom
afaik the template toolkit (tt-files) is having the option to convert perl hash to json.
so my first assumption is that znuny is having a "default" data structure (or a data tree) as a page model/object over all pages, which are working the tickets and articles.
If there would be a default page model, the model could already have a converted default js side json object.
If I understand you well, this is not the case?
So all pages are fully individually developed without a common page object?
so my first assumption is that znuny is having a "default" data structure (or a data tree) as a page model/object over all pages, which are working the tickets and articles.
If there would be a default page model, the model could already have a converted default js side json object.
If I understand you well, this is not the case?
So all pages are fully individually developed without a common page object?
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users