Loftware Spectrum User Guide
Loftware Spectrum User Guide
Version 3.0.1
User Guide
2017May. All rights reserved. Version 3.0.1
Loftware, Loftware Spectrum, LLM, Loftware Label Design, Loftware Print Server, LPS, Loftware Connector, Global Marking
Solutions, I-Push, and I-Pull are all registered trademarks of Loftware, Inc. Loftware WebAccess, LWA, and Loftware Web Services
are trademarks of Loftware, Inc. SAP is a registered trademark of SAP AG in Germany and in several other countries. Oracle and
Java are registered trademarks of Oracle and/or its affiliates. All other marks are the property of their respective owners. Loftware
Spectrum contains barcode components licensed from IDAutomation.com, Inc. These products may only be used as part of and in
connection with Loftware Spectrum.
Welcome to LoftwareSpectrum 20
Documentation and Support 21
About the LoftwareSpectrum UserGuide 22
Open the SpectrumUserGuide 23
User Interface: Help 24
About Loftware Spectrum 25
Tabs 26
Buttons 28
Licensing, Warranty, and Support 29
Technical Support 30
Contact Loftware 31
Sales 32
Customer Account Management 33
Engineering Technical Support (ETS) 34
Professional Services Group 35
Technical Requirements for Spectrum3.0 37
Server Requirements for Spectrum3.0 39
Requirements for Loftware Spectrum Database Server with Existing Oracle
Database 40
Requirements for Loftware Spectrum Database Server with Embedded Database 41
Requirements for Loftware SpectrumApplicationServer 42
Requirements for Multi-Site Deployment 43
Server Performance Tips 44
Client Computer Requirements for Spectrum3.0 46
Requirements for Spectrum Client Computers 47
Requirements for SpectrumRemotePrint Agent Computers 49
Other Requirements for Integrations 50
Requirements for Oracle Applications Integration 51
Requirements for Integration for use with SAP Applications 52
Log in to Spectrum 53
Spectrum Root Folder 57
Change Your Password 58
Loftware Spectrum Tools 59
Designing Labels 60
Configuring the Design Workspace 61
Set User Preferences 62
Select Data to Display in Design 63
Context Sensitivity
When you click Help in Spectrum, the SpectrumUserGuide displays a topic about the section you
are viewing. For example, if you click help while you are in Design, the help for the Design
page is displayed. From these topics, you can follow links to complete tasks and to view
reference material.
Dynamic Help
When you click Help in Spectrum, a dynamic web-based version of the help is opened by
default. The dynamic help system is hosted on Loftware's website, and it gives you access to up-
to-the-minute content updates, additions, and corrections. For information about how an
administrator can configure Spectrum to use a static copy of the help system instead, see
"Change the Source of Spectrum Help" on page 772.
Help Version
At the bottom of each topic is a copyright statement that includes the version of Spectrum and
the revision of the help that you are viewing.
The example shown below would indicate that this topic is from the B (or second) revision of
the 1.0 version of SpectrumUserGuide.
Copyright 2012 Loftware, Inc. All rights reserved. Version 1.0 Rev B
Comments
Each topic contains an Ask the Doc Team link. Please send us your thoughts about what we got
right, what we got wrong, and where we need to expand our documentation.
After logging into Spectrum, you can use the Help buttons to open the SpectrumUserGuide.
l Click near the top of the Spectrum window in the title bar.
l Click the button in dialog boxes in Spectrum to display context sensitive help.
The following tools are available while viewing the Help for LoftwareSpectrum.
Contents
The Contents tab contains a list of the help topics available. Think of it as the Table of
Contents of a book.
Glossary
The Search field allows you to search all the content in the help system.
Tabs
General
l Spectrum Version
l Server Name
l Usage
l Operating System
l Server ID
License
l Spectrum Version
l Server Name
l Usage
l Contract
l Data Management
l Business Rules
l Web Service Integrations
l Multi-Site (if applicable)
l Device Seats
l File Drop Integrations
l Oracle Integrations
l Integrations for use with SAP ERP
Advanced
l Spectrum Version
l Server Name
l Usage
l Operating System
l Server ID
l Contract
l Server Version
l Server Build Number
l Client Version
l Client Build Number
l Flash Player Version
l Flash Player Debugger
l Java Home
l Java Runtime Version
l Java Vendor
l Java Classpath
l OS Name
l OS Version
l OS Architecture
Buttons
Button Description
Copy to Saves a copy of the information on all tabs, which can be pasted into an
Clipboard application such as a word processor.
OK Closes the About Loftware Spectrum dialog box.
Tip: You can check the version of LoftwareSpectrum and obtain information
about its components, the SpectrumApplicationServer, and your Spectrum
license (including the integrations allowed) by clicking in the Spectrum
title bar. You can save a copy of the information by clicking the Copy to
Clipboard button in the About Loftware Spectrum dialog box and pasting into
an application such as a word processor.
Technical Support
Software licenses purchased directly from Loftware include the first year of Technical Support.
This initial 12-month support period starts on the day the product is shipped and invoiced from
Loftware's factory. During this period, customers are eligible to receive unlimited telephone and
web-based support and access to software upgrades and enhancements.
Contact Loftware
Locations
US Office GmbH Office
Corporate Headquarters Rmerstrasse 39
249 Corporate Drive 78183 Hfingen
Portsmouth, NH 03801 Germany
Phone: +1-603-766-3630 Phone: +49 771-8978-4250
Fax: +1-603-766-3631 Fax: +49 771-8978-4251
UK Office Asia Office
Abbey House 31 Rochester Drive Level 24
Brooklands Business Park Singapore 138637
Wellington Way, Weybridge Phone +65-6808-8763
Surrey KT13 0TT Fax +65-6808-8779
Phone: +44 (0) 1932 268470
Sales
Loftware's Sales Department is available for product information, quotes, and placing orders.
Call between 8:00a.m. and 5:00p.m. (Eastern Time), Monday - Friday. Email and faxes are
received 24 hours a day.
Phone: +1-603-766-3630, Option 1
Fax: +1-603-766-3631
Email: [email protected]
Loftware's Customer Account Management Department is available for product and license
information and placing orders. Call between 8:00a.m. and 5:00p.m. (Eastern Time), Monday -
Friday. Email and faxes are received 24 hours a day.
Phone: +1-603-766-3630, Option 2
Fax: +1-603-766-3631
Email for Customer Service: [email protected]
Email for Contracts Administration: [email protected]
If you are a Systems Analyst, Integrator, or an MIS, IS, or IT Director and your questions
specifically refer to integrating other applications or programs with Loftware, please contact one
of our System Analysts for a free telephone consultation. This is an extremely important and
invaluable service to those who are in the process of designing and developing labeling systems.
It is our desire to help you start your development process in the right direction. Email and faxes
are received 24 hours a day.
Phone: +1-603-766-3630 x209
Fax: +1-603-766-3631
Email: [email protected]
Server Requirements
All enterprise environments are unique. The server requirements necessary to fulfill your
organization's needs can be affected by the number of unique labels to be printed, the number of
devices to which labels will be printed, the relationship between the number of labels and the
number of devices, the complexity of your label templates, and other factors. Depending on
your organization's needs, you may able to use these recommendations as base guidelines.
Loftware's Professional Services Group can help you determine the server requirements
necessary to meet your exact business needs.
Database Server
You can configure and install Spectrum into your existing Oracle database, or you can use the
embedded database included with Spectrum.
l "Requirements for Loftware Spectrum Database Server with Existing Oracle Database"
on page 40
l "Requirements for Loftware Spectrum Database Server with Embedded Database" on
page 41
Note: For more information, see the LoftwareSpectrum Installation and Configuration
Guide.
Application Server
Whether you install the Spectrum database into your existing Oracle database or use the
embedded database, Loftware requires the SpectrumApplicationServer to be installed on a
dedicated server.
l "Requirements for Loftware SpectrumApplicationServer" on page 42
Tip: Spectrum can be configured with the application and embedded database on
the same computer. A combined server may be appropriate for proof of concept or
development environments, but it is not supported for production printing. You
must follow the Embedded Database Server requirements for a combined
application and embedded database server.
Device Requirements
LoftwareSpectrum supports printers from a variety of manufacturers. For a list of supported
printers, in Spectrum click Device Management, click Add Device, select a Family, and then
click Model to view the list of supported models. The printer models supported may vary with
the version of Spectrum.
Note: LoftwareSpectrum encodes print data using UTF-8. Ensure that your
device firmware supports UTF-8. Older devices may not support this encoding.
1A configuration of a Spectrum environment that includes Spectrum instances located at different sites within the same WAN. In a
multi-site deployment, each Spectrum instance acts as either a headquarters or a facility.
2A Spectrum Application Server and a Spectrum Database Server that are associated with each other by a Spectrum License.
These are the database server requirements for LoftwareSpectrum3.0 when it is used with a
new or existing Oracle database server.
Important! The storage for both the flash recovery area and the tablespace data
must be on a fault-tolerant system, such as SAN or NAS. The same is
recommended for all drives that hold the Spectrum applications and data.
Component Requirement
CPU 8 cores or better
Memory 32 GB RAM or more
Available disk space for 2 TB or more. Multiple factors can affect the amount of space
database required. Contact Loftware's Professional Services Group (PSG)
for assistance.
Available disk space for 2.5 TB or more
flash recovery
Oracle One of the following, as appropriate for the operating system:
l Oracle Database 12c
Constraints
The Loftware-supplied embedded database includes the following limits. If these limits are
exceeded, you must use the non-embedded database configuration. For more information, see
"Requirements for Loftware Spectrum Database Server with Existing Oracle Database" on page
40.
Component Maximum
Archive retention 12 months or less
period
Peak load 10 labels per second, summed across all distributed application
servers
Label throughput 1 million labels per month
Users 1500 users
Devices 1500 devices
Archive retention 50 million labels
Distributed servers 3 SpectrumApplicationServers, including the primary
If you are configuring a multi-site deployment1, the following are requirements for facility
sites.
l Each facility site can have only one SpectrumApplicationServer and one Spectrum
Database Server.
l Each facility site must use the Loftware-supplied embedded database.
l The name of the root folder in Spectrum must be the same at the headquarters site and at
each facility site associated with that headquarters.
l The headquarters and facility sites must be in the same WAN, but facilities are not
required to be able to communicate with each other.
1A configuration of a Spectrum environment that includes Spectrum instances located at different sites within the same WAN. In a
multi-site deployment, each Spectrum instance acts as either a headquarters or a facility.
The following information may help you configure your Spectrum environment and your servers
to optimize their performance.
Configuring for High Availability with Distributed Services
If you are planning a Spectrum environment that will include more than one
SpectrumApplicationServer, it is recommended that you configure your environment to
support distributed services. In a Spectrum environment with distributed services, all
SpectrumApplicationServers are configured to interact as peers within the Spectrum
environment, all accessing the same Spectrum database.
In such an environment, you use distributed services to manage which server or servers are
providing Spectrum functionality at any time. In Spectrum, you can configure distributed
services for high availability or for failover only. It is recommended that you configure for high
availability of distributed services in Spectrum. This approach involves configuring Spectrum to
load balance those services that support load balancing so that they are run concurrently on
multiple SpectrumApplicationServers. Services that do not support load balancing should be
configured to fail over among SpectrumApplicationServers so that if one or more servers go
offline, a standby server or servers begin running the associated services to minimize any
interruption for users.
For information about how to install Spectrum to support distributed services, see the
LoftwareSpectrum Installation and Configuration Guide in More Documentation. For information
about configuring distributed services, see "High Availability with Distributed Services" on page
716.
For information about how to install Spectrum to support distributed services, see the
LoftwareSpectrum Installation and Configuration Guide. For information about configuring distributed
services, see the LoftwareSpectrum UserGuide.
Optimizing Performance
The following tips may help you to optimize the performance of your Spectrum configuration.
l Consult your database administrator for guidance about database tuning.
l The more memory that you have configured for the SpectrumApplicationServer, the
greater the number of devices, label templates, and users that it can support. For more
information, see the LoftwareSpectrum Installation and Configuration Guide.
l Increasing the amount of memory available to the database server typically improves
performance. If you can make significantly more memory available, you can dramatically
increase performance because all or a significant portion of the label and configuration
data can be cached in memory.
l The amount of space on the database server required for recent history data is typically
greater and more variable than the space required for label and configuration data.
However, if you can make the amount of memory required for recent history data
available on the database server, you can dramatically increase the performance of
reporting.
l Sufficient network bandwidth must be available to support your expected printing
throughput.
Each computer on which the LoftwareSpectrum3.0 client software will be run must be able
to connect to the SpectrumApplicationServer and has the following requirements.
Component Requirement
CPU 2.0GHz Dual Core or better
Memory One of the following
l 4GB RAM or more (64-bit operating system)
l Windows 10
l Windows 8.x
l Microsoft Edge
DNS name.
l If Windows Server is installed, ensure that the Role
LoftwareSpectrum3.0 supports remote printing, the act of printing a label to a device that
would not normally be accessible to Spectrum by using your LAN or by using a direct
connection to Spectrum. For example, printing using a device that is physically connected to a
computer outside of your WAN. The SpectrumRemotePrint solution includes a Remote Print
Agent that is installed on a remote computer. Each Remote Site computer on which
SpectrumRemotePrint will be run has the following requirements.
Component Requirement
CPU 2.0GHz Dual Core or better
Memory 4GB RAM or more
Operating system One of the following 64-bit operating systems:
l Microsoft client computer operating systems
l Windows 10
l Windows 8.x
l Microsoft Edge
l Oracle 11g
LoftwareSpectrum Integration for use with SAP Applications is an optional component that
extends the functionality of SAP applications, incorporating LoftwareSpectrum capabilities so
that users can print labels from SAP applications. Print requests initiated by users in SAP
applications are processed and printed by Spectrum, and Spectrum reports the status of each
request to the originating application. You can configure as many integrations as your Spectrum
license allows. If you are integrating Spectrum3.0 with SAP ERP, you must meet the following
requirements.
Component Requirement
License Spectrum license that includes Integration for use with SAP Applications
SAP ECC SAPECC 6.0 or later with the latest enhancements
SAP JCo SAP JCo (sapjco3.jar) 3.0.16 or later must be deployed to the
SpectrumApplicationServer. SAP JCo can be obtained from SAP
Marketplace. For more information, see "Preparing for Integration for Use
with SAP Applications" on page 1086.
Java Java Development Kit (JDK) version 1.8 must be installed on the SAP
Application Server for the Command Line Interpreter
Log in to Spectrum
To log in to Spectrum, use this procedure.
Note: Logging into Spectrum simultaneously as different users from the same
workstation is not supported.
1. Open Spectrum from a supported browser. The Login page is displayed.
Example
Enter the following in the address field of your browser, where spectrum-server
is the name of the server hosting Spectrum for your organization:
http://spectrum-server:8080/loftwarespectrum
Note: If opening Spectrum in Internet Explorer, use the fully-qualified
name of the server, such as www.example.com, rather than a short form of
the server name such as example. To permit the use of short names, in
Internet Explorer configure the Compatibility View Settings so that intranet
sites are not displayed in Compatibility View.
Important: Changing the root folder name after you have started using Spectrum
is not recommended.
Note: In a multi-site deployment, the name of the root folder must be the same at
the headquarters (HQ) and at each facility associated with that HQ.
Designing Labels
The topics in this section describe how to use LoftwareSpectrum to perform the following
tasks.
l Configure your Design workspace by using User Preferences.
l Design and develop label templates, forms, layouts, reusable objects, or applications by
using Design.
l Design and develop business rules by using the Configurator in Process Design.
1A physical printer, print queue, or other target for output, such as an image file or a PDF file.
1A physical printer, print queue, or other target for output, such as an image file or a PDF file.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
1For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
2A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
To change the source for data displayed in Design, use the following procedure.
1. In Design, click Options > Design Data.
2. Select one of the following:
n Default Value: The values specified in the Default Value property for each field
are used.
n Placeholder: The data used for each field is placeholder data 1 provided by
Spectrum.
n LiveData Set: If configured, values from a live data set2 obtained from a
Database data source, an Alternate data source, or a Date/Time data source are
used. You can also add data map entries to the data set manually.
Tip: If the Default Value property or the value from a live data set is empty or
contains only a space and that option is selected, then a placeholder value is
displayed in the Label view or Form view in Design. No visible indication of the
field is displayed when you preview or print in Design.
1For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
2A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
To add data map entries to a data set by querying a Database data source, an Alternate data
source, or a Date/Time data source, use the following procedure.
1. In Design, click the title bar of the Data Sources pane in the left column and the Data
Sets pane in the right column to expand those panes if they are collapsed.
2. In the Data Sources pane, click a Database data source, an Alternate data source, or a
Date/Time data source.
3. Click to query the selected data source and save the data to a live data set.
4. Click File > Save or click the Save button on the toolbar to save the label template
or reusable object.
Important! A data set is part of a label template or a reusable object. If you
do not save the label template or reusable object, the data set that you
created will be discarded.
In the Data Sets pane, a data map entry or data map entries is added using data retrieved by
querying the data source.
To add data map entries to a data set by importing data from an XML file or a CSV file, use the
following procedure.
1. In Design, click the title bar of the Data Sets pane in the right column to expand it if it
is collapsed.
2. In the Data Sets pane, click the item that should be the parent of the new data map
entries, such as the Live data set.
3. Click to open the Import Data dialog box.
4. In the Import Data dialog box, select whether you are importing data from an XMLfile
or a CSV file.
5. If you are importing data from a CSV file, specify the following information about the
source data.
a. Select whether the source data is tabular data or key/value pairs (data map entries).
b. For Text Qualifier, enter the character that can be used to enclose the data of
one cell in the source data. By default, this is a double quotation mark (").
6. Select the XML or CSV file to import, and then click OK.
7. Click File > Save or click the Save button on the toolbar to save the label template
or reusable object.
Important! A data set is part of a label template or a reusable object. If you
do not save the label template or reusable object, the data set that you
created will be discarded.
To manually add a data map entry 1 to a data set or to alter a data map entry in a data set, use
the following procedure.
1. In Design, click the title bar of the Data Sets pane in the right column to expand it if it
is collapsed.
2. To add a new data map entry to a data set, do the following.
a. In the Data Sets pane, click the item that should be the parent of the new data
map entry, such as the Live data set.
b. Click to create a new data map entry.
c. In the Add Entry dialog box, enter a name and a value for the data map entry, and
then click OK.
d. Repeat for any other data map entries to be added.
3. To delete a data map entry from a data set, do the following.
a. In the Data Sets pane, click the data map entry that you want to delete from the
data set.
b. Click to delete the selected data map entry and its children, if any.
c. Repeat for any other data map entries to be deleted.
4. To change a data map entry in a data set, do the following.
a. In the Data Sets pane, click the data map entry that you want to change.
b. Click to edit the data map entry.
c. In the Edit Entry dialog box, change the name and value as needed, and then
click OK.
d. Repeat for any other data map entries to be changed.
5. Click File > Save or click the Save button on the toolbar to save the label template
or reusable object.
Important! A data set is part of a label template or a reusable object. If you
do not save the label template or reusable object, the data set that you
created will be discarded.
1A name (key) and value pair in the data map for a job.
You can add a grid overlay to your Design workspace to aid in aligning fields.
l Click View > Grid. The grid appears on the label and form view. The grid setting field
and Set Grid button are displayed.
To change grid settings
Zoom
To change zoom level
From the Menu
1. Click View, and point to Zoom.
2. Select a zoom percentage from the list.
The Design view changes to the new zoom level.
From the Toolbar
General Preferences
Preference Description
Display The language used in the user interface of Spectrum. Options include the
Language following:
l English
l German
l French
l Spanish
l Simplified Chinese
l Traditional Chinese
l Portuguese (Brazilian)
l Japanese
Landing Page The page (top-level tab) that is displayed when you log in to Spectrum.
Home Folder Folder in Spectrum initially selected and expanded in the tree when
opening, saving, or printing.
Initial Label The label template or process that is initially loaded when you click Print.
Default Process The process used if users to whom this profile is applied do not select a
process when printing a label template from Print.
ReprintProcess The Reprint process used when users to whom this profile is applied click
Reprint in Status.
Change Display a dialog box that allows you to change your password for
Password Spectrum.
Label/Document Preferences
These preferences control what is initially selected in Design when you create a new label
template. However, even if these preferences are locked down, you can change what is displayed
for the current session by selecting options in Design.
Preference Description
Size The default size used when producing a label template.
Width The default horizontal span of the label template.
The unit of measure is as defined in Units under Design Preferences, or in
Design under Options > Units.
Height The default vertical span of the label template.
The unit of measure is as defined in Units under Design Preferences, or in
Design under Options > Units.
Shape The default appearance of the outside edge of the label canvas when you
create a new label template.
Orientation Sets the default direction objects are aligned on the label when you create a
new label template.
Document The default resolution in dots per inch for objects on the label.
DPI
Font The default font category to be used on the label.
Category TrueType
DPL1
IPL2
ZPL II3
Note: If Use Label Font Category is selected, the default
type of font is whatever type was most recently used by that
user when creating a label template or reusable object.
New Whether to display the Create Label dialog box when creating a new label
Document template.
Dialog Box If Bypass and use my preferences is selected and if Size (or Width and
Height), Shape, Orientation, Document DPI, and Font Category are
configured in your preferences, then the dialog box is not displayed.
Otherwise, the dialog box is displayed.
Design Preferences
These preferences control what is initially displayed in Design when a Document Designer
creates or edits a label template. However, even if these preferences are locked down, the
Document Designer can change what is displayed for the current session by selecting options in
Design.
Preference Description
View Whether to initially display the Label View, Form View, or both.
Units The default unit of measure to be used to position and size objects in label
templates. Options include inches, cm, and mm.
Grid Whether to initially display an overlay grid to assist Document Designers with
aligning objects. The dots or lines of the grid are not displayed in printed
labels or in the forms displayed to Data Providers. The type of grid can be
configured in Grid Settings.
Align to Whether to initially force the top left corner of each object to align with the
Grid nearest alignment overlay dot or intersection of lines. Whether the grid is
used can be configured in Grid.
Grid The type of alignment overlay. Options include Dot, Line, Dotted Line, and
Settings Dashed Line.
The dots or lines of the grid are not displayed in printed labels or in the forms
displayed to Data Providers. Whether the grid is used can be configured in
Grid.
Preference Description
Design What data to show in fields when displaying a label template or a reusable
Data object in Design. This option affects what is displayed in the Label view and
Form view in Design, as well as what is displayed when you preview or print
a label in Design. More specifically, this option affects what is displayed in
text fields, barcode fields, and variable image fields.
l Default Value: The values specified in the Default Value property
1For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
2A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Print Preferences
These preferences control the default options when printing from Print. However, even if these
options are locked down, you can change printing options for the current session on Print.
Preference Description
Default The device 1 used unless you select a different device at print time.
Device
Clear fields Whether to automatically reset all values entered in the form for on-demand
after print after printing occurs.
successful
print
Navigation Whether the Documents Tree is displayed in Print.
Panel Show: The tree is displayed, but you can click a control to hide it.
Hide: The tree is hidden, but you can click a control to display it.
Hide and Lock: The tree is hidden and you cannot display it.
Allow Print Whether the Preview button is displayed in Print.
Preview Note: To use Print Preview, a user should have a role with
Print permission for Documents, have Print permission for
Documents for folders containing label templates and images to
be previewed, and have Allow Print Preview selected in User
Preferences.
View Data Whether to allow a user to click the object title in Print and display the data
Map on map entries in a dialog box. For more information, see " View the Print Data"
PrintPage on page 505.
1A physical printer, print queue, or other target for output, such as an image file or a PDF file.
Buttons
Button Effect
Save Save any changes that you have made to your preferences.
Cancel/Undo Discard any changes that you have made to your preferences.
Edits
Restore Reset all of your preferences to the default values specified in the user
Defaults profile applied to you. These default values can be changed in the user
profile by an administrator.
Note: You cannot import an object from an import (SER) file into a folder in
which an object with the same name already exists unless the folder is version-
controlled, the object in the folder is checked out to you, and the version
number of the object in the folder is less than the version number of the object
you are importing.
Recognizing version-controlled items
When you open a version-controlled object, the Version is displayed in the bar at the bottom
of the editing pane in Design or Process Design. A lock icon is also displayed in this bar if
the object is checked in. Also, in the File menu, the Version Control > Check In option is
available if the item is checked out, and the Version Control > Check Out option is
available if the item is checked in and you have the permissions needed to check out the
item.
Version-controlled folders are identified in console trees where they appear by the icon .
In a console tree, if a label template is checked out, it is identified by the icon . If
checked in, it is identified by the icon .
1The ability to maintain distinct versions of a label template or other item. An item is checked out to be modified, and checked in to
save a new version. After a version is checked in, that version cannot be changed.
1When version control is used, a version for which the minor version number is zero. Users with some permissions can print only the
latest published version.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
3When version control is used, a version for which the minor version number is zero. Users with some permissions can print only the
latest published version.
1When version control is used, a version for which the minor version number is zero. Users with some permissions can print only the
latest published version.
2A Spectrum role with all permissions except those needed for role administration.
3Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
4A Spectrum role with all permissions except those needed for role administration.
If label templates that you create are typically copied from one folder to another,
it is recommended that you save layouts and label templates in separate folders
to prevent confusion. Administrators can copy all label templates and layouts in a
folder to a second folder. If associated layouts and label templates are mingled in
the same folder, when an administrator copies all items in the folder to a second
folder, label templates in the second folder still point to the layouts in the
original folder.
Note: A version-controlled layout must be published before it can be attached to a
label template.
Save a Copy
To create a copy of a version-controlled object that you can edit, click File > Save As, select
the folder where you want to save the new copy, change the name if desired, and then click OK.
Next Steps
If the object is ready to be used in production, you can "Publish a Version-Controlled Object"
on page 87.
1A Spectrum role with all permissions except those needed for role administration.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
2In relation to media, the organization of labels specified by a layout. In relation to the Spectrum user interface, a top-level tab.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
You can use a label template to design a label for printed output.
To create a new label template, use this procedure.
1. In Design, click File > New > Label or click the button.
2. In the Create Label dialog box, configure the "Label Template Properties" on page 273.
Note: To view or configure the unit of measurement, in the menu bar
select Options > Units.
Tip: To configure a custom label template size, for the Size field select
Custom. Specify the dimensions of the label template in the Width and
Height fields.
3. Click OK. The Label and Form views are displayed.
Best Practice
Save your label template immediately after creation.
Save the Label Template
Create a Layout
You can use a layout to configure the organization of labels within a page (a sheet of stock or a
row of roll stock).
Note: Stock layouts are available in Document Templates\Stock Layouts.
To create a new layout, use this procedure.
1. In Design, click File > New > Layout or click the button. A new layout is
displayed.
2. In the Properties pane, configure the "Layout Properties" on page 282.
Tip: To configure a custom stock size, for the Stock Size field select
Custom. Specify the dimensions of the stock in the Width and Height
fields.
3. Click File > Save As.
4. In the Save As dialog box, select a folder in the document tree, and enter a name for the
layout.
Characters permitted in names
The following characters are permitted in the name: letters, numbers, parentheses, square
brackets, ampersands, asterisks, plus signs, equal signs, commas, semi-colons, and tildes.
Additionally, the following characters are permitted but cannot begin or end the name:
spaces, double quotes, single quotes, hyphens, underscores, periods, and grave accents.
For letters, the case that you specify is displayed, but case is ignored when Spectrum
interprets a name.
5. Click OK.
Best Practices
Save your layout immediately after creation.
If label templates that you create are typically copied from one folder to another, it
is recommended that you save layouts and label templates in separate folders to
prevent confusion. Administrators can copy all label templates and layouts in a
folder to a second folder. If associated layouts and label templates are mingled in the
same folder, when an administrator copies all items in the folder to a second folder,
label templates in the second folder still point to the layouts in the original folder.
Note: A version-controlled layout must be published before it can be attached to a
label template.
Create a Form
You can use a form to design a data entry user interface to use with your label templates.
To create a new form, use this procedure.
1. In Design, click File > New > Form or click the button. A blank form is displayed.
2. In the Properties pane, configure the "Form Properties" on page 284.
Note: To view or configure the unit of measurement, in the menu bar
select Options > Units.
Tip: To configure a custom form size, for the Size field select Custom.
Specify the dimensions of the form in the Width and Height fields.
3. Click File > Save As.
4. In the Save As dialog box, select a folder in the document tree, and enter a Name.
Characters permitted in names
The following characters are permitted in the name: letters, numbers, parentheses, square
brackets, ampersands, asterisks, plus signs, equal signs, commas, semi-colons, and tildes.
Additionally, the following characters are permitted but cannot begin or end the name:
spaces, double quotes, single quotes, hyphens, underscores, periods, and grave accents.
For letters, the case that you specify is displayed, but case is ignored when Spectrum
interprets a name.
5. Click OK.
Note: The first time you save a form to a version controlled folder, the form is
automatically checked out. When you are finished editing it, be sure to click File >
Check In to save and check in your version and make it available for others to
check out.
Best Practice
Save your form immediately after creation.
You can use a reusable object to include components for use in a form for data entry, a label for
printed output that, or both. After you create and save a reusable object, it is displayed in the
Library in Design so that it is available for use in label templates, forms, and reusable objects.
Note: Changes made to a reusable object are not reflected in copies already
incorporated into label templates, forms, or reusable objects. Also, after a reusable
object is incorporated into a label template or other object, the copy of the
reusable object in the label template or other object can be modified.
Tip: You can include any aspect of a label template or a form in a reusable object
except for Label Specific Options and Database data sources.
To create a new reusable object, use this procedure.
1. In Design, click File > New > Reusable Object or click the button.
2. In the Create Reusable Object dialog box, configure the "Label Template Properties"
on page 273 for the reusable object.
Note: To view or configure the unit of measurement, in the menu bar
select Options > Units.
Tip: To configure a custom label template size, for the Size field select
Custom. Specify the dimensions of the label template in the Width and
Height fields.
3. Click OK. The Label and Form views are displayed.
Best Practice
Save your reusable object immediately after creation. Always save reusable objects
in the Reusable Objects folder or a subfolder within it so that they can be
displayed in the Library and incorporated into label templates. If you want some
reusable objects to be version-controlled, create them in a version-controlled
subfolder of the Reusable Objects folder.
Save the Reusable Object
spaces, double quotes, single quotes, hyphens, underscores, periods, and grave accents.
For letters, the case that you specify is displayed, but case is ignored when Spectrum
interprets a name.
3. Click OK.
Note: The first time you save a reusable object to a version controlled folder, the
reusable object is automatically checked out. When you are finished editing it, be
sure to click File > Check In to save and check in your version and make it
available for others to check out.
To create a reusable object that includes existing fields from a label template, form, or another
reusable object, use this procedure.
1. Open the label template, form, or reusable object that contains the fields you want to
reuse.
2. Select the fields you want to include in the reusable object by holding the Shift key and
clicking the fields.
3. Right-click on one of the fields selected, and click Create Reusable Object.
4. In the Create Reusable Object dialog box, select the Reusable Objects folder or a
subfolder within it so that the reusable object can be displayed in the Library, and enter a
Name.
Characters permitted in names
The following characters are permitted in the name: letters, numbers, parentheses, square
brackets, ampersands, asterisks, plus signs, equal signs, commas, semi-colons, and tildes.
Additionally, the following characters are permitted but cannot begin or end the name:
spaces, double quotes, single quotes, hyphens, underscores, periods, and grave accents.
For letters, the case that you specify is displayed, but case is ignored when Spectrum
interprets a name.
5. Click OK. The reusable object that you created is added to the Library.
Note: Spectrum converts all image files to PNG, so you must give each
image that you import a name that is unique within the folder where it is
saved.
If the image is saved to a version-controlled folder, the image is automatically saved as a
published version to ensure that it can be printed by a Data Provider 1 with the Document
Printer role. It is not necessary to manually publish the image.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
You can export a label template, form, layout, image, reusable object, application, business rule,
or process to an import (SER) file that you can import into another instance of Loftware
Spectrum.
Example
You can import a label template, form, layout, image, reusable object, application, business rule,
or process into Loftware Spectrum if the object was previously exported to an import (SER) file.
For information about exporting to an import file, see "Export a Label Template or Other
Object" on page 98.
Tip: You can also import images that were not previously in Spectrum. For more
information, see "Import a New Image" on page 97.
To import a label template, form, layout, image, reusable object, application, business rule, or
process, use the following procedure.
1. Click Design.
2. Click File > Import.
3. In the Import dialog box, click Browse and select an import file.
4. In the Import Name field, you can specify what the name of the object will be in
Spectrum.
Characters permitted in names
The following characters are permitted in the name: letters, numbers, parentheses, square
brackets, ampersands, asterisks, plus signs, equal signs, commas, semi-colons, and tildes.
Additionally, the following characters are permitted but cannot begin or end the name:
spaces, double quotes, single quotes, hyphens, underscores, periods, and grave accents.
For letters, the case that you specify is displayed, but case is ignored when Spectrum
interprets a name.
5. For Import Location, select a folder in Spectrum where the object will be saved.
Important: When importing an image, it is recommended that you save it
to the Images\User Images folder. An image that will be used only as
part of a Variable Image may be saved to any folder in Spectrum. Otherwise,
for an image to be available to add to a label template, you must save it to
the Images\User Images folder, the Images\Stock Images folder, or a
subfolder of one of those folders.
Note: You cannot import an object from an import (SER) file into a folder
in which an object with the same name already exists unless the folder is
version-controlled, the object in the folder is checked out to you, and the
version number of the object in the folder is less than the version number
of the object you are importing.
Using Workflows
In LoftwareSpectrum, you can use workflows to track and manage the creation and
modification of label templates, while automating the approval and publishing process.
Depending on its configuration, a workflow can:
l Automatically select users to review or approve a label template
l Automatically email users when they need to review or approve a label template
l Allow users to see the current step of the workflow for a label template
workflow
l Use eSignature at any step
l Automatically publish a label template once the required users have approved
1. In Design, click File > Open or click the Open button in the toolbar.
2. In the Open dialog box, select a label template and then click OK.
3. Click File > Workflow > View Current Step Details or click the View Current
1. In Design, click File > Open or click the Open button in the toolbar.
2. In the Open dialog box, select a label template and then click OK.
3. Make changes to the label template as needed and save. If it is a version-controlled
object, see "Working in a Version-Controlled Environment " on page 79 for more
information.
4. Click File > Workflow > Start Workflow or click the Start Workflow button in
the toolbar.
5. In the Select a Workflow Template dialog box, select a workflow template and then
click OK.
Approving or rejecting an item in a workflow
If your Spectrum environment is using workflow, you may be responsible for reviewing and
approving a label template that someone else has edited.
To approve or reject a label template in a workflow, use this procedure.
1. In Design, click File > Open or click the Open button in the toolbar.
2. In the Open dialog box, select a label template and then click OK.
3. Click File > Workflow and select a progression as appropriate. For example, select
Approve to approve the changes to the label template.
Note: The options or progressions available are dependent on the
workflow template and your permissions.
4. Depending on the workflow template, a dialog box for comments may display.
5. Depending on the workflow template, you may be required to add your electronic
signature.
Using eSignature
In Spectrum, you can use eSignature to electronically sign a label template in a workflow,
Workflow Sample
A workflow is a sequence of steps that a workflow template follows. Your Administrator can
create workflow templates in Process Design.
1. In Design, click File > Open or click the Open button in the toolbar.
2. In the Open dialog box, select an object and then click OK.
3. In the right column, click the Tags title bar to expand the pane.
4. Perform one or more of the following actions:
n To add a tag to the object, click . In the Add Tags dialog box, select a
category and a value for the tag, and then click OK.
Note: The list of values available is dependent on the category
selected.
n To change the value of a tag that has been assigned to the object, click the row for
that tag, and then click . Select a value for the tag, and then click OK.
n To remove a tag from the object, click the row for that tag, and then click .
When prompted, click Yes to delete the tag.
Tip: Deleting a tag from a device does not delete the tag category
from Spectrum. You can add a new tag to the device and select that
same category again.
5. Click File > Save or click the Save button in the toolbar.
Built-in Tag Category: Source
A built-in tag category named Source is included with Spectrum. It is designed for use in a tag
that characterizes the origin of an object. If an object supports tags, then a tag with a category of
Source and a value of Spectrum is automatically assigned to it the first time that the object is
saved.
Value Purpose
System The object was built in to Spectrum.
Value Purpose
LPS The object was created in Loftware Print Server (LPS) and was migrated to
Spectrum.
Spectrum The object was created in Spectrum.
Unknown The origin of the object is unknown.
1. In Design, click File > Open or and select the label template that you want to
associate with a layout.
2. If a lock is displayed in the tab showing the name, click File > Check Out.
3. Click the Label view, and click the label canvas to display the properties of the label.
4. In the Properties pane, for Layout browse to select a layout.
Note: Stock layouts are available in Document Templates\Stock
Layouts.
6. Click File > Save or to save the label template. When the label template is printed,
the printed labels are organized as indicated in the layout.
7. If the label template is version-controlled, click File > Check In to save and check in a
version that includes your changes and to make the label template available for others to
check out. After you check in a version, that version cannot be changed.
1An item that defines an organizational structure for printing multiple labels by using the same label template.
1. Click File > Save As, or click the Save button on the toolbar.
2. In the left pane of the Save As dialog box, click the folder in which you want to save the
object. You can double-click a folder to display subfolders.
Tip: You can add a new folder within the folder selected in the left pane by
clicking the Add Folder button.
3. In the Name box, enter a name for the object.
Characters permitted in names
The following characters are permitted in the name: letters, numbers, parentheses, square
brackets, ampersands, asterisks, plus signs, equal signs, commas, semi-colons, and tildes.
Additionally, the following characters are permitted but cannot begin or end the name:
spaces, double quotes, single quotes, hyphens, underscores, periods, and grave accents.
For letters, the case that you specify is displayed, but case is ignored when Spectrum
interprets a name.
4. Click OK.
Note: If an object is in a version-controlled folder , you should check in the
object when you are finished working on it so that it is available for other users to
edit. Checking in an object also saves the object, but merely saving or closing an
object does not check it in.
l Click File > Save, or click the Save button on the toolbar.
To save an object with a new name or in a new location, use this procedure.
1. Click File > Save As.
2. In the left pane of the Save As dialog box, click the folder in which you want to save the
object. You can double-click a folder to display subfolders.
Tip: You can add a new folder within the folder selected in the left pane by
clicking the Add Folder button.
3. In the Name box, enter a name for the object.
4. Click OK.
Best Practice
Click the Save button or File > Save frequently while designing objects.
To close the active label template, form, layout, reusable object, or application, use this
procedure.
1. Click File > Close or click the Close button on the toolbar. The active label
template, form, layout, reusable object, or application is closed.
2. If you have not saved the label template, form, layout, reusable object, or application
since a change, respond to the Close dialog box.
To close all open label templates, forms, layouts, reusable objects, or applications, use this
procedure.
1. Click File > Close All. All open label templates, forms, layouts, reusable objects, or
applications are closed.
2. If you have not saved a label template, form, layout, reusable object, or application since
a change, respond to the Close dialog box.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
Migration Issues
If you are viewing a label template that was migrated from an LPS environment, you can
determine whether issues occurred during migration. If issues occurred, you can view
information about the issues and any changes that were necessary.
Review Migration Issues
To determine whether issues occurred during the migration of a label template, do the following.
1. In Design, click File > Open, select the label template that you want to review for
migration issues, and click OK.
2. In the Properties pane, review the value displayed for the Migration property.
n If the value is Successfully migrated, then no migration issues occurred for the
label template.
n If the value is Migrated with issues, then migration was performed but some
issues occurred and changes may have been necessary.
3. If the label template was migrated with issues, you can view information about the issues
and any changes that were necessary.
n To view a tool tip listing any migration issues for a particular field, in the
Properties pane click the flag icon for that field.
n To view a report of all migration issues for the label template, in the Migrated
property click the flag icon.
Tip: You can remove an individual icon by clicking the Clear Flag button, or
remove all of the icons and the report by clicking the Clear All Flags button.
You can configure how your label canvas in Spectrum is aligned in relation to objects in the label
template.
Note: To change the orientation of the label relative to the stock on which it will
be printed, see "Change the Print Rotation of a Label" on page 123.
In the Create Label dialog box, click Portrait or Landscape for the Orientation property.
The canvas changes shapes to match your selection.
When Editing an Existing Label Template
1. In Design, open a label template and then expand the Properties pane.
2. Click the Label view, and click the label canvas to display the properties of the label
template.
3. For Orientation, click Portrait or Landscape. The canvas shape changes.
Note: Objects on your label may move so that they stay on the label canvas.
To change the orientation of the label relative to the stock on which it will be printed, use this
procedure.
1. In Design, open a label template and then expand the Properties pane.
2. Click the Label view, and click the label canvas to display the properties of the label
template.
3. Select a value in degrees for Print Rotation.
Note: The appearance of the label in Spectrum is not changed. To change the
orientation of the label in Spectrum, see "Configure the Design Orientation of a
Label" on page 122.
Label Specific Options (LSOs) enable a Document Designer 1 to override device settings on a
per-label template, per-device model basis. For example, if devices are typically configured with
cutters turned off and a particular label template requires every label to be cut, then when
designing the label template you would create an LSO to override the default setting. LSOs
override device options, and device options override the settings on the device itself if Send
Device Options is enabled.
Tip: If available for the device, Send Device Options can be configured on the
Advanced tab in an LSO or in Device Management.
Each LSO that you create is associated with a specific label template and with a specific device
model or device family. If no LSOs are included in a label template, then the device options
configured in Device Management are used.
Best Practice
It is recommended that device options be configured in Device Management and
overridden by LSOs only where necessary.
To add a collection of Label Specific Options to a label template, use the following procedure.
1. In Design, open a label template.
2. In the right column of the Spectrum window, click the Label Specific Options title bar
to expand the pane.
3. In the Label Specific Options pane, click to open the Label Specific Options
dialog box.
4. For Family, select the family of the devices for which you want to override settings.
5. For Model, select the model of the devices for which you want to override settings.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
6. For each setting that you want to override, select the Override check box, and then
configure the option. (If there is more than one check box for the setting, the Override
check box is the first one following the option name.)
Tip: For information about specific device options, see " Device Driver
Options" on page 858.
Tip: If overriding the Paper Size or Paper Source option for a server
spooler device, you are not limited to selecting from the values displayed.
You can type in a custom value.
Note: Selecting the Print as Image property for a Barcode field overrides
the option for the relevant symbology on the Barcode Imaging tab for
both LSOs and device options, and the barcode is sent as an image.
Selecting Print as Image removes any potential device variation when
natively encoding the barcode data. If you have cleared Print as Image,
selecting Override in the LSO and selecting the relevant symbology also
causes barcodes to be generated by Spectrum and printed as an image.
7. Click OK to save the Label Specific Options collection.
8. Click File > Save or click on the toolbar to save the label template.
Important! An LSO is part of a label template. If you do not save the label
template, the LSO that you created will be discarded when you close the
label template.
To attach a data source to a field on the label or form, use one of the following methods:
l Drag the data source from the Data Sources pane to the field on the Label or Form
view.
l Enter the name of the data source in the Data Ref property of the field that you want to
display the data.
To position text fields, images, shapes, and barcodes in your label template, use the following
tools.
Tip: You can group fields together so that you can move and order them as a single
unit and configure some properties in common. However, fields within a group are
rotated, aligned, and distributed individually. If you copy and paste a group, the
fields are ungrouped when pasted.
To change the size of a circle, box, line, or the displayed size of an image, use one of the
following procedures.
Note: Resizing an image by using these procedures does not alter the image in the
Spectrum library.
Using Handles
1. Click a field to resize. Drag handles appear at the corners, sides, or ends.
2. If resizing an image in the Label view, for Resizing select Fit to Envelope.
3. Drag the handles to change the size.
Note: By default, images maintain proportionality when you change their sizes. To
disproportionately resize an image, clear the Lock Aspect Ratio check box in the
Properties pane.
Using Properties
1. Click a field to resize.
2. If resizing an image in the Label view, for Resizing select Fit to Envelope.
3. Open the Properties pane, and adjust the Width and Height properties.
Resize a Text Field
You can resize Fixed Text and Variable Text fields using the Chars Per Line and Font Size
properties.
1. Click a text field to resize.
2. Open the Properties pane, and adjust the Width and Height properties.
Rotate a Field
To freely rotate a field that permits it, do the following. This approach is not available for
barcodes or for groups of fields that include a barcode.
1. Click a field to rotate.
2. Move the mouse pointer outside one of the corners of the field. The pointer changes to
an arc with arrows on each end.
Note: Fields cannot be positioned off the label canvas. If you need to rotate a large
field, you may notice that the field is blocked by the edge of the canvas. You can
temporarily resize a field to rotate or reposition it.
Align Fields
You can position fields so their edges or centers are aligned with each other, or you can align a
single field relative to the label template. You can also align some types of fields within their
envelopes.
Tip: To move a field only horizontally or vertically from its current position, press
Shift while moving the field.
Tip: For a text field with only one line, you can display guidelines indicating the
top, text baseline 1, and bottom edge of text. To do so, click the text field, and in
the Properties pane, Font section, select the check box for Alignment Markers.
Align Fields with Each Other
To position fields so their edges or centers are aligned, use Align.
1. Select the fields to align. You can use one of the following methods to select multiple
fields.
n Click and drag over the fields. Envelopes appear around the fields selected.
n Press and hold the Shift key, and click fields.
1The conceptual line on which characters sit by default. Characters with a rounded bottom edge may extend slightly below the
baseline. Some characters (such as y) have descenders that extend significantly below the baseline. The baseline is not printed on
labels or displayed in forms, but is an alignment marker that can be viewed in Design.
2. Click Position > Align, and click one of the alignment options.
n Left
n Center
n Right
n Top
n Middle
n Bottom
Align a Field with the Label Template
To align a single field relative to the label template, use Align.
1. Select the field to align.
2. Click Position > Align, and click one of the alignment options.
n Left
n Center
n Right
n Top
n Middle
n Bottom
Align a Field with its Envelope
You can align a barcode, a variable image, or text within or relative to its envelope.
To align a field relative to its envelope, perform the following steps.
1. Select the field to align.
2. In the Properties pane, navigate to the section specific to the type of field, such as
Barcode, Image, or Font.
3. Click an option for Horizontal Alignment.
4. If available, click an option for Vertical Alignment.
Equally Distribute Fields
To separate multiple fields by an equal amount of space, use Distribute. You must select at least
three fields.
1. Select the fields to separate. You can use one of the following methods to select multiple
fields.
n Click and drag over the fields. An envelope appears around the fields selected.
n Press and hold the Shift key, and click fields.
2. Click Position > Distribute, and click one of the space options.
n Horizontally
n Vertically
To adjust the stacking order of overlapping fields, use Order. Within the Label view and within
the Form view, each field has a unique position in the stacking order.
1. Click a field for which you want to change the stacking order in relation to other fields in
the view.
2. Click Position > Order, and click one of the options.
n Bring to Front: Position forward of all other fields in the view. If this field
overlaps with others, this field appears in front of the other fields.
n Bring Forward: Move one step closer to the front of the view.
n Send to Back: Position underneath all of the other fields in the view. If this field
overlaps with others, this field appears behind the other fields.
n Send Backward: Move one step closer to the back of the view.
After adding a field, shape, image, or barcode to a label template, you may need to adjust the
properties of the field.
1. If the Properties pane is not visible in the right column, click the arrow at the top right
of Design.
2. Click the field, shape, image, or barcode in the label template or select it from the
Document Field drop down in the Properties pane. The properties of the field are
displayed in the Properties pane.
3. Change the properties of the field.
Tip: The option selected for Design Data controls what data is used in
fields when previewed, printed, or displayed in Design. Either default
data1, placeholder data2, or data from a live data set3 can be used. For
more information, see "Select Data to Display in Design" on page 63.
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Using Text
Fixed Text fields contain text that remains the same for all printed labels that use a particular
label template. For example, you can use Fixed Text fields for data such as company name or
address.
Variable Text fields and Text Box fields contain text that can vary among printed labels
produced using the same label template. For example, you can use Variable Text fields for data
such as customer name or part number. Text Box fields provide additional formatting options for
text that spans more than one line.
To add text that stays the same from label to label, use these procedures.
Add Fixed Text
1. From the Text list in the Library, click and drag Fixed Text to the Label or Form
view.
2. Double-click the Fixed Text field. The Edit Fixed Text dialog box is displayed.
3. Type the field text in the Enter Text field.
n Press Enter to add more lines to the field.
4. Click OK. The text is displayed in the label template.
Modify the Text in a Fixed Text Field
1. Double-click the Fixed Text field. The Edit Fixed Text dialog box is displayed.
2. Modify the text in the Enter Text field, and click OK.
The changed text is reflected in the Label view or the Form view, and in the Default Value
property in the Properties pane.
To add text that can vary from label to label, use these procedures.
Tip: For data that must fill a region of a specific size or for which you want to
control paragraph spacing, a Text Box field is recommended. For data that must be
restricted to a specific number of characters, a Variable Text field is recommended.
A Prompt appears on the Form view. A Data Entry data source is created.
Tip: The option selected for Design Data controls what data is used in fields
when previewed, printed, or displayed in Design. Either default data1,
placeholder data2, or data from a live data set3 can be used. For more
information, see "Select Data to Display in Design" on page 63.
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
To add a Text Box field to the Label view, use the following procedures.
Tip: For data that must fill a region of a specific size or for which you want to
control paragraph spacing, a Text Box field is recommended. For data that must be
restricted to a specific number of characters, a Variable Text field is recommended.
1. From the Text list in the Library, click and drag Text Box to the Label view.
2. Double click the Text Box field. The Edit Text Box Default Data dialog box is
displayed.
3. Type the default text for the Text Box field in the Enter Text field.
4. Click OK. The text is displayed in the label template.
Modify the Default Data for a Text Box
1. Double click the Text Box field. The Edit Text Box Default Data dialog box is
displayed.
2. Modify the text in the Enter Text field, and click OK.
The changed text is reflected in the Label view and in the Default Value property in the
Properties pane.
Tip: The option selected for Design Data controls what data is used in fields
when previewed, printed, or displayed in Design. Either default data1,
placeholder data2, or data from a live data set3 can be used. For more
information, see "Select Data to Display in Design" on page 63.
When configuring a Text Box field, the following is the behavior when data exceeds the length
of a line or the size of the Text Box.
Line wrapping in a Text Box
Data in a Text Box field automatically wraps at the end of each line if the text would
otherwise extend beyond the envelope of the field. When line wrapping occurs, the line
break is either at the end of a word or after a hyphen, en-dash, or em-dash. If a word is too
wide to fit in the field, a line break occurs within the word at the edge of the envelope.
When data exceeds the size of a Text Box
If the amount of data received for a Text Box field is more than fits, the Text Box Overrun
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Mode property controls how Spectrum responds. Text may overrun the Text Box and
continue until reaching the edge of the label, text may be truncated at the end of a word or
paragraph, or the print job may be failed. An administrator may configure this property
system-wide for Spectrum or for a specific device. You can override the system-wide and
device options by using Label Specific Options (LSOs). For more information, see "Override
Device Options with Label Specific Options" on page 125.
You can change the order in which prompts receive focus as a user enters information and
presses theTab key to move to the next prompt on the data entry form.
Alternatively, you can "Dynamically Manage the Tab Order of a Control" on page 176 or use a
"Focus Form Rule" on page 411. To manage whether the control is a tab stop, use the "Tab
Stop" on page 181 control property.
Note: By default, the first prompt that is added has a tab order value of 1, the
second prompt that is added has a tab order value of 2, and so on.
1. In the right column of the Spectrum window, expand the Field Tabbing Order pane.
2. Arrange the available fields by dragging them into the intended order.
The tabbing order is changed for users entering data in Print.
Text Properties
Text fields in a label template, a form, or a reusable objectsuch as Fixed Text, Variable Text,
and Text Boxhave the following properties.
Note: A Field Name, Data Ref, or Input Data Ref can include letters and
numbers. Additionally, the following characters are permitted but cannot begin the
name: hyphens, underscores, and periods.
Name and Data
Arrange
Top The distance from the top edge of the field to the top of All Fields
the label. The value is dependent on the unit of measure
for the label template.
Center X The distance from the middle of the field to the left edge All Fields
of the label. The value is dependent on the unit of
measure for the label template.
Center Y The distance from the middle of the field to the top of All Fields
the label. The value is dependent on the unit of measure
for the label template.
Width The distance from the left edge of the field to the right All Fields
edge of the field. The value is dependent on the unit of
measure for the label template. Chars Per Line, Max
Chars, and font formatting also impact this value.
For some properties, this property is automatically
configured and is read-only by default. For Fixed Text and
Variable Text, this property can be manually configured if
Auto Envelope is cleared.
1The conceptual line on which characters sit by default. Characters with a rounded bottom edge may extend slightly below the
baseline. Some characters (such as y) have descenders that extend significantly below the baseline. The baseline is not printed on
labels or displayed in forms, but is an alignment marker that can be viewed in Design.
Paragraph Vertical space preceding each paragraph within a Text Box Text Box
Before in lines of space. The height of a line of space is defined
by Line Spacing.
Paragraph After Vertical space following each paragraph within a Text Box Text Box
in lines of space. This spacing is in addition to any defined
by Line Spacing. The height of a line of space is defined
by Line Spacing.
Dynamic Font Whether to permit the point size for the text to increase Text Box
Sizing or decrease until the text reaches the envelope, or to
strictly adhere to the value specified by Font Size.
: The text size is specified by Font Size.
: The text size is automatically adjusted to allow the
text to more completely fill the Text Box field. The font
size is limited by Min Size, Max Size, and Maintain
Aspect Ratio.
Min Size If Dynamic Font Sizing is enabled, the smallest font size Text Box
that may be used. This value is in points.
Note: This property is available only if
Dynamic Font Sizing is selected.
1The conceptual line on which characters sit by default. Characters with a rounded bottom edge may extend slightly below the
baseline. Some characters (such as y) have descenders that extend significantly below the baseline. The baseline is not printed on
labels or displayed in forms, but is an alignment marker that can be viewed in Design.
specifications that can be applied to text fields. Format sources allow you to configure
formatting once, and then apply it to as many fields in the label template as needed. For more
information, see " Configuring Format Sources" on page 425.
Property Description Fields Where Available
Format Sources A list of format sources that are applied to the field. Fixed Text
To apply a format source to the field, expand the (Label view
Format Sources pane in the left column, and drag and only)
drop a format source onto a field in the Label view. Variable
To remove a format source from a field, click the field, Text
and in the Format Sources section of the Properties Text Box
pane select the name of a format source and click .
Using Controls
Controls such as Button1, Check Box2, Drop-Down List3, Device Selector 4,Folder
Selector 5, Label Selector 6, Radio Button Group7, Prompt8, User Selector 9, and Text Box
Prompt10 fields can be included in data entry forms to allow a Data Provider 11 to enter
information for use in printed labels. In addition to simple data entry, those controls as well as a
Table 12 control can be used to allow a Data Provider to run a data source query and select
information from a database, or to run a form rule or a business rule that performs complex
instructions.
When configuring controls such as drop-down lists and radio button groups that provide a list of
options from which to select, a Document Designer 13 can manually provide the option names
and values from which Data Providers can select. Alternatively, the available options can be
dynamically drawn from the data map14.
A Document Designer can dynamically manage the appearance of each control. You can manage
whether each control is displayed to or hidden from Data Providers. Also, you can manage
whether each control is enabled or disabled"grayed out" and not available for use.
Example
If a form in Design includes a Print Alternate Address check box, you can
configure the dynamic properties of the Check Box field so that it is displayed to a
Data Provider in Print only if an alternate address is available in the data map14.
1A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when clicked by a Data Provider.
2A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when the check box is selected or cleared by a Data Provider.
3A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when a Data Provider changes which item is selected.
4A control field in a form or in the data entry view of a label template that allows a Data Provider to select a printer or other device. A
Device Selector is displayed as a browse button and the name of the selected device. Clicking the browse button opens a dialog
box from which a Data Provider can select a device. A control can also be used to run a data source query, a form rule, or a business
rule.
5A control field in a form or in the data entry view of a label template that allows a Data Provider to select a folder. A Folder Selector
is displayed as a browse button and the name of the selected folder. Clicking the browse button opens a dialog box from which a
Data Provider can select a folder. A control can also be used to run a data source query, a form rule, or a business rule.
6A control field in a form or in the data entry view of a label template that allows a Data Provider to select a label. A Label Selector is
displayed as a browse button and the name of the selected label. Clicking the browse button opens a dialog box from which a Data
Provider can select a label. A control can also be used to run a data source query, a form rule, or a business rule.
7A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when a Data Provider changes which item is selected.
8A type of control or document field used to collect information from a Data Provider in the data entry view of a label template or in
a form. When a Data Provider submits data via a prompt, a data source query, a form rule, or a business rule may be run.
9A control field in a form or in the data entry view of a label template that allows a Data Provider to select a user. A User Selector is
displayed as a browse button and the name of the selected user. Clicking the browse button opens a dialog box from which a Data
Provider can select a user. A control can also be used to run a data source query, a form rule, or a business rule.
10A type of control or document field in the data entry view of a label template or in a form that can be used to allow a Data Provider
to retrieve lengthy data from a database and then manipulate the data retrieved.
11Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer.
A user acting as a Data Provider requires the Document Printer role or equivalent permissions.
12A control field in a form that systematically displays the results of a data source query, a form rule, or a business rule in columns
and rows.
13Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
Tip: For most on-demand data entry, a Prompt field is recommended. However, a
Text Box Prompt field is appropriate for situations in which Data Providers are
expected to retrieve lengthy data from a database and then manipulate the data
retrieved.
Adding Controls
You can add the following control fields to a label template, a form, or a reusable object:
Tip: For most on-demand data entry, a Prompt field is recommended. However, a
Text Box Prompt field is appropriate for situations in which Data Providers are
expected to retrieve lengthy data from a database and then manipulate the data
retrieved.
Add a Button
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
Best Practice
Save the label template or form immediately after configuring a control.
Add a Check Box
To add a Check Box control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag Check Box to the Form view of a
label template to or to a form.
2. In the Properties pane, enter a name for the check box in the Field Name property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
3. For the Default Value property, enter either true (selected) or false (cleared) for the
value that is returned by the check box by default.
4. For the Label Text property, enter text to be displayed next to the check box.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Add a Drop-Down List
To add a Drop-Down List control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag Drop-Down List to the Form
view of a label template to or to a form.
2. In the Properties pane, enter a name for the drop-down list in the Field Name
property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
3. In the Name and Data section, configure the initial appearance of the drop-down list.
You can either display text with no associated value to prompt the Data Provider 1 to
make a selection, or you can specify an option that is selected by default.
n To display text to prompt the Data Provider to make a selection, enter text for the
Prompt.
Note: This text is not associated with an option value. Also, if you
specify a Default Value, then the Prompt is not displayed to Data
Providers.
n To display a default option as selected, for the Default Value enter an option
value from the list.
Tip: Enter the option value, not the corresponding option name.
4. Click the Option Values pane to expand it, and then indicate whether you will manually
enter the options for the drop-down list or whether you will provide a data ref pointing to
the names and values for the options.
n To manually type the option names and values for the drop-down list, click
Manual Entry. Click Add Value. In the dialog box, enter an option name for
Label, enter the corresponding value, and click Add. Repeat for each option. For
the last option in the list, click OK to enter the option and close the dialog box.
n To configure Spectrum to retrieve the option names and values from the datamap,
click From Data Map. For Data Ref, enter a reference to a data map entry 2.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Add a Device Selector
To add a Device Selector control to a data entry form, use this procedure.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
2A name (key) and value pair in the data map for a job.
1. From the Controls list in the Library, click and drag Device Selector to the Form view
of a label template or to a form.
2. In the Properties pane, enter a name for the device selector in the Field Name
property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Add a Folder Selector
To add a Folder Selector control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag Folder Selector to the Form view
of a label template or to a form.
2. In the Properties pane, enter a name for the folder selector in the Field Name
property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
To add a Label Selector control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag Label Selector to the Form view
of a label template or to a form.
2. In the Properties pane, enter a name for the label selector in the Field Name property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Add a Radio Button Group
To add a Radio Button Group control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag Radio Button Group to the Form
view of a label template to or to a form.
2. In the Properties pane, enter a name for the radio button group in the Field Name
property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
3. For the Default Value property, enter the option value for the radio button that is
initially selected by default.
Tip: Enter the option value, not the corresponding option name.
4. Click the Option Values pane to expand it, and then indicate whether you will manually
enter the options for the radio button group or whether you will provide a data ref
pointing to the names and values for the options.
n To manually type the option names and values for the radio button group, click
Manual Entry. Click Add Value. In the dialog box, enter an option name for
Label, enter the corresponding value, and click Add. Repeat for each option. For
the last option in the group, click OK to enter the option and close the dialog box.
n To configure Spectrum to retrieve the option names and values from the datamap,
click From Data Map. For Data Ref, enter a reference to a data map entry 1.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Add a Prompt
1A name (key) and value pair in the data map for a job.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Add a User Selector
To add a User Selector control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag User Selector to the Form view
of a label template or to a form.
2. In the Properties pane, enter a name for the user selector in the Field Name property.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Add a Table
You can use a Table control to display the results of a data source query, form rule, or business
rule in an application in Print. You can also add rules to the table and to specific columns to
change the styling based upon the data in a cell. For more information, see "Add a Table Rule"
on page 164.
To add a Table control to a data entry form, use this procedure.
1. From the Controls list in the Library, click and drag Table to the Form view of a label
template or to a form.
2. In the Properties pane, change the Field Name to a meaningful name.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
3. For the Source Data Ref field in the Table section, enter the location in the datamap
from which the columns obtain data.
Example
/MyData
4. For the ColumnCount property, modify the value to add or remove columns in the
table as needed.
Tip: If you want the number of columns in the table to be determined from
the data source, set the Column Count to 0.
5. Decide whether the envelope 1 of the table should automatically resize based on row
height and column width or if the envelope should be a fixed size, then do one of the
following:
Automatically resize the envelope of the table
a. In the Table section of theProperties pane, select the Auto Envelope check
box.
b. Adjust the values in the Row Height and Row Count fields as needed.
Set a fixed size for the envelope of the table
a. In the Table section of theProperties pane, clear the Auto Envelope check
box.
b. In the Arrange section, adjust the values in the Width and Height fields as
needed.
6. To add a search toolbar to the table, select Show Search.
7. To display the number of each row, select Show Row Numbers. Row numbers are
displayed in Print.
8. To modify the fill color of alternating rows, use Alternating Row Colors.
9. Click the Columns and Table Rules pane.
1In the Label view or Form view in Design, a blue box that outlines a field when the field is selected.
10. In the ColumnHeaders section, do the following for each column in the table:
Note:If yourColumn Count is 0, skip this step.
a. Select the row of the column you want to configure and then click Edit . The
Configure Properties dialog box for the column is displayed.
b. Under Header, enter text for the header Display Name or leave this field blank
to use the name as defined in the data source.
c. UnderColumn, enter the name of the column as defined in the data source for
the Column Name.
d. If desired, modify the column Width and any additional header and column
properties. For more information, see "Columns and Table Rules" on page 189.
11. If desired, configure rules for the table and for specific columns. For more information,
see "Add a Table Rule" on page 164.
12. To style the table using a business rule, in the Style Data Ref field, enter the location in
the datamap from which the columns obtain styling data, and then add a trigger on the
form to run the business rule with the onLoad event. For more information, see "Style a
Table" on page 165.
Note: Styles defined by a Style Data Ref override the styles configured in
the Columns and Table Rules pane.
13. View the populated and styled table in Print. For more information, see View a Table.
View a Table
A table is displayed in an application in Print. To view a table, perform the following steps:
1. If the table data is populated by a business rule, add a trigger on the form to run the
business rule with the onLoad event.
2. Open or create an application and add the form to the application.
3. In Print, open the application to view your table with data and styling as specified.
Note: If a table cell is editable, editing the cell modifies the data map entry
but does not modify the data in the data source.
4. If a column is sortable, you can click the column header to sort the table by that column
in ascending or descending order.
5. To change the displayed order of a columns, click and drag the column in the table.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
l "Select Data Source Queries and Rules to Run" on page 168
l "Configure the Running Order for Queries and Rules" on page 172
l "Dynamically Manage If a Control Is Displayed" on page 174
l "Dynamically Manage If a Control Is Enabled" on page 175
l "Dynamically Manage the Tab Order of a Control" on page 176
l " Associate the Control Output with a Field in a Label" on page 177
Best Practice
Save the label template or form immediately after configuring a control.
Configure Table Rules
You can use table rules to change the styling of rows in the table based upon the data in the row,
and you can use column rules to change the styling of cells in a specific column based upon the
data in the column. For example, if you want the rows that contain a specific date to stand out,
you can add a table rule to change the background color of the rows containing that date to
yellow. If you add a rule to both the table and a column that overlaps, the column rule overrides
the table rule for that cell.
Example
You add a table rule to change the background color of rows that contain January 1 in
the Date column to yellow.
Table Rule
Column Name Operator Value Set Style Style Value
Date Equals January 1 BackgroundColor yellow
You also add a rule on the Date column to change the background color of cells in
the column that contain January 1 to green.
Column Rule
Column Name Operator Value Set Style Style Value
Date Equals January 1 BackgroundColor green
Result
When the table is displayed in Print, the cells containingJanuary 1 in the Date
column are green because a column rule overrides a table rule, and the other cells in
the row are yellow from the table rule.
Date Item Quantity
January 1 12345 100
January 2 12346 100
Style a Table
You can style a table using the options in the Properties pane and by configuring the properties
for each column in the Columns and Table Rules pane. However, if you have several tables
inSpectrum and you want to quickly apply the same styles to multiple tables, you can define the
table styles using a business rule and then apply those styles to a table using the Style Data Ref
property.
Note: Styles defined by a Style Data Ref override those configured in the
Columns and Table Rules pane.
Styles can be defined using the following locations in the datamap. If the same style is defined
in both locations, the Style Data Ref is used. For property keys and values, see "Columns and
Table Rules" on page 189.
Property
Location in DataMap Example
Type
Table /{Style Data Ref}/{Key} /myTableStyle/alternatingItemColors
Table /{Table Name}/{Key} /Table001/alternatingItemColors
Columns /{Style Data Ref}/columns/{Key} /myTableStyle/columns/horizontalAlign
Columns /{Table Name}/columns/{Column /Table0001/columns/Date/horizontalAlign
Name}/{Key}
To style a table using a business rule, perform the following steps:
1. In Process Design, create and save a new business rule that adds the desired values (or
"styles")to the appropriate data map entries (or "properties"). For more information, see
"Create a Business Rule in Configurator" on page 440. For property keys and values, see
"Columns and Table Rules" on page 189.
Tip: To apply these styles to more than one table, use the /{Style Data
Ref}/{Key} and /{Style Data Ref}/columns/{Key} locations in the
datamap.
2. In Design, open the label template or form with the table and click the table.
3. In the Table section of the Properties pane, in the Style Data Ref property, enter the
location in the datamap from which the columns obtain styling data as defined in your
business rule.
Example
/myTableStyle
4. On the form, add a trigger to run the new styling business rule with the onLoad event.
For more information, see "Create a Trigger to Run a Rule" on page 297.
5. View the styled table in Print. For more information, see View a Table.
To add a Text Box Prompt field to a data entry form, use this procedure.
Tip: For most on-demand data entry, a Prompt field is recommended. However, a
Text Box Prompt field is appropriate for situations in which Data Providers are
expected to retrieve lengthy data from a database and then manipulate the data
retrieved.
1. From the Controls list in the Library, click and drag Text Box Prompt to the Form
view. A Form Prompt and a Text Box Prompt are added to the Form view of the label
template. A Data Entry data source is added to the label template.
2. In the Properties pane, enter a name for the Text Box Prompt in the Field Name
property. This is shared by the Form Prompt and the Text Box Prompt.
Note: A Field Name, Data Ref, or Input Data Ref can include letters
and numbers. Additionally, the following characters are permitted but
cannot begin the name: hyphens, underscores, and periods.
3. For the Prompt property, enter text to be displayed next to the Text Box Prompt field.
Configure Functionality
You can configure more functionality for the control, such as running data source queries or
rules, dynamically displaying or hiding the control, dynamically enabling or disabling the control,
and associating the control with data.
If you want data source queries, form rules, or business rules to run when a Data Provider 1
performs a particular action using a control, you must configure a trigger 2 for each data source
or rule.
Trigger
Control When the Trigger Event Occurs
Event
Button3 onClick A Data Provider clicks a button.
Check Box4 onChange A Data Provider selects or clears a check box,
changing its state.
Drop-Down List5 onChange A Data Provider changes which option is selected in
a drop-down list.
Device Selector 6 onChange A Data Provider changes which printer or other
device is selected and clicks OK in a Device
Selector dialog box.
Folder Selector 7 onChange A Data Provider changes which folder is selected and
clicks OK in a Folder Selector dialog box.
Label Selector 8 onChange A Data Provider changes which label is selected and
clicks OK in a Label Selector dialog box.
Radio Button onChange A Data Provider changes which option is selected in
Group9 a radio button group.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
2A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
3A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when clicked by a Data Provider.
4A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when the check box is selected or cleared by a Data Provider.
5A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when a Data Provider changes which item is selected.
6A control field in a form or in the data entry view of a label template that allows a Data Provider to select a printer or other device. A
Device Selector is displayed as a browse button and the name of the selected device. Clicking the browse button opens a dialog
box from which a Data Provider can select a device. A control can also be used to run a data source query, a form rule, or a business
rule.
7A control field in a form or in the data entry view of a label template that allows a Data Provider to select a folder. A Folder Selector
is displayed as a browse button and the name of the selected folder. Clicking the browse button opens a dialog box from which a
Data Provider can select a folder. A control can also be used to run a data source query, a form rule, or a business rule.
8A control field in a form or in the data entry view of a label template that allows a Data Provider to select a label. A Label Selector is
displayed as a browse button and the name of the selected label. Clicking the browse button opens a dialog box from which a Data
Provider can select a label. A control can also be used to run a data source query, a form rule, or a business rule.
9A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when a Data Provider changes which item is selected.
Trigger
Control When the Trigger Event Occurs
Event
Prompt1 onCommit A Data Provider submits text via a prompt.
Note: After an interactive user has
typed text into the field, clicking to
another field, tabbing to another field,
or pressing the Enter key submits the
text in the Prompt field to Spectrum.
User Selector 2 onChange A Data Provider changes which user is selected and
clicks OK in a User Selector dialog box.
Text Box Prompt3 onCommit A Data Provider submits text via a text box prompt.
Note: After an interactive user has
typed text into the field, clicking to
another field, tabbing to another field,
or pressing the Enter key submits the
text in the Text Box Prompt field to
Spectrum.
Note: For information about how to add a control, see "Adding Controls" on page
153.
1A type of control or document field used to collect information from a Data Provider in the data entry view of a label template or in
a form. When a Data Provider submits data via a prompt, a data source query, a form rule, or a business rule may be run.
2A control field in a form or in the data entry view of a label template that allows a Data Provider to select a user. A User Selector is
displayed as a browse button and the name of the selected user. Clicking the browse button opens a dialog box from which a Data
Provider can select a user. A control can also be used to run a data source query, a form rule, or a business rule.
3A type of control or document field in the data entry view of a label template or in a form that can be used to allow a Data Provider
to retrieve lengthy data from a database and then manipulate the data retrieved.
4A connection to a database that acts as a data source and can serve as the data ref for a document field. A Database data source
is associated with a Database data service.
5A connection to a file external to Spectrum that acts as a data source and can serve as the data ref for a document field. An
Alternate data source is associated with either a File data service or an HTTP data service.
8. Click OK.
9. Repeat for any additional business rules to run when the control is used by a Data
Provider.
If a control acts as a trigger source 1 for more than one data source or more than one rule and
the order in which the they are run is important, then you must configure values for trigger
priority 2 for these triggers. In that situation, you can assign different values for Trigger
Priority for these otherwise identical triggers, and the data source, form rule, or business rule
with the lower value for Trigger Priority is run first. For data sources, whether the type of data
source differs is not relevant.
Note: For information about how to select data source queries, form rules, and
business rules to be run when a control is used, see "Select Data Source Queries
and Rules to Run" on page 168.
Note: Trigger Priority values for data sources are not compared with Trigger
Priority values for form rules and business rules. Regardless of their Trigger
Priority values, all data sources are run before any form rules or business rules are
run.
To configure the order in which data source queries are run relative to each other and the order
in which rules are run relative to each other, do the following:
1. If the control acts as a trigger for more than one data source and the order in which the
they are run relative to each other is important, do the following to assign values for
trigger priority for these triggers.
a. In the Triggers section of the Properties pane, double-click a trigger in the
Data Sources box.
b. In the Select a Trigger dialog box, click Next twice.
c. In the list of triggers, enter a value for Trigger Priority for the data source. The
data source with the lower value for Trigger Priority is run first.
Tip: Trigger priorities are compared only if the triggers have the
same trigger source, trigger event, and trigger key (if any). For
example, if a data source has both a button and a prompt that act as
triggers, their Trigger Priority values are not compared to each
other.
d. Click OK.
e. Repeat for each data source for which a trigger is listed.
1A field that is used in conjunction with a trigger event to interactively run a data source, form rule, or business rule. For example, a
button that runs a query when clicked, a prompt that runs a query when submitted, or a form that runs a query when loaded.
2The order in which data sources, form rules, or business rules that have otherwise identical triggers are run. Trigger values are
compared only if the triggers have the same trigger source, trigger event, and trigger key (if any). The type of data source is
irrelevant. Among data sources, form rules, or business rules with otherwise identical triggers, the data source with the lowest
value for trigger priority is run first.
2. If the control acts as a trigger for more than one rule (regardless of whether they are form
rules or business rules) and the order in which the they are run relative to each other is
important, do the following to assign values for trigger priority for these triggers.
a. In the Triggers section of the Properties pane, double-click a trigger in the
Form Rules box.
b. For Priority, enter a value for trigger priority for the rule. The rule with the lower
value for trigger priority is run first.
c. Click OK.
d. Repeat for each form rule or business rule for which a trigger is listed.
You can use the value referred to by a data ref to manage whether the control is displayed to or
hidden from Data Providers. The control is displayed only if a comparison between the value
associated with a field and a specified value is evaluated as true.
Note:By default, a control with no dynamic properties is enabled and visible and is
a tab stop.
1. Click the Dynamic Properties pane.
2. Click Add to open the Configure Properties dialog box.
3. For Property, select Visible.
4. For Data Ref, select the field to use to manage whether the control is displayed.
5. For Operator, select how the value associated with the field should be compared to a
specified value.
6. If the Value property is displayed, enter the literal value to which the value associated
with the field should be compared.
7. Click OK.
Tip: The Value property must not include a data ref or the name of a data map
entry. If you want to use a variable to manage whether the control is displayed, you
can accomplish this by using a business rule that includes a conditional business
rule component. Configure the output of the business rule to be a value in the
data map1, and then use that value to manage whether the control is displayed.
1A repository for the data for use when responding to a print request. Each data map entry is composed of a name (key) and a
value.
You can use the value referred to by a data ref to manage whether the control is enabled for Data
Providers to use. The control is enabled only if a comparison between the value associated with
a field and a specified value is evaluated as true. Otherwise, the control is displayed in a disabled
state"grayed out" and not available for use.
Note:By default, a control with no dynamic properties is enabled and visible and is
a tab stop.
1. Click the Dynamic Properties pane.
2. Click Add to open the Configure Properties dialog box.
3. For Property, select Enabled.
4. For Data Ref, select the field to use to manage whether the control is enabled.
5. For Operator, select how the value associated with the field should be compared to a
specified value.
6. If the Value property is displayed, enter the literal value to which the value associated
with the field should be compared.
7. Click OK.
Tip: The Value property must not include a data ref or the name of a data map
entry. If you want to use a variable to manage whether the control is enabled, you
can accomplish this by using a business rule that includes a conditional business
rule component. Configure the output of the business rule to be a value in the
data map1, and then use that value to manage whether the control is enabled.
1A repository for the data for use when responding to a print request. Each data map entry is composed of a name (key) and a
value.
You can use the value referred to by a data ref to manage whether a control field is a tab stop,
and, if it is, manage the order in which the field receives focus when a Data Provider uses the
Tab key for navigating in the form. The field is not a tab stop if the Tab Order value is -1.
Alternatively, you can select or clear the "Tab Stop" on page 181 property, manually "Change
the Field Tabbing Order" on page 139, or use a "Focus Form Rule" on page 411.
Note: By default, a control with no dynamic properties is enabled and visible and
is a tab stop.
1. Click the Dynamic Properties pane.
2. Click Add to open the Configure Properties dialog box.
3. For Property, select Tab Order.
Note: If the Tab Order option is not displayed, click the Properties pane,
select theTab Stop property for the control, and then click Save.
4. For Data Ref, select the field to use to manage the tab order of the control.
5. Click OK.
Tip: If you want to use a variable to manage the tab order value of a control, you
can accomplish this by using a business rule. Configure the output of the business
rule to be a value in the data map1, and then use that value to manage the tab
order value.
1A repository for the data for use when responding to a print request. Each data map entry is composed of a name (key) and a
value.
If the form containing the control is part of a label template, you can use a Data Entry data
source to associate the data provided via the control with a field in the Label view of a label
template. Data provided by using the control can be printed on a label. To do so, use this
procedure.
1. Expand the Data Sources pane.
2. Expand the Data Entry data sources.
3. Click and drag the listing for the control onto a Variable Text field or a Barcode field in
the Label view.
n : Displayed when the mouse pointer is over a field that can accept the data
source.
n : Displayed when the mouse pointer is not over a field that can accept the data
source.
The Variable Text or Barcode field is now configured to use the control as its source of data.
You can confirm this by clicking the Variable Text or Barcode field and noting that in the
Properties pane the Data Ref property contains the name of the control.
Important! After you assign a data source to a field, renaming the data source or
associated control breaks the connection between the variable field or barcode and
the data source. You must complete the association procedure again, or rename the
Data Ref property of the variable field or barcode to match the new name of the
data source.
Control Properties
The types of control fields available in Loftware Spectrum include Button1, Check Box2,
Drop-Down List3, Device Selector 4, Folder Selector 5, Label Selector 6, Radio Button
Group7, Prompt8, User Selector 9, Table 10, and Text Box Prompt11 fields. Control fields
can be used in a form, in the Form view of a label template, or the Form view of a reusable
object and have the following properties.
Name and Data
Note: A Field Name, Data Ref, or Input Data Ref can include letters and
numbers. Additionally, the following characters are permitted but cannot begin
the name: hyphens, underscores, and periods.
1A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when clicked by a Data Provider.
2A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when the check box is selected or cleared by a Data Provider.
3A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when a Data Provider changes which item is selected.
4A control field in a form or in the data entry view of a label template that allows a Data Provider to select a printer or other device. A
Device Selector is displayed as a browse button and the name of the selected device. Clicking the browse button opens a dialog
box from which a Data Provider can select a device. A control can also be used to run a data source query, a form rule, or a business
rule.
5A control field in a form or in the data entry view of a label template that allows a Data Provider to select a folder. A Folder Selector
is displayed as a browse button and the name of the selected folder. Clicking the browse button opens a dialog box from which a
Data Provider can select a folder. A control can also be used to run a data source query, a form rule, or a business rule.
6A control field in a form or in the data entry view of a label template that allows a Data Provider to select a label. A Label Selector is
displayed as a browse button and the name of the selected label. Clicking the browse button opens a dialog box from which a Data
Provider can select a label. A control can also be used to run a data source query, a form rule, or a business rule.
7A type of control or document field in the data entry view of a label template or in a form that can be used to run a data source
query, a form rule, or a business rule when a Data Provider changes which item is selected.
8A type of control or document field used to collect information from a Data Provider in the data entry view of a label template or in
a form. When a Data Provider submits data via a prompt, a data source query, a form rule, or a business rule may be run.
9A control field in a form or in the data entry view of a label template that allows a Data Provider to select a user. A User Selector is
displayed as a browse button and the name of the selected user. Clicking the browse button opens a dialog box from which a Data
Provider can select a user. A control can also be used to run a data source query, a form rule, or a business rule.
10A control field in a form that systematically displays the results of a data source query, a form rule, or a business rule in columns
and rows.
11A type of control or document field in the data entry view of a label template or in a form that can be used to allow a Data Provider
to retrieve lengthy data from a database and then manipulate the data retrieved.
1A value that is unknown. A null value is different from an empty string or a zero value.
l Alpha-Numeric
l Alpha-Only
l Code 39
l Code 93
l Full ASCII
l Hexadecimal
l Numeric-Only
l GS1
l GS1-128 Alpha-Numeric
l Uppercase Alpha-Numeric
l Uppercase Alpha-Only
Scan Only Whether data for the prompt can only be scanned in. Prompt
: Data can be entered by any means.
: Data for this prompt can be entered only by scanning.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
Note: Rotating a field does not change the values of these properties. For
example, regardless of what the value for Rotation is, the Width refers to the
distance from the left edge of the field to the right edge of the field when
Rotation is set to 0.
Property Description Fields Where Available
Left The distance from the left edge of the field to the left All fields
edge of the label. The value is dependent on the unit of
measure for the label template.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
Configure Properties
The following properties are displayed in the Configure Properties dialog box.
Property Description Values
Property A property of a control Enabled: Whether the control can be used
that can be turned on or by a Data Provider in Print. If a
off, such as whether the comparison between the value associated
control is enabled or with a field and a specified value is
whether the control is evaluated as true, then the control is
displayed to a Data displayed and can be used. If false, the
Provider 1 in Print. control is displayed in a disabled state and
cannot be used.
Visible: Whether the control is displayed
to a Data Provider in Print. If a
comparison between the value associated
with a field and a specified value is
evaluated as true, then the control is
displayed. If false, the control is not
displayed.
Tab Order: The order in which the
control receives focus when a Data
Provider uses the Tab key for navigating in
Print. The control is not a tab stop if the
Tab Order value is -1.
Data Ref The field used to manage The list of fields that exist in the form
whether the specified
property is turned on or
off.
Operator The operator used to Equals
compare the value Not Equal
referred to by the Data Greater Than
Ref to a specified value. Less Than
Is Empty
Is Not Empty
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
1A repository for the data for use when responding to a print request. Each data map entry is composed of a name (key) and a
value.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
3Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
Providers.
l Value: The option value, which is not displayed
to Data Providers.
l Add: Add the option to the list and clear the
For a table 1 in a label template or a form, the Column and Table Rules pane allows you to
add or remove columns in a table, configure properties and styles for the table, and add styling
1The view that is displayed to a user on the Print page that allows the user to enter information for a label. A Document Designer
can configure this view in the Form view on the Design page.
rules to the table and to specific columns. Additional table options can be found in
theProperties pane. For more information, see "Table" on page 185.
Note: Styles defined by a Style Data Ref override the styles configured on a
column.
Table Rules
You can use table rules to apply styling to rows that meet the specified criteria. Table rules are
implemented in order beginning with the rule at the top, and the last rule overrides previous
rules if applicable. Use the arrows to change the order in which the rules are
implemented. Table rules are overridden by rules for the column for that cell.
Property Description
Column Name The name of the column which the rule applies to.
Operator The rule operator. Options include Equals, Not Equals, Begins
With, Doesn't Begin With, Contains, Doesn'tContain, Is Empty, Is
Not Empty, Is Null, Is Not Null, Less Than, Less or Equal,
Greater Than, and Greater or Equal.
Value The data criteria. This field is case sensitive.
Set Style Which style to modify. Options include Background Color, Font
Color, Font Size, Font Style, Font Weight, and Text Decoration.
Style Value How the style is modified.
Header Properties
Header properties are overridden by those defined by a StyleData Ref.
Accepted
Property Description Key
Values
Display Name Content for the column String headerText
header. To use the name as
defined in the data source,
leave this field blank.
Header Background The column header #000000 headerBackgroundColor
Color background color. You can to
select a color or enter a #FFFFFF
hexadecimal RGB color value. (Default)
Header Height The vertical span of the 0 to 999 headerHeight
header row in pixels. (Default:
20)
Accepted
Property Description Key
Values
Header Horizontal The horizontal alignment of left headerHorizontalAlign
Align text in the column header cell. center
(Default)
right
Header Font Color Color of characters in the #000000 headerFontColor
column header. You can select (Default)
a color or enter a hexadecimal to
RGB color value. #FFFFFF
Header Font Size The size of type in the column 0 to 999 headerFontSize
header in points. (Default:
12)
Header Font Style Additional formatting for text normal headerFontStyle
in the column header. (Default)
italic
Header Font Weight Additional formatting for text normal headerFontWeight
in the column header. bold
(Default)
Header Opacity The opacity of the column 0 to 1 headerAlpha
header background color, (Default:
where 0 is transparent and 1 is .8)
solid.
Header Text Additional formatting for text none headerTextDecoration
Decoration in the column header. (Default)
underline
Column Properties
Column properties are overridden by those defined by a StyleData Ref.
Accepted
Property Description Key
Values
Column Name The name of the column in the data. String dataField
Editable Whether a Document Designer can true allowEditing
edit the contents of the column cells. false
(Default)
Accepted
Property Description Key
Values
Horizontal Align The horizontal alignment of text in the left horizontalAlign
column cells. (Default)
center
right
Padding Bottom The margin between the text and the 0 paddingBottom
bottom of the column cells. (Default)
to 999
Padding Left The margin between the text and the 0 paddingLeft
left edge of the column cells. (Default)
to 999
Padding Right The margin between the text and the 0 paddingRight
right edge of the column cells. (Default)
to 999
Padding Top The margin between the text and the 0 paddingTop
top of the column cells. (Default)
to 999
Renderer Whether the column cells display text checkbox renderer
or a check box. To allow a check box text
to be selected, Editable must also be (Default)
set to true for the column.
Resizable Whether a Document Designer can true resizable
adjust the column width. (Default)
false
Sortable Whether a DocumentDesigner can true sortable
sort the column cells. (Default)
false
Type The data type of values in the column. String datatype
(Default)
Number
Boolean
Text Decoration Additional formatting for text in the none textDecoration
column cells. (Default)
underline
Accepted
Property Description Key
Values
Vertical Align The vertical alignment of text in the top verticalAlign
column cells. middle
(Default)
bottom
Width The distance from the left edge of the 0 to 999 width
column to the right edge of the column (Default:
in pixels. 100)
Min Width The minimum width of the column in 0 to 999 minWidth
pixels. (Default:
20)
Word Wrap If text in a cell reaches the column true wordWrap
edge, whether to automatically move (Default)
the text to the next line. false
True: Text is moved to the next line if
it reaches the column edge. The Row
Height does not change.
False: Text is not moved to the next
line if it reaches the column edge and
does not display unless the column
width is increased.
Column Rules
You can use column rules to apply styling to cells in the selected column that meet the specified
criteria. Column rules are implemented in order beginning with the rule at the top, and the last
rule overrides previous rules if applicable. Use the arrows to change the order in which
the rules are implemented. Column rules override table rules for the cell. For more information,
see "Add a Table Rule" on page 164.
Property Description
Column Name The name of the column which the rule applies to.
Operator The rule operator. Options include Equals, Not Equals, Begins
With, Doesn't Begin With, Contains, Doesn'tContain, Is
Empty, Is Not Empty, Is Null, and Is Not Null.
Value The data criteria. This field is case sensitive.
Set Style Which style to modify. Options include Background Color, Font
Color, Font Size, Font Style, Font Weight, and Text
Decoration.
Style Value How the style is modified.
Example
The following column rule sets the background color to green for cells containing
January 1 in the Date column.
Colum- Style
Oper- Valu-
n Set Style Valu-
ator e
Name e
Date Equals Januar Backgrou green
y1 nd Color
Using Barcodes
Each barcode symbol has a unique set of properties that are used to define the symbol.
Add a Barcode
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
You can configure primary, secondary, and combined barcodes that comply with the UPN
specification for the Health Industry Bar Code (HIBC) Supplier Labeling Standard by using
LoftwareSpectrum. This standard is intended for use with products distributed in the
healthcare industry.
For more information about encoding HIBC barcodes, see the The Health Industry Bar Code
(HIBC) Supplier Labeling Standard listed in "External Links" on page 1645.
To add barcodes that comply with the HIBC standard to a label template, use the following
procedure.
1. Click Design and open a label template or create a new label template.
2. Add either a primary barcode and optionally a secondary barcode, or else a combined
barcode. The HIBC Supplier Labeling Standard considers a secondary barcode to be
optional. If using a 2D symbology, either use only a primary barcode or else use a
combined barcode.
For each barcode, do the following.
a. To create the barcode, in the Barcodes list in the Library, expand either Linear
or 2D.
b. Click one of the following symbologies and drag it to the Label pane: Code 128,
Code 39 (not Full ASCII), Aztec, DataMatrix, MicroPDF417, or QR Code.
c. In the Properties pane, change the Field Name to a meaningful name, such as
PrimaryBarcode, SecondaryBarcode, or CombinedBarcode.
d. Configure the Max Chars to meet or exceed the length of the data. In addition to
the data to be entered, you must allow space for the flag character and the check
character. For a Combined barcode, you must also allow space for a separator
character.
e. If using Code 39 or Code 128, set Check Digit to None so that you can
configure and use it separately.
f. If using Code 39 or Code 128, set Human Readable to None so that you can
configure it separately.
g. If using Code 39, for Ratio select 3.0:1.
h. Configure other fields as appropriate, leaving the Data Ref field blank.
3. Add a Variable Text field for the human readable text for each barcode. For each
barcode, do the following.
a. To create human readable text for the barcode, in the Text list in the Library,
click Variable Text, and drag it to the Label pane.
b. In the Properties pane, change the Field Name to a meaningful name, such as
PrimaryText, SecondaryText, or CombinedText.
c. Configure the Chars Per Line to meet or exceed the length of the data. In
addition to the to be data entered, you must allow space for the flag character,
check character, and two asterisks (denoting the beginning and end of the human
readable text). For a Combined barcode, you must also allow space for a separator
character.
d. Configure other fields as appropriate, leaving the Data Ref field blank.
4. For each input that you want to be entered by the Data Provider, create and configure a
Prompt (which will be automatically associated with a Data Entry data source and a Data
Ref). You do not need to create a Prompt for any component of the barcode data that is
static.
These inputs, defined by the HIBC standard, include some or all of the following.
Input Field Name
Labeler Identification Code LIC
Product or Catalog Number PCN
Unit of Measure Identifier UM
Reference Identifier RefId
Quantity Quantity
Expiration Date ExpDate
Lot/Batch or Serial Number Lot
For each input that you want to include, do the following.
a. To create a Prompt, in the Text list in the Library, click and drag a Prompt to
the Form pane. A Data Entry data source is created.
b. For each field in the Form pane, click the field to select it, and in the Properties
pane change the Field Name to a meaningful name and the Prompt to the text
that should be displayed to Data Providers. Either use the Field Names suggested
in the preceding table, or else change the Formulas in the following steps to
incorporate the Field Names that you chose.
c. Leave the Data Ref field blank.
d. Select an Entry Type and Character Mask for each input as appropriate.
e. Configure Chars Per Line for each input to meet or exceed the length of the data
to be entered.
5. Create Formula data sources to support each barcode. Leave the Data Ref field for the
Formula data source blank. For any component of the barcode data that is static, you can
replace the Data Ref shown in the formula below (such as {/Body/LIC}) with the
appropriate text enclosed in quotation marks (such as "A123").
Data
Description Source Formula
Name
Primary Pri_Base "+" + {/Body/LIC} + {/Body/PCN} + {/Body/UM}
barcode data
except for
check digit
Primary Pri_Check Mod43({/Pri_Base})
check digit
Secondary Sec_Base "+" + {/Body/RefId} + {/Body/Quantity} +
barcode data {/Body/ExpDate} + {/Body/Lot} + {/Pri_Check}
except for
check digit
Secondary Sec_Check Mod43({/Sec_Base})
check digit
Combined Com_ "+" + {/Body/LIC} + {/Body/PCN} + {/Body/UM}
barcode Base1 + "/"
data, part 1
Combined Com_ {/Body/RefId} + {/Body/Quantity} +
barcode Base2 {/Body/ExpDate} + {/Body/Lot}
data, part 2,
except for
check digit
Combined Com_ Mod43({/Com_Base1} + {/Com_Base2})
check digit Check
6. Create a Formula data source for each barcode. Leave the Data Ref field for the Formula
data source blank.
Data Source
Description Formula
Name
Primary barcode data Pri_Barcode {/Pri_Base} + {/Pri_Check}
Secondary barcode data Sec_Barcode {/Sec_Base} + {/Sec_Check}
Combined barcode data Com_Barcode {/Com_Base1} + {/Com_Base2} +
{/Com_Check}
7. For each barcode, click and drag the formula to be associated with that barcode, and drop
it onto that barcode in the Label pane. This populates the Data Ref field for the barcode.
8. Create a Formula data source for the human readable text for each barcode. These
formulas enclose the data in asterisks and replace any check digit that is a space with an
underscore, as specified by the HIBC standard. Leave the Data Ref field for the Formula
data source blank.
Data Source
Description Formula
Name
Human readable text Pri_Text "*" + {/Pri_Base} + ({/Pri_Check}.rtrim
for Primary barcode (" ")).rpad("_",1) + "*"
Human readable text Sec_Text "*" + {/Sec_Base} + ({/Sec_Check}.rtrim
for Secondary (" ")).rpad("_",1) + "*"
barcode
Human readable text, Com_Text1 "*" + {/Com_Base1}
line 1, for Combined
barcode
Human readable text, Com_Text2 {/Com_Base2} + ({/Com_Check}.rtrim("
line 2, for Combined ")).rpad("_",1) + "*"
barcode
9. For each barcode, click and drag the formula to be associated with the human readable
text, and drop it onto the appropriate Variable Text field in the Label pane. This
populates the Data Ref field for the human readable text.
If you need to configure barcodes for products in the healthcare industry that comply with the
UPN specification for the Health Industry Bar Code (HIBC) Supplier Labeling Standard but
need more flexibility than the basic HIBC barcode formats provide, the HIBC standard allows
you to use an alternative format defined in ISO/IEC 15434 with Data Identifiers (DIs). This
alternative format may be helpful if you want to include data not otherwise covered by the
HIBC standard or need to produce a small label for use on a small package.
For more information about encoding HIBC barcodes with DIs, see the The Health Industry Bar
Code (HIBC) Supplier Labeling Standard listed in "External Links" on page 1645.
To add barcodes that include DIs and comply with the HIBC standard, use the following
procedure. Because using DIs provides the flexibility to include custom inputs, you may use
different inputs than shown in this example. Including human readable text is optional according
to the standard.
1. Click Design and open a label template or create a new label template.
2. Add a barcode.
For each barcode, do the following.
a. To create the barcode, in the Barcodes list in the Library, expand 2D.
b. Click one of the following symbologies and drag it to the Label pane: Aztec,
DataMatrix, MicroPDF417, or QR Code.
c. In the Properties pane, change the Field Name to a meaningful name, such as
HIBC_Barcode.
d. Configure the Max Chars to meet or exceed the length of the data. In addition to
the data to be entered, you must allow space for the seven-character message
header, one-character data delimiters, DIs, and two-character message trailer.
Unlike a typical HIBC barcode, no flag character, check character, or separator
character is used.
e. Configure other fields as appropriate, leaving the Data Ref field blank.
3. If you want to include human readable text for the barcode, add a Variable Text field.
For each barcode, do the following.
a. To create human readable text for the barcode, in the Text list in the Library,
click Variable Text, and drag it to the Label pane.
b. In the Properties pane, change the Field Name to a meaningful name, such as
HumanReadText.
c. Configure the Chars Per Line to meet or exceed the length of the data. In
addition to the data to be entered, you must allow space for parentheses to enclose
each DI. The message header, data delimiters, and message trailer are omitted.
Unlike a typical HIBC barcode, no asterisks are used to enclose the human
readable text.
d. Configure other fields as appropriate, leaving the Data Ref field blank.
4. For each input that you want to be entered by the Data Provider, create and configure a
Prompt (which will be automatically associated with a Data Entry data source and a Data
Ref). You do not need to create a Prompt for any component of the barcode data that is
static.
This format gives you the flexibility to include standard HIBC inputs, custom inputs, or
both. The following inputs are used in this example, but you can include different
standard or custom inputs. If you always use the same Issuing Agency Code (IAC), then
you can incorporate it into your Formulas as a static value instead of creating a Prompt for
it.
Field
Input
Name
DI for the Issuing Agency Code, the Labeler Identification Code, and part PCNDI
number
Issuing Agency Code IAC
Labeler Identification Code for supplier LIC
Part number assigned by supplier PCN
DI for the first custom input Custom1DI
First custom input Custom1
DI for the second custom input Custom2DI
Second custom input Custom2
For each input that you want to include, do the following.
a. To create a Prompt, in the Text list in the Library, click and drag a Prompt to
the Form pane. A Data Entry data source is created.
b. For each field in the Form pane, click the field to select it, and in the Properties
pane change the Field Name to a meaningful name and the Prompt to the text
that should be displayed to Data Providers. Either use the Field Names suggested
in the preceding table, or else change the Formulas in the following steps to
incorporate the Field Names that you chose.
c. Leave the Data Ref field blank.
d. Select an Entry Type and Character Mask for each input as appropriate.
e. Configure Chars Per Line for each input to meet or exceed the length of the data
to be entered.
5. Create Formula data sources for the barcode. Leave the Data Ref field for the Formula
data source blank. For any component of the barcode data that is static, you can replace
the Data Ref shown in the formula below (such as {/Body/IAC}) with the appropriate
text enclosed in quotation marks (such as "RH"). If you are using different inputs than
shown in this example, you must change the barcode formula accordingly.
Data
Description Source Formula
Name
Message MsgHeader "[)>" + ASCII_RS() + "06" + ASCII_GS()
header
Message MsgTrailer ASCII_RS() + ASCII_EOT()
trailer
Barcode data BarcodeData {/MsgHeader} + {/Body/PCNDI} + {/Body/IAC} +
{/Body/LIC} + {/Body/PCN} + ASCII_GS() +
{/Body/Custom1DI} + {/Body/Custom1} + ASCII_
GS() + {/Body/Custom2DI} + {/Body/Custom2} +
{/MsgTrailer}
6. Click and drag the formula to be associated with the barcode, and drop it onto that
barcode in the Label pane. This populates the Data Ref field for the barcode.
7. If you are including human readable text for the barcode, create a Formula data source for
the human readable text. The message header, data delimiters, and message trailer are
omitted. Each DI is enclosed in parentheses. Leave the Data Ref field for the Formula
data source blank. If you are using different inputs than shown in this example, you must
change the formula accordingly.
Data Source
Description Formula
Name
Human readable text HumanReadData "(" + {/Body/PCNDI} + ")" +
for barcode {/Body/IAC} + {/Body/LIC} +
{/Body/PCN} + "(" +
{/Body/Custom1DI} + ")" +
{/Body/Custom1} + "(" +
{/Body/Custom2DI} + ")" +
{/Body/Custom2}
8. If you are including human readable text for the barcode, click and drag the formula to be
associated with the human readable text, and drop it onto the appropriate Variable Text
field in the Label pane. This populates the Data Ref field for the human readable text.
Common Properties
Barcode properties common to all symbologies
Symbology-Specific Properties
Note: To create a barcode that adheres to the Health Industry Bar Code (HIBC)
Supplier Labeling Standard, you can use Code 128, Code 39 (not Full ASCII),
Aztec, DataMatrix, MicroPDF417, or QR Code.
Linear
Symbology More Information
Code 39 Commonly used variable length symbology restricted to 43
characters. ISO/IEC 16388.
Code 39 Extended (Full ASCII) Code 39
Full ASCII
Code 93 Enhanced Code 39
Code 93 Extended (Full ASCII) Code 93
Full ASCII
Code 128 High density alphanumeric/numeric symbology. ISO/IEC
15417.
EAN-8 World-wide, GS1 approved symbology. ISO/IEC 15420.
EAN-13 World-wide, GS1 approved symbology. ISO/IEC 15420.
Interleaved Typically non-retail packaging. ISO/IEC 16390.
2 of 5
POSTNET There are no properties unique to a Postal Numeric Encoding
Technique (POSTNET) barcode.
The United States Postal Service (USPS) replaced POSTNET
with USPS Intelligent Mail in January 2013.
UPC-A Universal Product Code. ISO/IEC 15420.
UPC-E Zero-suppressed version of UPC-A
USPS The United States Postal Service (USPS) requires the use of a
Intelligent USPS Intelligent Mail barcode (IMb) to qualify for automation
Mail prices.
2D
Symbology More Information
Aztec ISO/IEC 24778
EAN/UPC
Barcodes using these symbologies are typically used on items to be scanned at point-of-sale.
Symbology
EAN-8
EAN-13
UPC-A
UPC-E
Composite
Composite barcodes have a 2D portion followed by a linear portion. In the barcode data, the 2D
portion appears first and is followed by a composite delimiter (|) and then the linear portion.
Within a Formula data source, the composite delimiter can be represented by the COMPDELIM
() function.
In addition to the Max Chars property, Spectrum also displays 2D Max Chars and Linear
Max Chars for composite barcodes. Otherwise, a composite barcode uses the same symbology
as the related type of linear barcode.
Symbology
EAN-8 Composite
EAN-13 Composite
GS1 DataBar Composite
GS1-128 Composite
UPC-A Composite
UPC-E Composite
Common Properties for Barcodes
Barcode fields in a label template all share the following properties. These properties relate to
the position on the label, the source of the data for the barcode, the symbology used, and the
formatting of the barcode. In addition to these common properties, a barcode may also have
properties specific to the symbology selected.
Note: For GS1-128 and GS1-128 Composite barcodes, the first two digits in the
data provided are assumed to be the application identifier, regardless of whether
they are enclosed in parentheses.
Note: A Field Name, Data Ref, or Input Data Ref can include letters and
numbers. Additionally, the following characters are permitted but cannot begin the
name: hyphens, underscores, and periods.
Tip: Properties for positioning a barcode relative to the envelope of that field are
listed in the Barcode section, while those for positioning a barcode relative to the
label are listed in the Arrange section.
Name and Data
Extension.
l GS1 DataBar: Affected by GS1
DataBar Type.
Symbology The type of barcode.
Horizontal Whether the barcode is left aligned, : Align to left edge of
Alignment horizontally centered, or right aligned within envelope
or relative to the envelope. : Align to horizontal
center of envelope
: Align to right edge of
envelope
Vertical Whether the barcode is aligned to the top : Align to top edge of
Alignment edge, vertical center, or bottom edge of the envelope
envelope. : Align to vertical center
of envelope
: Align to bottom edge of
envelope
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Code 39 Full ASCII is also known as Code 39 Extended (Ext).
Property Description Values
Bar The height of the bars in the barcode. Value is dependent
Height on the unit of
measure for the
label template.
1Device settings that can be sent to a printer or other device when a specific label template is used to print, overriding options
configured for the device in Device Management or in the operating system. LSOs can be configured in Design.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Code 93 Full ASCII is also known as Code 93 Extended (Ext).
Property Description Values
Bar The height of the bars in the barcode. Value is dependent
Height on the unit of
measure for the
label template.
Data Data entered in this field will be encoded in the barcode
Identifier but will not print in the human readable text field for the
barcode.
Data Identifiers are used to help the scanner identify the
field.
For Example
For an AIAG label, a barcode with a data
identifier of P contains a part number, a data
identifier of Q signifies a quantity field and a
data identifier of S signifies a serial number
field.
Human Whether a text representation of the barcode is printed. None
Readable The human readable text can be positioned anywhere on Free Floating
the label (free floating).
Line X- The width of the module (narrow bar) of the barcode. Thousandths of an
Dim The range of values available varies with the Document inch (mil) in fixed
DPI of the label template. increments
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Note: For GS1-128 and GS1-128 Composite barcodes, the first two digits in the
data provided are assumed to be the application identifier, regardless of whether
they are enclosed in parentheses.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Property Description Values
Cell The width of the barcode cell (module). The range of Thousandths of
Width values available varies with the Document DPI of the an inch (mil) in
label template. fixed increments
Cell Whether to round up, down, or to the nearest dpi Nearest
Width when printing to a device with a different resolution Up
Round from the resolution specified in the label template. Down
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Property Description Values
Cell The width of the barcode cell (module). The range Thousandths of an inch
Width of values available varies with the Document DPI of (mil) in fixed increments
the label template.
Cell Whether to round up, down, or to the nearest dpi Nearest
Width when printing to a device with a different resolution Up
Round from the resolution specified in the label template. Down
Symbol The number of rows and columns in the symbol. For Auto
Size more information, see the "Symbol Size" section Square Form: 10x10 to
following this table. 144x144
Note: This value limits Max Chars. Rectangular Form: 8x18
to 16x48
Error The level of error checking and correction employed ECC 0
Correction in the symbol. ECC 50
Note: The current DataMatrix standard ECC 80
requires the use of ECC 200. ECC 100
ECC 140
ECC 200 (recommended)
Square Form
Rectangular Form
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Note: Composite barcodes have a 2D portion followed by a linear portion. In the
barcode data, the 2D portion appears first and is followed by a composite delimiter
(|) and then the linear portion.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Property Description Values
Current When used with the structured append format, the position of the 0-8
Symbol symbol in a set.
Mode Modes 0 and 1 are part of the original MaxiCode specification and 0
are now considered obsolete. 1
Mode 2 is used for Domestic U.S. destinations. 2
Mode 3 is used for non U.S. destinations. 3
Mode 4 is free form data entry. 4
Mode 5, if supported by the device, is used for free form data entry 5
with Full Enhanced Error Correction. 6
Mode 6 is used for reader programming only.
Total When used with the structured append format, the total number of 0-8
Symbols the symbols in a set.
UPS Version 1: Implements an ANSI-compliant UPS MaxiCode format None
Compression for compressing data and increasing data storage. Version
None: No compression is performed on the data. The format of the 1
data is governed by original MaxiCode specifications and the
requirements of the printer command language.
MicroPDF417 Properties
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Tip: If the amount of data in a barcode exceeds the usable space, adjust the
Columns, the Security Level, or both.
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Property Description Values
Cell Width The width of the barcode cell Thousandths of an inch
(module). The range of values (mil) in fixed increments
available varies with the
Document DPI of the label
template.
Cell Width Round Whether to round up, down, or Nearest
to the nearest dpi when printing Up
to a device with a different Down
resolution from the resolution
specified in the label template.
Encoding Mode The type of information l Byte: 8-bit bytes
encoded in the symbol. (binary).
l Alpha: Uppercase
alphanumeric
characters and the
symbols $, %, *,
+, -, /, :, period,
and space.
l Numeric:
Numeric digits
15% error
correction.
l Q: Approximately
25% error
correction.
l H: Approximately
30% error
correction.
For more information about encoding QR Codes, see the QR Code entry listed in "External
Links" on page 1645.
UPC-A, UPC-E, and Composite Properties
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
Note: If using UPC-E, provide data on which zero suppression has already been
performed.
United States Postal Service (USPS) Intelligent Mail is a suite of barcode symbologies.
l For Intelligent Mail barcodes (IMb) for mailpieces (letters, cards, and flats), use the
USPS Intelligent Mail symbology.
l For Intelligent Mail Tray barcodes, use either Code 128 symbology with Start Code C or
Interleaved 2 of 5 symbology.
l For Intelligent Mail Container barcodes, use the GS1-128 symbology with Start Code C or
B.
l For Intelligent Mail Package barcodes (IMpb), use the GS1-128 symbology with Start
Code C.
The USPS Intelligent Mail barcode for mailpieces is a 4-state barcode that consists of 65 bars
that can encode up to 31 digits. The following information can be included:
l Barcode Identifier
l Service Type Identifier (STID)
l Serial Number
The USPS Intelligent Mail symbology in Spectrum supports all formats for Intelligent Mail
barcodes for mailpieces. Those formats include using a 6-digit Mailer Identifier, a 9-digit Mailer
Identifier, or the Origin IMb Tracing Intelligent Mail Barcode Format.
For more information about encoding USPS Intelligent Mail barcodes, see the USPS entry listed
in "External Links" on page 1645.
Using Images
Images can be used as background, to add brand information, or to help identify a product
associated with a label template.
Add an Image
You can add a Variable Image field to a label so that a specific image can be selected at print
time. The path to the actual image in Spectrum can be provided by entering data into a prompt,
by retrieving the path from a database, or by generating the path using a formula or script.
To add a placeholder for an image to a label so that the actual image can be selected at print time,
use this procedure.
1. From the Images list in the Library, drag Variable Image to the Label view. A
placeholder envelope appears for the image.
2. Expand the Data Sources pane and configure a data source to determine which of
several images should be displayed. The data source must return the full path to an image
in Library.
Note: If the image that you want to use is not listed in the Library, see
"Import a New Image" on page 97.
3. Drag the data source to the image placeholder in the Label view. In the Properties pane,
the data source name is displayed in the Data Ref property for the image.
4. To specify a default image to appear in case the data source does not return a value, click
next to the Default Value property, and then select an image file.
Note: If the data source returns a value, the Default Value will not be
displayed even if the value returned by the data source is not valid.
Tip: The option selected for Design Data controls what data is used in
fields when previewed, printed, or displayed in Design. Either default
data1, placeholder data2, or data from a live data set3 can be used. For
more information, see "Select Data to Display in Design" on page 63.
5. Configure other "Image Properties" on page 233.
Example: Using a Prompt and a Formula to Select an Image
Create a label template that allows a Data Provider 4 to enter a hazard code into a form and uses
a Formula data source to produce a label displaying an image based on the code entered.
1. In Design, create a label template, and add a Prompt to the Form view.
a. For Field Name, enter Hazard.
b. For Prompt, enter Hazard Classification (C, F, N, O, or T).
c. For Chars Per Line, select 1.
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
4Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
Image Properties
Note: A Field Name, Data Ref, or Input Data Ref can include letters and
numbers. Additionally, the following characters are permitted but cannot begin the
name: hyphens, underscores, and periods.
Tip: Properties for positioning an image relative to the envelope of that field are
listed in the Image section, while those for positioning an image relative to the
label or the form are listed in the Arrange section.
Name and Data
Property Description
Field The identifier of the image in the label template, form, or reusable object.
Name
Data Ref Data Reference. The data source used to provide a path to an image in
Spectrum.
Tip: By default, Data Ref fields are case sensitive. If the label
template is intended for use with an SAP BC-XOM integration
or an SAP RFC integration, use only uppercase text in the Data
Ref field.
Default Path in Spectrum to a default image for the field. If the field is populated by a
Value Data Ref that returns a null value or has not yet received data, this value is
used.
Tip: For a variable image, browse to select an image.
Image
Property Description
Lock Whether to use the latest version of the image or a specific version of the
Version image.
If cleared, then the latest version of the image is used.
If selected, then the specified version of the image is used.
Note: This property is not available for variable images.
Lock Whether to make the proportions between the height and width of the
Aspect image fixed.
Ratio
Property Description
Resizing Whether the displayed size of the image can be changed. You can use this
Method option to display images used for variable image with consistent dimensions.
None: The displayed size of the image cannot be changed. For a variable
image that is larger than the envelope, the image extends beyond the
envelope when printed.
Fit to Envelope: The image can be resized either by dragging a handle or by
changing the Width and Height. For variable images, each image will be
displayed with the specified dimensions.
Note: This property is displayed only for images in Label
view. Changing the displayed size does not alter the original
image in the library.
Dither What dithering method to apply to the image when printed on a label or
Method displayed in a form. If the image has greater resolution or color depth than
the printer or display supports, dithering may provide a smoother
representation of the image. The original image is not altered.
None: The image is not dithered.
Floyd-Steinberg: Floyd-Steinberg dithering is applied to the image. If this
method is applied to a color image, the image is displayed in gray scale.
Ordered: Ordered dithering is applied to the image. If this method is
applied to a color image, the image is displayed in gray scale.
Horizontal Whether the image is left aligned, horizontally centered, or right aligned
Alignment within the envelope.
: Align to left edge of envelope.
: Align to horizontal center of envelope.
: Align to right edge of envelope.
Note: This property is available only for variable images.
Vertical Whether the image is aligned to the top edge, vertical center, or bottom
Alignment edge of the envelope.
: Align to top edge of envelope.
: Align to vertical center of envelope.
: Align to bottom edge of envelope.
Note: This property is available only for variable images.
Arrange
Property Description
Left The distance from the left edge of the image to the left edge of the label or
form. The value is dependent on the unit of measure for the label template.
Property Description
Top The distance from the top edge of the image to the top of the label or form.
The value is dependent on the unit of measure for the label template.
Center X The distance from the middle of the image to the left edge of the label or
form. The value is dependent on the unit of measure for the label template.
Center Y The distance from the middle of the image to the top of the label or form.
The value is dependent on the unit of measure for the label template.
Width The horizontal span of the image. The value is dependent on the unit of
measure for the label template.
Height The vertical span of the image. The value is dependent on the unit of
measure for the label template.
Rotation The angle of the image in relation to the printed label. The value is in
degrees.
Printing Whether the image appears on the printed label.
Field Note: This property is only displayed for images in Label view.
Lock If selected, no changes can be made to the properties of the field, and the
Field field cannot be moved or deleted. The order of the field relative to other
fields in the label template can be changed regardless of whether the field is
locked.
Note: This feature can be used to prevent accidental changes to
fields. It does not prevent other Document Designers from
unlocking a field.
Using Shapes
Shapes include lines, circles, and rectangles and can be used to separate sections of a label
template, or to emphasize information.
Add Shapes
From the Shapes list in the Library, click and drag Circle to the Label or Form view.
Add a Box
From the Shapes list in the Library, click and drag Box to the Label or Form view.
Add a Line
From the Shapes list in the Library, click and drag Line to the Label or Form view.
Shape Properties
Shapes in label templatessuch as Circles, Boxes, and Lineshave the following properties.
Note: A Field Name, Data Ref, or Input Data Ref can include letters and
numbers. Additionally, the following characters are permitted but cannot begin the
name: hyphens, underscores, and periods.
Name and Data
Shapes Where
Property Description
Available
Field The identifier of the shape in the label template, form, All
Name or reusable object.
Arrange
Shapes
Property Description Where
Available
Left The distance from the left edge of the shape to the left edge of the All
label. The value is dependent on the unit of measure for the label
template.
Top The distance from the top edge of the shape to the top of the All
label. The value is dependent on the unit of measure for the label
template.
Center X The distance from the middle of the shape to the left edge of the All
label. The value is dependent on the unit of measure for the label
template.
Center Y The distance from the middle of the shape to the top of the label. All
The value is dependent on the unit of measure for the label
template.
Width The horizontal span of the shape. The value is dependent on the Circle
unit of measure for the label template. Box
Height The vertical span of the shape. The value is dependent on the unit Circle
of measure for the label template. Box
Length The span of the line. Line
Rotation The angle of the shape in relation to the printed label. The value is All
in degrees.
Printing Whether the object appears on the printed label. All (Label
Field view
only)
Shapes
Property Description Where
Available
Lock If selected, no changes can be made to the properties of the field, All
Field and the field cannot be moved or deleted. The order of the field
relative to other fields in the label template can be changed
regardless of whether the field is locked.
Note: This feature can be used to prevent accidental
changes to fields. It does not prevent other
Document Designers from unlocking a field.
Appearance
Shapes
Property Description Where
Available
Thickness The width of the line. The value is dependent on the unit of Line
measure for the label template.
Border The thickness of the line that forms the shape. The value is Circle
dependent on the unit of measure for the label template. Box
Border The color of the line that forms the shape. You can select a Circle
Color color or enter a hexadecimal RGB color value. Box
Tip: To swap the Border Color and the Fill
Color, click .
Shapes
Property Description Where
Available
Fill Whether the specified Fill Color is used within the shape. Circle
No Fill: The area within the shape has a transparent Box
background and the Fill Color is not used.
Solid Fill: The area within the shape is the color specified by
Fill Color.
Note: If a reusable object is changed, label templates, forms, and reusable objects
to which it was added before the change was made are not affected.
Tip: For information about creating reusable objects, see "Create a Reusable
Object" on page 95.
By adding a reusable object to a label template, a form, or another reusable object, you can
include all of the components of a label template that are part of that reusable object.
Tip: For information about creating reusable objects, see "Create a Reusable
Object" on page 95.
Using Forms
You can configure a form to accept data entry from a Data Provider 1. A form is included as part
of a label template or a reusable object, but can also be created as a separate object.
You can configure the loading of a data entry form to act as a trigger for a query of a data service
associated with a Database data source or an Alternate data source.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
You can configure the loading of a data entry form to act as a trigger 1 to run a data source. A
Database data source 2 or an Alternate data source 3 associated with the data service must
already exist.
Tip: If you have not yet created the data source for which the loading of this form
should act as a trigger, you can select the trigger when you create the data source
instead. For more information, see "Create a Database Data Source" on page 309 or
"Create an Alternate Data Source" on page 318.
To configure the loading of a form to act as a trigger, use this procedure.
1. For a label template or a reusable object, if both the Label view and the Form view are
displayed, click the Form view.
2. In the Properties pane, expand the Triggers section and click Select a Trigger.
3. In the Data Source Selector dialog box, click the data source for which the loading of
the form should act as a trigger, and then click OK.
4. If the form acts as a trigger for more than one data source and the order in which the data
sources are run relative to each other is important, then you must configure values for
trigger priority 4 for these triggers. To assign trigger priorities, do the following:
a. In the Triggers section of the Properties pane, double-click a data source.
b. In the Database Data Source or Alternate Data Source dialog box, click Next
twice.
c. In the list of triggers, enter a value for Trigger Priority for the form. When these
triggers cause the data services to run, the data source with the lower value for
Trigger Priority is run first.
Tip: Trigger priorities are compared only if the triggers have the
same trigger source, trigger event, and trigger key (if any). For
example, if a data source has both a button and a prompt that act as
triggers, their Trigger Priority values are not compared to each
other.
d. Click OK.
e. Repeat for each data source listed in the Triggers section.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
2A connection to a database that acts as a data source and can serve as the data ref for a document field. A Database data source
is associated with a Database data service.
3A connection to a file external to Spectrum that acts as a data source and can serve as the data ref for a document field. An
Alternate data source is associated with either a File data service or an HTTP data service.
4The order in which data sources, form rules, or business rules that have otherwise identical triggers are run. Trigger values are
compared only if the triggers have the same trigger source, trigger event, and trigger key (if any). The type of data source is
irrelevant. Among data sources, form rules, or business rules with otherwise identical triggers, the data source with the lowest
value for trigger priority is run first.
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Design Page
Click Design at the top of the LoftwareSpectrum window to display options for creating and
configuring a label template, form, layout, reusable object, or application.
When a label template 1 or a reusable object is open, you can see both the Label view and
Form view of the label template. When a form that is not associated with a label template is
open, you see only a Form view.
l The Label view of a label template or reusable object shows the design for printed labels
produced from a label template and optionally allows you to associate a layout with the
label template.
Note: The impact of character-level formatting is not displayed in Design.
You can determine whether a Character-Level format source has been
applied to a text field by clicking the text field and viewing the Properties
pane. View the Format Sources section for a list of the format sources
applied to the text field. Also, the impact of character-level formatting is
displayed in Print when previewing a label.
The Form view of a label template, reusable object, or form shows the design for data
l
entry forms produced from a label template. If a user acting as a Data Provider 2 enters
data in Print, they do so by using the data entry form produced by a label template.
A layout3 has only one view, which shows the slots for labels on a page 4.
Document Object Name
The name of each label template or other object currently open in Design appears on a tab
above the label template. An asterisk next to the name indicates that the label template or other
object has unsaved changes. Also, you can move the mouse pointer over the tab to display the
file path of the object.
If the active label template, form, layout, reusable object, or application is version-controlled,
the version number of the version displayed is shown at the bottom of the editing pane as the
Version. A lock indicates that the label template or other object is version-controlled and that
you are viewing a checked-in version.
1A digital representation of a label that can be combined with variable data and used by print jobs to generate print job details.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
3An item that defines an organizational structure for printing multiple labels by using the same label template.
4In relation to media, the organization of labels specified by a layout. In relation to the Spectrum user interface, a top-level tab.
For more information, see "Working in a Version-Controlled Environment " on page 79.
Design Data
The source of data displayed in Design is shown at the bottom of the editing pane when a label
template or a layout is displayed. This option affects what is displayed in the Label view in
Design, as well as what is displayed when you preview or print a label in Design. More
specifically, this option affects what is displayed in text fields, barcode fields, and variable image
fields.
l Default Value: The values specified in the Default Value property for each field are
used.
l Placeholder: The data used for each field is placeholder data1 provided by Spectrum.
l Live Data Set: If configured, a snapshot of live data obtained from a Database data
source, an Alternate data source, or a Date/Time data source is used. You can also add
entries to the data set manually.
For more information, see "Select Data to Display in Design" on page 63.
1For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
Toolbar
Command Description
Icon
New Label Open the Create Label dialog box, which allows
you to create a label template and configure
properties for a printed label, such as the height
and width.
New Form Create and open a form that is not associated with a
label template.
New Create and open a layout.
Layout
New Image Import a new image into the Spectrum library so
that it can be used in label templates.
Note: An image that will be used
only as part of a Variable Image may
be saved to any folder in Spectrum.
Otherwise, for an image to be
available to add to a label template,
you must save it to the
Images\User Images folder, the
Images\Stock Images folder, or a
subfolder of one of those folders.
New Create and open a reusable object. As with a label
Reusable template, you can add fields to a reusable object
Object and save it. You can add content from a reusable
object to label templates, forms, or reusable
objects.
New Create and open an application in which you can
Application design a flow of work that transitions among
multiple forms.
Open Open the Open dialog box, which lets you select
an existing object to open.
Close Close the active object .
Toolbar
Command Description
Icon
Save As Open the Save As dialog box, which lets you save
the active object under a different name and in a
particular folder. The folder can be an existing
folder, or you can create a new folder.
The Add Folder button allows you to create a
subfolder in the selected folder. Clicking this
button displays the Add New Folder dialog box,
allowing you to enter a folder name and description
and to specify whether version control is turned on
or off for any object in the new folder.
Note: You cannot change the
Version Control setting after you
save the folder.
The new object is displayed in the editor.
Export Export an object to a separate file outside of
Spectrum.
Tip: You can use this capability to
transfer a label template from one
instance of Spectrum to another.
Import Import an object that was previously exported to a
separate file outside of Spectrum.
Design Print a sample label using the current label
Print template and the device connection displayed in
the menu bar.
Note: The icon button for this
command is displayed in the menu
bar and is near the rightmost edge of
the window.
Design Display a preview of the label generated by using
Preview the current label template. The preview is
displayed in a separate window.
Note: The icon button for this
command is displayed in the menu
bar and is near the rightmost edge of
the window.
Toolbar
Command Description
Icon
Version Save the current version of the object and make
Control > this the object available for publication or for
Check In others to check out. Checking in creates a version
that can no longer be altered.
Available only for an object that is in a version-
controlled folder and only to the user who checked
out or has taken control of the object .
Version Create a new, editable version of the object ,
Control > increment the minor version number. Other users
Check Out cannot change the object or view the version that
you have created until it is checked in.
Available only for an object that is in a version-
controlled folder and is checked in.
Version Undo any changes made since the object was most
Control > recently checked out, and then check it in. The
Undo checked out version is discarded and the version
Check Out number is decremented to that of the previous
version.
Available only for an object that is in a version-
controlled folder.
Version Check in and create a new published version of the
Control > object, incrementing the major version number and
Publish setting the minor version number to zero.
Available only for an object in a version-controlled
folder. Available only to users with Publish (PB)
permission for Documents.
Toolbar
Command Description
Icon
Version Delete the published version1 with the highest
Control > version number. The next latest version that
Undo remains may be a minor version.
Publish WARNING: If you have already
initiated a print job using the
published version or have used or
link to that version, you may get
unexpected results.
Available only for an object in a version-controlled
folder. Available only to users with Publish (PB)
permission for Documents and only if the current
version of the object is a published version.
Workflow Open the Select a Workflow Template dialog
>Start box, which allows you to select a workflow for
Workflow tracking and managing modifications to the label
template.
Workflow View the details of the current step of the
>View workflow that the label is in.
Current
StepDetails
Edit Menu Commands
Toolbar
Command Description
Icon
Undo Reverse the most recent action on a label template,
form, or reusable object.
Redo Reapply the previously undone action on a label
template, form, or reusable object.
Cut Remove a selected item from a label template,
form, or reusable object and place it into the
clipboard.
Copy Create a duplicate of a selected item and place it
into the clipboard.
Paste Place an item from the clipboard onto a selected
label template, form, or reusable object.
1When version control is used, a version for which the minor version number is zero. Users with some permissions can print only the
latest published version.
Toolbar
Command Description
Icon
Delete Remove a selected element from a label template,
form, or reusable object.
Select All Select all fields in the current view (Label view or
Form view) so that you can cut, copy, paste, or
delete them.
View Menu Commands
Toolbar
Command Description Options
Icon
Label View Display the Label view in the full
window.
Form View Display the Form view in the full
window.
Split Changes the arrangement of the label Horizontally
Screen template, form, or reusable object Vertically
views displayed.
Grid Display an overlay grid on the label
template, form, or reusable object to
assist with aligning objects. The dots
or lines of the grid are not displayed in
printed labels or in the forms
displayed to Data Providers. The type
of grid can be configured under
Options > Grid Settings.
Zoom Change the magnification level at 200%
which the label template, form, or 150%
reusable object is displayed. 125%
100%
75%
50%
Position Menu Commands
Toolbar
Command Description
Icon
Align > Left For a selected object, align its left edge to
the left of the label template.
For two or more selected objects, line up
their left edges.
Toolbar
Command Description
Icon
Align > Center For a selected object, align its horizontal
center to the center of the label template.
For two or more selected objects, line up
their horizontal centers.
Align > Right For a selected object, align its right edge to
the right of the label template.
For two or more selected objects, line up
their right edges.
Align > Top For a selected object, align its top edge to
the top of the label template.
For two or more selected objects, line up
their top edges.
Align > Middle For a selected object, align its vertical
midpoint to the middle of the label template.
For two or more selected objects, line up
their vertical midpoints.
Align > Bottom For a selected object, align its bottom edge
to the bottom of the label template.
For two or more selected objects, line up
their bottom edges.
Distribute >
Horizontally
Distribute >
Vertically
Rotate >
Clockwise
Rotate >
Counterclockwise
Order > Bring
Forward
Order > Bring to
Front
Order > Send
Backward
Order > Send to
Back
Options Menu Commands
1For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
2A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Menu
Bar Command Description
Icon
View Job View information about your recent printing. The job
Status ID and time stamp are displayed in the menu bar as a
link. You can click the link to display additional
information in Status. This option is displayed only
if you recently printed a sample label in Design.
Browse Browse to select the device connection to use for
Devices previewing and printing labels from Design. A
device may be a physical printer, device queue, or
other target for output, such as an image file or a
PDF file.
Menu
Bar Command Description
Icon
Design Print a sample label using the current label template
Print and the device connection displayed in the menu bar.
Note: You must save the label template
before you can print.
1For each field, the value specified in the Default Value property for that field.
2For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
3A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
4For each field, the value specified in the Default Value property for that field.
5For a Variable Text field, the series of digits 1234567890, repeated until the maximum number of characters allowed for the field is
displayed. For a barcode field, a sample barcode that adheres to the specified properties. For an image field, a sample image.
Whether placeholder data is used in Design is controlled by the selection for Design Data.
6A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Library
Types of fields and objects that can be added to a label template or a reusable object are
displayed in the Library pane in the left column. When you click one of these items in the
library, an example of that type item is displayed in the preview box at the bottom of the pane.
Text
Name Description
FixedText Text that does not change for each printed label or each time
a form is displayed.
VariableText Text that may change for each printed label or each time a
form is displayed.
Text Box Text that may change for each printed label.
Controls
Name Description
Button A field in the Form that can allow Data Providers to select
information from a data source. For types of data sources that
accept a trigger 1, a button can be associated with the data source
so that an action is performed when a Data Provider clicks the
button.
Check A field in the Form that can allow Data Providers to select
Box information from a data source. For types of data sources that
accept a trigger 2, a check box can be associated with the data
source so that an action is performed if a Data Provider has
selected the check box.
Drop- A field in the Form that can allow Data Providers to select
Down information from a data source. For types of data sources that
List accept a trigger 3, a drop-down list can be associated with the data
source so that an action is performed if a Data Provider has
selected a particular item in the list.
Device A field in the Form that allows Data Providers to select a device to
Selector be used when printing.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
2A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
3A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
Name Description
Folder A field in the Form that allows Data Providers to select a folder.
Selector
Label A field in the Form that allows Data Providers to select a label.
Selector
Radio A field in the Form that can allow Data Providers to select
Button information from a data source. For types of data sources that
Group accept a trigger, a radio button group can be associated with the
data source so that an action is performed if a Data Provider has
selected a particular radio button.
Prompt Field in the Form that allows Data Providers to enter data. For
types of data sources that accept a trigger 1, a prompt can be
associated the data source so that an action is performed after a
Data Provider enters text into the prompt.
Tip: For most on-demand data entry, a Prompt field
is recommended. However, a Text Box Prompt field
is appropriate for situations in which Data Providers
are expected to retrieve lengthy data from a database
and then manipulate the data retrieved.
User A field in the Form that allows Data Providers to select a user.
Selector Example
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
Name Description
Text A field in the Form that allows Data Providers to enter data. For
Box types of data sources that accept a trigger 1, a Text Box Prompt
Prompt can be associated the data source so that an action is performed
after a Data Provider enters text into the prompt.
Tip: For most on-demand data entry, a Prompt field
is recommended. However, a Text Box Prompt field
is appropriate for situations in which Data Providers
are expected to retrieve lengthy data from a database
and then manipulate the data retrieved.
Shapes
You can add barcodes to labels. A list of the supported barcode symbology is displayed in
Spectrum.
Images
You can search the Library and view an example any type of field or object that you select.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
2An item that can contain components of a label and a form so that you can incorporate them into labels and forms efficiently and
consistently.
Data Sources
The Data Sources pane is displayed in the left column when a label template, form, or reusable
object is displayed. It is initially collapsed near the bottom of the left column. Click the title bar
for Data Sources to expand the pane.
Use this pane to manage label data sources such as Data Entry, Database, Date/Time, Formula,
Increment/Decrement, and Script data sources. For more information, see "Configuring Label
Data Sources" on page 305.
Buttons in the Data Sources pane
1A collection of data (names and values) that was retrieved from a data source and is specific to a label template or a reusable
object. A data set can be used to populate fields displayed in Design, in a preview, and when test printing.
Format Sources
The Format Sources pane is displayed in the left column when a label template or a reusable
object is displayed. It is initially collapsed at the bottom of the left column. Click the title bar
for Format Sources to expand the pane.
Use this pane to manage Character-Level format sources, which allow you to format spans of
text within a Fixed Text object or a Variable Text object. For more information, see " Character-
Level Format Source Properties" on page 431.
Note: Character-level formatting is supported for TrueType fonts only. Also,
you cannot use a Character-Level format source to format the human readable text
associated with a barcode or to format fields in the data entry form of a label
template.
Buttons in the Format Sources pane
Form Rules
The Form Rules pane is displayed in the left column when a form or an application is displayed.
It is initially collapsed near the bottom of the left column. Click the title bar for Form Rules to
expand the pane.
Use this pane to manage form rules such as Electronic Signature, Job Request, Map Operations,
and Static form rules. For more information, see "Form Rules Reference" on page 405.
Buttons in the Form Rules pane
Properties
The Properties pane is displayed in the right column. If the right column is collapsed, click the
arrow button at the top of the column to expand it. If the Properties pane is collapsed, click the
Properties title bar to expand it.
Note: When a label template, form, or reusable object is displayed, the name of the
view (Label or Form) or the field you have selected appears near the top of the
Properties pane. You can select other fields by name from the drop-down list, or
you can click a field in the Label view or Form view to select it. When a layout is
displayed, all properties are always displayed in the Properties pane. When an
application is displayed, initially the application-level properties are displayed.
When you click a form within an application, the form-level properties are
displayed.
Use this pane to view and change the following:
l "Label Template Properties" on page 273
l "Form Properties" on page 284
Tip: If you are viewing a label template that was migrated from a Loftware Print
Server (LPS) environment, a flag icon is displayed in the Migrated property for
each field. You can click the icon to display information about any migration issues
related to that field. To display a report of all migration issues for the label
template, click the Label view and then click the icon in the Migrated property.
You can remove the icons by clicking the Clear All Flags button in the Migrated
property. Also, if LPS-Style Font Rendering was turned on when the label template
was migrated, then a notice to that effect is displayed in the Properties pane. For
more information, see "Work with a Migrated Label Template" on page 119.
The Field Tabbing Order pane is displayed in the right column when viewing a label template,
form, or reusable object. If the pane is collapsed, click the Field Tabbing Order title bar to
expand the pane.
Use this pane to rearrange the order of input fields for users printing labels on demand. For more
information, see "Change the Field Tabbing Order" on page 139.
The Label Specific Options pane or Layout Specific Options pane is displayed in the right
column when viewing a label template or a layout. If the pane is collapsed, click the Label
Specific Options title bar or Layout Specific Options title bar to expand the pane.
Use this pane to customize device-specific options for an individual label template or layout. For
situations in which a label may be printed to more than one family or model of device, you can
create multiple configurations of Label Specific Options.
Tip: To configure baseline device-specific options for all label templates, use Device
Management.
Note: Label Specific Options cannot be included in a reusable object, and the
Label Specific Options pane is not displayed when editing a reusable object.
Tags
The Tags pane is displayed in the right column when viewing an application, business rule, data
service, device group, facility, form, image, integration, label template, layout, process, remote
site, reusable object, user, or workflow template. If the pane is collapsed, click the Tags title
bar to expand the pane.
You can categorize an application, business rule, data service, device group, facility, form, image,
integration, label template, layout, process, remote site, reusable object, user, or workflow
template by assigning tags to it. Each tag has a category and a value. For a version-controlled
object, tags cannot be changed in a previously checked-in version.
Buttons in the Tags pane
Data Sets
The Data Sets pane is displayed in the right column when viewing a label template. If the pane
is collapsed, click the Data Sets title bar to expand the pane.
You can use a data set to store a snapshot of live data retrieved from a Database data source. You
can use this data to produce a more realistic view when designing a label template. You can also
manually alter data map entries in a data set.
Buttons in the Data Sets pane
1A name (key) and value pair in the data map for a job.
Top Bar
Name Description
Username Displays the user name with which you are logged on.
Help Open the SpectrumUserGuide.
About View the version of Spectrum that you are using.
Logout Close Spectrum and sign out.
The following are properties that describe a label template 1. They include the Label2
properties and the Form 3 properties. The Label properties and the Form properties for a label
template are configured independently. The Trigger properties are part of the Form properties.
Tip: If you are viewing a label template that was migrated from a Loftware Print
Server (LPS) environment, a flag icon is displayed in the Migrated property for
each field. You can click the icon to display information about any migration issues
related to that field. To display a report of all migration issues for the label
template, click the Label view and then click the icon in the Migrated property.
You can remove the icons by clicking the Clear All Flags button in the Migrated
property. Also, if LPS-Style Font Rendering was turned on when the label template
was migrated, then a notice to that effect is displayed in the Properties pane. For
more information, see "Work with a Migrated Label Template" on page 119.
Label Properties
Label properties affect printed labels produced by using the label template. These properties
can be configured in the Create Label dialog box when you create the label template. In an
existing label template, these properties can be displayed by clicking the Label tab at the
bottom of the window or clicking the label background to select the Label view, and can be
configured in the Properties pane.
Property Description Options Notes
Font The type of fonts to be used on the label. TrueType
Category DPL4
IPL5
ZPL II6
1A digital representation of a label that can be combined with variable data and used by print jobs to generate print job details.
2The output or part of the output from a job, either printed on physical media or stored in a digital file.
3The interface for data entry by a data provider. A form is a separate object in Spectrum, but it can be combined with a label
template so that the form serves as the Form view for the label template.
4Datamax-O'Neil Programming Language, a printer control language.
5Intermec Printer Language, a printer control language.
6Zebra Programming Language II, a printer control language.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
An event such as the clicking of a button or the submission of text input via a prompt can
serve as a trigger 1 to run a label data source, form rule, or business rule. The loading of a
form or an application can also serve as a trigger to run a rule.
When you configure a form, you can add or remove triggers that use the loading of that form
as a trigger source. Because triggers do not have names, in the Properties pane for a form, a
trigger is identified by the name of the data source for which the loading of the form acts as a
trigger.
Note: The Triggers section is displayed when the Form properties are
displayed.
Property Description Options
Data Sources A list of label data sources for which the loading of this form Select a
acts as a trigger to run the data source. This list can include Trigger
Alternate data sources and Database data sources.
To select a trigger, click Select a Trigger, select the data
source to be run when the form is loaded, and click OK.
To remove a trigger, select the data source that the trigger
runs, and click .
To edit the properties of a data source acting as a trigger,
double-click the name of the data source.
Important! If the form acts as a trigger for more
than one data source and the order in which the
data sources are queried relative to each other is
important, then you must configure priorities for
these triggers. For more information, see
"Configure a Form to Run a Data Source" on
page 244.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
Layout Properties
The following are properties that describe a layout1 and affect how any label template 2 to
which the layout is attached is printed. These properties can be configured on the Properties
pane when the layout is opened for editing.
Note: A version-controlled layout must be published before it can be attached to a
label template.
1An item that defines an organizational structure for printing multiple labels by using the same label template.
2A digital representation of a label that can be combined with variable data and used by print jobs to generate print job details.
Form Properties
The following are properties that describe an on-screen data entry form. Unlike the properties
for a complete label template, they include only the Form 1 properties, of which the Trigger
properties are a subset. The properties of a form can be displayed by clicking the Form canvas
when editing a form or by clicking the icon for a form in an application, and they can be
configured in the Properties pane.
Note: For information about the properties of a form that are displayed when
editing an application, see " Form Properties in an Application" on page 302.
Form Properties
The following properties are displayed when editing a form but not when editing an
application.
Property Description Options Notes
Font The type of fonts to be used in the data TrueType This field is
Category entry form. read-only.
Size The dimensions of the data entry form inLetter This property
Design. Legal does not limit
A4 the dimensions
2x2 of the data
4x4 entry form
4x6 display area in
Custom Print.
Width The horizontal span of the form. If the Millimeters (up To view or
Size is set to Custom, you can manually to 356mm) configure the
configure this value. Centimeters (up unit of
to 36cm) measurement,
Inches (up to in the menu bar
14in) select Options
> Units.
Height The vertical span of the form. If the Size Millimeters (up To view or
is set to Custom, you can manually to 3810mm) configure the
configure this value. Centimeters (up unit of
to 381cm) measurement,
Inches (up to in the menu bar
150in) select Options
> Units.
1The interface for data entry by a data provider. A form is a separate object in Spectrum, but it can be combined with a label
template so that the form serves as the Form view for the label template.
Note: The Triggers section is displayed when the Form properties are
displayed.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
2A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
1An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
2A collection of component sets or business rule components that can be used to incorporate logic or to add, change, or remove
data or print parameters after a print request is submitted but before printing occurs. Business rules are similar to form rules, but
provide more robust functionality. Business rules are created on the Process Design page and can be designed using the
Configurator or programmed using XML.
Stock Layouts
Although you can create your own layouts, the following stock layouts are provided in the
Document Templates\Stock Layouts folder in Spectrum. You can use a stock layout as is, or
if you are creating a custom layout you can use a stock layout as a starting point by opening the
stock layout in Design and clicking File > Save As.
Layout Stock Labels Labels
Label Size Notes
Name Size Across Down
4x4-2x2 4"4" 2"2" 2 labels 2 labels 4 labels per page.
4x4-3x3 4"4" 1"1" 3 labels 3 labels 9 labels per page.
8x11-1x2 8"11" 4-3/4"7- 1 label 2 labels 2 labels per page.
3/4" Compatible with Avery
#6876.
8x11-2x2 8"11" 3-3/4"4- 2 labels 2 labels 4 labels per page.
3/4" Compatible with Avery
#6878.
8x11-2x3 8"11" 3"3-3/4" 2 labels 3 labels 6 labels per page.
Compatible with Avery
#6874.
8x11-2x5 8"11" 2"4" 2 labels 5 labels 10 labels per page.
Compatible with Avery
#15563.
8x11-2x6 8"11" 1-1/4"3- 2 labels 6 labels 12 labels per page.
3/4" Compatible with Avery
#6879.
8x11-2x10 8"11" 1"4" 2 labels 10 labels 20 labels per page.
Compatible with Avery
#5161.
8x11-3x10 8"11" 1"2-5/8" 3 labels 10 labels 30 labels per page.
Compatible with Avery
#8860.
8x11-4x20 8"11" 0.5"1.75" 4 labels 20 labels 80 labels per page.
Compatible with Avery
#18167.
You can use Application Architect to create custom front-end interfaces that empower end users
to make the decisions necessary to print what they need without deviating from a standard
procedure. For example, you could provide a flow of interactive forms that allows a Data
Provider 3 working in Print to select whether to print a kitting list, a production label, or a
shipping label, and then provide the information necessary to print the specified type of
document.
When using Application Architect, you create an application that connects individual forms by
using transitions. In an application, a trigger 4 can be used to run a form rule 5 or a business
rule 6. In a form, a trigger can also be used to run a data source. For data in a form, you can
manually enter a value, or you can use a data map entry 7.
1A framework that allows you to use Design to create custom applications that interface with Spectrum.
2An object in Spectrum that binds together all of the components to be used when responding to a print request. Among other
items, those components may include a label template, layout, device, and a business rule to be used when processing a print
request. Processes are created in the Process Design page.
3Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
4A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
5An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
6A collection of component sets or business rule components that can be used to incorporate logic or to add, change, or remove
data or print parameters after a print request is submitted but before printing occurs. Business rules are similar to form rules, but
provide more robust functionality. Business rules are created on the Process Design page and can be designed using the
Configurator or programmed using XML.
7A name (key) and value pair in the data map for a job.
Create an Application
Loftware Spectrum's Application Architect1 allows you to design complex, intelligent data
entry form experiences for Data Providers2. You can link individual forms together and
configure transitions that guide users from one form to another in response to their input or
other conditions.
Before You Begin: You should create the forms, business rules, and processes
that you intend to use with an application before you create the application. For
more information, see "Create a Form" on page 94 and "Designing Business Rules
with the Configurator" on page 437.
To create a new application, use this procedure.
1. In Design, click File > New > Application or click the New Application button
in the toolbar.
2. In the Forms pane, click the form that you want to be displayed to a Data Provider 3
when the application is initially loaded in Print, and then drag and drop the form into the
application.
3. Drag and drop additional forms into the application.
Note: You should not add more than one instance of a specific form to the
application.
4. Click the application canvas4 to display the properties of the application.
5. In the Properties pane, review the selection for Start Form and ensure that it is the
form that should initially be displayed when the application is loaded.
Best Practice
Save your application immediately after creation.
1A framework that allows you to use Design to create custom applications that interface with Spectrum.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
3Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
4The background of an application on which you can add forms and transitions. Clicking the application canvas displays the
properties of the application.
Next Steps
If the application includes more than one form, you should create transitions to allow Data
Providers to navigate from one form to the next by performing an action. For more information,
see "Create a Transition Between Forms" on page 295.
If you want to cause a form rule or a business rule to run when an application or a particular form
is loaded, when a Data Provider performs an action, or when other circumstances occur, see
"Create a Trigger to Run a Rule" on page 297.
1A framework that allows you to use Design to create custom applications that interface with Spectrum.
2A name (key) and value pair in the data map for a job.
1An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
Whenever the trigger event occurs, the form rule or business rule is run.
Tip: For more information about triggers, see "Triggers in Design" on page 419.
Before You Begin: You should create the forms, business rules, and processes
that you intend to use with an application before you create the application. For
more information, see "Create a Form" on page 94 and "Designing Business Rules
with the Configurator" on page 437.
To configure a trigger in an application to run a rule, use this procedure.
1. In Design, open an application.
2. Configure the rule to run either when the application is loaded, when a specific form is
loaded, or when a control in a form is clicked, changed, or used to commit text in a
prompt.
n If you want a rule to run when the application is initially loaded, click the
application canvas5, and then in the Triggers section click Select a Trigger.
n If you want a rule to run when a specific form is initially loaded, click the form,
and then in the Properties pane click Select a Trigger. In the Select a Trigger
dialog box, the form is selected as the Trigger Source by default.
n If you want a rule to run when a control in a form is clicked or changed or when
text is committed to a prompt, click the form, and then in the Properties pane
click Select a Trigger. In the Select a Trigger dialog box, for Trigger Source
select a control to associate with the trigger.
1An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
2A collection of component sets or business rule components that can be used to incorporate logic or to add, change, or remove
data or print parameters after a print request is submitted but before printing occurs. Business rules are similar to form rules, but
provide more robust functionality. Business rules are created on the Process Design page and can be designed using the
Configurator or programmed using XML.
3Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
4A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
5The background of an application on which you can add forms and transitions. Clicking the application canvas displays the
properties of the application.
3. In the Select a Trigger dialog box, use the Trigger Type to specify whether you want
to run a form rule or a business rule.
n If you have selected Form Rule as the trigger type, select a form rule to be run
when the trigger event occurs.
n If you have selected Business Rule as the trigger type, click the browse button
and select a business rule to be run when the trigger event occurs. For Event
Name, enter the name of an event as specified in the XML of the business rule.
When the trigger event occurs, the business rule is run as if this event has
occurred.
4. Click OK.
n If the rule is configured to run when the application is loaded, then the trigger is
displayed in the Triggers list in the Properties pane if you click the application
canvas.
n If the rule is configured to run when a form is loaded, then the trigger is displayed
in the Triggers list in the Properties pane if you click the form.
n If the rule is configured to run when a control in a form is clicked, is changed, or
is used to commit text, then the trigger is displayed in the Triggers list in the
Properties pane if you click the form.
5. Click File > Save or click the Save button to save the application.
Application Properties
The following topics describe the properties of applications and forms when configuring an
application by using Loftware Spectrum's Application Architect1.
l "Application Properties" on page 300
l " Form Properties in an Application" on page 302
Note: For information about the properties of a form that are displayed when
editing a form, see "Form Properties" on page 284.
1A framework that allows you to use Design to create custom applications that interface with Spectrum.
Application Properties
The following are properties of an application created by using Loftware Spectrum's Application
Architect1.
Settings
Property Description Options
Start The form that is initially A list of forms that have been associated
Form displayed when the application with the application.
is run. Note: An application should
not include more than one
instance of a specific form.
Triggers
An event such as the clicking of a button or the submission of text input via a prompt can
serve as a trigger 2 to run a label data source, form rule, or business rule. The loading of a
form or an application can also serve as a trigger to run a rule.
When you configure an application, you can add or remove triggers that use the loading of
that application as a trigger source. Because triggers do not have names, in the Properties
pane for an application, a trigger is identified by the name of the rule for which the loading of
the application acts as a trigger.
1A framework that allows you to use Design to create custom applications that interface with Spectrum.
2A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
1An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
2A collection of component sets or business rule components that can be used to incorporate logic or to add, change, or remove
data or print parameters after a print request is submitted but before printing occurs. Business rules are similar to form rules, but
provide more robust functionality. Business rules are created on the Process Design page and can be designed using the
Configurator or programmed using XML.
The following are properties that describe an on-screen data entry form. Unlike the properties
for a complete label template, they include only the Form 1 properties, of which the Trigger
properties are a subset. The properties of a form can be displayed by clicking the Form canvas
when editing a form or by clicking the icon for a form in an application, and they can be
configured in the Properties pane.
The following are the properties of a form that are displayed when viewing a form within an
application.
Note: For information about the properties of a form that are displayed when
editing a form, see "Form Properties" on page 284.
Triggers
An event such as the clicking of a button or the submission of text input via a prompt can
serve as a trigger 2 to run a label data source, form rule, or business rule. The loading of a
form or an application can also serve as a trigger to run a rule.
When you configure a form, you can add or remove triggers that use the loading of that form
as a trigger source. Because triggers do not have names, in the Properties pane for a form, a
trigger is identified by the name of the rule for which the loading of the form acts as a trigger.
1The interface for data entry by a data provider. A form is a separate object in Spectrum, but it can be combined with a label
template so that the form serves as the Form view for the label template.
2A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
1An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
2A collection of component sets or business rule components that can be used to incorporate logic or to add, change, or remove
data or print parameters after a print request is submitted but before printing occurs. Business rules are similar to form rules, but
provide more robust functionality. Business rules are created on the Process Design page and can be designed using the
Configurator or programmed using XML.
Events
Property Description Options
Events A list of events that cause the application to transition from :
the selected form to another form if one of the events Connect
occurs. If the trigger event occurs to the control serving as a Mode is
trigger source, then the application transitions to the next disabled,
form. so you
Note: Only controls that exist in the form are cannot add
included in the list of available trigger sources. transitions.
Only events appropriate to the selected trigger Click to
source are included in the list of available enable
trigger events. Connect
Mode.
Tip: If is displayed in the toolbar, then :
you are in Connect Mode and you can add a Connect
transition by clicking the form from which a Mode is
transition should begin and then the form to enabled,
which the transition should lead. so you can
For more information, see "Create a Transition Between add
Forms" on page 295. transitions.
Click to
disable
Connect
Mode.
:
Delete the
selected
transition.
Double-
click a
transition:
Configure
the
selected
transition.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
To use the data provided via a Data Entry data source, you can use that Data Entry data source
as a data ref in another field such as a Variable Text, Barcode, or Image field, or you can use it as
a data ref in a Formula data source.
To associate a Data Entry data source with a Variable Text field, use the following procedure.
1. Drag Variable Text from the Library to the Label view to create a Variable Text
field.
2. Expand the Data Sources pane, and expand the list of Data Entry data sources.
3. Drag a Data Entry data source to the Variable Text field. A green plus icon
appears when your pointer is over a field that can accept the data source. Alternatively,
you can enter the name of the Data Entry data source as the Data Ref property of a
Variable Text field. When the label is printed, that Variable Text field will display the data
received from the Data Entry data source.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
2A local administrator who creates and configures data services for use by Document Designers who configure Database data
sources and Alternate data sources.
6. Edit the data service configuration. Depending on how the data service is configured, you
may be able to edit some of the configuration information or data service parameters that
were provided by the Data Service Administrator.
a. If text boxes are displayed, you can enter either static values or data refs using the
format ${<DataRef>}. After you begin typing in the field, a message may be
displayed about the type of data required until you finish entering a value or data
ref. For information about default parameters, see " Configuration Parameters for
JDBC Data Services" on page 1020.
b. If a Result Map is displayed, you can configure which columns are displayed to a
Data Provider 1. For more information, see " Configuration Parameters for JDBC
Data Services" on page 1020.
c. For Auto Select Single Row, specify how the data service should respond if only
a single row is returned by the SQL Query.
n If this option is selected, the Data Source Results dialog box is not
displayed and the data from the row is inserted into the form automatically.
n If this option is not selected, the Data Source Results dialog box is
displayed and the Data Provider must manually click the row to select it.
Note: If you select this option, it is recommended that you
include at least one Prompt field in the Form that is
populated by the results to provide confirmation to the Data
Provider that the query was executed.
d. When you have finished configuring the data service parameters, click Next.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
7. If the label template must support on-demand printing, click Add Trigger and configure
at least one trigger 1 that a Data Provider 2 can use to run the SQL Query on the
database. Repeat for additional triggers if needed.
Tip: If you have not yet created the field that should serve as the Trigger
Source 3, you can skip this step and select the trigger when you create the
field.
nTo query the data source when a button is clicked, for Trigger Source select the
name of a Button field and for Trigger Event select onClick.
n To query the data source after submitting data at a prompt, for Trigger Source
select the name of a Prompt field and for Trigger Event select onCommit.
n To query the data source when the form is loaded, for Trigger Source select
/Body and for Trigger Event select onLoad.
8. If the label template must support both on-demand printing and integrations, click Add
Trigger again.
Note: If the label template is not required to support on-demand printing,
then no trigger is needed.
a. For Trigger Source, select Do Not Run.
b. For Trigger Event, select Enqueue.
c. For Trigger Key, enter the name of a data map entry 4 that will manage whether
the data source should be run. It is recommended that this data map entry not be
used for any other purpose. The value of this data map entry does not affect how
it functions as a trigger key.
n When the trigger key exists in the datamap, the data source will not run.
This is appropriate when using the label template with an integration. This
is also appropriate if you need to prevent the data source from running in
some situations when using on-demand printing.
n When the trigger key does not exist in the datamap, the data source is run.
This is appropriate when using the label template for on-demand printing.
Important! For a File Drop integration, if the data map entry
specified for Trigger Key does not exist in the drop file, then the
data source is queried and the first row of data is automatically
returned. This occurs regardless of whether Auto Select First Row
and Auto Select Single Row Result are selected.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
3A field that is used in conjunction with a trigger event to interactively run a data source, form rule, or business rule. For example, a
button that runs a query when clicked, a prompt that runs a query when submitted, or a form that runs a query when loaded.
4A name (key) and value pair in the data map for a job.
9. Assigning values for Trigger Priority 1 is necessary only if more than one data source in a
label template includes a trigger with the same trigger source, trigger event, and trigger
key (if any). In that situation, you can assign different values for Trigger Priority for
these otherwise identical triggers, and the data source with the lower value for Trigger
Priority is run first.
10. Click OK.
In the Data Sources pane, the Database section now lists the Database data source that you
created. Expand the Database data source to display the names of columns from the database
that you can use as data sources. You can drag a column data source onto a field in the Label
view such as a Variable Text or Barcode field to assign the data source as the data ref for that
field, or you can enter a data ref manually. You can create a formula and select the data refs for
the database columns for use in the formula.
Note: The format by which to refer to a database column data source is
/<DatabaseDataSourceName>/<ColumnName>.
Important! If you have not yet created at least one trigger for the data source, you
can do so by using the Triggers section in the Properties pane when you
configure a control, a form, or the Form view of a label template that will serve as
the Trigger Source 2. For more information, see "Adding Controls" on page 153,
"Label Template Properties" on page 273, or "Form Properties" on page 284.
1The order in which data sources, form rules, or business rules that have otherwise identical triggers are run. Trigger values are
compared only if the triggers have the same trigger source, trigger event, and trigger key (if any). The type of data source is
irrelevant. Among data sources, form rules, or business rules with otherwise identical triggers, the data source with the lowest
value for trigger priority is run first.
2A field that is used in conjunction with a trigger event to interactively run a data source, form rule, or business rule. For example, a
button that runs a query when clicked, a prompt that runs a query when submitted, or a form that runs a query when loaded.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
To create a Formula data source, a Document Designer 1 can use the following procedure.
1. In Design, open an existing label template or create a new label template.
2. Expand the Data Sources pane.
3. Click Formula, and click . The Formula Data Source dialog box is displayed.
4. For Data Source Name, enter a name for the label data source.
Note: The name of a label data source can include letters and numbers.
Additionally, the following characters are permitted but cannot begin or end
the name: hyphens, underscores, and periods.
5. Create the formula in the Formula section using the available "Formula Data Source
Operations and Functions" on page 394.
Verify the Formula Syntax
Click Verify Formula to check the syntax of your formula. The results of the check appear in
the Verify Results field.
Note: The Verify Formula function only checks the syntax of your formula. It
does not check the validity of references or data.
Click the Clear Formula button to remove the text from the Formula field.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
You can create a Formula data source to manipulate data obtained via a Prompt in the Form view
and then display the result of the formula in a Variable Text field or a Barcode field in the Label
view. When creating the Formula data source, you select the Data Entry data source associated
with the Prompt as a data ref that you incorporate into the formula. After you have created the
Formula data source, you drag it onto the Variable Text field or Barcode field so that the
Formula data source serves as the data ref for that field. You can use the same Formula data
source as the data ref for multiple fields, such as a barcode and human readable text.
Best Practice
Giving your fields meaningful names makes it easier to work with formulas.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
2A local administrator who creates and configures data services for use by Document Designers who configure Database data
sources and Alternate data sources.
7. If the label template must support on-demand printing, click Add Trigger and configure
at least one trigger 1 that a Data Provider 2 can use to run the data source. Repeat for
additional triggers if needed.
Tip: If you have not yet created the field that should serve as the Trigger
Source 3, you can skip this step and select the trigger when you create the
field.
nTo run the data source when a button is clicked, for Trigger Source select the
name of a Button field and for Trigger Event select onClick.
n To run the data source after submitting data at a prompt, for Trigger Source
select the name of a Prompt field and for Trigger Event select onCommit.
n To run the data source when the form is loaded, for Trigger Source select
/Body and for Trigger Event select onLoad.
8. If the label template must support both on-demand printing and integrations, click Add
Trigger again.
Note: If the label template is not required to support on-demand printing,
then no trigger is needed.
a. For Trigger Source, select Do Not Run.
b. For Trigger Event, select Enqueue.
c. For Trigger Key, enter the name of a data map entry 4 that will manage whether
the data source should be run. It is recommended that this data map entry not be
used for any other purpose. The value of this data map entry does not affect how
it functions as a trigger key.
n When the trigger key exists in the datamap, the data source will not run.
This is appropriate when using the label template with an integration. This
is also appropriate if you need to prevent the data source from running in
some situations when using on-demand printing.
n When the trigger key does not exist in the datamap, the data source is run.
This is appropriate when using the label template for on-demand printing.
Important! For a File Drop integration, if the data map entry
specified for Trigger Key does not exist in the drop file, then the
data source is queried and the first row of data is automatically
returned. This occurs regardless of whether Auto Select First Row
and Auto Select Single Row Result are selected.
1A means of running a data source, form rule, or business rule. Includes a trigger source if interactive (such as a button, a prompt,
or a form) and a trigger event (such as clicking a button, entering text at a prompt, loading a form, or submitting a job). For
example, you can specify a particular button as a trigger source that Data Providers can click to perform a query of a database.
2Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
3A field that is used in conjunction with a trigger event to interactively run a data source, form rule, or business rule. For example, a
button that runs a query when clicked, a prompt that runs a query when submitted, or a form that runs a query when loaded.
4A name (key) and value pair in the data map for a job.
9.
Assigning values for Trigger Priority 1 is necessary only if more than one data source in a
label template includes a trigger with the same trigger source, trigger event, and trigger
key (if any). In that situation, you can assign different values for Trigger Priority for
these otherwise identical triggers, and the data source with the lower value for Trigger
Priority is run first.
10. Click OK.
In the Data Sources pane, the Alternate section now lists the Alternate data source that you
created. You can drag an Alternate data source onto a field in the Label view such as a Variable
Text field to assign the data source as the data ref for that field, or you can enter a data ref
manually. You can create a formula and select the data refs for the Alternate data source for use
in the formula.
Important! If you have not yet created at least one trigger for the data source, you
can do so by using the Triggers section in the Properties pane when you
configure a control, a form, or the Form view of a label template that will serve as
the Trigger Source 2. For more information, see "Adding Controls" on page 153,
"Label Template Properties" on page 273, or "Form Properties" on page 284.
1The order in which data sources, form rules, or business rules that have otherwise identical triggers are run. Trigger values are
compared only if the triggers have the same trigger source, trigger event, and trigger key (if any). The type of data source is
irrelevant. Among data sources, form rules, or business rules with otherwise identical triggers, the data source with the lowest
value for trigger priority is run first.
2A field that is used in conjunction with a trigger event to interactively run a data source, form rule, or business rule. For example, a
button that runs a query when clicked, a prompt that runs a query when submitted, or a form that runs a query when loaded.
Using Scripts
A Script data source can be used to provide data for Variable Text, Text Box, Barcode, and
Variable Image fields.
Field Properties
You can change a field's characteristics such as font type, boldness, size, rotation, and visibility
based upon data included in the data stream, database fields on the label, or other data sources.
Example
A script can cause the font size of a field to change based on the number of
characters supplied for the field.
Math and Logic
A script can be used to perform if-then-else, mathematical, and Boolean logic on data elements
included in the data stream, database fields on the label, or other data sources.
Formula Functions
Use fields, operations, and functions also supported by the Formula data source.
Note: While the JavaScript environment provides some functionality similar to the
Formula data source, the syntax is different.
Considerations
l Because the value of a scripted field can depend on the values of other fields on the label,
you must first resolve the values of the script's dependencies.
l While Design allows different units of measure, Script data sources only support field
positions configured in inches.
l As a safeguard to protect against infinite looping, a script that has not finished running
after 10 seconds is terminated.
l Business rules can be used to perform the same tasks as Script data sources. Also, you
can incorporate scripts into business rules. For more information, see "Implementing
Business Logic" on page 1181.
Built-in Variables
A script includes contains the following standard variables.
l FORMAT: The label template containing all the fields that can be added to a canvas in
Design.
l MAP: The datamap, a repository for all data for use when responding to a print request.
l LOG: A class for logging information to the server log file.
Names to Avoid
There are a few functions and methods that are provided by default in scripts. Therefore, when
creating a script, these names should not be defined in the script.
l FORMAT
l MAP
l LOG
l context (A scripting engine object for internal use.)
l getField
Built-in Classes
The following classes are provided to all scripts. These classes allow you to manipulate the label
template fields and the data map entries, as well as to log information to the main Spectrum log
file.
l FORMAT
l MAP
l LOG
l FieldFormat: The standard field has a single format object that defines the location and
other details of the field on the label. A barcode field can have two formats, one for the
barcode and one for the human readable text.
MAP
The datamap is a repository for all data for use when responding to a print request. Each data
map entry is composed of a name (key) and a value. The datamap is referenced and
updated by all data sources. The datamap is then provided to the script for additional
modification.
The data in the datamap can be provided to the script in two ways.
l Method 1: A variable is added to the script and converted when the script is run. This
method provides the data as read only, and the method is resolved before the script runs.
This is the same method used with the Formula data source.
l Method 2: Retrieve the data from the datamap during the runtime of the script. The
datamap is able to be read and be written to at runtime, so you can change, add, or
remove any data map entry in the datamap.
LOG
The LOG variable is used to log messages to the Spectrum log. By default, the Spectrum log is
located in <SPECTRUM_HOME>\product\logs. This log is managed by using the same
mechanisms that are used for all logging on the SpectrumApplicationServer. The tag for the
logger is scriptLogger.
Script Example
LOG.debug("found key for value 1");
LOG.error(" an error occurred");
LOG.info("applying value");
LOG.warn(" an unexpected value was detected.");
To create a Script data source, a Document Designer 1 can use the following procedure.
1. In Design, open an existing label template or create a new label template.
2. Expand the Data Sources pane.
3. Click Script, and click . The Script Data Source dialog box is displayed.
4. Enter a name for the label data source in the Data Source Name field.
Note: The name of a label data source can include letters and numbers.
Additionally, the following characters are permitted but cannot begin or end
the name: hyphens, underscores, and periods.
5. Enter or paste your script in the Script field.
Enter Fields, Data References, and Database Columns
Use the Fields, Data Ref List, and Database Columns to enter fields and data references in a
script. Using these fields enters each reference with the proper syntax.
Verify the Script
To check the syntax of your script, click Verify Script.
If the syntax is correct, the Verify Results field displays Script verification completed
successfully.
If there are errors in the syntax, the Verify Results field displays the first error encountered.
For example, "Line 2: ReferenceError: x is not defined."
Clear the Script
To remove the current script from the Script field so that you can enter a different script, click
Clear Script.
1Person who creates and designs label templates for use by Data Providers. Also a default role in Spectrum.
Script Reference
There are script methods for accessing and managing label templates, fields, and datamap.
l "Script Methods for Label Templates (Formats)" on page 326
l "Script Methods for Fields" on page 327
l "Script Methods for Field Formats" on page 329
l "Script Methods for Shapes" on page 333
l "Script Methods for Images" on page 334
l "Script Methods for Text Fields" on page 335
l "Script Methods for Character-Level Formatting" on page 337
l "Script Methods for Barcodes" on page 347
l "Script Methods for Accessing the DataMap at Runtime" on page 343
Script Methods for Label Templates (Formats)
The following table describes the methods provided for label templates (formats).
Method Value Description
findField(String) Field Retrieve a field by using its fully-qualified name.
object Example
var field = FORMAT.findField
("/Body/Text0001");
field.setVisible=false;
findFields(String) A list Find a list of fields by using a set of criteria.
of field Operation Description
objects && Logical AND
|| Logical OR
!= Not equal
== Equal
~= Equal, ignoring case
Example
var fields = FORMAT.findFields
(type=='text');
var count = fields.size;
Example Criteria
(name=='t1' || type=='label') &&
visible!='false')
The following are the basic methods provided for all fields. Each type of field may have
additional methods provided.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set or move configure a
value for the property.
The following are basic methods provided for all field formats. Some field formats may have
additional methods.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set or move configure a
value for the property.
Method Value Description
getFormatType() String The type of the format.
Example
var type = fieldFormat.getFormatType
();
getTop() Int in The location of the top coordinate in 1/1000 of an inch at
1/1000 0 degrees rotation.
inch Example
var top = fieldFormat.getTop();
Return
Method Description Example
value
getFormatType() or "lineFormat" The type of field var type =
formatType line.type;
getThickness() or 1/1000 inch Retrieves the thickness of the line var t =
thickness line.thickness ;
setThickness(int) or n/a Sets the thickness of the line in 1/1000 of line.thickness
thickness an inch increments. = 500;
Circle Field
Method Return value Description Example
getType() or type "circle" The type of field var type = Circle.type;
Circle FieldFormat
Method Return value Description Example
getFormatType() or "circleFormat" The type of field var type = circle.type;
formatType
getThickness() or 1/1000 inch Retrieves the var t = circle.thickness ;
thickness thickness of the line
setThickness(int) or n/a Sets the thickness of circle.thickness = 500;
thickness the line in 1/1000 of
an inch increments.
isApplyBackgroundColor Boolean Retrieves the value var bc =
() specifying whether circle.applyBackgroundColor;
or applyBackgroundColor the background color
is applied or not.
setApplyBackgroundColor n/a Sets whether the circle.applyBackgroundColor
(boolean) background color = true;
or applyBackgroundColor should be applied or
not.
Script Methods for Images
Image Field
Return
Method Description Example
value
getType() or type "image" The type of the field var type = Image.type;
isMaintainAspectRatio() Boolean Retrieves the value for var ar =
or maintainAspectRatio specifying whether the image Image.maintainAspectRatio;
should maintain the aspect ratio
setMaintainAspectRatio none Sets whether to maintain aspect Image.maintainAspectRatio
(boolean) ratio or not. = false;
The following methods are provided for performing character-level formatting in fixed text and
variable text fields when using Script data sources. These methods are not supported in business
rules.
Note: Character-level formatting is supported for TrueType fonts only. Also,
you cannot use a Character-Level format source to format the human readable text
associated with a barcode or to format fields in the data entry form of a label
template.
Except where noted otherwise, each method returns a reference to the text field
being modified. This allows you to use a chaining approach. In this example, the
first eight characters are formatted with a strikethrough effect, an italic effect, and
gray text color.
var myField = getField("/Body/Text0001");
myField.addEffect("STRIKETHROUGH",0,7).addEffect("ITALIC",0,7)
.addStyle("FOREGROUND","#CCCCCC",0,7);
Tip: For more examples, see "Script Examples: Individually Format Characters
within a Field" on page 388.
Character Selection by Pattern
You can use literal text or use a regular expression as a pattern to specify text to which a style or
effect should be applied.
Important! Patterns for character-level formatting and for values returned from
data map entries are governed by the Java syntax for regular expressions.
Escape sequences are required for the following characters. Precede the character
with a backslash.
<>()[]{}|^-=+*$!?.\
By default, literal text within a pattern is case sensitive. You can make a pattern
case insensitive by beginning it with the special construct (?i). If you configure
both patterns and ranges in a Character-Level format source, ranges are resolved
before patterns.
For more information about Java syntax for regular expressions, see The Java
Tutorials: Regular Expressions on the Oracle website.
Methods Description
addEffect Apply the specified effect to characters in the text field that are specified
(effect, pattern) by the pattern.
Example
var field1=getField("/Body/Text0001");
field1.addEffect("BOLD","(?i)(Peanuts)");
field1.addEffect("BOLD","Warning");
field1.addEffect("ITALIC","Warning");
addStyle(style, Apply the specified style and value to characters in the text field that are
value, pattern) specified by the pattern.
Example
var field1=getField("/Body/Text0001");
field1.addStyle("FONT","Arial","Note");
getEffectsList Create a list of effects to be applied. You can add and remove items from
() the list by using add and delete methods for lists. Apply all effects in the
add(effect) list to characters in the text field specified by the pattern.
delete(effect) Example
addEffectMulti var field1=getField("/Body/Text0001");
(effects_list, var myList=field1.getEffectsList();
pattern)
myList.add("BOLD");
myList.add("ITALIC");
field1.addEffectMulti(myList,"Note");
Methods Description
getStyleMap() Create a map of effects and of styles and associated values. You can add
add(style,value) and remove items from the map by using add and delete methods for
delete(style) maps. For effects, specify an empty string as the value. Apply all of the
addStyleMulti styles and effects in the map to characters in the text field specified by the
(style_map, pattern.
pattern) Example
var field1=getField("/Body/Text0001");
var myStyleMap=field1.getStyleMap();
myStyleMap.add("FONT","Arial");
myStyleMap.add("SIZE","14");
myStyleMap.add("BOLD","");
field1.addStyleMulti(myStyleMap,"Note");
Character Selection by Range
You can use a numeric range of character positions within a text field to specify text to which a
style or effect should be applied.
Methods Description
addEffect Apply the specified effect to the text field beginning at the position
(effect, start, end) specified by start through the position specified by end.
Example
var field1=getField("/Body/Text0001");
field1.addEffect("BOLD",0,7);
addStyle(style, Apply the specified style and value to the text field beginning at the
value, start, end) position specified by start through the position specified by end.
Example
var field1=getField("/Body/Text0001");
field1.addStyle("SIZE","14",0,7);
getEffectsList Create a list of effects to be applied. You can add and remove items from
() the list by using add and delete methods for lists. Apply all effects in the
add(effect) list to the text field beginning at the position specified by start through the
delete(effect) position specified by end.
addEffectMulti Example
(effects_list, var field1=getField("/Body/Text0001");
start, end) var myList=field1.getEffectsList();
myList.add("ITALIC");
myList.add("STRIKETHROUGH");
field1.addEffectMulti(myList,0,7);
Methods Description
getStyleMap() Create a map of effects and of styles and associated values. You can add
add(style,value) and remove items from the map by using add and delete methods for
delete(style) maps. For effects, specify an empty string as the value. Apply all of the
addStyleMulti styles and effects to the text field beginning at the position specified by
(style_map, start, start through the position specified by end.
end) Example
var field1=getField("/Body/Text0001");
var myStyleMap=field1.getStyleMap();
myStyleMap.add("FONT","Arial");
myStyleMap.add("SIZE","14");
myStyleMap.add("BOLD","");
field1.addStyleMulti(myStyleMap,0,7);
Clearing Character-Level Formatting
You can remove character-level formatting from a text field.
Tip: To remove a style or an effect from a style map or an effects list, use delete
(style) or delete(effect).
Methods Description
clearStyles() Remove all styles and effects from the text field.
Example
var field1=getField("/Body/Text0001");
...
field1.clearStyles();
removeEffect(effect) Remove all occurrences of the specified effect from the text field.
Example
var field1=getField("/Body/Text0001");
field1.addEffect("ITALIC","Note");
...
field1.removeEffect("ITALIC");
removeStyle(style) Remove all occurrences of the specified style from the text field.
Example
var field1=getField("/Body/Text0001");
field1.addStyle("SIZE","14","Note");
...
field1.removeStyle("SIZE");
Arguments
The arguments used in the preceding methods include effects, styles, and other arguments.
Effects
Effects are string values and are not case sensitive.
Note: If multiple effects (such as BOLD and ITALIC) are applied to a the same
character, all of the effects are used.
Effect Description
BOLD Apply a bold, italic, strikethrough, subscript, superscript, or
ITALIC underline formatting effect to the text.
STRIKETHROUGH
SUBSCRIPT
SUPERSCRIPT
UNDERLINE
Styles and Values
Styles and values are string values. Styles are not case sensitive.
Note: If more than one value for a style (such as 12 and 14 for SIZE) is applied to
the same character, the last value applied is used.
"GRAY"
"#CCCCCC"
FONT Apply the specified font The name of the font.
to the text. Example
"Arial"
SIZE Apply the specified font The font size in points. Note that this is a
size to the text. string value.
Example
"12"
Other Arguments
The following is additional detail about the other arguments described in the methods for
character-level formatting. The argument names shown here are merely placeholders for
whatever variables you define.
The data available or generated when LoftwareSpectrum responds to a print request is stored
in a datamap. Each data map entry consists of a name (also called a key) and a value. You can use
a Script data source to access and alter data in the datamap after a print request is submitted but
before printing occurs. By using a Script data source to access the datamap, you can check for
the existence of a data map entry by using its fully-qualified name, retrieve the value of a data
map entry, change the value of a data map entry, and add new data map entries.
Note: The datamap can also be accessed and modified by using a business rule. If
a business rule and a Script data source both modify the datamap, the Script data
source is evaluated last.
You can access and modify data in the datamap by using the following methods:
Note: In the following methods, Name must be the fully-qualified name of a data
map entry, such as the name of a field or a data source. NewValue must be a text
string.
About the syntax documentation
Vertical bars indicate that you must choose one of the options shown. Italicized items can be
named or specified by you.
Return
Method Description
Value
keyExists(Name) Boolean Determines whether the datamap contains is an entry for the
specified name.
l true: A data map entry with this name exists.
Example
var dataMapEntryExists = MAP.keyExists
("/Body/Text0001");
putValue(Name, NewValue)Adds a data map entry or updates the data map entry associated
with the specified name by changing the value of that data map
entry to the new value.
Example
MAP.putValue("/Body/Text0001", "New Field
Value");
getValue(Name) Node Retrieves the value of the specified data map entry interpreted
as a node value. Null is returned if the name does not exist.
Example
var nodeVal = MAP.getValue
("/Body/Text0001");
getNodeType() String If a data map entry has been retrieved by using getValue, this
method retrieves the data type of the data map entry.
Example
var nodeVal = MAP.getValue
("/Body/Text0001");
nodeVal.getNodeType();
getStringValue String Retrieves the value of the specified data map entry interpreted
(Name) as a string value. Null is returned if the name does not exist.
Example
var stringVal = MAP.getStringValue
("/Body/Text0001");
Return
Method Description
Value
getIntegerValue Integer Retrieves the value of the specified data map entry interpreted
(Name) as an integer value. Null is returned if the name does not exist.
Example
var integerVal = MAP.getIntegerValue
("/Body/Text0001");
getDoubleValue Double Retrieves the value of the specified data map entry interpreted
(Name) as a double-length integer value. Null is returned if the name
does not exist.
Example
var doubleVal = MAP.getDoubleValue
("/Body/Text0001");
getDateValue Date Retrieves the value of the specified data map entry interpreted
(Name) as a date value. Null is returned if the name does not exist.
This method is useful for taking a binary Date value from a
Database data source, and converting it to a human readable
date value. This method should only be called using a data
source name parameter that has the Date data type and has data
values that are binary.
By default, the returned date is in the following format:
EEE MMM dd hh:mm:ss z yyyy
The following is an example of a date using this format:
Mon Mar 26 00:00:00 EDT 2012
For more information, see "Date/Time Data Source Formats"
on page 391.
Example
var dateVal = MAP.getDateValue
("/Body/Text0001");
getBinaryValue Byte Retrieves the value of the specified data map entry interpreted
(Name) array as a byte array value. Null is returned if the name does not exist.
Example
var binaryVal = MAP.getBinaryValue
("/Body/Text0001");
Return
Method Description
Value
getBooleanValue Boolean Retrieves the value of the specified data map entry interpreted
(Name) as a Boolean value. Null is returned if the name does not exist.
Example
var booleanVal = MAP.getBooleanValue
("/Body/Text0001");
setValue If a data map entry has been retrieved by using getValue, this
(NewValue) method changes the value of the data map entry to the specified
value.
Example
var nodeVal = MAP.getValue
("/Body/Text0001");
nodeVal.setValue("New Field Value");
The following are the barcode symbologies supported by LoftwareSpectrum, linked to the
script methods available for each symbology.
Common Methods
EAN/UPC
Barcodes using these symbologies are typically used on items to be scanned at point-of-sale.
Symbology
EAN-8
EAN-13
UPC-A
UPC-E
Composite
Composite barcodes have a 2D portion followed by a linear portion. In the barcode data, the 2D
portion appears first and is followed by a composite delimiter (|) and then the linear portion.
Within a Formula data source, the composite delimiter can be represented by the COMPDELIM
() function.
In addition to the Max Chars property, Spectrum also displays 2D Max Chars and Linear
Max Chars for composite barcodes objects in Design. Otherwise, a composite barcode uses
the same symbology as the related type of linear barcode.
Symbology
EAN-8 Composite
EAN-13 Composite
GS1 DataBar Composite
GS1-128 Composite
UPC-A Composite
UPC-E Composite
Common Script Methods for Barcodes
The following methods are common to all barcode symbologies. For symbology-specific
methods, see "Script Methods for Barcodes" on page 347.
Barcode Field
Method Return value or type Description
getType() "barcode" Retrieve the type of field.
getBarcodeFormatProxy()FieldFormat Retrieve the barcode field format.
getFormatProxy() FieldFormat Retrieve the human readable field format.
getMaxLength() int Retrieve the maximum number of characters.
setMaxLength(int) Set the maximum number of characters.
getPadding() String Retrieve the padding style.
setPadding(String) Set the padding style to use. The following
values are accepted:
n Leading zeros
n Leading spaces
n Trailing spaces
n Center with spaces
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Code 39 Full ASCII is also known as Code 39 Extended (Ext).
Methods Description Values
getBarHeight() The height of the bars in the barcode. Thousandths
setBarHeight(long) of an inch
(mil)
getCheckDigit() Add an optional check digit to the barcode. None
setCheckDigit(String) The listed check digits are optional forms of Mod 43
getUserGeneratedCheckDigit the selected symbology (For Example: Code User Mod
() 39 or Code 39 with check). 43
Special purpose check digits can be added to
the barcode using the Formula data source.
Note: When a form that includes
a check digit is used, the Data
Provider 1 is not alerted if the
check digit fails.
getDataIdentifier() Data entered in this field will be encoded in
setDataIdentifier(String) the barcode but will not print in the human
readable text field for the barcode.
Data Identifiers are used to help the scanner
identify the field.
For Example
For an AIAG label, a barcode
with a data identifier of P
contains a part number, a data
identifier of Q signifies a
quantity field and a data
identifier of S signifies a serial
number field.
getHumanReadable() Whether a text representation of the barcode None
setHumanReadable(String) is printed. freeFloating
The human readable text can be positioned
anywhere on the label (free floating).
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Code 93 Full ASCII is also known as Code 93 Extended (Ext).
Methods Description Values
getBarHeight() The height of the bars in the barcode. Thousandths
setBarHeight(long) of an inch
(mil)
getDataIdentifier() Data entered in this field will be encoded in the barcode
setDataIdentifier but will not print in the human readable text field for the
(String) barcode.
Data Identifiers are used to help the scanner identify the
field.
For Example
For an AIAG label, a barcode with a data
identifier of P contains a part number, a
data identifier of Q signifies a quantity field
and a data identifier of S signifies a serial
number field.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Note: For GS1-128 and GS1-128 Composite barcodes, the first two digits in the
data provided are assumed to be the application identifier. Optionally, these digits
may be enclosed in parentheses.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Methods Description Values
getXdim() The width of the barcode cell (module). The Thousandths of an
setXdim(float) range of values available varies with the inch (mil)
Document DPI of the label template.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Methods Description Values
getCellWidth() The width of the barcode cell (module). Thousandths of an inch
setCellWidth(int) The range of values available varies with (mil)
the Document DPI of the label template.
getSymbolSize() The number of rows and columns in the Auto
setSymbolSize symbol. For more information, see the Square Form: 10x10 to
(String) "Symbol Size" section following this table. 144x144
Note: This value limits Max Rectangular Form: 8x18 to
Chars. 16x48
data ref points, and you cannot explicitly define the data type in Spectrum. If the data can be
alphanumeric or binary, you should reduce the value of Max Chars to the limit shown in the
following table to ensure that data incorporated into the symbol is not unexpectedly truncated.
Note: If you select Auto for the Symbol Size, the value of Max Chars is not
changed automatically. However, with Auto selected, you can configure Max Chars
to any value up to 3116, which is the number of numeric characters that can be
represented when using a Symbol Size of 144x144.
Square Form
Rectangular Form
The following properties are specific to this barcode symbology. Additionally, barcode fields
using this symbology have properties that are common to all barcode fields.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Methods Description Values
getBarHeight() The height of the bars in the barcode. Thousandths of
setBarHeight(long) an inch (mil)
getCheckDigit() Add an optional check digit to the None
setCheckDigit(String) barcode. Mod 10
getUserGeneratedCheckDigit The listed check digits are optional User Mod 10
() forms of the selected symbology. (Interleaved 2
Special purpose check digits can be of 5 only)
added to the barcode using the
Formula data source.
Note: Specifying a value
other than None
decreases Max Chars to
allow a character for the
check digit, which is not
counted toward the value
of Max Chars.
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Methods Description Values
getCurrentSymbol When used with the structured append format, the position of 0-8
() the symbol in a set.
setCurrentSymbol
(int)
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Tip: If the amount of data in a barcode exceeds the usable space, adjust the
Columns, the Security Level, or both.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Methods Description Values
getCellWidth() The width of the barcode cell Thousandths of an inch
setCellWidth(int) (module). The range of values (mil)
available varies with the
Document DPI of the label
template.
getDataEncodingMode() The type of information l Byte: 8-bit bytes
Alphanumeric
characters and the
symbols $, %, *, +,
-, /, :, period,
comma, and space.
l Numeric: Numeric
digits
getErrorCorrection() The level of error checking l L: Approximately
15% error
correction.
l Q: Approximately
25% error
correction.
l H: Approximately
30% error
correction.
For more information about encoding QR Codes, see the QR Code entry listed in "External
Links" on page 1645.
UPC-A, UPC-E, and Composite Script Methods
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
Note: If using UPC-E, provide data on which zero suppression has already been
performed.
getXdim() The width of the module (narrow bar) of the barcode. Thousandths
setXdim(float) The range of values available varies with the Document of an inch
DPI of the label template. (mil)
USPS Intelligent Mail Methods
United States Postal Service (USPS) Intelligent Mail is a suite of barcode symbologies.
l For Intelligent Mail barcodes (IMb) for mailpieces (letters, cards, and flats), use the
USPS Intelligent Mail symbology.
l For Intelligent Mail Tray barcodes, use either Code 128 symbology with Start Code C or
Interleaved 2 of 5 symbology.
l For Intelligent Mail Container barcodes, use the GS1-128 symbology with Start Code C or
B.
l For Intelligent Mail Package barcodes (IMpb), use the GS1-128 symbology with Start
Code C.
The USPS Intelligent Mail barcode for mailpieces is a 4-state barcode that consists of 65 bars
that can encode up to 31 digits. The following information can be included:
l Barcode Identifier
l Service Type Identifier (STID)
l Mailer Identifier (MID)
l Serial Number
The USPS Intelligent Mail symbology in Spectrum supports all formats for Intelligent Mail
barcodes for mailpieces. Those formats include using a 6-digit Mailer Identifier, a 9-digit Mailer
Identifier, or the Origin IMb Tracing Intelligent Mail Barcode Format.
For more information about encoding USPS Intelligent Mail barcodes, see the USPS entry listed
in "External Links" on page 1645.
The following script methods are specific to this barcode symbology. Additionally, you can use
the "Common Script Methods for Barcodes" on page 350.
Tip: Script methods with names beginning with get or is retrieve the current value
for a property. Script methods with names beginning with set configure a value for
the property.
You can insert Lower ASCII characters into a script by using an escape sequence around the
hexadecimal value of the ASCII character. In this context, lower ASCII is the first 31 characters
of the ASCII character set.
Note: Loftware converts Upper ASCII characters, so they can be included in a
script without the escape sequence.
l Begin the escape sequence: #x
l End the escape sequence: ;
Script Examples
The following are examples of ways that you can use Script data sources.
l "Script Examples: Examine and Modify Data to be Used at Print Time" on page 375
l "Script Examples: Move Objects" on page 380
l "Script Examples: Search for Fields" on page 383
l "Script Examples: Change Rotation" on page 385
l "Script Examples: Turn Printing of Fields On or Off" on page 386
l "Script Examples: Calculate the Check Digit" on page 386
l "Script Examples: Change the Format of a Date" on page 387
l "Script Examples: Individually Format Characters within a Field" on page 388
Script Examples: Examine and Modify Data to be Used at Print Time
At print time, the data used for a field is usually pulled from the datamap (MAP). This is done
by getting the name (key) for the data map entry from the field (getFullyQualifiedKey) and then
doing a lookup in the datamap with this key to get the value. If the key does not exist, then the
default value is used. If you configure the data for the field explicitly by calling setData, then
what is configured will be used and the datamap and default data will not be checked.
Refer to the following sample fields and data for the examples that follow.
FORMAT
Field Name FQN Default data
Field1 Text0001 /Body/Text0001 Unset
Field2 Text0002 /Body/Text0002 "text2DefaultData"
Field3 Text0003 /groupedField Unset
Field4 Text0004 /groupedField Unset
Field5 Text0005 /groupedField Unset
MAP
Name (Key) Value
/Body/Text0001 "value1"
/groupedField" "value2"
Examine the Field Data Value to Print
The value to be used at print time for a field is based on conditions.
Field data has not been set and there is an entry in the datamap with the fully-qualified name of
the field will result in the value for the entry in the map to be used.
var field1 = getField("/Body/Text0001");
var dataToBePrintedForField1 =
field1.getPrintingValue(MAP);
Field data has not been set and no entry exists in the map for the fully-qualified name will result
in the default value for the field to be used.
var field1 = getField("/Body/Text0002");
var dataToBePrintedForField2 =
field1.getPrintingValue(MAP);
field1.setData("explicitValue");
var isSetNow = field1.isDataSet(); -- isSetNow will
return true, because the script data has been set.
field1.clearData()
var isSetAfterClear = field1.isDataSet(); --
isSetAfterClear will return false, because the script
data has been cleared.
field1.setData(null);
var isSetWithNull = field1.isDataSet(); -- isSetWithNull
will return true, because the script data has been set.
Override the field data for multiple fields with the same data reference
This example expects that there are a few fields on the label that have the same fully qualified
name. Refer to Text0003, Text0004, Text0005 in the example data above.
var field3 = getField("/Body/Text0003");
var fqn = field3.getFullyQualifiedName(); -- the FQN in
this case will be "/groupedField"
MAP.setValueForKey(fqn,"myglobalvalue");
var dataToBePrintedForField3 =
field3.getPrintingValue(MAP);
var dataToBePrintedForField4 =
field4.getPrintingValue(MAP);
var dataToBePrintedForField5 =
field5.getPrintingValue(MAP);
var dataToBePrintedForField2 =
field2.getPrintingValue(MAP);
l moveGroupFromTopLeft
Take care when using these calls where the human readable is not in close proximity to the
barcode as the call may have unintended consequences.
The standard move and rotate commands shown in the first examples will only move and rotate
the barcode itself.
Barcodes can only be rotated at 0, 90, 180, and 270 degrees. A barcode's human readable fields
can be rotated all 360 degrees.
Move a Field by its Center Position
The following example moves a box from its current position to centered at 3 inch by 3 inch on
the label.
var box = getField("/Body/Box0001");
box.moveFromCenter(3000,3000);
To move the box relative to its current position by some distance use the following:
var box = getField("/Body/Box0001");
box.moveFromCenter
(box.centerX+500,box.centerY+250);
This moves the box .5 inch to the right and .25 inch lower on the label from its current position.
Move and Rotate a Field by its Center Position
The following example moves a box from its current position to centered at 3 inch by 3 inch on
the label, and then rotates it to the 90 degree position. If it is already at 90 degrees then no
rotation will be applied.
var box = getField("/Body/Box0001");
box.moveFromCenter(3000,3000,90);
If you want to move it relative to its current position by some delta then do the following:
var box = getField("/Body/Box0001");
box.moveFromTopLeft
(box.rotatedTop+250,box.rotatedLeft+500);
This moves the box a half an inch to the right and a inch down the label from its current
position.
Note: The top/left coordinates are based on the bounding rectangle of the field.
This means that if the field is rotated at an "off-axis position (NOT one of 0, 90,
180 or 270) then the top/left position will be a point that is not on the object, but
a projection of the topmost and leftmost points of the object. For example,
consider an object rotated at 30 degrees where the leftmost corner is the
bottom/left corner and the topmost corner is the top/left corner.
Move and Rotate a Field by its Top/Left Corner Position
The following example moves a box from its current position to a position where its top left
coordinate will be at 3 by 3 on the label before rotation, and then it is rotated 90 degrees.
Unless the box is a square, the final top/left will not be at 3 by 3.
var bar1 = getField("/Body/Box0001");
bar1.moveFromTopLeft(3000,3000);
bar1.rotation=90;
To make the final top/left position of the box be 3 x 3, apply the rotation first.
var bar1 = getField("/Body/Box0001");
bar1.rotation=90;
bar1.moveFromTopLeft(3000,3000);
If you want to move it relative to its current position by some delta then do the following:
var bc = getField("/Body/Barcode0000")
bc.moveGroupFromCenter
(bc.groupCenterX+250,bc.groupCenterY+500);
var bc = getField("/Body/Barcode0000")
bc.moveGroupFromTopLeft(3000,3000);
If you want to move it relative to its current position by some delta then do the following:
var bc = getField("/Body/Barcode0000")
bc.moveGroupFromTopLeft
(bc.groupTop+250,bc.groupLeft+500);
or
bc.rotateGroup(90);
Case Sensitive
var barcode = FORMAT.findFields("type=='barcode'");
println("*** Barcode is "+barcode[0].name);
Case Insensitive
var barcode = FORMAT.findFields("type~='Barcode'");
println("***2 Barcode is "+barcode[0].name);
barcode = FORMAT.findFields("type~='BARCODE'");
println("***3 Barcode is "+barcode[0].name);
barcode = FORMAT.findFields("type~='BaRcOdE'");
println("***3 Barcode is "+barcode[0].name);
Search for fields of a specific type and name and make them invisible
var fields = FORMAT.findFields("(type=='label' ||
name=='text3') && visible=='true');
for(i=0;i<fields.length;i++){
var f = fields[i];
f.visible=false;
}";
Find all fields where the data has been set by calling setData()
var setFields = FORMAT.findFields("dataSet == 'true'");
var notSetFields = FORMAT.findFields("dataSet !=
'true'");
The variable FORMAT is available in the script. This is the top level object containing all the
fields in the label template. There is a field called rotation that allows you to change the rotation
of the label.
Note: The rotation needs to be set in 90-degree increments.
Script Example
var rotation=MAP.getStringValue
("/Body/Prompt0001");
if (rotation%90 == 0)
{
FORMAT.rotation=rotation;
}
This can be done either as a Formula or as a Label script. The example below shows it done as a
Label script. Map values are pulled to perform the calculation and then the field data member is
set at the end. This assumes that no other data source will be setting the data on this field at run
time.
Note: When a form that includes a check digit is used, the Data Provider 1 is not
alerted if the check digit fails.
To write this as a formula, remove the "var result" from the top, as it is already provided, and
return result at the bottom instead of modifying the field.
var result;
var input = new String;
var cf = ${/Body/Collection_Facility};
var cy = ${/Body/Collection_Year};
var sn = ${/Body/Seq_No};
input = cf +cy + sn;
println("cf ="+cf+" cy = "+cy+" sn = "+sn+" input =
"+input);
var ch,sum=0,charValue, isDigit, isUpperAlpha, count;
var
CharTable="0123456789ABCDEFGHIJKLMNOPQRS
TUVWXYZ*";
1Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
result = CharTable[charValue];
MAP. setValueForKey ("/Body/Check_
Character,result);
You can use a Script data source to convert a date value obtained from a database and processed
by LoftwareSpectrum into a human readable format suitable for printing.
For example, an Oracle database table can have a column of data type DATE. In Oracle SQLPlus
or SQL Developer, the values in this table column are displayed in a format of dd-MMM-yy.
However, when the table is used as a Database data source in LoftwareSpectrum, Spectrum
receives the date value in a special milliseconds format. By default, the Database data source
would return a value such as 13849236000000 at print time instead of a human readable date.
You can use a Script data source with MAP functions to convert the date from milliseconds
format to a human readable format appropriate for printing. In this example, the Database data
source column /DS_0001/DATE_COL is passed as a parameter to the MAP.getDateValue()
method. This method converts the milliseconds date value, such as 13849236000000, obtained
from the Database data source to a human readable format, such as Wed Nov 20 00:00:00 EST
2408.
Script Example
// Use the MAP function to change the date value from
milliseconds format to a human readable date format.
var dateVal = MAP.getDateValue("/DS_0001/DATE_
COL");
The following are some examples of configuring character-level formatting by using a Script data
source. Character-level formatting methods are not supported in business rules.
Important! Patterns for character-level formatting and for values returned from
data map entries are governed by the Java syntax for regular expressions.
Escape sequences are required for the following characters. Precede the character
with a backslash.
<>()[]{}|^-=+*$!?.\
By default, literal text within a pattern is case sensitive. You can make a pattern
case insensitive by beginning it with the special construct (?i). If you configure
both patterns and ranges in a Character-Level format source, ranges are resolved
before patterns.
For more information about Java syntax for regular expressions, see The Java
Tutorials: Regular Expressions on the Oracle website.
Example 1: Make all instances of an allergen name bold (case sensitivity)
You want all instances of the allergen name Peanuts within a text field to be bold,
regardless of case. You can accomplish this by using the following script in a Script
data source:
var field1=getField("/Body/Text0001");
field1.addEffect("BOLD","(?i)(peanuts)");
You want to format the first character in a field as bold, 16-point Letter Gothic
text. You can accomplish this by using the following script in a Script data source:
var field1=getField("/Body/Text0001");
var myStyleMap=field1.getStyleMap();
myStyleMap.add("FONT","Letter Gothic");
myStyleMap.add("SIZE","16");
myStyleMap.add("BOLD","");
field1.addStyleMulti(myStyleMap,0,0);
Tip: If you are associating a Date/Time data source with a variable text field,
ensure that the value of Max Chars (controlled by Chars Per Line and # Lines)
for the variable text field is great enough to accommodate the length of the
resulting data.
You can also include static text by enclosing it in single quotation marks. You can include
symbols such as a colon, slash, or hyphen without quotation marks.
In general, entering a single placeholder character produces a value including the minimum
number of characters required. Using repeated placeholder characters typically specifies the
minimum number of characters to use and may produce leading zeros in numeric values.
Tip: If you require a placeholder for the Julian day, Julian date, or ordinal date, use
D, which produces the day number of the year.
Number of
Placeholder Description placeholders
to use
a Period of day, such as AM or PM 1 or 2
D Day of year 1 or 3
d Day of month 1 or 2
E Day of week 1, 3, or 4
Note: Use one or three characters to produce a
three-character day abbreviation, or four
characters to produce the full name of the day.
F Day of week in month. For example, if referring to the second 1
Thursday in a month, the F placeholder would produce a
value of 2.
G Era, such as A.D. or B.C. 1
H Hour of day using 24-hour format (0-23) 1 or 2
h Hour of day using 12-hour format (1-12) 1 or 2
K Hour of day using 12-hour format(0-11) 1 or 2
k Hour of day using 24-hour format (1-24) 1 or 2
M Month of year 1, 2, 3, or 4
Note: Use one or two characters to produce the
month number, three characters to produce a
three-character abbreviation, or four characters
to produce the full name of the month.
m Minute of hour 1 or 2
S Millisecond of second 1 or 3
s Second of minute 1 or 2
u Day of week using numeric format (1-7), such as 1 1
(representing Monday).
W Week of month 1
w Week of year 1 or 2
Number of
Placeholder Description placeholders
to use
X ISO 8601 time zone, such as -04, -0400, or -04:00. 1, 2, or 3
Note: Use one character to produce a two-digit
time (hours only), two characters to produce a
four-digit time with no colon, or three
characters to produce a four-digit time including
a colon.
y Year 1, 2, or 4
Note: For a two-digit year, use two characters.
Otherwise, a four-digit year is displayed.
Z RFC 822 time zone, such as -0400. 1 or 5
z General time zone, such as Eastern Standard Time or EST. 1, 3, or 4
Note: Use one or three characters to produce a
three-character abbreviation, or four characters
to produce the full name of the time zone.
The following tables describe the operations and functions that you can use when creating
formulas.
In this table, input refers to a field name, data source, or data service parameter.
Tip: For string concatenation, use the + operator. Note that & is not a valid
concatenation operator.
l Occurrence: 1
l Direction: 0 (left
to right)
Length Returns the number of < {/Body/Text6}.length
characters in the string. input
>.length If Text6=A1BC2, then
the result is 5.
Property Description
Data Source Name The identifier assigned to the Inc/Dec data source.
Data Ref The data source used to populate a field with a value.
Definitions
Important: If the data source is populated from a Prompt, you should ensure
that the Max Length field of the data source and the Max Chars field of the
Prompt contain the same value. The Max Chars field is automatically
calculated based on the Chars Per Line and # Lines fields.
Tip: For these types of form rules, within each form rule you can create multiple
form rule entries. Each form rule entry allows you to configure one data map
entry 1 or data ref2.
Submitting Jobs
Rule Type Purpose Properties
Job Request Submit a job4 request or job preview request Job Request
to the SpectrumApplicationServer.
Note: This type of form rule is
available only in applications.
1A name (key) and value pair in the data map for a job.
2Data reference. The data source used to populate a field with a value. An Input Data Ref is the data source from which a Prompt
field obtains data.
3Data reference. The data source used to populate a field with a value. An Input Data Ref is the data source from which a Prompt
field obtains data.
4What is submitted for processing. A job is separated into print jobs and print job details based on the processing rules. A job
defines which processes to use.
Note: Each form rule must have a name by which it is identified, and this name
must be unique within the form in which it appears. This name can be modified in
the Data Ref field of the form rule and is displayed in the Form Rules pane after
the rule has been created. For form rules that have form rule entries, this name is
for the entire rule.
The following are the properties for a Close Application form rule.
Value Description
Submit The application submits the workflow progression to the server.
Cancel The application cancels the current progression and remains in the
current step.
Note: Each form rule must have a name by which it is identified, and this name
must be unique within the form in which it appears. This name can be modified in
the Data Ref field of the form rule and is displayed in the Form Rules pane after
the rule has been created. For form rules that have form rule entries, this name is
for the entire rule.
The following are the properties for an Electronic Signature form rule entry.
Important! Content in a form rule is case sensitive.
Value Description
Username Data Ref The username of the user.
Password Data Ref The password of the user generating the signature.
Domain Data Ref The domain of the user.
Action Data Ref The action being performed for this signature.
Entity Data Ref The fully qualified name to the object1 being signed.
Entity Type Data Ref The type of object being signed.
Workflow Instance Data The workflow instance ID.
Ref
Comments Data Ref The comments to attach to the signature.
Submit Status Whether the signature will have a Sign or Reject status.
Target Token Data Ref Where the token from a successful signature will be added to the
data map.
1An item in Spectrum such as a role, group, user, business rule, application, workflow template, data service, form, image,
integration, job, label template, layout, device, device group, process, reusable object, facility, Remote Site, Spectrum Application
Server, or server process.
Note: Each form rule must have a name by which it is identified, and this name
must be unique within the form in which it appears. This name can be modified in
the Data Ref field of the form rule and is displayed in the Form Rules pane after
the rule has been created. For form rules that have form rule entries, this name is
for the entire rule.
The following are the properties for a FileSelector form rule.
Export Export the contents of the Data Ref to the selected file.
Data Ref
A reference to the location in the datamap to import data to or to export data from.
File Filter
The type or types of files permitted to display in the dialog box for selection. If allowing
multiple file types, use a semicolon as a delimiter. If a file type is not specified, all file types are
permitted.
Example
*.xml;*.csv;*.txt;
1Data reference. The data source used to populate a field with a value. An Input Data Ref is the data source from which a Prompt
field obtains data.
Value Description
Text The file is XML,CSV, or TXT format.
Other The file is a PDF or an image such as PNG, GIF, JPG, BMP, or
PCX.
Character Encoding
The type of encoding to use when converting the file to text. The default character encoding is
UTF-8.
Note: This property is displayed only if Import is selected forOperation and
Text is selected for Type.
Post Selection Rule or Pre Selection Rule
If selected, you can configure a trigger to run a form rule 1 or a business rule 2 after (for
import) or before(for export) a Data Provider 3 selects a file to import or export.
For Trigger Type, select whether to run a Form Rule or a Business Rule after a file is
selected. If running a form rule, select the name of the form rule. If running a business rule,
select the business rule and enter an event name that is specified by the business rule.
1An entry or a collection of entries that provides a form or an application with enhanced functionality. A form rule can add or change
data or print parameters, submit a print request, validate user credentials, open a label template, form, layout, image, reusable
object, or application in Design, open a URL in a web browser, or close an application. Form rules are similar to business rules, but
simpler to create. Form rules are created on the Design page and are specific to a particular application or form. Some form rules
are available only in applications.
2A collection of component sets or business rule components that can be used to incorporate logic or to add, change, or remove
data or print parameters after a print request is submitted but before printing occurs. Business rules are similar to form rules, but
provide more robust functionality. Business rules are created on the Process Design page and can be designed using the
Configurator or programmed using XML.
3Person or process that enters data into a form or other data entry view for a label that was configured by a Document Designer. A
user acting as a Data Provider requires the Document Printer role or equivalent permissions.
Note: Each form rule must have a name by which it is identified, and this name
must be unique within the form in which it appears. This name can be modified in
the Data Ref field of the form rule and is displayed in the Form Rules pane after
the rule has been created. For form rules that have form rule entries, this name is
for the entire rule.
The following are the properties for a Focus form rule.