Software updates - list of transformers that are affected
Hi,
Does anyone know of a method where I can readily identify which transformers are affected (ie need an update / fixed / superseded!) when updating from one version to another?
Whilst I know there is documentation with each release, is there an easy way to compile a list that could be read into a workbench?
I am also aware that each transformer has a version number.
I want to create a method for identifying which workbenches are going to break before updating the software!
I am hoping someone has already thought of this and the solution is already built…
Any help much appreciated.
Stu
Page 1 / 1
Yes, you will need to install the latest FME Form/workbench. Then open the “Workspace Statistics” workpspace template provided by safe software. They were asking for your feedback, but you can run it for your own internal needs instead.
You will need to copy the FME server/flow respositories directory to somewhere you can access with Workbench. Alternatively if you have workspaces saved on a file server, point the workspace statistics fmw there.
I will give you a report in excel of all the transformers that require upgrading.
Click ‘Show Changes’
Please note. You don’t have to upgrade transformers. It’s optional, if you find the new parameters developed helpful. There are only a few transformers that have seen significant processing time improvements such as the spatial operators like Clipper, StatisticCalculator, Spatial%, GeometryFilter/Validator, FMEServerJobSubmitter
If you have multiples of the same transformer, upgrade the first transformer early in the workflow, on the left of the canvas. These changes will save through to the same transformers
Watch out for transformers that get deprecated. You will need to find the new complimentary transformer for any deprecated transformers. As such, deprecated readers/writers cause far more problems in my experience…. e.g. formats:
Use GEODATABASE_SDE, ORACLE_NONSPATIAL, SHAPEFILE, XLSXR
Do not use SHAPE, ESRISHAPE, SDE30, XLS_ADO (all deprecated) ORACLE8I_DB
Thank you, James @j.botterill
Apologies for the delay in responding, I am just having too much fun on all of my projects!
I will look into this solution, something we were nowhere near thinking of, so this is a proper left-field surprise that we can run a workspace statistics workspace to do this.
Thank you again.
Stu
Yes, you will need to install the latest FME Form/workbench. Then open the “Workspace Statistics” workpspace template provided by safe software. They were asking for your feedback, but you can run it for your own internal needs instead.
You will need to copy the FME server/flow respositories directory to somewhere you can access with Workbench. Alternatively if you have workspaces saved on a file server, point the workspace statistics fmw there.
I will give you a report in excel of all the transformers that require upgrading.
Click ‘Show Changes’
Please note. You don’t have to upgrade transformers. It’s optional, if you find the new parameters developed helpful. There are only a few transformers that have seen significant processing time improvements such as the spatial operators like Clipper, StatisticCalculator, Spatial%, GeometryFilter/Validator, FMEServerJobSubmitter
If you have multiples of the same transformer, upgrade the first transformer early in the workflow, on the left of the canvas. These changes will save through to the same transformers
Watch out for transformers that get deprecated. You will need to find the new complimentary transformer for any deprecated transformers. As such, deprecated readers/writers cause far more problems in my experience…. e.g. formats:
Use GEODATABASE_SDE, ORACLE_NONSPATIAL, SHAPEFILE, XLSXR
Do not use SHAPE, ESRISHAPE, SDE30, XLS_ADO (all deprecated) ORACLE8I_DB
