Added Best practices which will help to reduce the issues during instance scans.

Coding Best practices/CONTRIBUTING.md

@@ -0,0 +1,12 @@
+Add commensts to your code
+use descriptive function and variabe names
+construct resusable functions
+Avoid complex glide record quiries
+use GlideAggregate for aggregatre oprations.
+dont use hard code values
+avoid dot walking to the sys_id of reference fields
+prevent recursive buisness rules
+Avoid dom manipulation
+aviod using gs.log in scoped apps
+dont chnage the security manager default behaviour
+avoid infinte loops for event generation.

Coding Best practices/README.md

@@ -0,0 +1 @@
+These best practises help to reduce the code pitfalls and number of issues during instance scans.

Create Keep Database footprint small/CONTRIBUTING.md

@@ -0,0 +1,5 @@
+Maintain Audit delete and audit relations tables using table cleaner
+Optimise or maintain the attachment and attachment documents tables
+Activating/Adding table cleaners
+Reduce over additing
+lower the duration of table rotation.

Create Keep Database footprint small/readme.md

@@ -0,0 +1 @@
+The given best practises help the to maintain the database foorprint small and improve the instance scan

Integration best practices/CONTRIBUTING.md

@@ -0,0 +1,6 @@
+Create a unique account for each integration.
+Don't add itil role to integration account.
+Index the coalesce field after veryfing all coalesce field are correct.
+Use Dat stream for large data sets.
+Use event driven integrations instead of scheduled integrations. eg: instead of daily job to trigget the API to get foundational data from third party, use event driven ( share the master data import set table API to third party to send the data whenever there is any update.)
+Use most reliable authentication methods (oAuth or Certifcater based)

Integration best practices/README.md

@@ -0,0 +1 @@
+This integration best practises help to maintain proper connnections and performanance and improve the instance scan.