Release Notes: Datacard® TruCredential™ Software Version 7.2

Release Notes
Datacard® TruCredential™ Software Version 7.2
This document provides last‐minute product information for Datacard® TruCredential™ software. Documentation essential for using this product includes:

The TruCredential Installation and Administration Guide, Part No. 527666‐001.

The online Help system.
Users who want to migrate from ID Works or IDCentre 6.5 to TruCredential should refer to the Datacard® ID Works®/Datacard® IDCentre™ to TruCredential™ Migration Guide, Part No. 527677‐001, which provides complete instructions for migrating to TruCredential version 7.0 software. Once that migration is complete, follow TruCredential documentation procedures for upgrading to the desired version of TruCredential software.
This document includes:

Component Version Numbers on page 2

TruCredential™ Version 7.2 Software on page 2

TruCredential Version 7.2 New Features on page 2

TruCredential Version 7.2 Resolved Issues on page 3

TruCredential Version 7.2 Known Issues on page 4

Additions or Corrections to TruCredential Version 7.2 Documentation on page 11

Upgrading from TruCredential Version 7.1 to Version 7.2 Software on page 12

TruCredential Version 7.1 Software on page 12

TruCredential Version 7.1 Compatibility and Prerequisites on page 12

TruCredential Version 7.1 New Features on page 12

TruCredential Version 7.1 Resolved Issues on page 14

TruCredential Version 7.1 Known Issues on page 14

Frequently Asked Questions on page 20

Open Source Software on page 25

Technical Support on page 25
©2016 Entrust Datacard Corporation. All rights reserved.
527660‐001, Rev. C
Datacard® TruCredential™ Software Version 7.2
Component Version Numbers
Major components for this release are listed in the following table:
Component
Version
Datacard® TruCredential™ Suite software
7.2
Desktop Printer Interface software (DPI)
1.3
Datacard Adaptive Issuance™ Chip Interface software
6.0
Datacard Capture Manager™ software
1.3.0
Datacard Remote Product Activation
1.2.072
Datacard Software Licensing System
1.2.072
TruCredential™ Version 7.2 Software
TruCredential Version 7.2 New Features
2

A new EZ‐ID edition of TruCredential software is available for certain customers who need to get up‐
to‐speed fast with straightforward and streamlined hardware and software installations. If you purchase the EZ‐ID edition of TruCredential software, refer to the installation document that came with your products to proceed with licensing your software and designing and printing credentials. (NXID‐7566)

Database views and synonyms: For the H2, Microsoft SQL Server, and Oracle2 databases, views, synonyms (except for the H2 database), and the columns from all external tables in the primary database, display on the data connection page. (NXID‐7641; NXID‐7765)

Improved printer queue interface for easier printer queue management and monitoring. (NXID‐6226, NXID‐6231)

A new setting automatically deletes completed print jobs from the print queue after completion (the most recently completed print job is still displayed). (NXID‐6311)

The Directory Service (LDAP) configuration allows signing in as a user outside the search base. When configuring a Directory Service interface, user configuration is now independent from the search base. Previously the user had to be in the root of the search base. Note that the user account must now be specified as a fully qualified domain name. Refer to the specifications chapter in the TruCredential Installation and Administration Guide, Part No. 527666‐001, for details. (NXID‐7639)
Datacard® TruCredential™ Software Version 7.2

The workflow Search step was removed. Any projects migrated from ID Works software or TruCredential Version 7.1 software to TruCredential Version 7.2 software will no longer have the Search step. Configured search fields are displayed in the search capability. (NXID‐6112)

The batch workflow type was removed, and card designs are no longer linked to either single or batch workflow types. Instead, card designs can be set to function as either or both types in TruCredential Version 7.2. Note that if you are upgrading from an earlier version of TruCredential software, you cannot see your old batch workflow. You must either modify your batch workflows to single workflows before upgrading to Version 7.2 software and then set them to be produced in batch or create a similar batch workflow in Version 7.2 software that meets your needs. (NXID‐6112)

Licensing is streamlined. There is no longer a need to activate your TruCredential license. In the simplified process, enter the license provided with your purchase documentation and licensing is completed by the software. (NXID‐6887)

Support for rewritable card stock. (NXID‐5277)

Several files and the database schema are updated to accommodate the additional functionality in version 7.2, however no existing data is altered during the process of upgrading from an older version of TruCredential software.

When upgrading from version 7.1 to 7.2: Workflows containing the Photograph field or the Document Scan field are upgraded by being given default properties to accommodate new functionality.
TruCredential Version 7.2 Resolved Issues

Improved image dithering results in improved print quality.

Upon installing TruCredential version 7.1 software, under rare installation configurations, a fully qualified path displays on the screen in Step 13. Ignore this path. (NXID‐5202)

In some cases, the Datacard Capture Manager service does not start up correctly during installation. If this happens, you cannot capture photographs. To resolve this issue, either restart your computer, or start the Datacard Capture Manager service again as Administrator. (NXID‐5286)

Under rare circumstances, when you are working in the credential designer with the Emboss or indent layer, the green design guidance box expands and the color palette is not displayed. If this happens, select the Emboss or indent layer in the layers panel to make the layer display correctly. (NXID‐5685, NXID‐5953)

If you rename a field in your workflow, the old field name displays in the Configured fields box and the new name displays in the Available fields box. To resolve this issue, move the old field name from the Configured fields to the Available fields box, then move the new field name from the Available fields to the Configured fields box. Save the workflow. Close and re‐open the workflow. The fields now show the new field name correctly. (NXID‐5573)

If a printer displays the message “Ribbon low” on the front panel, you cannot print until the ribbon is changed or until the message is otherwise cleared. (DPI‐892)
3
Datacard® TruCredential™ Software Version 7.2

In the credential designer, the properties panel is not available if you clear multi‐selected fields.

In the card designer, the Signature field is now supported on the Ultraviolet layer. (NXID‐5969)

Writing to block 3 of any Mifare Classic smart card is now supported. (NXID‐4064)

For printer names, these characters are now allowed / \ ? ; (NXID‐5842)
TruCredential Version 7.2 Known Issues

If you change the name of any field in a card design, re‐establish connections to this “new” field in any workflows that use this card design. (NXID‐8675)

When upgrading from version 7.1 to 7.2: If you entered a constant value containing the space “ ” character in the Composite field in version 7.1, the space is replaced by an underscore in version 7.2. Therefore, verify all instances of the composite field after the upgrade to make sure that the constant values are correct.

To print to an SR200 or SR300 printer, set the card size to the Custom dimensions 3.5 inches wide by 2.24 inches tall. (NXID‐8602)

Version 7.1 files cannot be imported into version 7.2. To use version 7.1 files with TruCredential version 7.2 software, first import the files into TruCredential version 7.1 software and then upgrade that software installation to version 7.2. The version 7.1 files are upgraded to 7.2 during this process and may then be imported into other version 7.2 installations as‐needed. (NXID‐8113)

In the credential designer, the Advanced Properties of the graphics fields for opacity/percent opaque controls (both the slider bar and box) work backward. Instead of higher opacity or Percent opaque making the object more clear and less transparent, it was implemented so that the image is more transparent. (NXID‐8362)

In the credential designer: If a graphic is placed on the Background layer, a 50% opacity or transparency is applied to it by TruCredential software. The UI controls will not reflect this change. If you require a 100% opaque (0% transparent) image, place the image in a Static Graphic field on the Color layer and adjust the size as needed. Do not activate the Ghosting or Percent Opaque feature. (NXID‐8350)

In the Chrome browser, setting any of the following as the first, primary language does not immediately result in a change in the TruCredential software’s display language: Japanese, Spanish (Latin America)(NXID‐6360), and Dutch(NXID‐4468). To display these languages, follow this procedure for your language (Japanese is used for example purposes):
a. In Chrome’s Settings panel, click Show advanced settings, scroll to Languages and click Language and input settings.
b. In the Languages dialog box, click Add and select Japanese from the list of languages. Click OK.
c. Click and drag Japanese to the top of the list of languages. Click Done.
d. Close the Chrome browser.
4
Datacard® TruCredential™ Software Version 7.2
e. Navigate to c:\Users\UserID\AppData\Local\Google\Chrome\User Data\Default, where UserID is your user ID on the computer.
f.
Open the Preferences file using Notepad or another text editor.
g. Search for “accept_languages”.
If “accept_languages” is not present, make sure that you completed step a through step d before continuing this procedure.
h. Edit the entry’s comma‐separated values list, making sure that “ja‐JP” is the first entry. For example: {"accept_languages": "ja‐JP,en‐US,en"}
Enter the code for your language in the accept_languages entry, instead of what was originally listed, as follows:
Japanese: ja‐JP
Spanish (Latin America): es‐LA
Dutch: nl‐NL

i.
Set the file properties for the preference.js file for the Chrome browser to Read Only to prevent external modification of this file by the user.
j.
Run TruCredential software in the Chrome browser. The TruCredential software interface displays the selected preferred language.
The Chrome browser prohibits use of certain ports by default. If you change the TruCredential software’s port to such a port and then restart the Datacard TruCredential Software service, the Chrome browser displays a message indicating that the port is unsafe. To use this port, run Chrome.exe with a parameter that explicitly allows use of that port number. For example, to use port number 1 run the Chrome browser as follows: (NXID‐5947)
chrome.exe ‐‐explicitly‐allowed‐ports=1

In Internet Explorer browser versions prior to 11.0.9.30, on 32‐bit operating systems only, the Zoom menu in the TruCredential software’s credential designer does not function properly. The Zoom menu works properly in Internet Explorer browser versions 11.0.9.30 and higher.(NXID‐4909)

When uninstalling TruCredential version 7.2, the Datacard folder is not removed from the Windows Start menu. To delete this folder if it is empty, click Start then right‐click Datacard and select Delete. Click Yes to confirm that you want to delete this folder. The folder no longer displays in the Windows Start menu. (NXID‐8320)
5
Datacard® TruCredential™ Software Version 7.2

Lamination of cards is supported as follows with the following combinations of the Lamination layer property settings(NXID‐3718); other setting combinations are fully supported:
Front Side of Card
Back Side of Card
Laminator 1
Laminator 2
Laminator 1
Laminator 2
Result
Laminate once
Laminate once
Laminate once
Do not use
Results vary by printer. The card may print without lamination, or an error may display in the printer queue and no card is printed.
Laminate once
Laminate twice
Do not use
Laminate twice
Laminate twice
Do not use
Laminate once
Do not use
Laminate twice
Do not use
Laminate once
Laminate twice
Do not use
Laminate twice
Laminate once
Results vary by printer. The card may print with only one layer of lamination applied, or an error may display in the printer queue and no card is printed.
Do not use
Laminate twice
Do not use
Laminate once
Laminate twice
Do not use
6
Do not use
Laminate twice
Do not use
Do not use
Laminate twice
Results vary by printer. The card may print with only one layer of lamination, not two.

If you rename an element on a card design that is connected to a workflow element, the connection is deleted. Reconnect the two elements using the Field Connections tool. (NXID‐5193)

In the credential designer, if you enable (select) a layer but do not click the “eye” icon to make the layer active, then it will not print on the credential. You must enable (select) and click the “eye” icon for each layer that you want to print or otherwise appear on a credential before printing it. (NXID‐
6052)

The following applies when migrating projects from ID Works or IDCentre to TruCredential software where the path set in ID Works or IDCentre software is not present and the programs are installed on different computers. If the photograph and signature field properties in ID Works or IDCentre software have the Storage option on the Storage tab set as File select path, then you must manually copy the photograph and signature images to the TruCredential software computer.
Datacard® TruCredential™ Software Version 7.2

The green design guidance box on the credential designer’s Emboss or indent layer may not accurately reflect your printer’s capabilities or your industry’s requirements for content placed in that area. Refer to your own specifications to determine the positions required before finalizing a credential design that uses the Emboss or indent layer. (NXID‐5512, NXID‐4748)

TruCredential software supports only DirectShow‐compliant webcams. If you have a ThinkVantage Virtual Camera installed on a ThinkPad, disable it and instead use the Integrated Camera to take a photograph for TruCredential software. If you do not, either no picture is taken or a black image displays. (NXID‐5642)

If file import columns are not connected to a workflow field, they are lost and no table columns are created for those entries when you click Save. Upon importing a file with the original configuration, TruCredential software displays a message that the column sizes in the import file do not match the table configuration columns. (NXID‐5617)

You have a field that you want to be saved to the database during enrollment. You must make a table connection to that field during the design process. Otherwise, at enrollment time, the data in the field will not be saved and no error informs you of this fact. (NXID‐6047)

If you are using a Datacard SR200 or SR300 printer connected using USB (and not a network connection), the following applies. The Log On tab for the Windows Datacard TruCredential Software service must be configured as a member of the local Administrators group but not as the Local System account. This means that you cannot encode smart cards with either printer in this configuration; use a network connection to encode smart cards. (NXID‐5835)

Administrators must set the TruCredential Windows service account to a non‐privileged user account, rather than a Local System account, to correctly print card size CR‐80. (DPI‐724) To do this:
a. Open the Windows Services.
b. Right‐click Datacard TruCredential Software and select Properties.
c. On the Datacard TruCredential Software Properties (Local Computer) window, click the Log On tab and click This account.
d. Enter the name of a user’s account on the computer, for example [email protected]. It may be necessary to click Browse and possibly to change locations to choose from an LDAP, depending on your network configuration, and then click OK on the Select User or Service Account window.
e. On the Datacard TruCredential Software Properties (Local Computer) window, after This account is specified, enter a Password and a Confirm password, then click OK.
f.
On the Services window, right‐click Datacard TruCredential Software and select Start.

The All Tables option under Settings > Settings > Import and Export does not show connections between table columns and fields to be imported. View the actual table to see the connections.

The Auto‐Sequence and Print Count fields must not be mapped to the Identity Column in SQL Server because they are generated values. Map a read‐only field to the Identity Column instead. (NXID‐5408)
7
Datacard® TruCredential™ Software Version 7.2

For Select Path and Use TruCredential Path, do not use the same field name and path for both entries. If you do, files are overwritten during enrollment.

Configuration changes required to support USB‐connected printers prevent TruCredential from detecting smart card readers/couplers for the DPCL/DPCL2 printer. To enable smart card readers/
couplers to work, set up these printers as networked printers rather than connecting them with a USB cable.

An administrator can go to a user’s page (click Settings > Users and Groups > Edit User) to update information with or without changing the user’s existing password, which displays as “******”.

8
To leave the user’s password unchanged, either leave the existing password fields unchanged or leave the password fields empty and click Save. (NXID‐5782)

In the credential designer, the Emboss or Indent layer is only supported if the credential is in the landscape orientation. (NXID‐5692)

With paper printers, in certain installation configurations, you must change the TruCredential Windows service log on account and adjust the Windows Firewall settings. Factors affecting this include TruCredential software installation type, whether or not workstations are authenticated to a corporate network, and where the paper printer is located and how it is connected. (DPI‐724, NXID‐
4790)

All print jobs sent to a Generic‐type printer are entered into the Windows printing system with the same generic name, rather than with the value of the Print Job Identifier field from TruCredential software. (NXID‐5578)

When you migrate a project from TruCredential version 7.0 to version 7.1 software, be sure to click the table button for additional details about specific projects and whether additional action is necessary on your part to complete the migration.

A signature in WMF format overlaps the field above it in the workflow designer unless you adjust its location in the designer. (NXID‐4944)

WMF‐formatted signatures do not display in report queries until they have been displayed in a workflow (where they are converted to SVG). However, they never display in PDF reports. (NXID‐5098)

If you use a comma, space, or other special character in the Field Name, upon import or export the contents of the properties panel disappear and the boundary style changes. (NXID‐5115, NXID‐3570, NXID‐5678)

When creating a batch workflow, clicking the Add button ought to take you to add a smart card workflow, but instead you a Save alert displays. (NXID‐5270)

The Emboss layer properties for the back of the credential are, instead, applied to the front. (NXID‐
5601)

The Code 39 and Code 39 extended bar codes cannot be printed at high density on the K‐panel of the printer ribbons. For new credential designs, either use the color layer or a different bar code. For migrated designs from the prior version of TruCredential software, update the design according to these restrictions. (NXID‐5874)
Datacard® TruCredential™ Software Version 7.2
Deleting templates (workflow or credential templates) from the Import and Export page is not supported.

The Undo and Redo functions in the credential designer do not support field properties. (NXID‐4120, NXID‐4561)

Magnetic stripe encoding on the front side of a card is not supported. (NXID‐3272)

Ultraviolet printing is not supported on SR200 and SR300 printers.

In the credential designer, the following feature combinations are supported as follows (NXID‐5970):
Field
Layer
Photograph
Background
Variable Graphic
Static Graphic
Borders

Grayscale
Use of the Microsoft Access database is not supported on a network drive. It is supported on a local drive. (NXID‐3907)
Backdrop Removal/
Remove backdrop

Ghosting/Semi‐opaque/
Percent Opaque Option
The U.S. Postal Service’s POSTNET ZIP+4 bar code is not supported. (NXID‐651)
Sizing Options

This field cannot be used on this layer.
Color
—
Yes
Yes
Yes
Yes
Black
—
—
Yes
—
Yes
Ultraviolet
—
—
—
—
Yes
Background
Yes
Yes
—
—
—
Color
Yes
Yes
—
—
—
Black
Yes
—
—
—
—
Ultraviolet
Yes
—
—
—
—
Background
Yes
Yes
—
—
—
Color
Yes
Yes
—
—
—
Black
Yes
Yes
—
—
—
Ultraviolet
Yes
Yes
—
—
—
9
Datacard® TruCredential™ Software Version 7.2
10

