Faster workflows with integrations and apps for WoodWing Studio and Assets

Hi everyone, and welcome to today's session. This is a very insightful webinar for all, on the subject of faster workflows with integration and extension apps for our products, WoodWing Assets and Studio. I'm Magdalena, a Product Marketing Manager here at WoodWing, and I'll be your moderator today.

As I said, we're really excited to have you all here today. I assume it's a mix of current users and customers of WoodWing Assets and Studio, or maybe you're somebody who's interested, just looking around and interested to find out more about the integration options around our products.

Joining me today are two of our internal experts from WoodWing. That's Jeff Gapp, joining us today from the US. He is the Product Manager for WoodWing Connect, and he's been leading the development of our integrations and pre-built applications. And from the EMEA side, or UK, Paul Walker, the Product Development Manager at WoodWing, who is working closely with our customers and partners to design and deliver the WoodWing extension apps.

They will walk you through how integrations and apps like the Workflow Assistant, the Content Delivery Hub, the PDF Manager, and of course our pre-built integrations, which I already mentioned, can help you and your teams eliminate manual steps, reduce silos, connect systems, and increase the speed and velocity of your go-to-market efforts throughout the session.

We're also going to run two short polls. We'd like to hear your input and your stance on the current position in terms of having extension apps or integrations within your organization. Please take a moment to participate. These polls are going to run on the side panel of WebinarGeek and won't interrupt our speakers when they present the key integrations and applications.

Of course, feel free to drop any questions that you might have in the Q&A option on the side during the webinar, and we'll spare some time at the end to try to answer them all.

Before we begin, a quick overview of what we're going to present today with our speakers. The WoodWing apps that I mentioned are the Workflow Assistant, the Content Delivery Hub, and PDF Manager. Afterwards, we have pre-selected a couple of highlighted integrations that are already listed and available on the WoodWing integrations marketplace.

My colleagues are going to be demoing some of these that are listed here, and I'm sure it's going to be an insightful demo. You'll get to see firsthand the possibilities and the possible use cases for these applications and pre-built integrations.

With that, let's get started. I'd like to invite my colleague Paul to the stage to start you off with the WoodWing apps.

Paul, thank you, Magdalena. Good introduction. Let's start with the Workflow Assistant. What is the Workflow Assistant? It's for WoodWing Assets primarily, and the idea for users of DAM systems, users who are working in Assets, is that they have quite a tough job sometimes.

What we're presenting here is a highly configurable interface, and this is tailored to individual roles that users are performing. What we're trying to do is reduce the complexity for users. Quite often, business rules that the users have to follow as things go through a workflow can be difficult to remember and difficult to train.

We reduce that complexity. It also helps channel the workflow process. The idea is, in providing this configurable interface, that the steps that the user might have to follow can be laid out very clearly, and in doing that also provide detailed feedback.

At every step of the way, there are required metadata fields you need to fill in these forms. Or if you are here, we're looking for you to change it to one of these two statuses. Don't list all the statuses. Reduce it down. Only show them the statuses that they need to see for that role, for that job.

Also, the idea is to present this in friendly language. Use the words that they use, because this is adaptable. We have a facility that can change throughout the business. Often, we find that different groups and different departments within the business might use slightly different terminology for the same thing.

Quite often in media groups, you might have one group saying or referencing the hero image, the major image, or the master image. If you can use that language with each department, but actually channel that down into something common under the hood, then as a business, you keep it simple, but you can express it in different ways for the different groups of users.

This also includes territories, because sometimes you have different territories that might use slightly different words but actually mean the same thing. It also acts as a common gateway to other services.

Within WoodWing Assets, sometimes you can get yet another interface, yet another panel, and this can be true of so many different DAMs across the business. What we can do here is provide a gateway application that users can channel their workflow through. If you need to launch services, you don't need yet another visual surface. You can do it through this visual surface here.

This also leans into WoodWing Assets' vast array of tools, services, and facilities. You can control quite a lot of them through this tool.

