GuidesAPI
DocumentationAPICommunitySupportLog In

Add Prioritized and Deprioritized Entry Points

Prioritizing Entrypoints

OverOps allows you to define packages that will be prioritized over other entry points in the call stack.

  1. Open Settings by clicking Settings in the top right corner of the OverOps dashboard.

This opens the Settings dashboard for the environment you're in (you can see the environment in the upper left corner of the screen).

  1. Under the General Settings tab, select Entry Points - Prioritized.
Prioritized EntrypointsPrioritized Entrypoints

Prioritized Entrypoints

  1. In the Packages field, enter the packages that will be grouped as a single entry point, and then click Add.
  2. Next, in the Classes field, enter the classes that will be grouped as a single entry point and then click Add.

Note that you can add multiple values (separated by a space and comma or by a semicolon (:).

Deprioritizing Entry Points

The entry points automatically detected by the system aren't always the most relevant entry point, so you also need to be able to mark certain packages and classes as a lower priority (for example, common entry points that group events such as logins, common security filters, authentications, etc.). This means that their information is still stored (rather than just sending them to the third-party blacklist), and they'll still be identified as entry points - as long as there are no other options in the call stack.

  1. Under the General Settings tab, select Entry Points - Deprioritized.
Deprioritized EntrypointsDeprioritized Entrypoints

Deprioritized Entrypoints

  1. In the Packages field, enter the packages that will be grouped as a single entry point, and then click Add.
  2. Next, in the Classes field, enter the classes that will be grouped as a single entry point and then click Add.
    Note that you can add multiple values (separated by a space and comma or by a semicolon (:).

What’s Next