From 0a1b4524bb9e69ed5fb066712d01fcba4effe720 Mon Sep 17 00:00:00 2001 From: Ivan Kohler Date: Fri, 5 Dec 2014 15:30:19 -0800 Subject: [PATCH] add condition on signupdate age, RT#31213 --- FS/FS/part_event/Condition/signupdate_age.pm | 44 ++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 FS/FS/part_event/Condition/signupdate_age.pm diff --git a/FS/FS/part_event/Condition/signupdate_age.pm b/FS/FS/part_event/Condition/signupdate_age.pm new file mode 100644 index 000000000..70b4bbd7b --- /dev/null +++ b/FS/FS/part_event/Condition/signupdate_age.pm @@ -0,0 +1,44 @@ +package FS::part_event::Condition::signupdate_age; +use base qw( FS::part_event::Condition ); + +use strict; + +sub description { 'Customer signup age'; } + +#lots of falze laziness w/cust_bill_age, basically just swapped out the field + +sub option_fields { + ( + 'age' => { label=>'Age', type=>'freq', }, + ); +} + +sub condition { + my( $self, $cust_bill, %opt ) = @_; + + my $age = $self->option_age_from('age', $opt{'time'} ); + + ( $cust_main->signupdate - 60 ) <= $age; + +} + +sub condition_sql { + my( $class, $table, %opt ) = @_; + + my $age = $class->condition_sql_option_age_from('age', $opt{'time'} ); + + "( cust_main.signupdate - 60 ) <= $age"; +} + +# i don't think it really matters what order, since we're a customer condition? +# this is for ordering different events for a customer +sub order_sql { + shift->condition_sql_option_age('age'); +} + +sub order_sql_weight { + -1; +} + +1; +1; -- 2.11.0