WorldServer - Scoping configuration for new projects has changed. Why is this happening?

Our projects are being created using a different scoping configuration than the one used previously. What could be the cause for this behaviour?

Configure the Cost Model(s) in Management >> Business Rule Linkage > Project Types, applying the one that contains the desired scoping configuration. You can configure this for all languages or you can apply different Cost Models to certain languages. The projects created will automatically apply the scoping configuration defined in the selected Cost Model.

1. Select the Project Type.
2. Select the Processing tab.
3. In the Cost Models section select the default cost model for all locales, or
4. Select the advanced options checkbox and specify a Cost Model per locale (as displayed below):



5. Save the Project Type and the specified Cost Model (and its respecting scoping configuration) will be used during the next project creation.

There can be three reasons for this change of behavior:

1- The new projects with the changed scoping configuration have been created with project types that use no Cost Model while previous projects used a Cost Model associated with a different scoping configuration. If a project type has no Cost Model associated with it, it will apply the default scoping configuration, to be found under Management > Linguistic Tool Setup > Scoping Configurations

2- The new projects with the changed scoping configuration have been created with project types that use a different Cost Model than previous projects. The two Cost Models use different scoping configurations.

3- Previous and current projects were created with a project type that has no Cost Model associated with it, but the default scoping configuration has been changed. This will affect all projects created after this change.
 

This article might be relevant:

WorldServer - can I create a project using a scoping configuration that is not the default one?