But what does it mean for the business? We touched on it before. The key is to reduce training time. Quite often, if you've got complex business rules, we're aiming here to separate the business logic from the users. The users don't have to know, “Fill in these five metadata fields to approve something.” They just want to click a button: “I approve.”

Under the hood, the tooling gives you the mechanism to add the right business rules, maybe trigger downstream services, or provide information for an audit trail.

If you have that separation from the business logic, you can help reduce training time, onboard people quicker, and get them in. If you need to bring more people in to speed something up, you can do it quicker.

It also improves consistency by having this channeled workflow tailored to someone's role. You want to make sure that the steps they do are channeled. That has the added benefits of reducing errors and reducing the need for support.

Quite often, if you're not careful, you might have done something within your business logic where there are five options, but in this instance we only want you to choose one of these. What happens if they choose the other options?

The worst-case scenario is that you've got the wrong metadata polluting your trail downstream, and it might cause a problem. By having this constrained workflow for users, keeping it friendly but very much channeling it down, you can reduce errors, reduce the need for support, and ultimately that adds up to increased productivity.

If you keep people flowing and channeling through these workflows, then we should see a reduced time to market.

One of the key things as well is this is actually a suite of tools. Not only do we have the Workflow Assistant that sits on the front end, but in the back end the configuration of this is a drag-and-drop interface, keeping it as WYSIWYG as possible.

You can create complex rule sets where you can see and reveal different buttons, messages, and notifications, constrained by a query. So only if the user selected a video asset and the video asset has this metadata, show them this message.

This helps channel the user through these things and reduces error. That configurator is given to you also. Either the consultants can help you work through that, or you can make the changes yourself. Again, keeping you firmly in control. You don't always have to dial home for any changes.

I'm just going to give you a short video, and this will show you a little flavor of what the front end offers and how it could be used. It's not that long. It's about three and a half minutes, and I'll see you on the other side.

First of all, it's a panel plugin. Here we have a number of panels available. Each of these is fully configurable and tied to an individual role. If I'm a media producer, for example, all I'll see is media producer. If I'm a picture researcher, I might only see picture research. Both of these might also see asset details.

Today I'm just in the sample panel, and I'll give you a quick demo. First of all, you can see, as we mentioned before, signposting instructions for users on what this section does. Guidance: select one or more assets, not collections.

Here, constant feedback is being given to the user. It's also contextual. I might select an asset over here, and we have description appears. For images, description might be a required field, whereas for a PDF it is not. So again, we're constantly trying to reaffirm to the user, reduce what is displayed, so they can just focus on the job at hand.

We'll talk about this in a moment. Grouping assets is but one kind of feature. Tagging the system, various lists from straight lists to hierarchical lists, all the usual things that you would expect here. Again, we can have notes.

Here, an external file. If I click through here, we notice some different types of messaging. Whereas this asset has required metadata fields, this does not. Here is my publish to the platform. I'm unable to publish this video. It doesn't meet the metadata requirements. I have to fulfill those metadata requirements before I'm able to publish.

Now the warning errors have gone. Here we have the publish to platform and withdraw. I can't withdraw it until I've published it. Once we publish it, the withdraw will be shown and I can withdraw it.

This is how the contextual nature of the Workflow Assistant can make sure that users are less error-prone and can perform the function driven by the instructions that you are presenting to them.

How do we do it on the back end? If we have a quick look at the configurator, here we have many fields and different types of buttons, from browse to metadata stamping, add one or more metadata fields, perform a query.

Here is a user-definable metadata stamp. It appears on the front end to generate a metadata report. We have notifications. We have preset combinations. This is an ever-growing list, so we'll be adding more to these.

And grids. Previously, the publish and the withdraw were side by side rather than just using vertical alignment.

Coming back to things, for example the button for the metadata looking here for the ISBN. This is where you're displaying an ISBN, and we're giving the user a button: show all briefs with the same ISBN.