A WMF signature may overlap other credential fields when it is converted to SVG by TruCredential software. Adjust the card design to accommodate this. (NXID‐4944)

Margins required by particular printers are not supported by TruCredential software. Users must be aware of any margin limitations of their printers when designing their credentials. (NXID‐5523)

If you are designing a data‐driven credential workflow, you must use the same type of bar code on each credential. (NXID‐5873)

Images that are not supported:

1 bit per pixel images.

Images that are not in RGB format.

Images that make use of transparency.

Images in the following formats: EPS, PCT, PCX, PSD, TGA, and WMF, among others.

Limited support of JPEG 2000 (J2K) images; JPEG 2000 part 1 is supported, part 2 is not. (NXID‐
5822)

Printing a bar code with a black background using the color picker does not result in a viable bar code. To print a black‐on‐black bar code that cannot be copied for security purposes, create the bar code on the Black layer in the credential designer and then, on the Color layer, create a black box behind the bar code. (NXID‐5514)

Smart card features that are not supported:

Smart card personalization is not supported for the following Datacard printers: SP25+, SP35+, SP55+, SP75+, CP80+TM.

DESfire keys of type “DES” that are 16 or 24 bytes long (8 bytes is supported).

AES keys are not supported for the DESfire EV1 smart card chips. (NXID‐5694)

In a single‐workstation installation, you cannot print smart card jobs to a DPCL or DPCL2 printer that is connected using a USB cable. Non‐smart card print jobs do succeed in this configuration, however. (NXID‐1028)

Smart card encoding is not supported on the SR‐200 or SR‐300 printer if the printer is connected via USB cable.

Smart card encoding is not supported when the Windows TruCredential Service is configured as, not the Local System account, but as some other member of the local Administrators group.

Exporting of chip profiles. (NXID‐6067)

Naming support:

Quick Start wizard: The name that you specify cannot start with the “$” character.

A workflow field used in a composite field must not contain an underscore in its field name.
Datacard® TruCredential™ Software Version 7.2

Field connections do not support spaces in field names; spaces are removed when mapping fields.

After a software upgrade, spaces in composite fields are replaced with underscores. (NXID‐4873) 
For the Microsoft Access database, column names with spaces in them are not valid. (NXID‐5651)
Additions or Corrections to TruCredential Version 7.2 Documentation
Installation and Administration Guide
In the Administration Reference chapter, add the following procedure:
Modify the Memory Assigned to the TruCredential Java Virtual Machine (JVM)
1. In the Services window, select the Datacard TruCredential Software Service and click Stop.
2. From a command prompt, run "C:\Program Files\Datacard\AppContainer\bin\tomcat8w.exe //ES/
TRUCREDENTIAL".
3. Click the Java tab.
4. Set the "Initial memory pool" value to the amount of memory to allocate to TruCredential when it starts.
5. Set the "Maximum memory pool" value to the maximum amount of memory used by TruCredential.
6. Click OK to save the changes.
7. In the Services window, select the Datacard TruCredential Software Service and click Start.
Help System
In the Operator Tasks section of the Help system, there is a correction to step 11 and step 12 of the procedure Print a Card. Those two steps should be replaced by:
11. Click one of the following:

Previous: Returns to the previous step in the workflow without saving any data.

Save: Saves the data gathered by the workflow to the database, including any changes made after a card was printed.

Cancel: Closes the workflow and returns to the Home page without saving any data.

Close: Closes the workflow and returns to the Home page without saving any data.

New Enrollment: Displays the first step in this workflow so that you can begin issuing a new card using this workflow.
11
Datacard® TruCredential™ Software Version 7.2
Upgrading from TruCredential Version 7.1 to Version 7.2 Software
The following changes occur after upgrading from version 7.1 to version 7.2 of the software:

The trucredential.properties file contains additional properties. No existing properties change.

The database schema is updated. No existing data changes.

The LDAP is updated with new entries required by TruCredential software. No existing entries change.

Workflows that contain the Photograph or Document scan fields are updated with new properties, which are populated with default values.

By default, print jobs are deleted after they are completed. This can be changed by editing the Settings.
TruCredential Version 7.1 Software
TruCredential Version 7.1 Compatibility and Prerequisites
Licensing
Refer to the TruCredential Installation and Administration Guide, Part No. 527666‐001, for information about licensing your software.
If you must re‐host your license due to an upgrade or other change, first move the license to the new location and then reactivate it according to the instructions in the manual. You must reactivate or purchase a new license if you are changing editions, changing from one software version to another, or making similar changes. If you have the Express Edition, re‐hosting is not available; contact your sales representative for more information.
Supported Browsers

Google Chrome version 44.0.2403.107m through Chrome 48.0.2563; TruCredential 7.1 software is not compatible with Chrome 48.0.2564 or later.

Internet Explorer version 11.
TruCredential Version 7.1 New Features
12

Batch workflows.

A non‐printable area credential design layer.

A Quick Start wizard that helps users through the process of creating a credential. It also dynamically creates data capture workflows and field connections from a credential design.
Datacard® TruCredential™ Software Version 7.2

The Co‐Branding feature requires special arrangement and agreement with Entrust Datacard. If you are interested in co‐branding the TruCredential application, please contact your sales person for more information.

A blank step is included in the selection of workflow steps.

Expanded, context‐sensitive online Help.

Support for configuring the application to run in HTTPS (secured communication over SSL/TLS). Refer to the release notes for TruCredential version 7.1 software for information on this.

New webcam support: Logitech C920 webcam and DirectShow‐compliant webcams.

Reporting:

Design reports with custom layouts, headers, footers, and data fields.

Create and run reports.

Export reports in PDF format for printing or saving.

Batch printing: Send multiple records to the queue for printing.

External database read and write: A workflow step supports external database read and write operations for Microsoft Access, Microsoft SQL Server, and Oracle databases.

Additional smart card support for HID iCLASS and HID Prox cards.

ID Works version 6.5 and IDCentre version 6.5 migration: migrate your legacy card design, production form, and field connections to TruCredential software version 7.1.

A web‐based user interface.

All functionality is included within the application: a credential designer, enrollment, workflows, and reports.

Drag‐and‐drop workflows:

Pre‐built workflow steps for commonly used functionality in ID programs.

Drag‐and‐drop user interface configuration.

Quickly configure, encode, and personalize Mifare smart cards.

Integration with physical access control and human resources systems.

Embedded H2 database included.

Convenient soft licensing key (no USB device is necessary for licensing).

QR code support.

Numerous additional enhancements:

Usability improvement.
13
Datacard® TruCredential™ Software Version 7.2

Performance enhancement.

Support for a photograph field captured in color to be printed in grayscale on the color layer.

Paper badge support.

Print a sample card during the card design process.

Support for NTT/JIS magnetic stripe encoding.

Additional capture photograph property settings: auto‐capture, auto‐next, and camera rotation.
TruCredential Version 7.1 Resolved Issues

Chip profile configuration is now supported.

Sorting in the Users and Groups table. (NXID‐3184)

“Stopped” or “Failed” print jobs can now be deleted. (15270180)
TruCredential Version 7.1 Known Issues
14

If you rename an element on a card design that is connected to a workflow element, the connection is deleted. Reconnect the two elements using the Field Connections tool. (NXID‐5193)

In the credential designer, if you enable (select) a layer but do not click the “eye” icon to make the layer active, then it will not print on the credential. You must enable (select) and click the “eye” icon for each layer that you want to print or otherwise appear on a credential before printing it. (NXID‐
6052)

The following applies when migrating projects from ID Works or IDCentre to TruCredential software where the path set in ID Works or IDCentre software is not present and the programs are installed on different computers. If the photograph and signature field properties in ID Works or IDCentre software have the Storage option on the Storage tab set as File select path, then you must manually copy the photograph and signature images to the TruCredential software computer.

Upon installing TruCredential version 7.1 software, under rare installation configurations, a fully qualified path displays on the screen in Step 13. Ignore this path. (NXID‐5202)

In some cases, the Datacard Capture Manager service does not start up correctly during installation. If this happens, you cannot capture photographs. To resolve this issue, either restart your computer, or start the Datacard Capture Manager service again as Administrator. (NXID‐5286)

Under rare circumstances, when you are working in the credential designer with the Emboss or indent layer, the green design guidance box expands and the color palette is not displayed. If this happens, select the Emboss or indent layer in the layers panel to make the layer display correctly. (NXID‐5685, NXID‐5953)

The green design guidance box on the credential designer’s Emboss or indent layer may not accurately reflect your printer’s capabilities or your industry’s requirements for content placed in that Datacard® TruCredential™ Software Version 7.2
area. Refer to your own specifications to determine the positions required before finalizing a credential design that uses the Emboss or indent layer. (NXID‐5512, NXID‐4748)

If you rename a field in your workflow, the old field name displays in the Configured fields box and the new name displays in the Available fields box. To resolve this issue, move the old field name from the Configured fields to the Available fields box, then move the new field name from the Available fields to the Configured fields box. Save the workflow. Close and re‐open the workflow. The fields now show the new field name correctly. (NXID‐5573)

TruCredential software supports only DirectShow‐compliant webcams. If you have a ThinkVantage Virtual Camera installed on a ThinkPad, disable it and instead use the Integrated Camera to take a photograph for TruCredential software. If you do not, either no picture is taken or a black image displays. (NXID‐5642)

If a printer displays the message “Ribbon low” on the front panel, you cannot print until the ribbon is changed or until the message is otherwise cleared. (DPI‐892)

If file import columns are not connected to a workflow field, they are lost and no table columns are created for those entries when you click Save. Upon importing a file with the original configuration, TruCredential software displays a message that the column sizes in the import file do not match the table configuration columns. (NXID‐5617)

You have a field that you want to be saved to the database during enrollment. You must make a table connection to that field during the design process. Otherwise, at enrollment time, the data in the field will not be saved and no error informs you of this fact. (NXID‐6047)

If you are using a Datacard SR200 or SR300 printer connected using USB (and not a network connection), the following applies. The Log On tab for the Windows Datacard TruCredential Software service must be configured as a member of the local Administrators group but not as the Local System account. This means that you cannot encode smart cards with either printer in this configuration; use a network connection to encode smart cards. (NXID‐5835)

Administrators must set the TruCredential Windows service account to a non‐privileged user account, rather than a Local System account, to correctly print card size CR‐80. (DPI‐724) To do this:
a. Open the Windows Services.
b. Right‐click Datacard TruCredential Software and select Properties.
c. On the Datacard TruCredential Software Properties (Local Computer) window, click the Log On tab and click This account.
d. Enter the name of a user’s account on the computer, for example [email protected]. It may be necessary to click Browse and possibly to change locations to choose from an LDAP, depending on your network configuration, and then click OK on the Select User or Service Account window.
e. On the Datacard TruCredential Software Properties (Local Computer) window, after This account is specified, enter a Password and a Confirm password, then click OK.
f.
On the Services window, right‐click Datacard TruCredential Software and select Start.
15
Datacard® TruCredential™ Software Version 7.2
16

The All Tables option under Settings > Settings > Import and Export does not show connections between table columns and fields to be imported. View the actual table to see the connections.

In the credential designer, the properties panel is not available if you clear multi‐selected fields.

The Auto‐Sequence and Print Count fields must not be mapped to the Identity Column in SQL Server because they are generated values. Map a read‐only field to the Identity Column instead. (NXID‐5408)

For Select Path and Use TruCredential Path, do not use the same field name and path for both entries. If you do, files are overwritten during enrollment.

Configuration changes required to support USB‐connected printers prevent TruCredential from detecting smart card readers/couplers for the DPCL/DPCL2 printer. To enable smart card readers/
couplers to work, set up these printers as networked printers rather than connecting them with a USB cable.

