Description

BridgeWorkerScanner scans a folder for new XML files that define new documents to be imported into ENOVIA. The XML folder and format are the same as those used to manage the update Part in ERP and Post AR file of the publication feed in the ERP.

The only difference is in the header of the XML document, the document's root tag must specify that the requested action is a document import:

<Root action="ERPImportDocument">


This also works if the root tag is named ERPImportDocument:

<ERPImportDocument>

       ...

</ERPImportDocument>


Treatment

The source XML file can be converted to Bridge using a conversion file using XSL technology. The XSL document to use is set in the VISWorker.properties configuration file.

Options for importing documents include:

########################## DOCUMENTS related configuration ###############################

#Default type used for ERP import document

visbridge.erp.import.document.default.type = Document


#Default policy used for ERP import document

visbridge.erp.import.document.default.policy = Document Release


#Default vault used for ERP import document

visbridge.erp.import.document.default.vault = eService Production


#Document revise copy files from current object, or not

visbridge.erp.import.document.revise.copy.files = 0


#Notify by email when document is created

#Available formats:  Person:user1;Company:Company Name;Group:Software Engineering;Role:ctx::VPLMAdmin.Company Name.Default

visbridge.erp.import.document.output.mail = Person:user1


# Location of the XSL transformation file for the IMPORT create document process

# This is a UNC path

visbridge.erp.import.document.import.xsl = \\\\VSOL-DEV2017X/visbridge-temp/document/import/xsl/DDPSImportDocument.xsl


# Location of the XSL transformation file for the EXPORT create document process

# This is a UNC path

visbridge.erp.import.document.export.xsl = \\\\VSOL-DEV2017X/visbridge-temp/document/import/xsl/DDPSExportDocument.xsl

#How access to the object from outside of 3DEXPERIENCE - to add to the CAS URL

visbridge.erp.external.url.object = /common/emxTree.jsp?objectId=


# Enable deletion of the heavy files in case of success

# Default = enable = 1

visbridge.erp.import.success.files.deletion = 1


A message must then be published to notify of a new treatment.