4

Depending on your Trigger in the rule, I would suggest just adding a time-based condition. If contribution, add criteria «Field Value Comparison» for «Date Received» and set the operator to less than the desired date. If activity, use activity date. If new membership, use membership start date, and so on...


4

Welcome to SE. I think this may be a bug with Civirules 2.21, where something has obviously changed as I now see the action "Add Tag to entity" rather than "Add Tag to contact which was in 2.20. I also don't get offered any tags to select. I'm guessing you may have an older version on your Drupal site. Nothing in the release notes (https://lab....


2

This sounds like it might be a bug in CiviRules. I suggest that you raise an issue. Looking at the issues, #127 might be related.


2

By default, CiviCRM uses the default participant role specified in the event settings. As there is only one participant role defined per event in CiviEvent, the desired behaviour can't be achieved through CiviRules. When doing a batch import of participants, the role(s) can be set in the .csv-file. When manually registering participants, one or multiple ...


2

This table is used to prevent that cron triggers fire two times on the same day. So entries older than a day can be deleted. The table is also a help debugging. For example, in the 'Manage CiviRules' form, they are used to show the latest contact a rule is triggered for. This information possible dissapears if you delete the older entries. (But beware, in ...


2

This is not a direct answer but potentially this extension might help you to keep track of old addresses? https://civicrm.org/extensions/former-communication-data


2

Thanks for sharing your problem. As you can see there are a few outstanding issues with tags: https://lab.civicrm.org/extensions/civirules/-/issues?scope=all&utf8=%E2%9C%93&state=opened&search=tag As you are probably aware CiviRules is open source like the rest of CiviCRM. That means that issues will be fixed in a number of ways: organizations ...


2

There is no import/export function as far as I know but..... your rules will be saved in a few tables: civirule_rule will contain your rules civirule_rule_action will contain the combination of actions in your rules civirule_rule_condition will contain the combination of conditions in your rules civirule_rule_log will contain the logs of your executed rules ...


1

1/ if you have civirules installed then a/ you should see it listed as 'installed' at /civicrm/admin/extensions?reset=1 b/ you should find a CiviRules menu item under Administer (usually gets added at the bottom of the list) 2/ in terms of using it to send out a receipt, if you are wanting to include the amount they you may need an extension such as https://...


1

Edit after reading email api code: AFAICS, contributions should work. Please try a contribution token. Original: I'm afraid you have to code a new action maybe by extending the send-email-action to add the context. I'm having the same problem with a case and will tell you if I succeed. Token processing is WIP: https://lab.civicrm.org/dev/core/-/issues/1614


1

This Rule seemed to work fine but perhaps it misses a nuance you need: Contribution is added Linked Condition(s) Condition = Total Contributed Amount Description = Total amount all time (with status: Completed) >= 1 Linked Action(s) = Add Tag to Contact = Volunteer (The above will be viewable at https://dmaster.demo.civicrm.org/civicrm/civirule/form/...


1

There is no strange behaviour, just lack of information ;-) A trainee was using this e-mail address to create 'Activity'


1

I don't think you can do this (at least without development). Most significantly, there isn't any trigger from within the bulk mail system in Civirules so you would not be able to catch the bounces that don't put the email on hold. I suspect that adding that functionality would be very difficult as I doubt that these email bounces go near the sort of things ...


1

My solution to this isn't elegant, but it gets the job done. I simply added a little code with hook_webform_submission_insert that takes the original webform submission data and resubmits the essential details to a second webform as many times as the user bought tickets. That second webform serves as the official list of tickets sold and sends an email for ...


Only top voted, non community-wiki answers of a minimum length are eligible