An administrator can go to a user’s page (click Settings > Users and Groups > Edit User) to update information with or without changing the user’s existing password, which displays as “******”.

To change the user’s password, enter a new password in the password fields and click Save.

To leave the user’s password unchanged, either leave the existing password fields unchanged or leave the password fields empty and click Save. (NXID‐5782)

In the credential designer, the Emboss or Indent layer is only supported if the credential is in the landscape orientation. (NXID‐5692)

With paper printers, in certain installation configurations, you must change the TruCredential Windows service log on account and adjust the Windows Firewall settings. Factors affecting this include TruCredential software installation type, whether or not workstations are authenticated to a corporate network, and where the paper printer is located and how it is connected. (DPI‐724, NXID‐
4790)

All print jobs sent to a Generic‐type printer are entered into the Windows printing system with the same generic name, rather than with the value of the Print Job Identifier field from TruCredential software. (NXID‐5578)

When you migrate a project from TruCredential version 7.0 to version 7.1 software, be sure to click the table button for additional details about specific projects and whether additional action is necessary on your part to complete the migration.

A signature in WMF format overlaps the field above it in the workflow designer unless you adjust its location in the designer. (NXID‐4944)

WMF‐formatted signatures do not display in report queries until they have been displayed in a workflow (where they are converted to SVG). However, they never display in PDF reports. (NXID‐5098)

If you use a comma, space, or other special character in the Field Name, upon import or export the contents of the properties panel disappear and the boundary style changes. (NXID‐5115, NXID‐3570, NXID‐5678)
Datacard® TruCredential™ Software Version 7.2

When creating a batch workflow, clicking the Add button ought to take you to add a smart card workflow, but instead you a Save alert displays. (NXID‐5270)
The Following Are Not Supported in TruCredential Software Version 7.1

The Windows 10 operating system. (15925530)

The Code 39 and Code 39 extended bar codes cannot be printed at high density on the K‐panel of the printer ribbons. For new credential designs, either use the color layer or a different bar code. For migrated designs from the prior version of TruCredential software, update the design according to these restrictions. (NXID‐5874)

The U.S. Postal Service’s POSTNET ZIP+4 bar code is not supported. (NXID‐651)

The Emboss layer properties for the back of the credential are, instead, applied to the front. (NXID‐
5601)

Laminate twice is not supported, though it appears in the user interface under Layer Properties for the Lamination layer. (DPI‐588, NXID‐3718)

Any browser not listed in “Supported Browsers” on page 12, including Firefox, Safari, and Opera.

TruCredential v7.0 credentials, workflows, and other files cannot be imported into TruCredential v7.1. (NXID‐5236)

Use of the Microsoft Access database is not supported on a network drive. It is supported on a local drive. (NXID‐3907)

Deleting templates (workflow or credential templates) from the Import and Export page is not supported.

The Undo and Redo functions in the credential designer do not support field properties. (NXID‐4120, NXID‐4561)

Magnetic stripe encoding on the front side of a card is not supported. (NXID‐3272)

Ultraviolet printing is not supported on SR200 and SR300 printers.

In the credential designer, the Signature field is not supported on the Ultraviolet layer. (NXID‐5969)
17
Datacard® TruCredential™ Software Version 7.2
Background
Variable Graphic
Static Graphic
18
Borders
Photograph
Grayscale
Layer
Backdrop Removal/
Remove backdrop
Field
Ghosting/Semi‐opaque/
Percent Opaque Option
In the credential designer, the following feature combinations are supported as follows (NXID‐5970):
Sizing Options

This field cannot be used on this layer.
Color
—
Yes
Yes
Yes
Yes
Black
—
—
Yes
—
Yes
Ultraviolet
—
—
—
—
Yes
Background
Yes
Yes
—
—
—
Color
Yes
Yes
—
—
—
Black
Yes
—
—
—
—
Ultraviolet
Yes
—
—
—
—
Background
Yes
Yes
—
—
—
Color
Yes
Yes
—
—
—
Black
Yes
Yes
—
—
—
Ultraviolet
Yes
Yes
—
—
—

A WMF signature may overlap other credential fields when it is converted to SVG by TruCredential software. Adjust the card design to accommodate this. (NXID‐4944)

Margins required by particular printers are not supported by TruCredential software. Users must be aware of any margin limitations of their printers when designing their credentials. (NXID‐5523)

When importing a batch workflow, only one workflow (containing all the steps of the single and the batch workflow) is imported. There should be two separate workflows, one batch and one single, upon importing a batch workflow. (NXID‐5253)

If you are designing a data‐driven credential workflow, you must use the same type of bar code on each credential. (NXID‐5873)
Datacard® TruCredential™ Software Version 7.2

Printing a bar code with a black background using the color picker does not result in a viable bar code. To print a black‐on‐black bar code that cannot be copied for security purposes, create the bar code on the Black layer in the credential designer and then, on the Color layer, create a black box behind the bar code. (NXID‐5514)

Images that are not supported:



1 bit per pixel images.

Images that are not in RGB format.

Images that make use of transparency.

Images in the following formats: EPS, PCT, PCX, PSD, TGA, and WMF, among others.

Limited support of JPEG 2000 (J2K) images; JPEG 2000 part 1 is supported, part 2 is not. (NXID‐
5822)
Smart card features that are not supported:

Smart card personalization is not supported for the following Datacard printers: SP25+, SP35+, SP55+, SP75+, CP80+TM.

DESfire keys of type “DES” that are 16 or 24 bytes long (8 bytes is supported).

AES keys are not supported for the DESfire EV1 smart card chips. (NXID‐5694)

In a single‐workstation installation, you cannot print smart card jobs to a DPCL or DPCL2 printer that is connected using a USB cable. Non‐smart card print jobs do succeed in this configuration, however. (NXID‐1028)

Smart card encoding is not supported on the SR‐200 or SR‐300 printer if the printer is connected via USB cable.

