Skip to content

docs: Document Segment filter for Form submissions#798

Draft
promptless-for-oss wants to merge 2 commits into
mautic:7.2from
Promptless:promptless/segment-form-submission-filter
Draft

docs: Document Segment filter for Form submissions#798
promptless-for-oss wants to merge 2 commits into
mautic:7.2from
Promptless:promptless/segment-form-submission-filter

Conversation

@promptless-for-oss

Copy link
Copy Markdown
Contributor

Open this suggestion in Promptless to view citations and reasoning process

Documents the new 'Submitted a specific form' Segment filter introduced in PR #15964.

Changes

segments/manage_segments.rst

  • New section: Filtering by Form submissions - Documents the new filter available under 'Contact behavior and actions' that allows building Segments based on Form submission history
  • Lists all available operators: empty, not empty, including any of, excluding any of, including all of, excluding all of
  • Includes step-by-step instructions for using the filter
  • Adds a tip with a practical use case example

Trigger Events


Tip: Enable auto-create PR in your Configuration to review suggestions directly in GitHub 🤖

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Line 303)

New 'Submitted a specific form' filter added to Segment builder in PR #15964. Filter appears under 'Behavior and Actions' with operators: empty, not empty, including any of, excluding any of, including all of, excluding all of.

Source: mautic/mautic#15964

@adiati98

Copy link
Copy Markdown
Contributor

@promptless-for-oss please rebase to 7.2 branch.

Add new section documenting the Form submission filter for Segments,
including available operators and usage examples. Rebased onto 7.2.
@promptless-for-oss promptless-for-oss force-pushed the promptless/segment-form-submission-filter branch from 647f257 to a607d5b Compare June 27, 2026 07:18
@promptless-for-oss promptless-for-oss changed the base branch from 7.1 to 7.2 June 27, 2026 07:18
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

@adiati98 Done — I've rebased this onto the 7.2 branch and retargeted this PR's base to 7.2.

The branch now applies cleanly on 7.2. The accept.txt vocabulary entries (CKEditor, strikethrough) were dropped from the diff since they already exist on 7.2, so this PR now only changes docs/segments/manage_segments.rst.

@introfini

introfini commented Jun 28, 2026

Copy link
Copy Markdown

Thanks for putting this together! I reviewed the content against the implementation and it's accurate: the location (Contact Behavior and Actions), the filter label, and all six operators match the behaviour of the underlying ForeignValueFilterQueryBuilder.

One small wording suggestion, since these two operators are easy to mix up:

  • excluding any of — contacts who submitted none of the selected Forms.
  • excluding all of — contacts who did not submit the complete set of selected Forms (i.e. they're missing at least one; someone who submitted some but not all is still included).

The current text for excluding all of ("haven't submitted all of the selected Forms") is technically correct, this just adds the contrast for readers. Everything else looks good to me. ✨

…on filter operators

Per source PR author review (mautic/mautic#15964), contrast the two
easily-confused operators: 'excluding any of' matches Contacts who
submitted none of the selected Forms, while 'excluding all of' matches
Contacts missing at least one of the complete set.
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks for the careful review, @introfini! Updated the two "excluding" bullets to spell out the contrast:

  • excluding any of — Contacts who submitted none of the selected Forms.
  • excluding all of — Contacts who haven't submitted the complete set of selected Forms (they're missing at least one, so someone who submitted some but not all is still included).

All other operator descriptions, the steps, and the tip are unchanged, since you confirmed those match the ForeignValueFilterQueryBuilder behaviour. Pushed to the PR branch. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants