Uses of Record Class
com.kingsrook.qqq.backend.core.actions.permissions.fieldaccess.FieldAccessHelper.PendingExactMatch
Packages that use FieldAccessHelper.PendingExactMatch
Package
Description
-
Uses of FieldAccessHelper.PendingExactMatch in com.kingsrook.qqq.backend.core.actions.permissions
Methods in com.kingsrook.qqq.backend.core.actions.permissions that return FieldAccessHelper.PendingExactMatchModifier and TypeMethodDescriptionCorePermissionEnforcer.checkReadCriteria(AbstractTableActionInput input, List<QueryJoin> queryJoins, QQueryFilter filter, Collection<String> additionalFieldNames) For read-style actions that are being enforced: check READ on every joined table (explicit or implied by the filter), and that the filter / additional field names satisfy field access policy. -
Uses of FieldAccessHelper.PendingExactMatch in com.kingsrook.qqq.backend.core.actions.permissions.fieldaccess
Methods in com.kingsrook.qqq.backend.core.actions.permissions.fieldaccess that return FieldAccessHelper.PendingExactMatchModifier and TypeMethodDescriptionFieldAccessHelper.assertCriteriaAllowed(String tableName, List<QueryJoin> joins, QQueryFilter filter, Collection<String> sortGroupAggregateFieldNames) Check filters and ordering before querying; successful exact searches are audited once per table.FieldAccessHelper.assertCriteriaAllowed(String tableName, List<QueryJoin> joins, QQueryFilter filter, Collection<String> sortGroupAggregateFieldNames, boolean checkExactMatch) Criteria-only mode has no fingerprints, guardrail callbacks or audit events.