﻿WEBVTT

00:00:00.000 --> 00:00:08.400
XMPie is pleased to announce the availability of PersonalEffect and uCreate Print version 25.2.

00:00:08.400 --> 00:00:16.733
This version introduces many new and improved features as well as the usual updates to security and bug fixes.

00:00:16.733 --> 00:00:20.566
There is a lot to cover in this overview, so I will jump right in,

00:00:20.566 --> 00:00:25.532
but if something stands out, you can jump forward to the relevant time shown here.

00:00:25.533 --> 00:00:31.566
The main area of development has been in the print production area of the uProduce server

00:00:31.566 --> 00:00:39.866
When you visit the process page, you will notice that the data selection and range fields are rearranged and simplified.

00:00:39.866 --> 00:00:44.832
It takes up much less screen real estate and is easier to understand.

00:00:44.833 --> 00:00:50.633
You will also see that some sections are now listed as legacy or deprecated.

00:00:50.633 --> 00:00:57.666
While these are still there and working, they have been replaced by a new feature that offers more functionality,

00:00:57.666 --> 00:01:01.032
and the old settings will eventually be removed.

00:01:01.033 --> 00:01:07.866
The deprecated features are all things that are applied to the output files after they are created.

00:01:07.866 --> 00:01:14.266
So, the new feature that replaces these settings is called Post Composition Operations.

00:01:14.266 --> 00:01:20.066
Post Composition Operations are defined in the settings area by an administrator.

00:01:20.066 --> 00:01:24.232
Today, there are several types of operation that can be defined.

00:01:24.233 --> 00:01:29.833
Each one offers more than what the old feature did on the process page.

00:01:29.833 --> 00:01:34.199
For example, compression now allows you to select the compression level 

00:01:34.200 --> 00:01:41.266
and doesn’t have the 2GB file size limitation of the old compression setting on the process page.

00:01:41.266 --> 00:01:53.566
Copying output to network, FTP and AWS destinations now include an option to create a subfolder named by the job id or creation date.

00:01:53.566 --> 00:02:01.366
SFTP or secure shell file transfer is a new option introduced in this release.

00:02:01.366 --> 00:02:09.732
And the new JDF option gives you full control to edit the JDF to suit the needs of your printing and finishing equipment.

00:02:09.733 --> 00:02:18.266
After being created by an admin, the Post Composition Operations can be selected and added to your job in any order.

00:02:18.266 --> 00:02:24.132
So, this is another advantage. You now have control of the sequence of the operations.

00:02:24.133 --> 00:02:33.366
Important if, for example, you want the uncompressed file to go to the printer and the compressed version to an archive location.

00:02:33.366 --> 00:02:41.099
The Post Composition Operations are not yet available in uCreate Print when using the uProduce connectivity feature.

00:02:41.100 --> 00:02:44.566
This feature will be added in a future version.

00:02:44.566 --> 00:02:53.566
Future versions will also add more operation types including improved imposition settings and the selection of network printers.

00:02:53.566 --> 00:03:01.332
There are several videos about creating and using Post Composition Operations here in XMPie Campus.

00:03:01.333 --> 00:03:05.566
While we are on the process page, under the Bleed and Marks heading,

00:03:05.566 --> 00:03:13.932
the previous version of PersonalEffect added these settings which can add printer marks to the output without having to use imposition.

00:03:13.933 --> 00:03:18.866
This was available only for PDF and PDF/VT output formats,

00:03:18.866 --> 00:03:28.099
but in this release, printer marks are available also for the PostScript output formats including VPS, VIPP, PPML.

00:03:28.100 --> 00:03:33.966
Again, this feature will be added to uCreate Print connectivity in a future version.

00:03:33.966 --> 00:03:40.599
Customers with Cross Media servers can now access the list of recipients who have unsubscribed from the account

00:03:40.600 --> 00:03:44.900
by using the account setup page in the uProduce dashboard.

00:03:44.900 --> 00:03:48.933
Here you can export and download the list of email addresses

00:03:48.933 --> 00:03:54.633
of recipients who have unsubscribed from marketing emails sent from this account.

00:03:54.633 --> 00:03:57.999
You can also edit the list and import it again.

00:03:58.000 --> 00:04:05.100
For example, if you are requested to unsubscribe recipients, perhaps after a phone call or reply email

