►
From YouTube: FactSet + Adaptive Cards
Description
During this 23-minute Developer and Citizen Developer-focused demo, FactSet engineers Matt Pineau and Andrew Curtice share how FactSet has been using Adaptive Cards for last 1.5 years. FactSet - a financial services company, utilizes and has extended Adaptive Cards in their Signals product to proactively deliver brief and atomic information to customers. Adaptive Cards are integrated through Power Automate into Microsoft Teams and Outlook. FactSet’s WorkStation product uses the Extensibility feature of Adaptive Cards in its Fusion UI renderer to deliver responsiveness across platforms with little code. Q&A throughout. This demo is taken from the Adaptive Cards community call – October 2021, recorded on October 14, 2021.
Demo Presenters:
• Matt Pineau (FactSet)
• Andrew Curtice (FactSet)
Supporting materials:
• API - signals-api | https://developer.factset.com/api-catalog/signals-api (includes the /events/adaptive-cards URL endpoints AND a document Client Workflow and Triggers for each Signal, that shows example adaptive cards.
• General website - FactSet.com | http://factset.com
Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos
A
Hello:
everyone,
my
name
is
matt,
I'm
a
senior
engineer
at
factsa
we're
a
financial
data
services
company,
and
we
want
to
give
you
a
little
presentation
today
on
what
we
do
and
how
we've
been
utilizing
adaptive
cards
for
the
last
gosh,
maybe
year
and
a
half
now
so
we've
been
we've
been
using
it
pretty
extensively
and
it's
worked
really
well.
So
we
want
to
dive
into
some
of
that.
A
So
first,
I'm
just
going
to
give
you
guys
a
brief
overview
of
our
company,
then
we're
going
to
dive
into
a
little
overview
of
signals,
which
is
the
project
that
we
work
on.
Specifically.
We
want
to
talk
about
why
adaptive
cards
is
perfect
for
our
use
case
and
why
we
chose
to
sort
of
go
that
route,
and
then
we
want
to
provide
some
examples
of
some
cool
stuff
that
we've
built
out
using
that.
B
In
today's
fast-paced
world,
taking
your
ideas
from
concept
to
execution
quickly
is
critical
to
developing
innovative
approaches
and
tackling
complex
problems.
Factset
offers
the
ability
to
seamlessly
discover,
evaluate
and
implement
the
data
you
need
within
your
existing
workflow
expand
your
catalog
of
data
with
the
open
factset
marketplace,
the
destination
for
best-in-class
data
and
solutions
from
factset
and
third-party
providers,
leverage,
factset's,
deep
expertise
and
data
integrity
and
connectivity
to
unlock
the
true
power
of
data.
We've
pre-linked
data
provided
by
carefully
selected
sources
with
our
proprietary
data,
such
as
ownership
supply
chain
and
fundamentals.
A
We're
a
financial
services
company
and
we've
been
around
for
a
while
and
we're
looking
to
integrate
all
of
these
data
points
and
service,
all
sorts
of
user
classes
across
the
industry,
and
so
one
of
one
of
the
problems
that
we've
seen
more
well.
I
guess
for
a
little
while
now
is
the
fact
that
we
just
have
so
much
information
that
our
clients
historically
have
had
to
like
pour
over
tables
and
charts
and
stuff.
A
So
what
we
want
to
do
is
we
we
create
this
signals
product
which
is
supposed
to
be
actual
insights,
that
sort
of
find
our
clients
as
opposed
to
them,
having
to
dig
through
it.
So
some
examples
here,
essentially
yeah.
We
want
to
overcome
this
information,
overload
and
focus
on
meaningful
research.
So
it's
sort
of
a
method
of
aggregating
different
content
sets
into
a
normalized
way
and
meeting
our
clients
where
they
are
to
provide
a
brief
hint
at
sort
of
what
might
be
interesting
to
them
and
then
next
steps
for
how
to
investigate
it.
A
So
I
think
it's
probably
easiest
to
look
at
some
examples.
So
these
are
some
examples
of
signals
that
we've
collected
from
a
series
of
different
content
sets
that
we
have
and
we
have
our
own
in-house
cognitive.
So
one
of
the
cool
ones
here
is
s
p,
500
predictions,
so
we're
actually
predicting
when
a
company
is
going
to
be
added
to
the
s
p.
A
We
work
with
a
lot
of
third
party
data
providers
such
as
news,
but
also
credit
rating
companies,
esg
companies
to
collect
data
there
and
transform
those
into
a
normalized
signal
and
then
also
just
rules
based.
You
know
some
some
conditions
are
met
for
a
company,
a
data
point
changes
and
all
of
a
sudden,
you
know
something
like
an
m.
A
sale
was
announced
right,
that's
an
event,
and
we
can
just
trigger
a
signal
like
that.
So
we're
collecting
all
of
these
content
sets
and
trying
to
provide
meaningful
information
for
our
clients
from
them.
A
This
is
an
example
of
one
that
could
be
useful
to
someone.
So
this
is
the
s
p,
500
predictions,
so
one
of
our
clients
might
come
in
to
start
doing.
Research
on
a
company
right
say
this
mpwr
company
and
the
first
thing
they
see
at
the
top.
Is
that
hey
we're
predicting
that
this
is
going
to
go
into
the
s
p
500?
A
We
can
see,
then,
that
it
follows
up
with
a
street
account
when
it
actually
happens.
So
a
breaking
news
banner
that
it
was
added.
You
know,
seven
days
later,
so
we're
able
to
give
folks
a
jump
on
on
some
of
this.
The
things
that
might
be
happening
under
the
scenes
that
they
would
have
to
you
know
collect
data
from
across
multiple
applications
to
really
to
really
figure
out
for
themselves.
A
A
It's
probably
too
big
to
be
a
signal
because
all
of
a
sudden,
it
just
becomes
you
know
a
new
report,
and
so
we've
we've
worked
to
follow
this
kind
of
idea
and
build
out
all
of
the
ui
representations
of
our
signals
as
adaptive
cards.
So
we
have
one
of
our
you
know.
Flagship
products
is
the
factset
workstation
a
series
of
of
web
applications
and
we've
integrated
into
there
with
sort
of
a
fact
set
styled
adaptive
card.
So
this
is
some
adaptive
card
data.
A
C
A
Card
payloads
are
by
nature
very
small,
so
that
works
with
our
product
fact
search,
which
is
provides.
You
know,
type
type
of
head
cards
as
someone's
typing,
and
we
can
quickly
flash
that
information
to
them
and
catch
their
attention
at
a
reasonable
speed
and
again
off
off
platform.
You
know
this
is
all
provided
through
an
api
first.
So
if
we
sell
our
api
to
a
client-
and
they
want
to-
you-
know,
extend
our
adaptive
cards
or
you
know
just
have
that
ui
representation
right
off
the
bat
we
can.
A
A
Adaptive
cards
as
a
really
sort
of
good
idea
and
way
to
to
implement
all
of
this
so
continuing
on
here's,
here's
sort
of
an
example
of
the
power
of
using
this
as
an
adaptive
card
so
because
we
have
all
of
our
ui,
as
in
this
adaptive
card
format,
we're
able
to
set
up
microsoft
flows
for
for
our
clients.
So,
for
example,
we
we
can
build
this
out
so
that
when
a
user
gets
a
certain
type
of
email
from
anywhere
really
but
theoretically.
In
this
example,
it's
a
fat
set
alert.
A
A
To
just
sort
of
again
find
meet
the
clients
where
they
are
and
surface
that
information
without
them
having
to
check
every
single
portfolio
company
that
they're
watching
for
the
day
every
single
day.
So
you
know
we
we've
we've
loved
adaptive
cards
for
the
microsoft
integration.
A
lot
of
our
clients
use
microsoft
products
so
that
alone
being
able
to
push
into
outlook
microsoft
teams.
A
All
of
these
different
products
has
been
huge
for
us,
but
sort
of
a
problem
that
we've
had
is
that
a
lot
of
companies
have
their
own
styles
style
signatures,
the
css,
that's
really
driving
the
cohesiveness
of
a
product.
So
we've
tried
a
couple
of
approaches
to
apply
this,
and
I
think
it's
alluded
to
in
the
docs
extensibility
that
adaptive
cards
provides
just
beyond
the
native
renderer.
A
So
one
example
of
this,
we
actually
were
able
to
implement
our.
What
we
have
is
sort
of
what
we
call
the
fusion
design
system.
It's
the
way
to
hook
up.
You
know,
responsiveness
throughout
our
applications,
all
of
our
styles
different
fonts
and
whatnot-
that
sort
of
facts
certify
for
lack
of
a
better
word,
the
ui
here.
So
using
this
idea
of
extensibility
and
overwriting,
the
internal
render
functions
that
microsoft
provides
us.
A
We
were
able
to
do
something
as
simple
as
first
of
all,
override
some
of
the
global
styles
and
then
just
override
a
couple
of
elements,
namely
the
column
set
and
columns
to
be
transformed
into
what
we
call
flex
layouts
and
flex
cells.
So
what
you
get
is
that
these
two
are
sort
of
they
they
get
rendered
using
that
same
renderer,
except
instead
of
columns.
It'll
render
all
of
that
data
inside
of
a
flex
cell,
and
you
can
see
it
actually
breaks
on
the
iphone
x
and
becomes
rows.
So
you
know
to
do
that.
It
wasn't.
A
It
really
wasn't
a
lot
of
code
and
I
think
that
that's
just
sort
of
a
powerful
example
of
how,
without
waiting
for
responsiveness
from
microsoft,
which
has
a
whole
lot
of
other
problems,
you
know
making
it
work
in
teams
and
outlook
and
all
these
other
integration
points
you
can
kind
of.
Do
it
yourself
with
not
a
lot
of
lift
awesome.
E
That
is
super
cool
to
see.
I
love
that
you
guys
took
advantage
of
that.
We've
been
we've
been
chipping
away
at
responsiveness
internally,
haven't
really
been
able
to
share
much
yet
because
again,
we
have
to
solve
it
in
every
platform
which
has
its
own
quirks,
but
that's
really
cool
to
see
I've.
I've
always
wanted
to
sort
of
see
that
happening
where
columns
can
just
grow
into
a
flex
style.
E
A
It
is,
it
is
javascript
based,
it
will
render.
I
mean
we're
rendering
all
of
our
web
apps
as
as
javascript.
I
I
believe
I
don't
work
on.
You
know
the
mobile
team
or
anything
like
that.
So
I'd
have
to
double
double
check,
but
the
idea
is
that
these
are
sort
of
view
components
under
the
hood
that
do
enter
in
in
it's
supposed
to
be
across
the
board.
Any
screen
width
properly
yeah,
so
so
it
is.
It
is
web-based,
though
okay
gotcha
yeah.
So
that
was
one
thing
and
that's
sort
of
the
newer.
A
A
So,
in
fact
that
you
know
we
have
this
concept
of
an
infographic,
which
is
a
styled
text
block
and
what
you
would
end
up
doing
is
writing
how
that
can
compile
down
to
adaptive
cards,
which
would
just
be
sort
of
two
column
sets
with
a
text
block
so
that
when
the
same
schema
and
data
points
are
plugged
into
the
either
renderer
the
factset
one
inside
our
products
renders,
with
factset
styles
and
fapset
components,
but
the
adaptive
cards
one
keeps
that
keeps
that
parity.
So
you
can
see
here
we
actually
implemented
a
table.
A
D
F
F
Now
we
want
to
have
even
more
than
that,
so
we
wanted
to
have
a
solution
where
we
can
build
out
these
cards
to
display
in
multiple
environments,
but
we
didn't
want
to
have,
to
you
know,
manage
multiple
different
cards
for
different
environments.
So
what
we
have
here
is
just
an
extension
of
the
adapter
cards.
That
kind
of
allows
us
to
keep
our
inside
of
our
internal
application.
A
This
is
this
is
an
example
of
we
initially
built
it
out,
and
we
wanted.
You
know
the
adaptive
card
for
the
microsoft
products
and
that
integration
point,
while
also
keeping
you
know
view
and
being
able
to
keep
it
looking
proper
inside
of
our
own
products,
and
so
what
we
did
was
we
built
this
designer
so
that
we're
not
building
out
a
view
component
every
single
time,
and
this
actually
builds
up
that
schema
for
for
both
cases
right,
so
it
adds
on
those
fds
properties
that
signify
to
our
renderer
hey.
F
So
this
is
that
that
second
element
that
you
were
seeing
in
that
last
slide
that
infographic
group,
which
is
really
just
two
different
text
blocks,
and
you
can
see
in
the
highlighted
parts
on
the
left
side
there
that
you
know
those
are
our
extensions
to
the
adapter
card
schema
where
we
kind
of
just
add
some
hints
to
the
renderer
saying
this
text
block
here.
We
actually
want
this
to
be
one
of
our
existing
components
that
we
have
already
written
and
view
and
just
the
way
that
the
adapter
card
schema
is
laid
out
made.
F
So
we're
using
view-
and
it's
you
know
pretty
easy
for
us
to
have
this-
get
mapped
to
just
two
view:
components
for
the
the
different
infographic
text
blocks
and
then
you
can
see
on
the
right
hand,
side
how
this
adapted
card
json
ends
up
getting
rendered.
So
on
the
top
side,
you
just
have
the
regular
text
blocks
with
the
bolder
weight
and
the
small
spacing,
whereas
on
the
bottom
you're
seeing
our
components
that
are
rendered
in
view
with
those
overrides
that
we
have
in
that
that
fds
section.
F
A
Worth
noting
is
that
this
approach
you
had
said
the
schema
makes
it
really
easy
to
to
extend
we
sort
of
jumped
on
this
bandwagon.
Like
I
said
almost
a
couple
years
ago,
and
I
think
the
renderer
was
still
in
beta,
we
didn't
really
know
a
whole
lot
about
it.
I
think
it's
picked
up
a
lot
of
steam
since,
but
we
felt
you
know
with
this
approach.
A
We
were
comfortable
enough
that,
even
even
if
microsoft
decided
to
chuck
adaptive
cars
as
a
product
that
the
schema
was
good
enough,
that
we
could
continue
to
support
it
internally,
and
you
know
we
had
this
this
power
to
do.
This
we'd
obviously
lose
the
microsoft
integration
point,
but
it
was
still
a
really
good
approach
approach
for
us
just
for
internal
rendering
but
yeah.
A
So
those
are
those
are
sort
of
the
two
approaches
that
we've
taken
at
factset
to
utilize
adaptive
cards
and
also
extend
it
to
get
a
lot
of
the
features
that
aren't
yet
native.
But
I
think
that
make
it
easier
to
support
in
our
our
own
environments,
and
I
think
it's
a
a
process-
and
maybe
maybe
matt
and
jp,
can
speak
a
little
bit
more
to
it.
A
E
Yeah,
it's
really
cool
to
see
the
the
extensibility
stuff
was
made
for
what
you're
doing
you
know
as
as
an
escape
hatch,
so
people
weren't,
always
locked
in
you
know
you
guys,
came
up
with
a
table.
It
took
us
a
little
bit
to
get
a
table
in
there
and
you
know:
that's
that's
why
we
really
wanted
that.
Not
a
lot
of
people
are
rendering
cards.
E
A
Yeah
definitely
and
yeah
I
mean
that's,
that's
pretty
much
our
our
presentation,
I
put
up
a
slide
for
for
questions
or
discussion
or
anything.
If
anyone
wants
I'm
not
sure
what
we're
looking
like
time
wise
on
the
presentation,
if
you
guys
want
to
take
it
back,
but
I
figured
if
you
want,
we
could
open
the
floor.
C
D
E
A
Yes,
so
I
know
that
all
the
stuff
that
we're
rendering
inside
of
our
reports
is-
and
that's
that's
going
out
to
to
most
of
our
our
clients
today,
so
that
that
would
be
our
own
custom
renderer
internally.
I
know
that
we
are
using
like
adaptive
cards
in
in
teams-
I'm
not
a
hundred
percent
sure
if
we
have
clients
hitting
that
yet.
But
it's
you
know
it's
well
in
the
pipeline
and
we
have
all
the
all
the
schemas.
A
D
A
A
All
we
had
this
sort
of
track
was
where
those
were
positioned
under
the
different
so
like
if
an
infographic
is
on
the
same
level
or
underneath
a
column
that
sort
of
makes
sense
but
sort
of
just
hooking
up
the
ui,
and
it
was
a
lot
of
that
stuff
was
written
with
third-party
libraries,
but
I
won't
speak
to
the
ease
of
it
because
I
didn't
write
it.
It
seems
like
andrew
whipped
it
up
pretty
pretty
fast
a
couple
weeks
or
so.
E
I
I
think
this
is
the
coolest
thing
about
that,
and
it's
just
something:
I've
learned
and
gotten
really
excited
about
about
adaptive
cards
over
the
years.
Is
we
never?
I
like?
I
have
never
our
ceo
now
satya
says
citizen
developer,
basically
at
every
conference,
which
is
really
referring
to
power
users
and
users
of
like
the
power
platform,
I
hadn't
even
crossed
my
mind
as
an
audience
and
now
I'd
say
a
significant
chunk
of
the
folks
on
this
call
fall
into
that
camp.
E
You
know
what
isvs
to
do
or
all
sorts
of
stuff
and
adaptive
cars
has
come
along
as
this
thing
to
enable
them
to
build
like
these
lightweight
uis,
where
you
don't
have
to
have
a
lot
of
skill
in
that,
and
I
think
it's
really
cool
just
taking
that
concept,
and
you
know
whether
using
an
app
of
card
designer
is
sort
of
less
important
than
just
making
these
things
accessible
to
a
broader
range
of
users
and
use
cases.
So
it's
cool
cool
to
see
that.