Essentials of Automations: Exploring Attributes & Automation Parameters

SafeSoftware 561 views 42 slides Jun 19, 2024
Slide 1
Slide 1 of 42
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42

About This Presentation

Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “key...


Slide Content

Essentials of Automations:
Exploring Attributes &
Automation Parameters

Bailey
Knapp

FME Flow Technical Support
Specialist
Safe Software

Tim
Shin

FME Flow Technical Support
Specialist
Safe Software

Kate
Brillinger

FME Flow Technical Support
Team Lead
Safe Software

Welcome to Livestorm.
A few ways to engage with us during the webinar:


Audio issues? Click this for 4 simple
troubleshooting steps.

Poll: Have you ever used
FME Flow Automations?

Automation Webinar
Series
●May 29: Optimizing FME
Workflows with Parameters
●June 5: The Art of Triggers and
Actions in FME
●Today! Exploring Attributes &
Automation Parameters

Agenda
1What are Output Attributes & Automation Parameters?
2Demo: Build Automation using Attributes & Parameters
3Bonus: Intro to Split-Merge Block functionality
4Using Attributes and Parameters in an Automation App
5Q&A


Agenda

Automating processes saves
time & money, improves data
quality, helps businesses scale
and so much more.

1
What are Output
Attributes and
Automation
Parameters?

FME Flow Automations allow you to build complex enterprise integration workflows by sending
JSON-formatted messages between components (Triggers & Actions).







Output Attributes and Automation Parameters store the JSON key-value pairs in a user-friendly
format so they can be used downstream in the workflow.

Resource: Working with Output Attributes in Workflows


What are Output Attributes and Automation Parameters?

Event Attributes
What: predefined output attributes specific
to the trigger, internal and external action
type.

Why: to create dynamic workflows that
process event information in real-time.
What are Output Attributes and Automation Parameters?

Custom Attributes
What: output attributes that can be defined on a component by the user building the
automation.

Why: when the same action is present more than once in a workflow to prevent overwriting
certain attributes or use attributes from multiple events in the same downstream parameter.
What are Output Attributes and Automation Parameters?

Manual Parameters
What: output attributes that can be defined
manually through the editor, or imported from a
JSON file. They are only present when a Manual
Trigger is used

Why: allows users to create output parameters
that allow for different types of user inputs at
workspace runtime

Resources: Manual Trigger and Manual
Parameters Editor
What are Output Attributes and Automation Parameters?

Automation Writer Attributes
What: attributes that store attribute
values from each feature processed by a
workspace. They are present on the Run
Workspace Action only when there is an
Automation Writer in your workspace
Why: Enhance Automations
functionality by orchestrating data-driven
workflows.
What are Output Attributes and Automation Parameters?

Deployment Parameters
What: parameters that are created in
FME Form or Flow and stored in FME
Flow. They provide a way to define and
reuse text string, database connections
and web connection parameters in
workspaces shared between FME Flow
instances
Why: allows workspaces that are
uploaded to multiple FME Flow
environments to run without having to
update parameter values
What are Output Attributes and Automation Parameters?

Automation Parameters
What: text values defined by the user building the Automation for use at the Automation level
without ties to a specific component.






Why: reduce maintenance efforts by enabling you to reference the same value in multiple
places.
What are Output Attributes and Automation Parameters?

For ultimate flexibility use
attributes and parameters
to create dynamic
Automation workflows.
What are Output Attributes and Automation Parameters?

2
Demo: Build
Automation using
Attributes &
Parameters

Goal Block Key Result
Breakdown a State
into Counties & Blocks
for processing and
send a single email at
the end


Using Attributes and Parameters in an Automation
There are many
attribute and
parameter types, and
it’s confusing to know
when to use them.



Use Output Attributes
and Automation
Parameters to pass
information between
workspaces and send
messages
downstream.


Using Output Attributes,
Automation Parameters and
the Split-Merge Block allows
you to pass event, feature
attribute, or user-defined
information throughout an
Automation, and send a
single email at the end


Demo: Build Automation using Attributes & Parameters

Step One: Manual Trigger Parameters
●Provide a user-defined JSON message at
Automation runtime
●Create attributes from the JSON
key-value pairs
{“state”:“Hawaii”}
Note: This also applies to the Webhook Trigger


