Anurag Tripathi
Mega Patron
Mega Patron

Hi Everyone,

 

As an MVP I look at, and respond, to a lot of questions on the community and so here are a few suggestions from me that might help you ask the question in a better way:

 

  • Don't Assume People on this community as familiar with your problem: A lot f times people provide very less information and ask a very abstract question. You should avoid that, always read your question and ask yourself that a person who is completely unaware of this problem, will they understand the ask?
  • Screenshots help: Screenshots really help whenever you can give, whether it is script or forms behavior, so whenever you can, add screenshots.
    Make sure you embed the screenshots instead of adding them as attachments.
  • Don't just paste the problem statement your client gave: Some individuals just copy the requirement they received from the client 
    For EG: 'The calculation on Field XYZ is wrong for End Users'
    But what is the expected behavior, is it oob or custom calculation?
  • If you have a script, provide information on the logs : A lot of times people ask for help on script that is not working as expected and we even see logs(if not you should add logs/alerts). So in your question you should mention what log values are you seeing, this helps us understand how the code is working and till where.
  • If you paste screenshot of script, kindly paste the script also: It just gets easier for someone helping to copy/paste it and run /modify it.
  • Don't hesitate to write scripts: A lot of times people ask for scripts without willing to put any efforts themselves, I understand that not everyone is from a scripting background and so in some cases it is fair, but a lot of people who are working as a 'developer' should not be doing this. I encourage you to write the script when someone shows you a path, fi the script is not working you show it again and you will get the help. This will help you learn as well.
  • Provide enough information but avoid long paragraphs: While it is important to  provide all the necessary information, but it is also import to avoid long paragraphs as the person reading may get distracted, or might simply chose to ignore. Try to keep the information crisp and to the point, use bullets and paragraphs.
  • Correct Forum: Cross check that you are raising the question in the correc tforum, so that it can come in the radar of the correct set of people.
    For eg, if you have an issue with PDI, raise it in the 'Instance Help' forum.
  • Use Add Source: This makes a script more readable and just easy to process.

 

And Finally: The help you get on this community is from some of the best minds and absolutely free. So please show a little gratitude for people who help you by taking time out of their busy schedules.

 

Hope this helps.

-Anurag

Comments
Pranav Bhagat
Kilo Sage
Thank you for sharing Anurag.
Miguel Donayre
ServiceNow Employee
ServiceNow Employee

There is already a recent post VERY similar to this one. It was even a feature article. 

https://community.servicenow.com/community?id=community_article&sys_id=d450b434dbba1850fa192183ca961...

Anurag Tripathi
Mega Patron
Mega Patron

There are even more im sure, I just felt the need to write it down so I did.

Nicely put by Kieran.

-Anurag

Anurag Tripathi
Mega Patron
Mega Patron

Thanks Mate

hanaphouse
Giga Guru

Just to add, others forget to use the add source sample feature. It makes code reading much easier.

find_real_file.png

Koti1
Kilo Contributor

hii i have a query on ITOM. like we are developing a application for some company like amazon.amazon has 3 prob as assets.Now 1 customer using 1&3 prob. 2 nd customer 2&3.3rd customer using 1&3.if any prob down it has to create incident automatically using discovery.

Bowen Lu
Tera Contributor

thanks, it really help a lot

Version history
Last update:
‎10-29-2020 02:35 AM
Updated by: