►
From YouTube: SharePoint Syntex - Content Assembly (Modern Mail Merge)
Description
In this 18-minute developer focused demo, Leon Armston explains how Syntex has moved beyond baseline document classification and metadata extraction to Content Assembly - create (assemble) new documents based on existing documents (templates). Step through creating a Modern template - opening an existing document (contract, SOW…) in Syntex template engine, adding placeholders, mapping fields to data sources, publishing the template, and generating documents. Then couple this Content Assembly capability with workflow in Syntex Contracts Management template from look book. See samples and resources. This PnP Community demo is taken from the General Microsoft 365 Developer community call recorded on March 31, 2022.
Demo Presenter: Leon Armston (Intelogy) | @LeonArmston
Supporting materials:
• Article - SharePoint Syntex (series) | bit.ly/LeonSyntexSeries
• Samples - Microsoft SharePoint Syntex Samples | https://github.com/pnp/syntex-samples
• Marketing site - SharePoint Syntex | aka.ms/SharePointSyntex
• Demo - Making SharePoint Syntex testing easy – new templates in look book service - Sean Squires (Microsoft) | @iamseansquires – https://youtu.be/-MXd0mhxORQ?t=800
• Get Started - SharePoint Syntex Adoption | https://adoption.microsoft.com/sharepoint-syntex-adoption/
• Look book - SHAREPOINT SYNTEX CONTRACTS MANAGEMENT | https://lookbook.microsoft.com/
• Roadmap - Microsoft 365 roadmap – Syntex | aka.ms/SyntexRoadmap
• Feedback - SharePoint Syntex | aka.ms/Syntex/Feedback
• Learning Path - Get Started with SharePoint Syntex | https://docs.microsoft.com/learn/paths/syntex-get-started/
• Article - Syntex content assembly and the content lifecycle | https://techcommunity.microsoft.com/t5/sharepoint-syntex-blog/syntex-content-assembly-and-the-content-lifecycle/ba-p/3060175
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
A
A
So
there
may
be
some
people
on
this
call
that
are
experts
at
sharepoint
syntax
who
have
used
it
lots.
There
may
be
some
people
that
have
perhaps
installed
the
trial
had
a
play
about
with
sharepoint
syntax
and
maybe
not
seen
the
true
power
or
the
new
functionality
of
sharepoint
syntax,
and
then
there
might
be
some
people,
even
that
are
like
what
is
sharepoint
syntax.
A
So
the
idea
is,
you
use,
syntax,
to
create
an
ai
model
and
there
are
two
main
concepts
for
the
model.
So
documents
are
classified
I.e.
Your
model
is
trained
to
target
a
particular
type
of
document,
so
you
set
your
model
to
pick
out
invoices
or
statements
of
work
or
contracts,
for
example,
and
then,
within
that
model
as
well,
you
set
it
to
extract
metadata.
A
So
you
create
rules
to
extract,
say
for
a
contract,
a
contract
id
or
contract
or
an
amount
or
who
who
the
contracts
to
or
their
date,
for
example,
and
then
to
extract
and
classify
these
two
main
features.
Well,
it
features
two
extract
data
and
that's
forms
processing,
so
the
concept
of
forms,
processing
that
uses
machine
learning,
which
is
part
of
ai
builder,
to
identify
and
extract
key
value
pairs
and
table
data
from
structured
or
semi-structured
documents.
A
So,
as
the
name
says,
it's
good
for
forms
or
invoices,
where
yeah
there's
reliable,
structured
data
in
front
of
and
you're
targeting
a
particular
section
on
a
particular
piece
on
a
form,
then
there
is
document
understanding
which
works
best
for
unstructured
documents,
such
as
letters
or
contracts,
that
have
texts
that
can
be
identified
from
phrases
or
patterns
so
document
understanding.
So
your
documents
could
be
one
page.
A
The
next
document
might
be
two
pages.
Three
pages
it's
variable
lengths
and
the
metadata
might
be
on
different-
that
you
want
to
extract,
might
be
on
like
different
pages
per
per
document,
and
then
the
third
one
that
I've
mentioned
is
content
compliance.
So
because
we're
picking
out
particular
types
of
documents,
we
could
set
a
retention
label
to
whenever
there's
a
statement
of
work
say
it
has
to
be
retained
for
seven
years
or
or
longer,
and
we
can
also
do
the
same
with
sensitivity
labels.
A
So
about
content
assembly,
it
was
released
quite
recently
at
the
end
of
january
this
year.
It
enables
you
to
use
an
existing
microsoft
word
document
to
create
a
modern
template
and
then
use
that
template
to
automatically
generate
new
microsoft,
word
documents
and
using
sharepoint
lists
or
manual
user
inputs
as
a
data
source.
A
A
The
idea
is
that
content
comes
in
it's
processed,
so
it
might
be
processed
by
syntax
to
extract
the
metadata,
and
then
you
have
to
respond
to
it.
So
that
could
be
using
the
metadata
in
a
workflow.
It
could
be
manual
process
and
then
you
you're
going
to
do
something
with
it.
So
it
might
be
yeah
that
we
use
content
assembly.
A
The
whole
purpose
of
this
presentation
to
create
a
new
document
to
respond
to
that
content,
and
then,
secondly,
and
finally,
that
document
is
say
sent
out
for
signature,
maybe
comes
back
a
few
months
later
signed
and
then
it's
fed
back
in
and
a
syntax
model
picks
it
up
again.
So
the
idea
is,
there
might
be
many
different
content
life
cycles.
A
So
here
we
have
a
list
of
superstars.
This
is
a
sharepoint
list
and
we
have
these
superstars
have
been
submitting
to
the
pmp
repositories
and
doing
pull
requests
etc.
So
we
want
to
reward
them
for
their
contributions,
so
we
want
to
send
them
a
letter
outlining
this.
So,
first
of
all,
I'm
going
to
do
this
all
from
scratch,
so
we're
just
going
to
create
a
new
document
library,
so
we'll
call
this
pmp
rewards.
A
A
A
So
I'll
then
name
this
name,
my
placeholder
and
then
I
need
to
select
which
sharepoint
list
or
document
library
to
get
my
data
from
so
like
it
could
be
on
a
different
site,
but
this
is
the
same
site.
So
I
want
to
go
to
this
superstars
list
here
now.
I
need
to
map
the
field,
so
I've
got
a
field
called
location,
name
that
I'm
going
to
map
that
to.
A
You
can
have
manual
fields,
so
we
could
have
when
the
document
is
generated.
We
ask
them
for
a
date
and
time.
So
that's
what
I
want
to
do
here
and
now
I
want
to
ensure
that
this
letter
goes
to
pmp
parker
here.
So
I'm
going
to
call
this
name
and
go
back
to
my
superstars,
and
I
know
that
the
name
is
in
the
title
here.
So
I'm
going
to
add
that
now
I'm
going
to
change
the
name
of
the
template.
A
And
now
I'm
going
to
publish
this
template
here,
so
that's
now
published
and
available
in
my
library.
So
if
I
go
to
the
new
section,
I
can
go
to
my
pmp
recognition
letter
here
and
now.
If
I
go
to
name
here,
I
can
select
pnp
parker
here
and
we're
going
to
produce
a
letter
for
for
him
and
now
I
select
I
want
it
to
be
today's
date.
A
So
you
may
be
wondering
yeah:
why
can't
we
do
this
in
or
automate
it
or?
Why
can't?
Why
isn't
there
an
api
to
do
this?
So
I've
spoken
with
microsoft
about
this
and
they've
I've
shared
to
them
that
yeah
an
api
would
be
good.
It
would
be
good
to
do
bulk
automation
so
yeah.
They
have
acknowledged
that
this
feedback
and
are
working
on
something
for
later
in
the
year.
A
So
now
I
just
want
to
show
you
quickly
the
content
life
cycle.
So
the
idea
is
where
I
spoke,
where
content
could
be
created,
content
can
be
actioned
and
it
keeps
going
around.
So
there
is
a
contract
management
template
that
is
available
in
the
sharepoint
lookbook.
So
I'm
just
going
to
show
so
here
we
could
request
a
contract,
so
clippy
has
requested
a
contract
for
pnp
parker.
A
A
So
then
that
contract
might
be
emailed
out
posted
out
and
then
it's
received
back
as
a
pdf.
So
on
this
library
we
have
a
syntax
model,
so
a
person
might
upload
it
in
here
and
the
syntax
model
extracts
the
fee
amount,
the
contractor
the
clients,
and
then
we
can
do
stuff
like
that
with
that,
so
we
can
do
a
workflow,
so
we
could
yeah
when
the
contract
is
popped
out.
This
could
perhaps
go
to
the
ceo
to
say.
A
Then,
once
that's
been
approved,
it
will
go
out
to
the
payout
list
and
then
that
could
be
picked
up
by
a
workflow.
It
could
go
to
a
third-party
finance
system
who
could
make
the
payment
automatically
or
or
it
could
be
a
manual
payment.
Now
we
want
to
produce
a
payment
receipt
to
pmp
parker
to
say:
we've
paid
you.
A
A
I
now
want
to
bring
to
your
attention
some
information
on
how
to
get
started
with
syntax
or
how
to
further
contribute
to
syntax.
So
in
the
pmp
github
organization,
there
is
a
repository
for
syntax
samples,
so
this
contains
community
submitted
document
understanding
model
templates,
which
you
can
download
and
deploy
to
your
tenant
today
and
yeah,
see
how
other
people
are
using
syntax
see
how
microsoft
are
using
syntax.
It
has
all
the
documents
and
yeah
gives
you
a
great
start
to
see
yeah
how
to
use
syntax.
A
There
is
some
lots
of
other
information
on
that
site
on
how
to
get
started
with
syntax
and
to
template
models.
So
perhaps
you
have
a
pre-production
environment
where
you've
created
some
models
and
you
want
to
move
them
to
production.
You
can
use
the
good
old
pnp
provisioning
engine
to
with
get
pnp
site
template
and
invoke
pnp
site
template
to
move
them
across
between
environments
or
you
could
template
your
model
and
yeah
create
a
pull
request
and
add
it
to
the
pmp
syntax
samples
within
pmp
powershell
as
well.
A
There
are
five
syntax
commandlets,
so
that's
really
good
for
seeing
what
models
are
applied
to
a
site,
pushing
it
out
to
many
different
sites,
so
multiple
hundreds
of
sites
on
publishing
models,
there's
lots
of
yeah
powerful
commandlets
there.
This
is
a
contract
management
template
that
I
was
talking
about
on
tuesday.
Sean
squires
did
a
good
demonstration
on
the
m365
platform
call
of
the
sharepoint
lookbook
syntax
templates.
So
I'm
not
gonna
talk
anymore
about
these
but
yeah.
A
A
few
links
here
you
might
want
to
take
a
print
screen
on
how
to
get
started.
But
as
I
mentioned,
I
took
quite
an
interest
in
sharepoint
syntax.
I've
created
lots
of
blogs
about
it.
So
if
you
go
to
my
blog,
so
here's
a
short
link
bit
dot,
ly
slash
leon,
syntax
series
or
go
to
that
qr
code.
It'll.
Take
you
to
all
my
blogs
on
sharepoint
syntax,
there's
a
few!
I'm
not
gonna
list
all
of
these
out,
but
there's
syntax
resources
from
microsoft.
A
So
that's
the
end
of
my
presentation
today.
I
want
to
thank
you
all
for
watching
and
seeing
the
power
of
content
assembly
and
also
yeah
the
power
of
syntax
and
yeah.
A
lot
lots
more
to
come
from
syntax
feel
free
to
connect
me
or
ask
me
any
questions
about
sharepoint
syntax
or
connect
yeah,
twitter,
linkedin
or
github.