Do you have a data workflow that you need to automate? Send it to us and we’ll show you how to build event-based workflows in our live webinar. As we run through real-world scenarios, you’ll learn how FME Server can be used to automate the flow of data between applications, making tedious data tasks a thing of the past! This includes an exciting preview of our new FME Server Automations functionality. Submissions for the webinar are closed, but you can always post questions and get answers on the FME Knowledge Center

1. Automating Enterprise Workflows with FME
Server
February 6, 2019

2. Your photo hereYour photo here
Holly Coxon
FME Server Technology Expert
Jennifer Luther Thomas
Technical Experts Team Lead
Behind the screen today...
Laura Wu
Technical Experts Team Lead
Your photo here

3. Agenda
● Directory Watch
● FTP Watch
● Schedule Database Updates
● CAD Validation
● Workspace Chaining
● Cityworks Salesforce to Jira
Thanks to everyone who submitted a workflow!

4. FME 2019.0 is still under development
Warning!
Everything you see today is subject to change probably going to change before release:
- Automations UI is currently being redesigned
- Terminology changes of nodes in Automations will change
- Nodes may change
BUT the methodology is still the same
Mostly aesthetic changes

5. “I’m looking for a way to monitor an input
folder and run an FME Server task when a
new file is saved by an external (not FME)
process).”

6. Directory Watch
● Monitor Folders both in FME
Server and external locations
● Can now filter incoming message
to only parse certain files
● No longer need a Topic!

7. “We use FME to download gas/oil well data to our SDE
from Colorado and New Mexico state agency FTP sites.
In the case of CO, we get data for the entire state. For
NM, we get data for the entire district that we operate
in.”
“Is there a way to use FME to select only those records
that are in our area of interest and write that to our
SDE? The record count would be greatly reduced and
our users’ portal experience enhanced.”

8. Use Feature Reader so we
can assign a spatial filter
Dataset = User
Parameter so it can be
set to the FTPWatch
JSON
Spatial Filter = Initiator
Contains Result
FTP Watch

9. “We want to use FME Server to update a
PostGIS instance from an ESRI SDE
overnight. We have a boundless exchange
where our clients view project data. We
want to create that data in SDE locally then
have it mirrored on a PostGIS instance we
have through boundless.”

10. No transformers!
SDE Reader PostGIS Writer - Table
Definition: ‘Copy from Reader’
‘Auto Connect Attributes’
SDE to PostGIS

11. Use Automations
Add a Schedule as a
Trigger
Add a Workspace
Action
Save and enable your
Automation!
Schedule the Workspace

12. “I need Digital Plan and As-Built Standards accessed so
someone can upload a DWG, enter project name, project
number, firm, name, etc. It will then process the DWG and
either pass or fail the drawing after validating it against a set
of predefined rules.
Once passed, it will add the project information and
annotation to the data. It will also clean up attribute names
and finally, Integrate the data into our ArcSDE database.
We would like to get an FME Server solution with a web front
end that can kick out emails on pass fail, when and why to
resubmit.”

13. The Back End
Workspace for validation and data processing tasks
Simple automation for sending emails

14. The Front End

15. The Front End

16. The Front End

17. “We have a multi-step process that consists of many workspaces
to process millions of features.”
Inputs
The raw data sources are multiple ESRI File Geodatabases
(FGDB’s) with state-based feature class layers, one state per FGDB.
The intermediate data source is a SQL Server database with
multiple nationwide layers, one layer per table. Native geometries
are used in the tables.
Outputs
The data delivery products are layers in ESRI Shapefiles and
FGDB’s and separated into regions with each format having
different schemas.

18. PART 1 – Data Ingest
The large majority of the state-wide FGDB’s have 4 main layers of
differing granularity that are loaded into SQL Server using a
python process.
Only one state that has an FME process to load the data into SQL
Server. There are also additional reference layers that are also
loaded by FME.
The FME processes are run on a Windows Server 2012 R2 VM with
FME Desktop installed. They are run manually as needed with
FGDB readers and SQL Server writers.

19. Add Directory
Watch as a trigger
Add a Filter and
Workspace Action
This will load the
incoming datasets into
the database
Part 1 - Data Ingestion

20. PART 2 – Data Delivery
After the SQL Server database is loaded with any state updates, an
FME Server runs multiple FME processes to create the data delivery
products.
Because the processes are running in Docker on linux, SQL Server
JDBC Spatial readers, Generic Shape writers and File GDB API
writers are used.
We eliminated any ESRI dependencies and setup multiple Views on
the SQL Server in order to query the database for the different
output regions.
We are currently using python to manually update the FME Server
through the API. Scripts load all resources and workspaces as well
as kick off all the jobs.

21. Extend Automation
Part 2 - Extract from database to shape and geoDatabase
Add another
Workspace Action
This will extract any
updated areas for the
delivery products

22. PART 3 – Post Processing
After the data delivery products are created, we take all the
Shapefiles and File GDB’s and run multiple python scripted
post-processes.
Unfortunately, we cannot run these on FME Server because we
have to take advantage of some of the ESRI ArcGIS tools to finalize
the products.
The first process corrects a difference between the File GDB API
writer and the ESRI File GDB writer. The attribute order is different
in the API writer.
The next process loads XML metadata into all the layers. And the
last 2 processes QC and Zip all the deliverables.

23. Part 3 - Product Finalization
Add another
Directory Watch as
a trigger
Add an Email Action
This will notify someone
when the newly extracted
data delivery products are
available for finalization

24. Chaining Workspace Options
Scheduler with
Job Queues
Notification
Service
FMEServer
JobSubmitter
But...

25. But...
● Time dependencies
● Notification Service interface is
not user friendly
● Using topic info requires a JSON
reader
● Cannot make alterations to
FMESJS in Web GUI
Automations ticks all the boxes

26. “Our GIS group currently receives map change requests (redlines) for
our sewer/drainage/water system in Cityworks. Our IT group also
uses JIRA as a task management application where we must log and
track all our GIS tasks and projects.
I’m very interested in trying to hit Cityworks and query for new redline
workorders (possibly by user), and automatically creating an issue in
JIRA. Once the issue has been closed in JIRA ideally I would like the
workorder to be closed in Cityworks.”

27. Integrate FME Server with
Cityworks
● Action Manager
○ Event = Work Order Created
○ Action = Webhook
● Link to FME Server Topic
POST URL: Message as Subscribe
Content

28. Part 1 - Create Issue in Jira

29. Part 2 - Close Task in Salesforce

30. 2 Notifications in a
single workflow
Add a Topic as a
Trigger
Add 2 Workspace
Actions
Automate the Workflow
Add an Email as a
Trigger

31. Thank you!
Get a free trial of FME at safe.com