00:04:05.100 --> 00:04:11.466
instead of the automated process of the recipient clicking the unsubscribe link in the email.

00:04:11.466 --> 00:04:18.499
This feature means that you don’t need to access the server and run the email subscriber manager executable.

00:04:18.500 --> 00:04:24.433
So, this tool is now removed from the uProduce filesystem during the upgrade.

00:04:24.433 --> 00:04:29.899
Work has also happened behind the scenes to allow Circle to access the information.

00:04:29.900 --> 00:04:37.866
So, we hope that a future version of Circle will also have the option to manage the email unsubscribe list.

00:04:37.866 --> 00:04:44.332
Version 25.2 also introduces a new, optional, single sign on feature. 

00:04:44.333 --> 00:04:50.833
It replaces the plug-in that was sold separately by the XMPie Professional Services team.

00:04:50.833 --> 00:04:58.666
Customers who have purchased the plug-in, should contact the support team to request a license to enable the built-in feature.

00:04:58.666 --> 00:05:05.199
After adding the license, the dashboard log on screen will show this “Sign in with Microsoft” button.

00:05:05.200 --> 00:05:14.266
Version 13.2 already introduced a feature to use the local Microsoft domain as the source of authentication.

00:05:14.266 --> 00:05:24.199
Single sign on is designed for customers who host their uProduce servers outside of their local network and are using Microsoft Azure.

00:05:24.200 --> 00:05:31.300
Apart from adding the single sign on license to uProduce, there are no further uProduce settings required.

00:05:31.300 --> 00:05:35.966
But there are some additional steps to perform on your Azure domain.

00:05:35.966 --> 00:05:39.799
There is a separate technote about how to complete the setup.

00:05:39.800 --> 00:05:48.766
Once those two steps are done, users can be created in the dashboard with either the domain option, or with the basic option.

00:05:48.766 --> 00:05:53.832
The domain setting will force the user to sign in with Microsoft.

00:05:53.833 --> 00:06:03.399
While the basic setting allows the user to enter the username and password or use the Microsoft authentication.

00:06:03.400 --> 00:06:07.800
Moving onto the smaller but still very useful enhancements.

00:06:07.800 --> 00:06:14.433
PersonalEffect is sold either with a production unit license, or with unlimited production.

00:06:14.433 --> 00:06:19.666
Several customers with the production unit license have asked for more visibility

00:06:19.666 --> 00:06:27.266
on how many clicks or production units were used for each job to make it easier to bill their end clients.

00:06:27.266 --> 00:06:34.266
To help with this request, the job center now reports the number of clicks used for the job production.

00:06:34.266 --> 00:06:42.766
This is available for servers with either type of license since it may also be helpful for customers with the unlimited license.

00:06:42.766 --> 00:06:49.532
But in this case, it will show that it was not charged. Proof jobs are also not charged.

00:06:49.533 --> 00:06:53.599
Another item added is the number of pages generated.

00:06:53.600 --> 00:07:03.100
Of course, this is important for jobs where the number of pages is different for each recipient and again can be useful for billing your clients.

00:07:03.100 --> 00:07:08.300
Several new barcode types have been added to the XMPBarcode function.

00:07:08.300 --> 00:07:16.333
Most of these new formats are used in the health and pharmacy industries and will be helpful if you work in those verticals.

00:07:16.333 --> 00:07:22.399
In addition, there are some new barcode parameters: BarShape and OutputType.

00:07:22.400 --> 00:07:31.900
A common feature request has been to show barcodes with different shapes. For example, the QR codes with circles instead of squares.

00:07:31.900 --> 00:07:35.366
There are now several options available.

00:07:35.366 --> 00:07:38.999
The setting is also available on linear barcodes.

00:07:39.000 --> 00:07:44.700
But remember that this can impact readability or how well the barcode will scan.

00:07:44.700 --> 00:07:49.266
So, we recommend that both you and your client thoroughly test scanning

00:07:49.266 --> 00:07:53.899
several sample barcodes before committing to it in your print designs.

00:07:53.900 --> 00:08:01.800
Also, a second word of caution: By default, XMPie creates the barcodes as PDF graphics

00:08:01.800 --> 00:08:06.400
because that works best and fastest for our composition engine.

