Documentation Required Before Application Publishing

[SahithiK04]

Hi Community,

We are currently preparing to publish a ServiceNow application and are working on the required documentation before moving to the publishing stage.

So far, we have prepared/documented:

• Application configuration details

• Positive and negative test cases

• Store listing information

We would like to understand if we are missing any important documentation or validation steps.

Could anyone with experience in publishing applications to the ServiceNow Store please advise on:

• Mandatory documentation required before submission

• Recommended templates or formats

• Installation/upgrade and security-related documentation

• Commonly missed items or reasons for applications being sent back during review

• Any checklist or best practices you recommend

Any guidance or experience would be greatly appreciated.

Thanks!

[Ankur Bawiskar]

@SahithiK04 

I have usually uploaded Design Document, Unit Test case document, Installation guide

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[SahithiK04]

Hi Ankur, thank you for sharing this. This is helpful.

We are currently preparing the documentation for an application that we are planning to publish, so I wanted to understand the documentation expectations a little better.

Apart from the Design Document, Unit Test Case Document, and Installation Guide, are there any other documents that you would typically recommend preparing for the ServiceNow Store submission/review process?

Also, is there any ServiceNow-provided template, checklist, documentation guideline, or sample document that you normally refer to while preparing these?

If you have any templates, sample documents, checklists, or references that you can share, it would be really helpful for us to understand the expected format and level of detail.

Thanks again for your guidance!