Versions Compared

Old Version 1

changes.mady.by.user Julver Petrova

Saved on

compared with

New Version Current

changes.mady.by.user Stanley Neychev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Power Admin tries to find everything that is associated with the configuration object you've selected. This way, you can fix or update any broken or unwanted correlations. However, when scanning for dependencies Power Admin looks for direct matches - elements referring to that object by its name or idID. This approach allows you to clearly see the direct references to the object , instead of spending time filtering out the indirect ones first.

On the other hand, CMJ searches for everything referenced by and to a specific configuration object - be it a direct or indirect dependency. It's designed like this so that it doesn't miss any important associations and break the target instance configuration.

Infotip

For example …

If you search for filters where the project A is used, here is what will happen:

  • Power Admin will show you results from all filters where there’s a direct reference to the project, i.e., project = ABC and project != ABC;

  • CMJ will show you results from all filters, i.e. project = ABC, project != ABC, and project != XYZ because projects different from XYZ means all projects that are not XYZ which includes ABC (ABC != XYZ).

...