adminui.payload.downloadLink.extraContextPath=/${tif.instance.id}/${tif.node.id}
08 September 2023
Windows File Modifier now also supports XLSM file format, e.g. when creating PDFs.
Downloading the payload for a job must be done from the TIF instance which was executing the job. That is because the files are stored locally to that TIF instance.
When using a multi TIF instance setup behind a load-balancer / reverse proxy this requires some extra configuration in the proxy-server in order to route the request to the correct TIF instance.
As of this release, some new configuration options have been added to simplify this.
To add some extra context-path information to the URL, you can add this parameter to \${TIF_HOME}/modules/enovia/etc/module.custom.properties
adminui.payload.downloadLink.extraContextPath=/${tif.instance.id}/${tif.node.id}
As shown in the example above, you could use macros but you may also use static values. In the proxy server, you need to match on the context path and when forwarding to the backend TIF instance you need to remove the additional context path data.
Alternatively, you could append some extra information as query string parameters. This is shown below:
adminui.payload.downloadLink.appendInstanceId=true adminui.payload.downloadLink.instanceIdParam=x-tif-instance-id adminui.payload.downloadLink.appendNodeId=true adminui.payload.downloadLink.nodeIdParam=x-tif-node-id
Below is the list of fixed bugs as of this release.
Issue No | Description |
---|---|
956 |
Adress issue related to Apache POI, used for setting document properties, vs certain inflate ratios in the corresponding document files. |