Restrictions to Scoped Applications

[Ian Elrick1]

Hi

Can someone point me to the definitive statement that describes limitations to scoped apps that can be developed and still count as scoped platform applications ? 

For instance, can scoped apps use tables inherited from task? Can they inherit from CMDB tables etc? Can scoped apps use approvals?

If they can do all of the above what are the things that scoped apps cannot do? What are the limitations to workflows in scoped apps? 

There is a licence model for an App User. I want to know all the conditions for an app to meet that licence model and not encroach on itil or whatever.

Thanks in advance.

Ian

[Deepak Ingale1]

Hello,

1) Scoped app can be extended out of TASK or TASK extended tables like sm_order ( See create from Service Template option, this option is visible if you have Service Management plugin install), shortly, you can create application extended out of TASK

2) It can have approvals as well, I did not see issue in creating approval records in scoped application

3) There are certain APIs which are not working in scoped app, like JSUtil.nil() or TableUtils() etc, but I wont say it is limiation since there are workaround available for these limitations ( Most of the limitations I would say )

4) Workflow I have not seen any limitations as well in scoped app, those work fine as in global scope

Below links will assist you to get more insights about scoped applications

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

https://community.servicenow.com/community?id=community_question&sys_id=1c10c721db98dbc01dcaf3231f96...https://community.servicenow.com/community?id=community_question&sys_id=71c387a5dbd8dbc01dcaf3231f9619a7

5) About licensing, its better to talk to account manager since these things can vary customer to customer and based on contract

Note: Please mark reply as correct if it has answered your queries.