Configure pre-filter in Assai DMS

Assai connector: delta prefilter (skip unchanged published files)

This feature reduces unnecessary file scraping for Assai publish-file deltas.

When enabled, the connector skips publish-file scraping only for metadata-only changes since the last pull.

The following table provides the configuration details:

Required or recommended Assai API parameters

For endpoint: {code} /api/customservices/dbi_document_revision_digitaltwin {code}, use the following:

• project_code

• is_latest=Y

• response_type=csv

• for_polling=Y (mandatory)

If columns are missing in default CSV view, include selected_columns=document_nr,revision_code,latest_change_date_subq,last_modified_pub_file_date,latest_change_date_pub_file

Date fields used by connector

These are the output CSV fields consumed by connector logic:

• latest_change_date_subq (metadata change date)

• last_modified_pub_file_date (publication file date)

• fallback - latest_change_date_pub_file (if last_modified_pub_file_date is not present)

  Note: The *_after and *_before fields are request filters, not output fields.

Last pull timestamp resolution

The connector resolves last pull timestamp exactly like %DeltaDate% request replacement:

• Uses runtime config values: StartingDate and IsFirstLoad.

• If IsFirstLoad=true, then last pull timestamp = DateTime.MinValue.

• If IsFirstLoad=false, then parse StartingDate.

Decision logic (when ProcessOnlyChangedPublishFiles=true)

This logic applies only to the publish_file type:

• Resolve lastPullTimestamp.

• Read metadata date from latest_change_date_subq.

• Read file date from the last_modified_pub_file_date (fallback latest_change_date_pub_file).

• If parsing fails, continue processing (safe fallback).

• If metadataDate > lastPullTimestamp and fileDate <= lastPullTimestamp, then skip scraping.

• Else, you can proceed with the processing.

The following table lists the behavioral scenarios:

• This optimization applies only to the publish-file path.

• The connector processes rows non-blockingly; if parsing or field issues occur, it still processes the row.

• Ensure selected_columns includes required date fields when Assai default view omits them.

Administrator Dashboard (ADDA) user interface

The following checkbox is available in ADDA for Assai connector configuration:

The following table maps UI controls to backend configuration settings:

User impact of enabling the prefilte

When unchecked (false):

• Connector processes publish-file rows as before.

When checked (true):

• Connector skips publish-file scraping for metadata-only deltas.

• Connector still processes rows where file content changed.

Dependencies and preconditions

• Assai delta requests must use for_polling=Y.

• CSV output must contain required date fields (through selected_columns if needed):

  • latest_change_date_subq

  • last_modified_pub_file_date (or latest_change_date_pub_file fallback)

Validation or support notes

If date fields are missing or cannot be parsed, connector falls back to processing (no data loss behavior).