- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2023 12:37 PM
Seeing an issue in Toyko, where there is no Source Control option for Citizen Developers w/ sn_app_eng_studio.user role, even after the linking an app to source control. Admin's can see it fine.
Per https://docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/concep... -- After your admin has linked an application to Source control, all application developers on a non-production instance can perform these actions.
I've tried going into delegated developer control panel for the app, changing them from OWNER to CUSTOM and giving access to source control (plus owner defaults). That makes it visible, but you can't select it.
Thanks!
Solved! Go to Solution.
- Labels:
-
App Engine Studio
-
Source Control
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 02:14 PM
My solution was:
- Going into App Engine | Colloboration | Descriptors
- Clicking on Owner
- Adding source_control role to Development Permission Sets tab related list.
*Note: I tried adding source_control directly to the user PRIOR to figuring this out during and it would not work. There is something with the way App Engine Studio Owner permission OVERRIDEs the out of box delegated developer roles.
Unsure why ServiceNow doesn't mention Application Colloboration within the relevant pages on the doc site. Seems like it would really help out to have it linked here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/app-engine-studio/con...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2023 12:12 PM
Hello! I was able to replicate the issue you're seeing above in a relatively untouched instance.
In addition to everything you've done thus far, give the following a try: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/task/giv...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2023 09:44 AM
It did not work.
- I've tried giving them source_control role.
- I've tried setting this system property: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/task/giv...
- I've tried https://docs.servicenow.com/bundle/utah-application-development/page/build/applications/task/delegat..., but the user already has "OWNER" permission. There is no further ability to assign source control to owner.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 02:14 PM
My solution was:
- Going into App Engine | Colloboration | Descriptors
- Clicking on Owner
- Adding source_control role to Development Permission Sets tab related list.
*Note: I tried adding source_control directly to the user PRIOR to figuring this out during and it would not work. There is something with the way App Engine Studio Owner permission OVERRIDEs the out of box delegated developer roles.
Unsure why ServiceNow doesn't mention Application Colloboration within the relevant pages on the doc site. Seems like it would really help out to have it linked here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/app-engine-studio/con...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 02:40 PM
Thanks for the updating this. If you are logged into the Docs site you should see the option to provide feedback at the bottom of the page. Just click the down arrow and leave a comment letting them know how the page can be improved. It'll create a record for the Docs team and they'll take a look!
As for the AES permissions, that does make some sense. I know that when you grant someone permissions to use AES they are granted APP SPECIFIC permissions/roles when they create an app or they are added as a dev to an existing app. So I would be that if you looked through your user's roles if you'd see something like sn_dd_appname_sourcecontrol instead of just "source_control".