Smart card encoding is not supported when the Windows TruCredential Service is configured as, not the Local System account, but as some other member of the local Administrators group.

Writing to block 3 of any Mifare Classic smart card is not supported. (NXID‐4064)

Exporting of chip profiles. (NXID‐6067)
Naming support:

Quick Start wizard: The name that you specify cannot start with the “$” character.

A workflow field used in a composite field must not contain an underscore in its field name.

Field connections do not support spaces in field names; spaces are removed when mapping fields.

After a software upgrade, spaces in composite fields are replaced with underscores. (NXID‐4873)

For the Microsoft Access database, column names with spaces in them are not valid. (NXID‐5651)

For printer names, these characters are not allowed / \ ? ; (NXID‐5842)
19
Datacard® TruCredential™ Software Version 7.2
Frequently Asked Questions
What is Supported?
Does TruCredential software Version 7.2 support databases hosted in cloud storage? (14057990)
No, this has not been tested by Entrust Datacard.
Can multiple printers be connected to one workstation via USB? (14058103)
No. TruCredential software Version 7.2 supports only one USB‐connected printer per workstation at this time.
Does TruCredential software Version 7.2 support manual duplex printing, in which cards are flipped over by hand? (14647308)
This is a feature of some printers. If a particular printer supports manual duplex printing, then Datacard® TruCredential™ Software v7.2 supports it.
Does TruCredential software Version 7.2 support deleting an existing database record? (14057861)
No, this is not supported at this time. You must modify the database directly.
What languages does TruCredential software Version 7.2 support? (15270227)
English
Spanish (Latin American)
Portuguese (Brazilian)
French
German
Japanese
Simplified Chinese
Smart Card‐Related Questions
For an existing workflow design that uses a smart card workflow, how do I change to a different smart card workflow?
Disconnect all field connections and then make the change to the other smart card workflow.
For the DESfire chip type, what is the size of the keys that must be entered in TruCredential software
Version 7.2? (14057925)
All DESfire keys of type “DES” must be 8 bytes long. Therefore, enter 16 ASCII hex characters in TruCredential software Version 7.2.
For the PICC Master Key for v7.0 and v7.1, only a DES key is supported so enter 16 characters to form the 8‐byte key.
In a 1‐wire network‐connected printer configuration, what smart card reader types can I use? (15270854)
The Duali is the only one permitted, which is identified by the “S7” label on the printer’s swing arm that you open to load ribbon. Note that all other reader types (S1‐S12) require a two‐wire USB connection.
20
Datacard® TruCredential™ Software Version 7.2
Why, when registering a Datacard® SD 360™ card printer (with a DPCL2 board), are no key readers found by TruCredential software when I click Discover? The key reader that I want to use is listed in the Windows Control Panel Devices and Printers list. (15270976)
Make sure to log on under the default Local System account setting, not as an Administrator or member of the Administrators group. Restart the TruCredential software Windows service and you can see the key readers.
How do I configure a multiple workstation environment in which one client workstation has a USB‐
connected printer?
Make sure that the printer driver for the printer is installed on the client workstation and that the log in account is left at the default “Local System”. Configure the Windows firewall on the client to allow inbound traffic on whatever port you used for the “Domain” profile, assuming both computers were authenticated to the corporate network. Note that you may be required to restart the Datacard TruCredential Service if you change the paper size, however.
Specific Error Messages
What can I do if I get an “error in locking the printer”? (15271369)
Typically all that you must do is to restart TruCredential software, which resets the software printer lock.
How can I recover from, “Initialize Error: The specified network password is not correct.”? (15271474)
Restart the Datacard Capture Manager service. Click on your system tray and show hidden icons (at the bottom right of your Windows screen) and verify that the Datacard Capture Manager service is displayed. Click the Datacard Capture Manager service icon to display the status window. If there is an error string in this window, record it in case you need to contact Support. Click the close button to stop the service. Click Start > Datacard > Capture Manager > CaptureManager and then right‐click Service and select Run as administrator. Make sure that the Datacard Capture Manager service is now running properly.
I got the message, “The capture device configured is not available.” when trying to take a photograph. What could be the cause of this? (15925533)
Make sure that your camera is turned on and plugged in to your computer. If you still get this message, click on your system tray and show hidden icons (at the bottom right of your Windows screen) and verify that the Datacard Capture Manager service is displayed. If not, contact your TruCredential administrator for assistance.
21
Datacard® TruCredential™ Software Version 7.2
During an external database write operation, I got the following message: “The system did not complete the task due to an unexpected error. Contact your TruCredential software administrator for assistance.” What could be the problem? (15271747)
Check the logs under C:\Installation Path\Datacard\TruCredential\logs. Often this is a database error caused by a “not null” column that was not updated by the system during an insert.
Note that the external database Write operation determines whether to insert or update the database. So, this may work on database inserts but not on updates.
When clicking on field connections, what could cause the error, “The system did not complete the task due to an unexpected error. Contact your TruCredential administrator for assistance.”? (15271304)
The following could be the cause of this error:

If your primary data source is a Microsoft Access database, there might be a space in the identity column name that is your primary key column. Spaces are not supported; delete the space to clear the error.

If no Data Source Configuration was set to Primary and the workflow was set to Use primary data source, you get this error. To clear the error, set the data source configuration to Primary.