If I was to select an asset and an ISBN was to show in here, what we have in the settings is a query. This allows the user not to have to know what the Lucene query language is. They can select an asset and say, “Show me things of a similar type.”

Here we have extensive features to contextualize, disable, and confirm button messages. Each option comes with an extensive array of different features.

That's a broad view of what the system is. We also have a data panel in which you can plug in external data. Your lists can be driven by lists from external sources. They don't have to exist in Assets.

That's just a quick review. Thank you very much for watching the Workflow Assistant.

That gives you a quick flavor of the Workflow Assistant and what it can do. Now we're going to move on to the Content Delivery Hub.

What is the Content Delivery Hub? We describe it as a modular content orchestration platform. This is a Studio-based product, or sits alongside Studio, where you can use the fantastic and very rich toolset to create your print and digital content.

It's then expressing that content to the many different streams. Over the years, more and more channels have been added to the ever-growing list of requirements from publishers and other industry verticals.

The key thing with the Content Delivery Hub is its modularization. To look at that in a bit more detail, we have a four-step process. The first one is preprocess. Before you export, is there anything that you want to do? Then transform: how you want to change that article. Post-process: what do you want to do after you've transformed the article? Then publish: where do you want to publish it?

At the very end of that, we have notify. Keeping the users informed about what's just happened, where it has gone, and whether there were any problems along the way.

Looking in a little bit more detail, the first one we have is preprocess. This is where we collect more information that might otherwise be present on the article itself. Looking at the dossiers and the metadata that it came from, looking at the images contained, where that image might have come from on the layout of a page, and equally collecting data from other external sources.

Actually, we need to enrich this with more data, and that data could be used in the publishing, or it could be used in any one of the next steps.

The very next step would then be to transform this. Once you've got your article, you might need to convert it to XML, WordPress, Drupal, JSON, or anything else. When you're pushing it to different services, it would be great if everybody used the same format, but rarely do they.

This gives us the power to be able to transform any article into any kind of stream service that we need. If we don't have it, then it's modular enough that you can trigger something else. For example, Jeff will be talking about this soon: using WoodWing Connect, you can tap into another resource and say, “We want to trigger this from a webhook. Take the data, transform it into another service, another different format.”

If we haven't done the module, that doesn't stop there. We can fire triggers that can go off, and either we write another transform, you write another transform, or you leverage another. The list can be endless. Using this service, you can take this to almost any format that you need.

Once you've done the transformation, there might be a little bit more you want to do. For example, callbacks: “Hey, I'm done. I just want to let you know.” Trigger another downstream service. Reset metadata back into Studio. Basically say, “Yes, the publishing is underway. It's going to these different services.” And manipulate images: slicing, dicing, cropping, reducing the color space, all the transforms that you might need to push this further downstream.

What we then have is the publishing process. Again, very much like the transform, all of these stages are modularized. If we haven't created a module already, it's open enough that we can create more modules.

We currently have publish to S3, SNS topics, webhooks, SMS, Drupal, WordPress. It's a fairly extensive list, but if you look out there, there are so many CMSs in the world. This is why we came up with this, because you need that flexibility.

You don't want to be locked into a particular delivery mechanism. If there is a business need to change, your tooling needs to be able to adapt. This is where the Content Delivery Hub can help with that. In the entire publishing process, as the business adapts to an ever-changing landscape, the publishing process is already there to adapt with it.

The key features are, within WoodWing Studio, being able to publish out to multiple channels, taking data from articles, images, layouts, dossiers, metadata, custom metadata, and external sources, using either articles to drive these, layouts to drive these, or issues to drive these.

However your business is organized from a structural point of view in how you publish a page, an issue, or an article out through to your external sources, the Content Delivery Hub is there to be your partner in this.

That's my presentation concluded. I'll be available for any questions. What I'm going to do now is hand over to my colleague Jeff Gapp.

Very good. Thank you, Paul. Again, my name is Jeff Gapp. I'm the Product Manager for WoodWing Connect, and we're going to be talking about a variety of things. First, we're going to talk about PDF Manager.

What PDF Manager is, is a tool that's been around for a little while. What we wanted to do is make the process of generating PDFs in general, but also make the process of creating IDML files, packaged files, JPEG and PNG exports of the pages, and XML files a little bit more seamless.

The idea here is that when you're inside Studio, you can of course use a trigger to generate a PDF, and you can do that in multiple ways. For instance, you might create a single-page PDF layout. Page one, two, three, four, five, six: that's one file per page.

You can of course merge those pages together. You could have configurable parameters around things like the naming structure using the data that's coming from Studio. There is a wide range of different ways and unique names. You can have names based on your issue, your brand issues, status values, and so on.

You can use defined job options and color settings. Of course, you can dictate those when you send a job over to your design server, and those are yours. Customizable file names, pre-flight checking, and you can get the errors back into WoodWing Studio and update the workflow.

You can have “trigger a PDF,” “PDF in progress,” “PDF completed,” or “PDF had an error,” and then you can see the error right within Studio. Of course, you can package InDesign layouts, export XML and images, and extract images from the layout if that's what you want to do.

For the workflow options within PDF Manager, there are multiple ways to trigger this process. You can use statuses, which is a typical way of doing that. If you don't want to use statuses, maybe because you don't want to have five different statuses within your workflow, you could use a metadata field.

So you have a Boolean field, you click on it, and the PDF gets generated. We also have a tool that's coming up called the PDF dialog, which will allow you, with a publication overview, to bring up a dialog and generate single or multi-page PDF files.

Those can then get merged together, say of a spread, and we can also do things like watermarking and social DRM. Those are things that are coming up next with that plan.

There are some really key capabilities. Yes, it's pretty straightforward to generate the different kinds of files you want, but you can also then deliver them to different locations. One location, of course, is Assets 6 or Assets 10. You trigger the generation of the tool, and it delivers these files automatically to those systems.

You might put them back inside Studio Server, inside a dossier, as part of the issue. You might put them in S3. Long story short, you can deliver these to any endpoint that you want, as long as that endpoint can handle the incoming messages and do something with the content.

Obviously, we support both standard and custom workflows within this environment.

One of my favorite things here, and we are just completing work on this, is the PDF dialog. As you can see here in the middle, this is the basic user interface where you put in an email address and a message: salutation, remarks, a subject, decide if it's going to be a spread, document options, page range, those kinds of things.

Then hit the button, and a user will get an email with a link to how to download it. It might be from Amazon S3, or you might say the download link is in Assets, or whatever else you might have out there. This is a really cool tool, and we'll have more about this very soon.

The other thing that happens with PDFs, and Paul's team is working on this, and actually this is delivered and working for a customer now, is the idea of PDF Certify.

PDF Certify is this ability to say, from either Studio or Assets, to trigger the sending of a PDF to PitStop, and then have PitStop certify the file based on the standards that you want, deliver the certified file back to whichever of the tools you want, along with the reports.

“Hey, this integration is currently in development.” That's incorrect. That development is actually completed, and the tool is available as of right now. Another pretty cool tool.

This is a totally different topic. PDF Manager and its associated tools are all about workflow and delivering content to a destination. The next tool is called AI Assistant.

On-demand PDF generation. AI Assistant is this tool where the name actually covers a wide variety of capabilities within the AI Assistant. Really, it's about automating some routine tasks that you do while you're editing content, and then maybe offering contextual suggestions.

It's really designed to help you make your workflows more efficient and help produce higher-quality results in a faster timeframe.

What I'd like to do here is switch to our movie, and we're going to take a look at that movie. Let's go ahead.

In this video, we'll introduce one of our latest technology previews, the AI Assistant inside WoodWing Studio's digital editor. The AI Assistant is designed to make your daily work easier, helping you generate content or copyedit your stories with just a few clicks.

Let's explore what it can do. You can find the AI Assistant in the toolbar on the right side of the digital editor.

