M
mparish
Guest
Back in version 4.3 you could use EDC to automatically store the rule messages to a database in order to provide an audit trail of execution. This feature was removed in version 5.x but we are considering bringing it back. If this is something you would like to see please leave comments (or simply vote) Some questions: On top of storing the RuleMessages in the Database, would you also want to store the payload in the Database so that you can cross-reference what RuleMessages applied to what payload? Should this be a service, which isn’t tied to EDC so that customers that haven’t bought an EDC license can still store RuleMessages in the Database? In version 4.x, the Studio’s Vocabulary - Database Access - Create Rule Messages Table was the only way to create the RuleMessages Table. Do you think this is good enough or do you think an alternative way to create the Table is needed? If you have an EDC license and have configured your Vocabulary to go against Database A, do you think you would want to store the RuleMessage in a different Database than A…let’s say Database B?
Continue reading...
Continue reading...