IRC between Lobo and I
jalama: dlobo my initial thought is you will also have to incorporate Drupal token integration
[11:01am] jalama: but if you can deal with that it would be a good thing
[11:01am] jalama: disclaimer I have little Rule scheduler experience
[11:02am] dlobo: jalama: for rules integration, we use civicrm mailer to send stuff
[11:02am] dlobo: so u can use civicrm tokens
[11:02am] jalama: oh right
[11:02am] dlobo: thats the way we did civimail + rules, seemed a lot easier that way
[11:02am] jalama: so they would set up a civimail for the people who registered then those who attanede
[11:03am] jalama: I see
[11:03am] dlobo: hmm
[11:03am] dlobo: dont think so
[11:03am] dlobo: ideally u'll do something like:
[11:04am] dlobo: 7 days before event, send mail to all registrants who ahve status: XXX/YYY/ZZZ
[11:04am] jalama: but the mail would have to be built in Civi right
[11:04am] dlobo: (and i think thats where rules scheduler comes in)
[11:04am] dlobo: jalama: the mail contents are just text box in the rules form
[11:05am] jalama: dlobo I''m more worried about the list of recipients
[11:05am] dlobo: the action which is done by civi-code would then use our mail infrastructure
[11:05am] jalama: how do we pass that to CiviMail?
[11:05am] dlobo: the registrants can be a smart group (for ultimate flexibility)
[11:05am] jalama: or the one off mail function
[11:05am] dlobo: jalama: its one off mail
[11:05am] jalama: maybe that's the answer
[11:05am] dlobo: not civimail
[11:05am] jalama: right
[11:06am] dlobo: but u r right
[11:06am] dlobo: if u have 100+ registrants
[11:06am] dlobo: we should think more along civimail
[11:06am] dlobo: since 1 off will never scale
[11:06am] jalama: we would need to be able to define a smart group from rules and pass that as a parameter/arg to CiviMail
[11:08am] jalama: or maybe we could have some sort of default token for event.xxx.registrants
[11:08am] jalama: that is passed as a group to civiMail