Add Cross Scope Privilege to App in Studio?

[ctsmith]

How does one handle cross scope privilege in moving apps built in the studio between instances?  For example, I have an app that needs to access a script include in the Global scope and I changed the include to allow for all scopes.  That doesn't get captured in the app.  What's the best practice here?  Fix Script to add the cross scope records?  Something else?

Thanks!

[Pradeep Sharma]

Hello Chris,

Yes, you are right. Changes related to global scope are not captured in your scoped application file. You can create an update set in GLOBAL scope to capture changes related to global files. This is assuming that the application is not targeted to be released to store. The reason I mention this because changes related to global files are not published to store.

- Pradeep Sharma 

[ctsmith]

Okay, thanks for the advice. So is the idea to move all the cross scope records that have been created during my development into a global UDS and commit the UDS after the app is installed in the next instance?

Yep, this is not for the store.  But... if it was, how would this be handled?  No cross scope records to global, period?  Not allowed?

[Pradeep Sharma]

To clarify cross scope records are captured in scoped app. What is not captured is if you change/modify the global scope field column i.e in this case you have updated it to "Allow application scopes". Yes changes like this are not allowed when it comes to store app. Also before I modify those settings I would check if there is any scoped API or any other workaround to fulfill the same requirement.

The changes related to global scope can be committed to the target instances once the scoped app is installed.

I hope this answers your question.

- Pradeep Sharma

[ctsmith]

Good point.  I am talking about two different things here.  The cross scope records AND the change I made to script include record.