Hi @richardtriesfme,
Have you looked into the FMEServerJobSubmitter transformer? Just connect it to the "updated" port of the ChangeDetector transformer (UpdateDetectorParcels in your case). But you need to create a new workspace and put in your CAD_Properties workflow.
You do not need to use the tester, just connect the "updated" port to the WorkspaceRunner or FMEServerJobSubmitter
Note: If you use FME desktop you should use the "WorkspaceRunner" transformer, however if you are using Server you should use the "FMEServerJobSubmitter" transformer
I hope this helps.
Hi @richardtriesfme,
Have you looked into the FMEServerJobSubmitter transformer? Just connect it to the "updated" port of the ChangeDetector transformer (UpdateDetectorParcels in your case). But you need to create a new workspace and put in your CAD_Properties workflow.
You do not need to use the tester, just connect the "updated" port to the WorkspaceRunner or FMEServerJobSubmitter
Note: If you use FME desktop you should use the "WorkspaceRunner" transformer, however if you are using Server you should use the "FMEServerJobSubmitter" transformer
I hope this helps.
Thanks, I need to run the Workspace/FMEServerJobSubmitter runner only after the entire rest of the first workspace has ran as properties depends on the finalisation of the parcels results. Is this possible?
If you would use the FeatureReader to read features for the second part, all the processes can be performed within a single workspace.
- Connect a single Sampler to the Updated, Inserted, and Deleted ports of the UpdateDetector,
- sample only the first feature (Group By: <not set>, Sampling Rate: 1, Sampling Type: First N Features),
- connect between the Sampler and the FeatureReader. Only if a feature is output from the Sampler, the feature kicks off the FeatureReader.
Thanks, I need to run the Workspace/FMEServerJobSubmitter runner only after the entire rest of the first workspace has ran as properties depends on the finalisation of the parcels results. Is this possible?
@richardtriesfme, right after the ChangeDetector if you want to start the new workspace.
In my case I would use a different approach; I would just add a FeatureWriter after the ChangeDetector (updated port) to write/save the data "lccgis.CAD_PARCELS then a FeatureReader in the to read the "lccgis.CAD_PARCELS" at the beginning of the "CAD_Properties" group to continue the same process within the same workspace.
It would be great to consider creating custom transformers to group your transformers.