In Service Portal, what benefit is there in using an Angular Provider instead of another widget?

[ITSM Dev]

N00b question.

In ServiceNow, what benefit is there in using an Angular Provider instead of another widget to handle some functionality? Any examples where it is especially useful?

[Marcin20 · Accepted solution]

Hi,

I have found this material that may be useful:

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

Best Regards,

Marcin

If my answer helped you in any way, please mark this answer as helpful and correct.

[ITSM Dev]

Thanks! I did find that video quite useful and it more or less answered my question.

Couple of take-aways that I got from it:

• Angular Providers allow creating re-usable client side JavaScript that can then be used to embed HTML or JavaScript functionality. Being that an Angular Provider only holds client side code, it is more lightweight than a widget.
• Examples shown in the video included embedding HTML segments and JavaScript functionality defined in an Angular Provider.
• An Angular Provider can be injected into a widget's Client Script simply by referring to the Angular Provider by name in the widget's Client Script arguments. Like as shown below.