Hey folks,
I've been tinkering with writing a local procedure to populate some default values for new consitiuents, but i really don't want to run a procedure at high frequency, and even so...its just not looking like the way to go...So i went for a coffee and thought about it;
I then found TG_CUSTOMER_INSERT, and in a few minutes i was done! But, is there anything wrong with this? It'll probably get screwed up on version updates huh? Is there a better way?
I thought of calling another LP from LP_CUSTOMER_RANK, but that is only called on TG_CUSTOMER_UPDATE, not necessarily INSERT...which may be fine, but might not...On second thought, it wouldn't really work because if a keyword is unchecked, it is removed from TX_CUST_TKW, so you couldn't really see if someone unchecked it.
Thoughts? Anyone?
Thanks
James
It really is not supported to change exiting triggers or add additional triggers to application tables. With the existing framework for local procedures, support has an easy way to disable the customizations if there is a problem in order to see if the customization is the cause. If you start adding triggers, we don't have this ability and support becomes very difficult.
On the positive side, starting with version 11 you will have the ability to create service plug in code that will essentially do the same thing with a lot more flexibility and granularity.
In the meantime you can use LP_CUSTOMER_RANK--it is called with when a new constituent is added as well.