Process Recommendations › Ways to Improve Processes › Reports › To Determine Expansion Conflicts

To Determine Expansion Conflicts

Developers performing subsetting frequently receive Modify or greater protection on objects included in their subsets as neighborhood objects. This can cause other team members to be downgraded when requesting one of the neighborhood objects for their development work. A common work-around to this problem is to override the downgraded subset, have the first developer upload, allow the second developer to download his/her subset, then have the first developer download his/her subset again. This involves many unnecessary uploads and downloads. This situation can be avoided by running a References report for scoped action diagrams before downloads.

This report lists the "called" action diagrams (which may be included as neighborhood objects depending on the expansion used). The developer can then explicitly scope on these objects for Access or Read Only to prevent future conflicts with other development team members. This also reduces the need to run costly expansion conflict reports.