Planning invoice in vifib is just good enough.

master/bt5/vifib_base/SkinTemplateItem/portal_skins/vifib_simulation/VifibInvoiceTransaction_postGeneration.xml

@@ -118,17 +118,17 @@ if related_order is not None and context.portal_skins.hasObject(\'erp5_simulatio
 if not invoice.hasTitle() and related_packing_list.hasTitle():\n
   invoice.setTitle(related_packing_list.getTitle())\n
 \n
-# initialize accounting_workflow to confirmed state\n
-confirm_tag = \'%s_confirm\' % invoice.getPath()\n
+# initialize accounting_workflow to planned state\n
+plan_tag = \'%s_plan\' % invoice.getPath()\n
 if invoice.getSimulationState() == \'draft\':\n
   invoice.activate(after_path_and_method_id=(related_simulation_movement_path_list,\n
   (\'immediateReindexObject\',\'recursiveImmediateReindexObject\')),\n
-  tag=confirm_tag).Delivery_confirm()\n
+  tag=plan_tag).plan(comment=translateString(\'Initialised by Delivery Builder.\'))\n
 else:\n
-  # call builder just same as after script of \'confirm\' transition\n
+  # call builder just same as after script of \'plan\' transition\n
   invoice.activate(after_path_and_method_id=(related_simulation_movement_path_list,\n
   (\'immediateReindexObject\',\'recursiveImmediateReindexObject\')),\n
-  tag=confirm_tag).Delivery_expandAndBuild()\n
+  tag=plan_tag).Delivery_expandAndBuild()\n
 \n
 # First set the invoice in the building state on the causality workflow\n
 invoice.startBuilding()\n
@@ -136,7 +136,7 @@ invoice.startBuilding()\n
 # Then an activity should put the causality state in diverged or solved\n
 invoice.activate(after_path_and_method_id=(related_simulation_movement_path_list,\n
   (\'immediateReindexObject\',\'recursiveImmediateReindexObject\')),\n
-  after_tag=confirm_tag).updateCausalityState()\n
+  after_tag=plan_tag).updateCausalityState()\n
 
 
 ]]></string> </value>

master/bt5/vifib_base/bt/revision

-341
\ No newline at end of file
+342
\ No newline at end of file