Record Producer Application scope getting changed

[Saurabh Parwani]

Hi team,

We have few record producers in one of our applications and for those record producer 1 Variable set and 1 catalog client script lies in another application.

So when we install only 1st applications where we have our record producer then everything is fine record producer are installed in correct application scope and we are able to submit record producers.

But when we install the other application where we have that 1 variable set and 1 catalog client script then the scope of those existing record producer are getting changed.

Hence when we are submitting the record producer we are getting issue like setAbortAction is called from different scope.
 

Link to repos :
https://code.devsnc.com/dev/app-spend-catalog

https://code.devsnc.com/dev/app-spend-pop

https://code.devsnc.com/dev/app-spend-ppm

[Amit Gujarathi]

Hi @Saurabh Parwani ,
I trust you are doing great.

To address this issue, you can follow the steps below:

1. Identify the affected record producers: Determine which record producers are experiencing scope-related issues after installing the second application.

2. Review scoping and application dependencies: Understand the scoping of the applications involved and any dependencies between them. Ensure that the scope hierarchy is correctly set up and that the record producers, variable sets, and catalog client scripts are defined within the appropriate application scopes.

3. Update application scopes: If necessary, modify the application scopes to ensure that the record producers, variable sets, and catalog client scripts are aligned with the desired scope configuration. This may involve adjusting the scope of the existing record producers to match the scope of the second application.

4. Test and validate: After updating the application scopes, thoroughly test the functionality of the record producers. Verify that they can be submitted without encountering the "setAbortAction is called from different scope" error.

5. Apply best practices: Follow recommended guidelines from ServiceNow documentation to ensure proper scoping and avoid scope-related issues. The documentation provides insights into scoping concepts, converting global applications to scoped applications, information on record producers, and set values updates[

[Saurabh Parwani]

@Amit Gujarathi  This issue is coming only on latest Vancouver versions. but the Same codebase is working fine in Utah