If this was after a migration from ID Works or IDCentre software, make sure that you have copied the database, images, and signatures over to the new TruCredential software location.
Printing‐Related Questions
What does the Test Configuration button on the Printer Registration page test? (15271322)
It tests whether TruCredential software can communicate with the printer.
How can I clear the print queue? (14057556)
Click Settings > Tools > Printer Queues. A data table displays the print jobs in the system. You can delete or restart the print jobs.
Why is the print count that displays in the workflow different from that shown in the preview?
The two print count values are different until you click Personalize. The current print count that shows in the workflow is what the database print count value is equal to at the current time. It is updated to the number shown in the preview after you click Personalize.
I correctly registered an HIF‐type printer (for example, the SP35+) and printed a credential to it, but the Print Job status said “Waiting” indefinitely. How can I print this credential? (15270780)
Select Start > Devices and Printers. Right‐click the printer driver for your printer and select Printer properties. Click Print Test Page, and then click OK and close the Devices and Printers page. A test page and your card now print, as will any future cards that you send to the printer without waiting.
Why does my SR300 printer, connected via USB, eject two cards instead of printing on the back side of the first card? (15925402)
Like most paper printers, the SR300 prints single‐sided by default. To print on both sides of the same card, on your computer select Start > Devices and Printers. Right‐click on the SR300 printer and select Printer Preferences. On the Print tab, select Print on both sides.
22
Datacard® TruCredential™ Software Version 7.2
I wasn’t able to print to both sides of the credential when printing: the front design printed on one card and the back on a second card. What could be the trouble?
This can happen if the Windows TruCredential Service is configured as, not the Local System account, but as some other member of the local Administrators group. It can also happen if certain printers are connected by USB cable rather than by a network connection. It can also happen if your printer preferences aren’t set correctly. To correctly set the printer preferences:
a. Go to Start > Control Panel > Hardware and Sound > Devices and Printers.
b. Right‐click on your configured printer name and select Printing preferences.
c. Under the Layout tab, set Print on Both Sides to Flip on Long Edge.
d. Click the Advanced button and set the options Apply the Laminator material 1 and Apply the Laminator material 2 to Do not apply.
General Questions
Why are batch personalization and using an external database not available in TruCredential software version 7.1 if I have upgraded from TruCredential software version 7.0?
If you are upgrading from version 7.0 to version 7.1, you must upgrade your license to get the new features “Batch Personalization” and “External DB Operation”.
How can I select a Line in the credential designer?
Zoom in, click and hold the mouse button, and then create a selection box around the line.
I have made field connections in the File Import Configuration field connector. Why is the Save button not available?
To save field connections, connect all of the table column primary keys.
When configuring a Microsoft Access database, what is the correct URL to use? (15271628)
Use this URL: jdbc:ucanaccess://Path to the database.accdb. Note that it might be easier to configure the database by specifying the properties.
How do I configure TruCredential software to use a different product license server? (15271800)
1. In a text editor such as Notepad, open the file C:\Installation Path\Datacard\TruCredential\properties\trucredential.properties where Installation Path = Program Files by default.
2. Under “# License server configuration”, change the property “trucredential.license.server.ip=” to the IP address of the computer that is hosting the product license server that you want to use. For example, “trucredential.license.server.ip=123.45.6.78”.
3. Restart the Datacard TruCredential Software service.
Does uninstalling TruCredential software remove the database?
No. The database and its data are left intact when the software is uninstalled.
23
Datacard® TruCredential™ Software Version 7.2
What can I do if the image that I captured is poor quality or pixelated? (14647919)
If you are capturing a .jpg or .jpg 2000 image, make sure that the compression is not set too high: over‐compression can cause this problem.
Where is the default TruCredential software database on my computer? (15925555)
C:\Users\Public\Public Documents\Datacard\TruCredential\db
How can I include a Composite field in the card design? (NXID‐5725)
Include a Composite field by adding a Composite field to a workflow, a Text field to the card design, and then connecting the two fields using the field connector.
How does the Check Box field threshold work? (15271691)
The Check Box field can be connected to the following database column types: BIGINT, BIT, BOOLEAN, CHAR, INTEGER, NUMERIC, SMALLINT, TINYINT. If the Check Box field is connected to a numeric data type column (BIGINT, INTEGER, NUMERIC, SMALLINT, TINYINT) and not to a read‐only field, then the system saves the value according to the threshold value manipulation based on whether the Check Box field is selected or cleared. If the Check Box field is read‐only, then TruCredential software does not send any data for that column. If the database also provides no data, there is a null value in the database for that column.
While loading enrollment records, the Check Box field behaves as follows:

If the connected database column has a null value, then the Check Box field state is set according to the field’s property The display state for NULL values.

If the connected database column has a numeric value (provided by the database), and if it is greater than the threshold value, then the Check Box state is selected. If it is less than the threshold value, the Check Box is cleared.
How do I connect to an external LDAP? (15271611)
There are two ways to connect to an external LDAP using TruCredential software. Both ways involve editing the External LDAP configuration section of the file using information about your external LDAP
C:\installation path\Datacard\TruCredential\properties\trucredential.properties.
24

If you want to sign in using a common name or display name, such as FirstName LastName, edit the following lines as shown:
external.ldap.base.provider.url=ldap://IP address:port number
external.ldap.base.dn=Distinguished name
external.ldap.user.dn=Organizational unit
external.ldap.user.dn.login.attr=cn

If you want to sign in using a sign‐in name or user ID created in Active Directory, edit the following lines as shown:
external.ldap.base.provider.url=ldap://IP address:port number
external.ldap.base.dn=Domain name
external.ldap.user.dn=Not required, leave blank
external.ldap.user.dn.login.attr=samaccountname
Datacard® TruCredential™ Software Version 7.2
I am an administrator, and I just changed the authentication method from Delegate Authentication to Application. Why was I signed out of the application immediately?
Administrators: If you change the authentication method from Delegate Authentication to Application, you are signed out immediately when you click Save. This automatic sign‐out action does not apply to the first user to sign in to TruCredential software, which is the admin user. All other users having Administrative permissions are signed out. Now, the admin user must assign temporary passwords to all other users of the system, including Administrators group members.
Open Source Software
Open source software that is included with or is part of this software product is listed in Open_Source_Software_Information.htm
Technical Support
For technical inquiries, please include your product model and serial number in your email, or have this information available when calling.
Americas
Email: [email protected]
Phone: +1 800.328.3996 or +1 952.988.2316
Europe, Middle East, and Africa
Email: [email protected]
Phone: +44 1489 555 600
Asia Pacific
Email: [email protected]
Phone: +852 28210126
Go to entrustdatacard.com/support for information about getting support in your region of the world.
25