Here you'll see a list of standard actions, such as creating titles, social posts, teasers, or running checks to analyze your content. For example, you can use it for copy editing a story, performing an SEO check, or running a tone and style analysis to verify your story, or even compare it against a reference story within Studio.

Beyond the standard actions, you can also create or configure custom prompts. Your administrator can set these up for brand, and you can decide which prompts to activate based on your needs.

Let's look at some examples. First, we'll select create titles. Here you'll see options for both digital and print titles. Suppose you want a short print title. Just hit the copy button, and you can quickly replace the title in your article.

The same goes for social posts or teasers. Simple, fast, and efficient.

Now, let's try copy editing. When we select this action, the AI Assistant runs a series of checks looking at grammar, brevity, clichés, and more. After a short moment, you'll see the analysis results.

You can review the suggestions, choose the parts you want to update, and hit replace to apply them directly to your story.

Finally, let's look at custom prompts. For instance, you might want to generate an FAQ from your article. With just one click, the AI Assistant creates a set of questions and answers you can reuse, either in this story or elsewhere.

The possibilities are truly endless. We can't wait to hear your feedback as you start exploring what the AI Assistant can do for your content workflows. Thank you for watching.

That's one of my favorite recent developments. Not terribly recent, right? We've been working on that for a while. It's a pretty cool tool to help with efficiency, speed, etc.

The next thing to take a look at here is some WoodWing integrations. Quite some time ago, three years ago, what we did is we created a product called WoodWing Connect. WoodWing Connect is really the idea of an umbrella over a variety of things. It's the PBIs, the APIs that we have, trying to make things easier, better, and faster for partners and our customers to create these best-of-breed solutions.

As part of that, we came up with this idea of pre-built integrations. The idea here was for customers to be able to come in, go through a list of integrations we've built in our marketplace, and actually use those integrations relatively quickly.

The idea here is to meet a simple set of requirements: make the integrations easy to deploy, make them so they can be modified for deeper requirements, because everybody always wants a little bit more. We try our best to meet the base use cases, and of course you may have something else you want, and make sure they are affordably priced.

When we built these, we selected a group of categories within the PBIs. Things that are AI-driven, project management, content reuse, file data, miscellaneous, and technology partners.

From there, what we said is, let's pick a variety of different vendors to work with and base what we're building off customer requests over time.

As you can see here, I'm not going to read this entire list, but things that are AI-driven: Rekognition, Clarifai, and visual search. Content reuse, project management, miscellaneous tools like Slack and Teams for communication. Power BI is a nice integration. We have file data import and export. Lastly, we have technology partnerships, Tansa and Infogram, for spellcheck and tables within the digital editor.

Each one of these tools has some use case that we created. With visual search, you may want to be able to find exact duplicates of images that you have within your system, or maybe you want to select an image and say, “I want to find everything that's similar to this.”

Our tools identify, discover, and locate exact duplicates. Here within the demo, we're going to show a quick movie. Let me click on the video here. Sorry about that. There we go.

In this video, we're going to see how our visual search pre-built integration works. We're going to do a couple of things. We're going to search for duplicates of the images we have, and those images that may have some resemblance to other images within our system. Then we'll do a little bit of AI tagging as well.

The first thing that we're going to do is select an image, and then we're going to select the user interface for the visual search piece. Here, what we see is basically two inputs: a percentage score and the number of results.

What this does is the percentage score is basically saying how much similarity should we have between the image you have selected and the results of the search list that we have in the system. In this case, if we set the percentage score to 80, from 80 to 100%, what we're going to see is that we're going to find duplicates of the selected image.

We can also set the number of results here. But if we do a search, what happens is we get a second tab, and we see that indeed, here is an exact duplicate of the original image that we had within the user interface.

If we come back here and look, we see, yes, they are duplicates.

The other thing that you can do, of course, is select an image and then say, “I want to find things that are similar to this.” Similarity is wide-ranging. It could be color, positioning of something within the photo, etc.

