Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
CiviCRM Core
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container registry
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Development
CiviCRM Core
Commits
dbec742b
Commit
dbec742b
authored
3 years ago
by
totten
Browse files
Options
Downloads
Patches
Plain Diff
(NFC) MailingQueryEvent - Update docblock
parent
0029275a
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Civi/ActionSchedule/Event/MailingQueryEvent.php
+4
-7
4 additions, 7 deletions
Civi/ActionSchedule/Event/MailingQueryEvent.php
with
4 additions
and
7 deletions
Civi/ActionSchedule/Event/MailingQueryEvent.php
+
4
−
7
View file @
dbec742b
...
...
@@ -32,13 +32,10 @@ use Symfony\Component\EventDispatcher\Event;
*
* - Joining to business tables - to help target filter-criteria/temporal criteria on other entites.
* (Ex: Join to the `civicrm_participant` table and filter on participant status or registration date.)
* - Joining business tables - to select/return additional columns. Feed the data downstream for mail-merge/token-handling. As in:
* - (Recommended) Return the IDs of business-records. Use the prefix `tokenContext_*`.
* Ex query: `$event->query->select('foo.id AS tokenContext_fooId')
* Ex output: `$tokenRow->context['fooId']`
* - (Deprecated) Return detailed data of business-records. Ex:
* Ex query: `$event->query->select('foo.title as foo_title, foo.status_id as foo_status_id')`
* Ex output: `$tokenRow->context['actionSearchResult']->foo_title`
* - Joining business tables - to select/return additional columns. In particular, return the IDs of business-records that
* may be useful for token-handling. Use the prefix `tokenContext_*`.
* Ex query: `$event->query->select('foo.id AS tokenContext_fooId')
* Ex output: `$tokenRow->context['fooId']`
*
* There are several parameters pre-set for use in queries:
* - 'casActionScheduleId'
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment