What are best practices when developing a service portal?

[Thomas Lindenho]

Hello!

I have talked to a SerivceNow customer lately who has started to develop a service portal to create and manage requests. They ran into some troubles, like

• Developers had issues overwriting their changes (on widgets and scripts)
• Hardly reuse of components/widgets 
• Performance issues when embedding widgets
• Poor development performance

I believe there are solutions. Therefore I am interested what are best practices when building a new service portal.

• Do you build it in a scoped application?
• Do you use update sets or application repository to release new versions?
• Do you use source control integration? How (branching)?
• Is it better to use the REST API or server scripts from widgets?
• What has to be considered in regards to platform upgrades?

Thanks a lot for any answers. Chances are high that my team has to build a service portal as well. And I don't want to run into the same issues.

Kind regards
Thomas

[Thomas Lindenho]

Thanks a lot for your detailed answers, much appreciated!

[Sumanth16]

Hi,

Please go through the below article:

https://community.servicenow.com/community?id=community_question&sys_id=35195131dba72700107d5583ca96...

Please mark it as helpful (or) correct if it helps 

Thanks,

Sumanth

[Thomas Lindenho]

Thanks for the link. I have found this one, too. The provided links lack the technical answers.