Community
Custom code in Agent
Links used in this discussion
Links used in this discussion
Pepa Kokes,
User (Posts: 32)
Feb 23, 2019 8:44:12 am EST
Support level: Free or trial
Would it be possible to extend the Agent builder ( https://www.remoteutilities.com/support/docs/agent-package/ ) with a way to run our custom code? There are at least two use cases where that would be very useful:
1) Use a different communication channel for sending the ID+password than just e-mail. For example, we already have a channel for automatic updates, online backup and reporting. We could use this channel to send the connection data to our servers, where any available tech could pick them up, click a link, which would execute the Viewer with the right command line directly, without having to type anything.
2) We could connect to our application's database, checking for any relevant information before even making the connection. We could, for example, read the customer's name from the database (to be displayed to the tech handling the case), or check for their support level in our systems (e.g., do they even have a support agreement? Do they have a specific tech assigned to handle their cases?).
I imagine a simple DLL with one exported function, such as:
BOOL AgentStartRequested(LPCSTR internetID, LPCSTR password, BOOL * canStart, LPCSTR * message)
The agent would load the DLL, check for the function, call it, then read the canStart parameter to determine the result and display the content of the message parameter.
pepak
1) Use a different communication channel for sending the ID+password than just e-mail. For example, we already have a channel for automatic updates, online backup and reporting. We could use this channel to send the connection data to our servers, where any available tech could pick them up, click a link, which would execute the Viewer with the right command line directly, without having to type anything.
2) We could connect to our application's database, checking for any relevant information before even making the connection. We could, for example, read the customer's name from the database (to be displayed to the tech handling the case), or check for their support level in our systems (e.g., do they even have a support agreement? Do they have a specific tech assigned to handle their cases?).
I imagine a simple DLL with one exported function, such as:
BOOL AgentStartRequested(LPCSTR internetID, LPCSTR password, BOOL * canStart, LPCSTR * message)
The agent would load the DLL, check for the function, call it, then read the canStart parameter to determine the result and display the content of the message parameter.
pepak
Conrad Sallian,
Support (Posts: 3049)
Feb 25, 2019 7:22:04 am EST
Hello Pepa,
Thank you for your suggestion.
Public API is on our wishlist for future versions, but unfortunately for now it isn't among our immediate priorities.
Don't hesitate to ask me if you have other questions.
Thank you for your suggestion.
Public API is on our wishlist for future versions, but unfortunately for now it isn't among our immediate priorities.
Don't hesitate to ask me if you have other questions.
* Website time zone: America/New_York (UTC -5)