00:08:06.400 --> 00:08:15.166
However, to use Ellipse or BigEllipse, the barcode software must create PostScript images instead of PDF.

00:08:15.166 --> 00:08:21.866
This is the reason for the OutputType parameter that you will need to use with these two options.

00:08:21.866 --> 00:08:29.766
Now the warning is because using PostScipt images will slow down the VDP print composition process.

00:08:29.766 --> 00:08:35.132
So, we recommend you use these settings only for smaller print runs

00:08:35.133 --> 00:08:44.066
or when the design absolutely must have the Ellipse barcodes and you are prepared to wait a little longer for the job to process.

00:08:44.066 --> 00:08:50.999
In the delivery providers area, the SMTP server settings look exactly the same as before.

00:08:51.000 --> 00:09:02.966
But behind the scenes, a totally new component is being used, meaning that Microsoft Office 365 and Gmail SMTP servers are now supported.

00:09:02.966 --> 00:09:11.432
The important things to remember are:
For Gmail, use port 587 and check the SSL option.

00:09:11.433 --> 00:09:15.699
This will automatically use the STARTTLS command.

00:09:15.700 --> 00:09:19.933
You will also need to create an app password on Gmail’s website

00:09:19.933 --> 00:09:26.266
to bypass the multi-factor authentication that a normal Gmail password requires.

00:09:26.266 --> 00:09:32.932
Setting up Office 365 is very similar with the difference being the server address.

00:09:32.933 --> 00:09:40.899
There can also be some specific settings required on the Office 365 setup side for you IT department to look after.

00:09:40.900 --> 00:09:45.766
There is a technote that covers these if you run into any problems.

00:09:45.766 --> 00:09:51.999
If you use another flavor of SMTP server, you can configure the port required.

00:09:52.000 --> 00:10:01.933
For example to use SSL the port would probably be 465, but your IT department can also use other custom ports.

00:10:01.933 --> 00:10:10.433
My last point on this topic is another warning: SMTP servers should be used only for notification emails.

00:10:10.433 --> 00:10:18.299
Cross media customers should use XES or XMPie Email Services for sending bulk or marketing emails.

00:10:18.300 --> 00:10:25.666
Using your SMTP server for bulk emails will get your email domain blacklisted.

00:10:25.666 --> 00:10:32.299
Legacy PDF is now formally deprecated and will be removed after 12 months.

00:10:32.300 --> 00:10:36.700
There is also another change behind the scenes for Legacy PDF.

00:10:36.700 --> 00:10:42.300
The previous version used Adobe Normalizer to convert the PostScript to PDF.

00:10:42.300 --> 00:10:47.100
From version 25.2, the Adobe Normalizer has been removed.

00:10:47.100 --> 00:10:52.400
Legacy PDF will now use Adobe Distiller instead of Normalizer.

00:10:52.400 --> 00:10:57.800
If you experience any problems, remember you can use the other PDF formats,

00:10:57.800 --> 00:11:04.300
or create PostScript output and then use your own PDF distiller application.

00:11:04.300 --> 00:11:11.000
The uProduce REST API now supports Open API Specification 3.1.

00:11:11.000 --> 00:11:16.900
Note that many of the tools that consume REST APIs do not yet support this version,

00:11:16.900 --> 00:11:24.433
so the default selection is version 3.0.3 and we continue to support version 2.0.

00:11:24.433 --> 00:11:29.133
But when you need it, version 3.1 is there and ready to go.

00:11:29.133 --> 00:11:36.933
There is also a new developer hub for information about using all of the XMPie application APIs.

00:11:36.933 --> 00:11:45.033
The site contains new information about developing custom hot folder applications and post composition operations,

00:11:45.033 --> 00:11:49.366
as well as links to all the other developer resources.

00:11:49.366 --> 00:11:56.499
PersonalEffect version 25.2 adds supports Windows Server 2025.

00:11:56.500 --> 00:12:02.266
And, as usual, we continue to run the latest penetration tests and security checks.

00:12:02.266 --> 00:12:10.232
So, version 25.2 includes the latest updates and patches to fix any issues identified.

00:12:10.233 --> 00:12:15.833
The PersonalEffect team hopes you find value in the latest version upgrade.

