TIF 2025.3.0 Release Information
This release was published 2025-08-31
Data Mapping
A new configuration type called datamapping have been added to allow re-map values from the ENOVIA/3DEXPERIENCE format into another format.
In contradiction to using a stylesheet, which typically is used to restructure the structure of the data, the new data-mapping feature will only focus on translation / transforming values from one format to another.
The data mapping is referenced from within the payload configuration like shown below:
<Payload>
<TableContent outerElement="bill-of-materials">
<Table ref="PartBasic.xml" />
<DataSet ref="SingleLevelEBOM.xml" />
<DataMapping ref="DefaultMapping.xml" /> (1)
</TableContent>
</Payload>| 1 | Referencing the datamapping. |
The data mapping itself will not conduct any additional database calls for the transformation, it will operate upon the fetched data via the used table.
To get a better understanding over the capabilities of the data mapping itself, please look at this document.
REST ID Locator - Macro Support for Custom Responses
The response from the REST service can be customized if the ID locator does not meet certain conditions. This functionality has now been extended to also support resolving the response content from macros.
For example:
<IdLocator type="tnr">
<AllowWildcards>false</AllowWildcards>
<IfNotFound statusCode="200" contentType="application/json">
{
"error_code": "E0003",
"reason": "Object not found",
"item_type": "${pathparam_0}",
"item_name": "${pathparam_1}",
"item_revision": "${pathparam_2}",
"tif_instance": "${tif.instance}",
"custom_key": "${job.java.a.b.c.TheResolver:the-key}",
}
</IfNotFound>
</IdLocator>Please read more from here.
REST Service - Multipart File Upload
When invoking the create/update integration via a configurable REST service, it is now possible to upload the files using multi-part file upload instead of posting a ZIP archive.
A multipart request are internally handled as if they were submitted as part of a ZIP archive.
Example via CURL:
curl -X PUT -u creator:tif http://localhost:8181/enovia/jaxrs/service/file-upload-test/DOCUMENTS/ABC-00001/A -F "file=@test.doc" -F "fi le=@test.xslx" -F "file=@/c/temp/data.json"
And in the create/update integration configuration, one needs to specify that a ZIP archive is being used and point out the main data file.
<CreateConfiguration>
<InputFormats>
<Zip>
<InputFiles>data.json</InputFiles>
<Transformer>
<JSON charset="UTF-8" rootElementName="Data" elementNameFallback="Items" arrayItemElementName="Item" />
</Transformer>
</Zip>
</InputFormats>
...
</CreateConfiguration>Payload Data Access
A new user role has been added to make it possible to restrict users from accessing payload data via the Administration UI.