I need help in knowing when glide.email.inbound.max_body_chars this was introduced

Bathanapall
Tera Contributor

He Team,

 

Want to know when was this "glide.email.inbound.max_body_chars" introduced.

 

We don't have this property in our system. So assuming this came with OOB package with default size limit.We see the email errored out with character limit error from MAY 2022 in our system.  But if someone can help me with the exact or approximate date and which release this was introduced it will be very helpful.

 

I also referred the article but did not get the date introduced. 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0785037

 

Thanks in advance,

Mahesh.

6 REPLIES 6

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @Bathanapall 

 

As per the KB update from 2023, which is about two years ago, the change was introduced around four releases back. However, it’s difficult to specify the exact release name.

 

DrAtulGLNG_0-1753268076048.png

 

 

DrAtulGLNG_1-1753268134350.png

 

 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

GlideFather
Tera Patron

Hi @Bathanapall 
you asked the same question 2 weeks ago:
https://www.servicenow.com/community/itom-forum/when-was-this-property-introduced-in-servicenow-quot... 

Was that information as accepted solution not sufficient?

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


yes it was helpful, but however we have a couple emails with this error showing up from May 2022 in our system.  So, it should be introduced even before 2023. To double confirm this, I have put this question again

Ok ok and what does the error message from 2022 say?

(it might be nearly impossible to debug something from 2022... is it really important for the 2025 reality?)

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */