How to get ATF test runs triggering cross-scope access requests?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2019 10:47 AM
I am trying to use ATF for a custom app.
It looks like when running the tests in the dev environment with Runtime Access Tracking set to "Tracking", the tests run nicely, but without triggering Cross-Scope Access requests:
When installing the app in the next higher environment (for example Dev Test) all tests fail due to missing Cross-Scope Access grants.
I can reproduce this in the Dev environment by setting Runtime Access Tracking set to "Enforcing".
The tests are created within the app, but need to access tables in global.
Preferably I'd like to understand how to get the ATF runs to trigger cross-scope access requests.
Thanks, Christian
- Labels:
-
Best Practices

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2019 06:30 AM
Hi Christian,
I don't think you'll be able to get ATF to generate the cross-scope access records, mainly because anything that ATF generates during a test will get rolled back at the end of the test. Generating those should really be a development activity that you take care of as you're building out your scoped application.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2019 06:37 AM
Hmm, that's what I also concluded. However, in that case, it would make sense to at least get some visibility IMHO.
My use case was maybe a bit unusual as well: In order to check / confirm correct role assignments, I added record queries against sysuser_has_role. So I kind of get that from inside the app scope those queries are maybe not expected. (Still on Madrid, so can't use the new "create user" ATF command yet. But that would also not allow checking which roles are actually available for a group member).
Thanks, though!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2019 06:32 AM
I am running into the same issue. In NY, I would not see an error at all. It would just stay there when I try to do a records lookup. Madrid gives a cross scope error.
Have you found a resolution? I am working w/ SNOW support but do now have a resolution yet. He did point to a PRB (PRB1370603), but it does not have a solution and is closed.
Regards,
Mon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2019 07:53 AM
Hi, yes that is "my" problem. I was advised though, that the Problem was closed as it was determined to be a product enhancement. At the same time there was a hint to also submit it as an idea to get more traction. It's here: Idea - track cross-scope violations via ATF runs maybe you want to "upvote" it 😉