Affects Version/s: 10.10
Currently, when operation Document.SetMetadataFromBlob is called in an automation script triggered by a Before document modification event handler, it calls CoreSession.saveDocument(DocumentModel (see here), which causes recursive calls.
Saving the document must be an option (e.g. using a save parameter), like it is done in several operations that update the document's properties (e.g. Document.SetProperty).
- in Studio, define the following metadata mapping in a XML extension:
- define an event handler, triggered by event Before document modification for documents of type Picture, running the following automation script:
- log in the Web UI
- create a Picture document without an attached blob
- attach an image containing the metadata mentioned in the metadata mapping above
the metadata is extracted from the image file and the document property is set with its value
the metadata is extracted from the image file but the document property is not set. If the automation tracing is activated, a lot of logs should be generated in the server.log file, showing recursive calls