ATF Test fails with error "Security restricted: Execute operation on API '' from scope ' was denied"Issue When executing a Scoped ATF test on an instance different from the Scoped application development instance, the tests might fail with a cross-scope error if they use Javascript. For example, Custom scripted step configurations or Server side script steps. Security restricted: Execute operation on API '<API NAME>' from scope <CUSTOM APPLICATION SCOPE>' was denied Examples of common ATF APIs are: StepResult.setOutputMessage and Step.sibling CauseThe application was developed on an instance where runtime access was set to tracking. In relation to ATF, this means that cross-scope records are automatically created/approved during test execution, and deleted/rolled-back afterward.In the target instance, if the runtime access is set to enforced, the records will need to be explicitly created for the cross-scope access to be allowed as they are not automatically approved. See more about runtime tracking here.ResolutionCreate cross-scope records for each ATF API that you need to execute: Identify which API caused the failure from the Test results.Make sure that you are in the application's scope.Navigate to the 'Application Cross-Scope Access' menu item and create a new cross-scope record.Use the following configuration: Target Scope: GlobalTarget Name: <API IDENTIFIED IN STEP 1>Target Type: ScriptableOperation: Execute API operation.Status: Allowed Run the test and repeat the procedure if more APIs are identified