WEBVTT 00:00:00.000 --> 00:00:09.500 XMPie is pleased to announce the availability of uDirect and PersonalEffect versions 25.4 and 26.0. 00:00:09.500 --> 00:00:13.866 Both versions feature the same updates with one exception: 00:00:13.866 --> 00:00:24.466 Version 26 supports Adobe InDesign CC2026, while 25.4 requires InDesign CC2025. 00:00:24.466 --> 00:00:32.799 For customers with PersonalEffect Pro servers, it is important to note that Adobe usually releases the server version of InDesign 00:00:32.800 --> 00:00:36.033 a month or so after the desktop version. 00:00:36.033 --> 00:00:44.033 So, if you have uDirect only, or a PersonalEffect XLIM-only edition, and have a current maintenance and support contract, 00:00:44.033 --> 00:00:49.433 you're free to upgrade your InDesign desktop and PersonalEffect server today. 00:00:49.433 --> 00:00:53.099 But if your uProduce includes InDesign Server, 00:00:53.100 --> 00:01:00.633 it is best to wait until Adobe has released the server version before you update InDesign on your desktop. 00:01:00.633 --> 00:01:08.066 So, apart from InDesign CC2026 support, what other new features are included in this release? 00:01:08.066 --> 00:01:14.666 The latest Macintosh OS X version 26 or "Tahoe" is now officially supported. 00:01:14.666 --> 00:01:19.766 There are several small improvements for customers using delimited text files. 00:01:19.766 --> 00:01:27.732 Both when using the data source for recipients, and when exporting CSVX data during server production. 00:01:27.733 --> 00:01:34.999 Graphic content objects now support the download of images from a URL without the need for a function. 00:01:35.000 --> 00:01:42.733 Developers can take advantage of some new features allowing connection to the uProduce server with user tokens. 00:01:42.733 --> 00:01:47.766 There is also a new dashboard user setting that you may find helpful. 00:01:47.766 --> 00:01:53.966 Developer documentation additions, and the usual security enhancements and bug fixes. 00:01:53.966 --> 00:02:04.332 Let's dive in. If I happen mention "version 25.4", remember the same features are also relevant for version 26.0. 00:02:04.333 --> 00:02:10.399 Several customers have requested better support for separated text data sources. 00:02:10.400 --> 00:02:14.266 Listening to the various reasons and problems customers reported, 00:02:14.266 --> 00:02:19.632 XMPie has introduced a number of small features to address these issues. 00:02:19.633 --> 00:02:26.399 On the desktop, the first change is in the uCreate Print preferences on Windows computers. 00:02:26.400 --> 00:02:34.566 Users can define their preferred default encoding type when the data file does not include the byte order mark or BOM. 00:02:34.566 --> 00:02:43.599 This setting was already available on the Macintosh, but Windows previously used a system default defined in a Windows control panel. 00:02:43.600 --> 00:02:48.100 When connecting to a data source, if the file itself includes the BOM, 00:02:48.100 --> 00:02:53.566 the encoding is set automatically, based on the BOM, and the dropdown is disabled. 00:02:53.566 --> 00:03:02.166 If there is no BOM in the data file, the setting from preferences is used by default, but can be changed by the operator. 00:03:02.166 --> 00:03:10.799 While I mostly work with Unicode data files, I know this file is encoded with Shift-JIS which is common in Japan. 00:03:10.800 --> 00:03:17.533 And, you can see that the Japanese characters are correctly represented in the Dynamic Content panel. 00:03:17.533 --> 00:03:23.433 Also, for your convenience, there are some more options in the separator drop-down list. 00:03:23.433 --> 00:03:28.899 But if the character you need is not listed, you can simply type the character you want. 00:03:28.900 --> 00:03:34.733 And to improve usability for our European, South American and African customers, 00:03:34.733 --> 00:03:40.533 the decimal separator can also be changed to comma instead of point. 00:03:40.533 --> 00:03:44.199 When uCreate Print is linked to a uProduce server, 00:03:44.200 --> 00:03:51.533 the new data source option also allows configuration of the text file delimiter and separator. 00:03:51.533 --> 00:04:00.166 In the uProduce dashboard, when creating a new data source these settings were already available since version 25.0. 00:04:00.166 --> 00:04:06.166 In uPlan, there are no changes to the new plan wizard. 00:04:06.166 --> 00:04:11.032 In the uProduce dashboard, when processing a document or generating a proofset, 00:04:11.033 --> 00:04:16.933 you can output the resolved content object values as flat CSVX data. 00:04:16.933 --> 00:04:22.933 New in version 25.4 is this option to select the delimiter character. 00:04:22.933 --> 00:04:30.299 Important if you're in a region where the decimal separator is a comma and generally helpful anywhere else. 00:04:30.300 --> 00:04:37.533 The option is available for both InDesign and XLIM production, but if you are using uCreate Print connectivity, 00:04:37.533 --> 00:04:41.099 the feature is not yet implemented here. 00:04:41.100 --> 00:04:51.500 uCreate, uPlan and uProduce version 9.8.1 introduced a QLingo function Web.URLContentAsFile() 00:04:51.500 --> 00:04:57.600 which allows you to download a file from the internet to use in your dynamic documents. 00:04:57.600 --> 00:05:01.066 For example, an image could be requested from a URL, 00:05:01.066 --> 00:05:07.366 perhaps in a digital asset management system, and then used in your personalized document. 00:05:07.366 --> 00:05:17.599 Version 25.4 enhances this feature for images. A graphic content object can now simply include a URL like this. 00:05:17.600 --> 00:05:25.833 The software is now smart enough to understand that in a graphic content object, a text starting with http 00:05:25.833 --> 00:05:32.233 is going to be a URL to an image file that it should download to use as the image. 00:05:32.233 --> 00:05:37.633 The same string in a text content object will just be text. 00:05:37.633 --> 00:05:44.799 The URLContentAsFile function is still relevant if you want to download other asset file types. 00:05:44.800 --> 00:05:49.133 Or take advantage of other parameters available with the function. 00:05:49.133 --> 00:05:57.133 The graphic files will be downloaded to this folder which is the same one used by the URLContentAsFile function. 00:05:57.133 --> 00:06:05.899 On the desktop, the images are cached there until InDesign is closed and the downloaded images are automatically deleted. 00:06:05.900 --> 00:06:13.033 On the uProduce Server, you can cleanup the URL download cache using the maintenance tools. 00:06:13.033 --> 00:06:20.766 For customers in a highly secure environment, where it may not be permitted or desirable to download remote files, 00:06:20.766 --> 00:06:26.632 there is a registry key available from XMPie support that will disable this feature. 00:06:26.633 --> 00:06:31.766 Version 25.4 adds three new user account features. 00:06:31.766 --> 00:06:37.232 The first extends the use of tokens for server-to-server access. 00:06:37.233 --> 00:06:46.033 Administrators and system administrators can use this new User Tokens setting page to create new user tokens. 00:06:46.033 --> 00:06:54.599 There is more information about the different token types and how to use tokens in a separate video here in XMPie Campus. 00:06:54.600 --> 00:06:59.466 When creating a new user token, you should give it a descriptive name. 00:06:59.466 --> 00:07:03.866 Select the user that the token will grant access as. 00:07:03.866 --> 00:07:10.732 When using the token, the system will grant access to the same accounts that are permitted for this user. 00:07:10.733 --> 00:07:17.333 And then set an expiry date when the token should stop working. 00:07:17.333 --> 00:07:22.533 To save, enter the admin password. 00:07:22.533 --> 00:07:31.199 You must copy and retain the token. There is no way to see or copy the token again after leaving this page. 00:07:31.200 --> 00:07:38.166 It is treated like a password and cannot be accessed from the user interface or from the database. 00:07:38.166 --> 00:07:47.632 If building an application with the uProduce REST API, you can use the token as the bearer token for API access. 00:07:47.633 --> 00:07:58.066 You can also use the API's basic authentication method by entering the username "token" and the token as the password. 00:07:58.066 --> 00:08:02.399 This method can also be used to access the dashboard. 00:08:02.400 --> 00:08:06.366 00:08:06.366 --> 00:08:15.632 The second feature added to user accounts, is an option for the user account to have access to all, including new, accounts. 00:08:15.633 --> 00:08:19.499 Previously, you could select all accounts for a new user, 00:08:19.500 --> 00:08:25.233 but when someone created a new account, it was possible to not grant this user access. 00:08:25.233 --> 00:08:33.866 But, with this new setting, when a new account is created, the user is already selected and it is not possible to remove them. 00:08:33.866 --> 00:08:40.966 This feature may be useful, perhaps for uStore customers who create a user for uStore access 00:08:40.966 --> 00:08:46.766 and want the uStore user to be able to access documents in all accounts. 00:08:46.766 --> 00:08:51.266 And perhaps even to use a token instead of a password. 00:08:51.266 --> 00:08:55.299 Which brings me to the third new user account feature. 00:08:55.300 --> 00:09:02.866 From version 25.4 it is possible to create a user account without defining a password. 00:09:02.866 --> 00:09:10.199 This is not a regular user account. The user will not be able to access the uProduce dashboard. 00:09:10.200 --> 00:09:16.833 But, if I was now to create a user token for this account, an external system like uStore 00:09:16.833 --> 00:09:24.199 could use the token to access the uProduce server with the permissions granted to the user. 00:09:24.200 --> 00:09:32.233 While not directly related to the features of the version, there are two new topics in the Developer Hub that are worth mentioning. 00:09:32.233 --> 00:09:38.099 The uProduce Email Plug-in SDK is now documented in the developer hub. 00:09:38.100 --> 00:09:46.800 The sample solution for the Email Plug-in SDK is still available from support for customers with the uProduce API license, 00:09:46.800 --> 00:09:53.600 but the documentation is now online instead of being part of the sample Visual Studio solution. 00:09:53.600 --> 00:09:56.966 Also, depending on their current project, 00:09:56.966 --> 00:10:05.432 developers may find it useful to use the Document Structure XML as a method of obtaining information about the document, 00:10:05.433 --> 00:10:13.933 and the content objects it uses, without the need to launch InDesign to interrogate the document. 00:10:13.933 --> 00:10:23.199 Not a huge feature, but again a frequently requested change was to increase the number of characters permitted in uProduce entities. 00:10:23.200 --> 00:10:31.533 Account, campaign, document and other entity names have increased from 50 to 255 characters 00:10:31.533 --> 00:10:35.499 providing more flexibility when naming objects. 00:10:35.500 --> 00:10:43.200 Previous XMPie versions used two different methods of working with CSV recipient data files. 00:10:43.200 --> 00:10:53.133 If the data was Unicode, an XMPie data engine was used, while files encoded differently were handled by a Microsoft data engine. 00:10:53.133 --> 00:10:59.033 To solve some problems with the Microsoft engine, and to support the other new CSV features, 00:10:59.033 --> 00:11:04.766 version 25.4 now uses only the XMPie data engine. 00:11:04.766 --> 00:11:16.732 And, as with every version release, there are some bug fixes and versions 25.4 and 26 have undergone full security and penetration tests.