-
Vincent Pelletier authored
Internally remember which identifiers have been created to prevent the system from allowing to create the same check twice if done in the same reception. Use composition category to remove the need for a dirty hack (string replacement). Use paths instead of titles as part of identifiers. Now that there is an object as part of the identifier, use serialize. Resource is set differently if the object is a check or a checkbook, move and duplicate setter use downward. Trigger a dummy tagged activity even when creating a check, like what's done when creating a checkbook. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@14551 20353a03-c40f-0410-a6d1-a30d3c3de9de
5041f302