If we come here to visual search again, this time we're going to select 80% and hit search. What we end up seeing is those images that are 80% similar to the selected image from the search that we did.

You can see here that we've got some Cybertrucks mostly, and then we've got this color, most likely because of the color of the car plus the positioning of the vehicle within the image.

Lastly, just as a bonus, we'll also talk a little bit about AI tagging. AI tagging can happen in multiple ways. For instance, when an image comes into Assets, the image can be tagged by a service.

In this case, for demonstration purposes, we're going to go ahead and tag the selected car within this user interface here. We're going to do that via a status.

Again, how the tagging happens can vary. It can happen on ingestion. It could be ad hoc afterwards. It can have a variety of different tools that do the AI tagging. In this case, we're using a tool called Clarifai.

What we're going to do is just put this into production. What we'll see in a moment here is the tags show up from Clarifai. WoodWing actually supports multiple services, Rekognition and Clarifai being the most familiar, and some other ones.

I hope you enjoyed this demonstration. Again, reach out to us if you have interest in talking about this more. Thank you.

We're back. Visual search was the one we just saw. Let's go to the next item, and we're going to talk about WordPress and Studio.

I'm going to give you a little bit of a use case here. We had customers who were transferring data via copy and paste. It could go both ways. It could go from Studio to WordPress or WordPress to Studio. In the video, you're going to see we're talking about pushing data from WordPress over to Studio.

That's fairly straightforward. This customer is also a highly templated magazine, and what they wanted to do is flow the content all the way through and get it onto an InDesign layout.

All of this is happening basically with a status change out of WordPress and then API calls to Studio. Let's go ahead and take a look at that. We're going to do a demo and fire this video.

Hi there. My name is Jeff Gapp, and I'm the Product Manager for WoodWing Connect. Today what we're going to do is take a look at sending content from WordPress to Studio and some of the things that are possible.

In this case, what we're first going to do is mimic a call from WordPress over to our recipe to then send the content into WoodWing Studio. This is done by using a tool, Postman.

What happens here is we send a webhook over to the recipe, and it sends some information here. This article ID is the most important piece here, along with, of course, the notification type.

When we do this, what ends up happening is the recipe will then talk back to WordPress. It will get the article and push it over to Studio. We're going to hit send here, and it's that fast.

If we come over here into WoodWing Studio and refresh, we see that the article is already here. It's created the dossier that we need. It's also created, and you can see some activity going on here, the digital article that was created based on the article from WordPress.

As part of that process, we also create a layout, which you see here. You can see that it's done working with it, and we create a print article.

All of the capabilities are in Studio to do what we're doing now. In other words, there's an API for the digital side. There are APIs for creating the layout and placing the digital article onto the InDesign layout.

If we were to come over to InDesign and refresh our palette, what we end up seeing here is, at the top, again, the InDesign article. If we look closely, we'll see that this little guy here is saying that the article is placed onto the layout.

If we open this up, what happens is the InDesign client opens the article, and it's got some instructions from the process. In this case, it placed the headline and it placed the body of the text onto the page.

How things get onto the page is configurable. The conversion of the digital article to the print article: you could determine what kind of component it goes into, what stylesheets are used, etc.

Very simply, we are taking content from WordPress, putting it into Studio, creating a layout, creating a print article, and then placing the article onto the InDesign layout. All happens behind the scenes very fast.

If you have any questions, please contact us. Thank you.

Lastly, we have a pre-built integration for monday.com. This one I really love, because the intention of the pre-built integrations, of course, is that a customer can take this and then work with our teams to build something even more complex and more interesting based on what they want to do.

That's actually what we did with this monday.com pre-built integration. What the PBI does is it takes the part of the PBI for Studio and Assets. Users of monday.com can create projects within monday.com, and in Studio you get a dossier. As part of that process, you can also create InCopy or digital articles, and you can also create layout templates.