Resource: Run an Automation using the Manual Trigger
Demo: Build Automation using Attributes & Parameters

Step Two: Run Workspaces using
Automation Writer Attributes
●Create additional output port per Automation Writer Feature Type
●Use the Automation Writer to parse attributes out of a workspace downstream in
an Automation workflow
●Trigger one downstream event for every feature that enters the
Automation Writer





Resource: Building Integrations with the FME Flow
Automation Writer
Demo: Build Automation using Attributes & Parameters

Tip
To use Attributes and Parameters in a
Workspace Action, the Workspace
must contain Published Parameters!
Demo: Build Automation using Attributes & Parameters

Demo
Demo: Build Automation using Attributes & Parameters

Key Takeaways
●Manual triggers can be used to pass in user-defined messages at runtime as manual
parameters
●Automation Writers allow us to pass data downstream from one workspace to create
data-driven workflows
●Every feature that gets passed into an automation writer is submitted as a downstream
event.
○1 feature equals 1 event
Demo: Build Automation using Attributes & Parameters

Poll: How can we
consolidate workspace
actions?

3
Intro to the
Split-Merge
Block
Functionality

●Split-Merge Blocks will output one event
attribute per input
●Compatible with Automation writers
●Event attributes aren’t aggregated, you’ll only
receive information from the very last job



Resource: Job Orchestration with Automations
Step Three: Rethinking Attributes with the
Split-Merge Block
Intro to the Split-Merge Block Functionality

Step Four: Automation Parameters and Email
Recipients
●Automation Parameters can be used anywhere in an Automation!
●Great for repeatedly-used parameters (i.e: Email recipients, file paths)
●One single parameter to manage our Email To recipients

Resource: Send email from Automations
Intro to the Split-Merge Block Functionality

Custom Email Subject & Body using
Event Attributes
●Multiple attributes can be used in a single parameter
●Concatenate key values together or build custom text bodies
Intro to the Split-Merge Block Functionality

Demo
Intro to the Split-Merge Block Functionality

Key Takeaways
●Split-Merge Block allows you to output a single message for the final job in the block
●With Automation Parameters you can edit a single value and have it update everywhere
that it’s used in your automations.
●Use the Text Editor to add multiple attributes in a single parameter value.
Intro to the Split-Merge Block Functionality

4
Using Attributes
and Parameters
in Automation
Apps

Automation Apps
●Allow users to run Automations that
originate from a Manual Trigger as "apps"
from a web browser
●Apps are shared as URLs, and may be
presented through customizable web
pages
●Manual Parameters allow for user input
into the Automation from the App
Using Attributes and Parameters in Automation Apps

Allow multiple
users to pass
parameters and
run automation

Goal Block Key
Manual Parameters in an Automation App
Result
Difficulty
configuring and
customizing
workflow
parameters

Leverage
Manual
Parameters and
Automation
Apps

Users can trigger
Automations
with custom
parameters
taken as inputs
Using Attributes and Parameters in Automation Apps

Demo
Using Attributes and Parameters in Automation Apps

Key Takeaways
●Manual Parameters send values that can
be used as input throughout the
automation
●Automation Apps pass Manual
Parameters to the automation triggered
from the app
Using Attributes and Parameters in Automation Apps

6
Resources

Get our Ebook
Spatial Data for the
Enterprise

fme.ly/gzc


Guided learning
experiences at your
fingertips
academy.safe.com


FME Academy
Resources
Check out how-to’s &
demos in the knowledge
base
support.safe.com
Knowledge Base Webinars
Upcoming &
on-demand webinars

safe.com/webinars

7
Next Steps

We’d love to help you get
started.
Get in touch with us at
[email protected]
Experience the
FME Accelerator
Contact Us
A world where data is not just a
commodity but a catalyst for
real change.
fme.safe.com/accelerator



Next Steps

Claim Your Community Badge &
Dive into the new Community!
●Get community badges for watching
webinars
●community.safe.com
●Today’s code: 4H7HE4


Join the Community today!
Next Steps

8
Q&A

Thank You
Recap of Next Steps

1Join the FME Community
2Contact us
3Experience the FME Accelerator

Please fill out our
webinar survey
Tags