- cleaned up the code for using namespaces

- fixed LISP error

intranet-ubl.info

@@ -14,12 +14,13 @@
         <vendor url="http://www.project-open.com/">]project-open[</vendor>
         <description format="text/plain">Includes export functionality from ]po[ financial documents to the Oasis UBL Universal Business Language XML format</description>
 
-        <!-- No dependency information -->
+        <provides url="intranet-ubl" version="3.3.1.1"/>
 
         <callbacks>
         </callbacks>
         <parameters>
-        <!-- No version parameters -->
+            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="UblExportConverterProc"  default="im_package_ubl_invoice2ubl" description="What procedure to use for exporting UBL documents? The reason for this parameter is that existing users might want to continue to use &quot;bugy&quot; exports in even if there are newer or better versions available. The reason is that the customer might have created a script on the other side that actually depends on these &quot;bugs&quot;..."/>
+            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="UblExportPathUnix"  default="/web/projop/filestorage/ubl" description="Path to the directory on where to write UBL documents for batch export."/>
         </parameters>
 
     </version>

sql/postgresql/intranet-ubl-create.sql

@@ -12,3 +12,11 @@
 --
 -- This module just exports (future: imports) XML documents
 -- in UBL formal
+
+
+
+-- Add a flag to the im_costs table to remember whether the
+-- cost item has already been exported or not.
+alter table im_costs
+add ubl_exported_p char(1) default 'f';
+