How to fix it

  1. Navigate to System Definition > Script Includes or check your error logs to identify the exact table, Script Include, or function being accessed across scopes.
  2. Go to System Applications > Cross Scope Access and check if a sys_scope_privilege record exists for your source app accessing the target resource.
  3. If no privilege record exists, click New and set:
    • Source Scope: Your scoped application
    • Target Scope: The target application or global scope
    • Target Name: Specific table name (e.g., incident) or Script Include name
    • Operation: read, write, create, or delete
  4. For broader access, navigate to System Applications > Applications and open the target application record.
  5. In the Accessible from field, select All application scopes or add your specific source application.
  6. If the target resource is in global scope, go to System Applications > Cross Scope Access > Application Cross Scope Access and create a new record.
  7. Set the Source Application to your scoped app and Target Application to Global or the specific target app.
  8. Check ACLs by navigating to System Security > Access Control (ACL) and filtering by the target table name.
  9. Review ACL scripts for conditions like gs.getCurrentApplicationId() or role requirements that might block cross-scope access.
⚠️

Granting broad cross-scope access can bypass security controls. Always grant the minimum necessary privileges for specific tables or Script Includes rather than full application access.

  1. If this is shared utility code, consider moving it to a global Script Include and setting Accessible from to All application scopes.
  2. Clear the application cache by navigating to System Diagnostics > Cache Statistics and clicking Flush Cache or restart the instance.
💡

Test your fix by reproducing the original operation. Check System Logs > All for any remaining cross-scope access errors to ensure all required privileges are granted.