Next/Previous Navigation

  • Updated on Mar 21, 2025
  • Published on Feb 11, 2025
  • 2 minute(s) read
  • DL
  • Migration Team
 Prev Next

How to Configure Next/Previous Navigation

To enable Next/Previous Navigation, follow these steps:

  1. Navigate to Site Configuration → {Module} → Proofing and Comments.

  2. Click Edit Settings.

  3. Locate the option Proofing Next/Previous Navigation Criteria and enter the desired filter criteria.

  4. Click Save to apply the changes.

Filter Criteria Examples

Here are some supported filter criteria examples

Important: The filter criteria in the examples below have been validated against specific customer use cases. Therefore, there is no guarantee that other customer use cases are fully supported.

Navigation Rules to keep in mind

  • All filters are ignored except for the one set in the online proofing settings.

  • If no sorting is specified in the query, the default module sorting will be applied.

  • Sorting cannot be performed on fields of type calculation/concatenation, as their values are not stored in the database.

  • The Next and Previous buttons will navigate across the entire module search results, regardless of where the item was originally opened (e.g., from a widget with a defined filter or an inline module filtered by a parent item).

  • If the item does not match the Proofing Next/Previous Navigation Criteria, clicking Next or Previous will redirect the user to the nearest item that matches the filter criteria.

  • A blank page will be displayed for items that either have missing files or are in a file format not supported for proofing.

Example 1:

SELECT * FROM MODULE_612 FD WHERE FD_8444 = :currentItem_FD_8444

Explanation:

  • MODULE_: A string representing the module ID where online proofing is enabled

  • FD_: The field ID representing the module’s link to the main (parent) module.

  • :currentItem_FD_: This instructs the query to fetch all items in the module where the value of the specified field (FD_) matches the field value of the current item.

Example 2:

SELECT * from MODULE_NAME_Pages FD
WHERE FD.FD_NAME_Status = 4003
and FD.`FD_NAME_Remove Reviewers from Widgets` not in (currentUserIdFromUserModule())
and (
FD.`FD_NAME_Reviewer: Marketing` in (currentUserIdFromUserModule()) or
FD.`FD_NAME_Reviewer: Creativity` in (currentUserIdFromUserModule()) or
FD.`FD_NAME_Reviewer: Shop` in (currentUserIdFromUserModule()) or
FD.`FD_NAME_Reviewer: Purchasing` in (currentUserIdFromUserModule()) or
FD.`FD_NAME_Reviewer: Financing` in (currentUserIdFromUserModule()) or
FD.`FD_NAME_Reviewer: Pool` in (currentUserIdFromUserModule())
)
ORDER by PAGES.`FD_NAME_Text Catalog ID/Catalog Structure` ASC

Explanation:

  • MODULE_NAME_: A string representing the proofreading module name.

  • ORDER BY: Specifies the field definition by which the filtered list will be sorted. Please note that only one field can currently be specified as the sort field. The field types that are supported in sorting are the same as across the system. For example, you cannot sort by fields that are not stored in the database, such as calculation or non-searchable concatenation fields.

  • FD.FD_NAME_: Field names representing filtering criteria for the navigation item list. There are no limitations on the number of fields you can specify for the query, but it is the configurator's responsibility to ensure that the query is valid.

     

Related articles