That's the basic PBI. When a user changes the status of the dossier or the underlying layouts or articles, the statuses of those items are updated inside monday.com.

That's the basics of the PBI. For Assets, it's essentially the same but a little different. Again, in monday.com you can send the monday.com interface to create, say, a brochure request that's sent over to Assets. We create a collection, a folder structure, etc.

When a user adds an image to the collection, that collection is then updated, and the image preview is sent over to monday.com so that somebody can approve that. That's a really cool one that we do.

The next item is a tool that is really here and meant to meet a feature gap for some customers. We have some engineering firms that have CAD/CAM files, and CAD/CAM files, like the preview and thumbnail generation tools in Assets, use ImageMagick. ImageMagick doesn't handle CAD/CAM, so we needed a third-party tool to be able to do that.

The idea here is that you can submit a CAD/CAM file to Assets 6 or Assets 10, and that ConvertAPI will generate a JPEG preview of that file for the user. If you take a look at convertapi.com, you'll see all the capabilities of that tool and what it can do for generating unusual files.

They're not unusual, but they're maybe not standard to DAM implementations. It's a really cool one, a great tool, and pretty interesting to work with.

So we are at key takeaways. Magdalena.

Yes. Thank you so much, Jeff and Paul. I'd like to summarize the featured or highlighted WoodWing applications and integrations that our audience was able to see within these last 40 minutes. I'm sure it's a lot of information, but I'd like to summarize everything.

In the beginning, you were able to preview what Paul showcased, and that's the Workflow Assistant and the Content Delivery Hub. With the Workflow Assistant, what the end user gets is a very simplified user interface that is role-based.

It really is helpful for training and onboarding new users to the system of WoodWing Assets. What it also does is boost their productivity, because they don't feel lost and they can really navigate across the WoodWing Assets digital asset management user interface through that Workflow Assistant.

Then, the Content Delivery Hub really enables a true multi-channel publishing solution from one source and ensures that there is consistency and the content is always on brand across print, web, and digital channels.

Then you were able to preview the WoodWing Connect PDF Manager, how to standardize the output and automate all that content generation through the PDF Manager, but not just focus on PDF files. It can really include many more configurable file formats in order to improve accuracy, consistency, speed, and compliance when you are pushing your content towards the digital channels.

Then Jeff Gapp showcased the WoodWing Connect pre-built list of integrations that we hand-selected for this webinar. That was monday.com, ConvertAPI, WordPress to WoodWing Studio, and the like.

Again, he showcased the AI-powered assistant and the automation possibilities it offers to the users within WoodWing Studio's digital editor.

I hope I managed to cover everything. We do have quite a small timeframe to answer the potential questions that we have. In the meantime, I had a poll in the side, and I'm going to run the results for everybody to see.

But yes, I do have a couple of questions, and I would like to ask Paul and Jeff to join us on stage for these.

One of the first questions was an interest in the pricing and packaging, or the pricing and licensing options, for these integrations. I've asked anybody that is interested, and we are going to follow up with you after the webinar. We are going to provide you with all the information on the pricing and licensing options.

This webinar's sole purpose was to showcase the potential and the options we have within those WoodWing pre-built integrations and the WoodWing apps.

There is a question for Jeff from Paulo. Paulo asks: how does the PDF Manager handle Adobe fonts?

Sure. Just like InDesign, InDesign Server needs to have the fonts that are available to them. You need your full set of fonts within InDesign Server. If you're in the WoodWing Cloud, we have a process right now to help you manage those, which goes through our teams.

What we're hoping to do in the very near future is provide a mechanism for you to be able to upload and manage your fonts yourself. But right now, we just have to have the fonts.

Thank you. I don't think the other questions... Oh yes, there we have a new one. Are these shown features already available, and if not, when will they be available?

I'm not sure for which specific application this is, but maybe Jeff and Paul can both answer.

Everything you saw is available from me. PDF Manager, PDF dialog, the PBIs, the AI Assistant, all of that's available right now.

