Servicenow - application to collect data and submit ticket
up vote
0
down vote
favorite
What I would like to build is a small web forms applications that runs on windows computers, collects logged on user and computer details in the background and allows the end user to fill a form and submit a ticket.
For example, deploy the application to a specific clients (windows) computers. A shortcut on their desktop opens a client that in the background collects the logged on user details, computer details, network details and so on. Possibly with WMI service. In the background is also an API sync on the specific customer ServiceNow business services or custom fields. The end user then fills out the mandatory information and submits the ticket which is done via API/REST. After the ticket is submitted there is a screen showing the ticket number (with URL), possibly SLA information (expectations management) and help-full links.
I've been looking for an example or some solutions, but have not found much about the topic. Other than "Help the Helpdesk" which is a little different (client data collector that submits the data to ServiceNow CMDB but no ticket form).
End goal is to decrease the amount of pre-populated data from end users and reduce Help-desk time spent on recurring questions like, what computer are you using, is the problem affecting you or many users, when did the issue start, etc.
I'm hoping that someone can point me into the right direction.
wmi servicenow servicenow-rest-api
add a comment |
up vote
0
down vote
favorite
What I would like to build is a small web forms applications that runs on windows computers, collects logged on user and computer details in the background and allows the end user to fill a form and submit a ticket.
For example, deploy the application to a specific clients (windows) computers. A shortcut on their desktop opens a client that in the background collects the logged on user details, computer details, network details and so on. Possibly with WMI service. In the background is also an API sync on the specific customer ServiceNow business services or custom fields. The end user then fills out the mandatory information and submits the ticket which is done via API/REST. After the ticket is submitted there is a screen showing the ticket number (with URL), possibly SLA information (expectations management) and help-full links.
I've been looking for an example or some solutions, but have not found much about the topic. Other than "Help the Helpdesk" which is a little different (client data collector that submits the data to ServiceNow CMDB but no ticket form).
End goal is to decrease the amount of pre-populated data from end users and reduce Help-desk time spent on recurring questions like, what computer are you using, is the problem affecting you or many users, when did the issue start, etc.
I'm hoping that someone can point me into the right direction.
wmi servicenow servicenow-rest-api
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
What I would like to build is a small web forms applications that runs on windows computers, collects logged on user and computer details in the background and allows the end user to fill a form and submit a ticket.
For example, deploy the application to a specific clients (windows) computers. A shortcut on their desktop opens a client that in the background collects the logged on user details, computer details, network details and so on. Possibly with WMI service. In the background is also an API sync on the specific customer ServiceNow business services or custom fields. The end user then fills out the mandatory information and submits the ticket which is done via API/REST. After the ticket is submitted there is a screen showing the ticket number (with URL), possibly SLA information (expectations management) and help-full links.
I've been looking for an example or some solutions, but have not found much about the topic. Other than "Help the Helpdesk" which is a little different (client data collector that submits the data to ServiceNow CMDB but no ticket form).
End goal is to decrease the amount of pre-populated data from end users and reduce Help-desk time spent on recurring questions like, what computer are you using, is the problem affecting you or many users, when did the issue start, etc.
I'm hoping that someone can point me into the right direction.
wmi servicenow servicenow-rest-api
What I would like to build is a small web forms applications that runs on windows computers, collects logged on user and computer details in the background and allows the end user to fill a form and submit a ticket.
For example, deploy the application to a specific clients (windows) computers. A shortcut on their desktop opens a client that in the background collects the logged on user details, computer details, network details and so on. Possibly with WMI service. In the background is also an API sync on the specific customer ServiceNow business services or custom fields. The end user then fills out the mandatory information and submits the ticket which is done via API/REST. After the ticket is submitted there is a screen showing the ticket number (with URL), possibly SLA information (expectations management) and help-full links.
I've been looking for an example or some solutions, but have not found much about the topic. Other than "Help the Helpdesk" which is a little different (client data collector that submits the data to ServiceNow CMDB but no ticket form).
End goal is to decrease the amount of pre-populated data from end users and reduce Help-desk time spent on recurring questions like, what computer are you using, is the problem affecting you or many users, when did the issue start, etc.
I'm hoping that someone can point me into the right direction.
wmi servicenow servicenow-rest-api
wmi servicenow servicenow-rest-api
asked Nov 10 at 5:44
Skuli Axelson
4291817
4291817
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236320%2fservicenow-application-to-collect-data-and-submit-ticket%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown