Application scope access error: permission denied for target scope

No cross-scope access policy exists between the source application and target application scope to allow the requested operation. (high likelihood)

The cross-scope access policy exists but is configured with incorrect operation types or does not include the specific table, Script Include, or API being accessed. (high likelihood)

The cross-scope access policy is inactive or has been disabled, preventing the scope access even though the policy configuration appears correct. (medium likelihood)

The script is running in a different scope context than expected, such as when called from a different application or when scope inheritance is not working as anticipated. (medium likelihood)

The target resource has been moved to a different application scope since the original cross-scope access was configured, breaking the existing access policy. (low likelihood)

Step 1: Navigate to System Diagnostics > Log > Application Log and locate the specific error entry to identify the source application scope, target scope, and the exact resource being accessed.

Step 2: Go to System Applications > Cross-Scope Access and search for existing policies between the source and target application scopes identified in the error log.

Step 3: If no cross-scope access policy exists, click New to create one, setting the Source Scope to your application and Target Scope to the application containing the resource you need to access.

Step 4: Configure the cross-scope access policy with the appropriate Operation (read, write, create, delete) and specify the Target Table, Script Include, or API that your application needs to access.

Step 5: If a policy already exists, verify that it is Active and that the Operation and Target Table/Script Include fields match exactly what your script is attempting to access.

Step 6: Test the script execution again after saving the cross-scope access policy, as the changes should take effect immediately without requiring a system restart.

Step 7: If the error persists, check the Application Scope of the calling script in the System Logs to ensure it matches the Source Scope configured in your cross-scope access policy.

Step 8: Review the target resource in the Application Navigator to confirm it still exists in the expected application scope and has not been moved or deleted.