Thank you. There is a question from, I suppose, a customer. We're using both WoodWing Assets and Wrike. What is the pre-built Wrike integration mentioned in the slide?

Just like the monday.com integration, it's fairly simple and straightforward. The idea is, within Wrike, to be able to create a project, pass that project over to Studio and Assets, create either in Studio or with Assets a directory structure plus a collection, and then be able to update information from Studio or Assets back into Wrike.

It follows the same basic model. Again, it's fairly simple and straightforward, mainly just like monday.com and Wrike, because the workflows of customers are so different in how they choose to implement them. We've left things very straightforward, and then we get into a discussion with you about how you might wrap that around your business.

Thank you. I don't think we have a new question. Oh yes, there is a new question from Chris. Can the monday.com integration be used to update the status of an item in monday.com when you set the article or layout to a specific status in Studio?

Yes. The answer is yes. And here's the caveat. The thing that ends up happening is you need to do the initial creation of things from monday.com. If you create an initial article, what ends up happening is we send data over, we might create an article, and when we do that, we create an item or a sub-item in monday.com.

Now we have a unique link. We know what the IDs are, and as you change statuses, we just pass that information back to monday.com.

Thank you. As we've seen... Oh, and there is another question. When sending an article from WordPress to Studio, how does the automatic layout creation work?

Great question. There have been APIs within Studio for quite some time called create object relations. What we do is, at WordPress, it doesn't really matter how you do this with WordPress, but essentially what happens is WordPress sends a message to a recipe and says, “Hey, somebody wants to put this into Studio.”

We then grab that, take the article from WordPress, put it in Studio as a digital article, and then issue an API call that says, “Put this on a layout using this layout template, create the article, and then save the object.”

We use InDesign Server to do that whole operation. There's an API call that allows us to do that whole thing in one call, and it's called the create object operations.

Thank you so much. I wanted to comment that on the side panel, we did receive quite a few answers on which areas the audience benefits most from automation in their organization.

There is, I would have to say, an even type of answer for all of the options. The one that wins the most, or almost 50%, said system integrations with CMS, PM, PIM, or CRM systems, etc.

I would like to also showcase the results from the first poll, and maybe Paul can comment on these. We asked the audience how integrated their current content workflows are today, and we did get a mixed volume of answers. The majority said that they heavily rely on manual steps and file sharing, and some of them do have a few automations in place.

Do you have a comment or a final takeaway for the users that are joining this webinar to learn more about the applications and the integrations we offer?

Absolutely. You can try and automate things via code and services, but ultimately there are still a lot of decisions that need to be made that, thankfully, humans can still make. Hence why manual steps can be the way people look toward.

But with these manual steps, trying to make them efficient and less error-prone, this is exactly where the Workflow Assistant really comes to the fore. Taking those manual processes and helping people reduce that time and making it clear step by step.

Sometimes with manual processes, you might onboard interns and say, “Here's a million images. Please process these in this particular way.” This is exactly the job where the Workflow Assistant steps in.

Thank you. I would like to wrap up the session, because we've answered all of the questions in the panel.

I'd like to again thank both speakers today, Paul Walker and Jeff Gapp. Thank you so much for these insightful videos and demonstrations. I think we managed to showcase and demo the majority of the integrations and apps, and also highlight the business benefit and the end-user benefit in a nutshell.

After this webinar, you'll receive two links. After we end the session, you can explore our integrations marketplace, where I believe all of the integrations and apps mentioned today are listed. For some of them, of course, there are demo videos that Jeff and Paul have recorded, and you can watch them in action.

Feel free to reach out to us for a personalized demo if you have a specific need that you'd like to highlight or solve, and we'll be more than happy to come back to you.

For all the ones that joined us live today, you'll again receive the recording of this webinar, and all the registrants that were unable to join us during this live moment are going to receive the recording.

Thank you very much for today, and hope to see you soon. Bye-bye.

Note: this transcript has been auto-corrected using AI, it may contain mistakes.