﻿WEBVTT

00:00:00.000 --> 00:00:04.700
Hi. Welcome to PersonalEffect and uDirect version 13.2 

00:00:04.700 --> 00:00:13.500
which introduces several new PDF features, the ability to use a Windows domain or LDAP for uProduce dashboard authentication, 

00:00:13.500 --> 00:00:19.800
several more useful enhancements, and the usual bug fixes and security updates.

00:00:19.800 --> 00:00:28.166
This version introduces support for more PDF password features when generating VDP output with Adobe InDesign Server. 

00:00:28.166 --> 00:00:33.499
The option to require a password to open the PDF was added some time ago. 

00:00:33.500 --> 00:00:41.366
New in 13.2 is this checkbox that can disallow specific PDF features unless the password is entered. 

00:00:41.366 --> 00:00:50.099
Note that the PDF password settings are only available when processing separate file for each record, or Interactive PDF. 

00:00:50.100 --> 00:00:57.366
Several of the settings are mutually exclusive. For example, you can disallow high resolution printing, 

00:00:57.366 --> 00:01:05.932
leaving it possible to print in low resolution. But disabling printing altogether means that this setting is now irrelevant.

00:01:05.933 --> 00:01:10.033
You can either enter a static password in the text box, 

00:01:10.033 --> 00:01:18.599
or select to use a password from one of the ADORs which is unique for each PDF and relevant only to the individual recipient.

00:01:18.600 --> 00:01:25.866
The extra PDF permissions are implemented as a separate setting because it grants a higher level of permission. 

00:01:25.866 --> 00:01:33.032
For example, consider an HR department document where each recipient employee can open their own document 

00:01:33.033 --> 00:01:41.699
with their individual password, but the HR department can also access any of the documents using their higher-level password. 

00:01:41.700 --> 00:01:48.600
And of course, additional permissions could be granted to the HR department, but restricted for the employee.

00:01:48.600 --> 00:01:52.033
In addition to using the setting in the uProduce Dashboard, 

00:01:52.033 --> 00:02:00.933
it is also possible to use the PDF password setting on the desktop when using uCreate Print Connectivity to process the job on the server. 

00:02:00.933 --> 00:02:09.533
The PDF password options are not available when processing XLIM documents, or on the desktop when linked directly to a database.

00:02:09.533 --> 00:02:16.333
XMPie has also extended the PDF accessibility features introduced in version 12.2. 

00:02:16.333 --> 00:02:22.066
In this latest version, the document language can also be set into the PDF properties. 

00:02:22.066 --> 00:02:28.399
Accessible PDF readers use this value to give a better result when parsing the document. 

00:02:28.400 --> 00:02:37.800
The language setting is a clear text field that can be set as a static value for all recipients or if the text in the document is changed by ADOR logic, 

00:02:37.800 --> 00:02:42.600
the relevant accessible language can also be set via a content object. 

00:02:42.600 --> 00:02:50.200
Again, the option is available in the desktop when connected to the uProduce server with uCreate Print Connectivity.

00:02:50.200 --> 00:02:55.566
For customers who have the uProduce server installed locally inside their LAN, 

00:02:55.566 --> 00:03:01.732
there is now an option to use your Windows Domain Controller for authentication into the uProduce dashboard. 

00:03:01.733 --> 00:03:09.399
If your uProduce server is a member of a Windows domain, then to create a uProduce user that uses LDAP authentication, 

00:03:09.400 --> 00:03:16.933
all you need to do is to select Built-in Windows Domain and enter the name of a user that is in the Windows domain. 

00:03:16.933 --> 00:03:24.199
Notice that there is no need to set a password – uProduce will pass the authentication request to the domain controller 

00:03:24.200 --> 00:03:28.000
and access is granted or denied based on the response. 

00:03:28.000 --> 00:03:34.933
Remember that once you are using this authentication, all the password policies are controlled by the domain controller, 

00:03:34.933 --> 00:03:45.533
so things like password complexity, expiry and lockout periods are being controlled by your organization’s domain controller not uProduce.

00:03:45.533 --> 00:03:56.199
It is also possible to enable LDAP authentication if your uProduce server is not a member of the domain, or if you have a complex LDAP setup. 

00:03:56.200 --> 00:04:00.666
In settings, there is a new option to configure Authentication Providers. 

00:04:00.666 --> 00:04:09.832
These settings allow you to point the uProduce server to use a specific domain controller when the server itself is not a member of the domain, 

00:04:09.833 --> 00:04:14.599
or when more specific LDAP settings are required in your environment. 

00:04:14.600 --> 00:04:21.666
Once this is defined, the specific authentication settings can be selected when creating the user.

00:04:21.666 --> 00:04:26.366
When a uProduce user account is configured to use LDAP authentication, 

00:04:26.366 --> 00:04:31.366
all uProduce applications will use this authentication method for the user. 

00:04:31.366 --> 00:04:37.332
This includes Circle, uCreate Print Connectivity, uProduce APIs, and the dashboard. 

00:04:37.333 --> 00:04:43.366
You should be aware that Circle and uCreate Print Connectivity cache the username and password, 

00:04:43.366 --> 00:04:52.166
so when your domain controller enforces you to change the password, these applications will need to be updated to use the new credentials.

00:04:52.166 --> 00:04:56.866
Several customers experienced problems with the sequence of the data changing 

00:04:56.866 --> 00:05:01.199
when connecting to Excel or CSV data files on the desktop. 

00:05:01.200 --> 00:05:07.333
Recognising the difficulty this caused customers, XMPie has implemented a fix for this problem, 

00:05:07.333 --> 00:05:12.533
and data will now remain in the same order that it appears in the data file. 

00:05:12.533 --> 00:05:19.333
In earlier versions XMPie added a preference to allow the data to be sorted by the primary key. 

00:05:19.333 --> 00:05:24.899
This feature is still available to change the default sort order if desired.

00:05:24.900 --> 00:05:31.500
The QLingo Skip operator, which was originally designed to work only when used on the uProduce server, 

00:05:31.500 --> 00:05:39.066
has now been extended to uCreate Print desktop VDP production as well as with uCreate Print Connectivity. 

00:05:39.066 --> 00:05:46.966
Skip allows you to use a content object rule to ignore or skip a record when generating VDP output.

00:05:46.966 --> 00:05:52.899
The GetEnv function has been extended to include two new options:

00:05:52.900 --> 00:05:57.400
TopMostJobID will return either the ID of the job 

00:05:57.400 --> 00:06:04.733
or the ID of the parent job if the production was split automatically across multiple InDesign server instances.

00:06:04.733 --> 00:06:12.266
RecipientFilter returns the table name, plan filter name or query used for production. 

00:06:12.266 --> 00:06:17.999
These two values could be accessed before but required some technical nous. 

00:06:18.000 --> 00:06:22.233
Now they are more easily accessible and are particularly useful 

00:06:22.233 --> 00:06:31.366
for customers creating custom automated workflows where documents are processed programmatically against different data files.

00:06:31.366 --> 00:06:40.299
All PersonalEffect product installers are now signed to provide better security compliance on both Windows and Macintosh computers.

00:06:40.300 --> 00:06:44.933
Font kerning in XLIM document production has been improved.

00:06:44.933 --> 00:06:53.033
And, as usual with every update, there are several security enhancements with a number of 3rd party libraries now updated, 

00:06:53.033 --> 00:06:56.199
and several bugs have been resolved.

