hp-support-head-portlet

Actions
Loading...

Welcome to HP Customer Support

hp-contact-secondary-navigation-portlet

Actions
Loading...

hp-share-print-widget-portlet

Actions
Loading...
  • Information
    Looking for Site Help?

    Learn about the features of the HP Customer Support site and how to use them to meet your online support needs. Click Here

     

hp-concentra-wrapper-portlet

Actions
Loading...

HP Digital Sending Software 4.25 - Configuration of Default Settings for DSS Workflows on FutureSmart Devices

The Preferences tab in an Mfp Configuration of DSS allows setting default scanner settings such as paper size and document type corresponding to items in the More Options screens available in each application on the device. These settings are applicable for all job types in pre-FutureSmart devices and all job types except Workflows in FutureSmart devices. As a workaround to this limitation, a supplementary configuration file may be created to establish these default values in FutureSmart device workflow jobs. In fact, this configuration file offers settings for FutureSmart workflows that far exceed the settings exposed on the Configuration Utility’s Preferences tab for the other job types. These settings and example configurations are described below.
FutureSmartWorkflowSettings File
Establishment of these custom configuration settings starts with the creation of a file called FutureSmartWorkflowSettings.xml in the DSS installation directory (usually C:\Program Files\Hewlett-Packard\HP MFP Digital Sending Software or C:\Program Files (x86)… on 64-bit operating systems).
Configuration entries in this file are pushed to the FutureSmart device whenever communication is performed if Send to Workflow is currently enabled for that device.
The file follows the industry-standard XML file format, where the terms element, attribute and element value (aka content) are used to describe different types of information in the file. An element comprises a start-tag of the form <elementName> and an end-tag of the form </elementName>. The element’s start-tag may contain an attribute and the element itself may contain content or may contain other elements in a nested fashion. Here’s a simple example of an XML file:
<?xml version="1.0" encoding="utf-8"?>
  note:
This document does not contain information on this header text above, just make sure it’s there.
<rootElement><Element1><childElementA attribute=“value”>child element A value</childElementA><childElementB>child element B value</childElementB></Element1><Element2>element #2 value</Element2></rootElement>
While this white-paper cannot serve as a comprehensive primer for XML, the above format is all that’s needed for construction of a valid FutureSmartWorkflowSettings.xml file. The basic file must contain the following elements: the xml header, the <FutureSmartWorkflowSettings> element, the <Form> element and one or more elements corresponding to a “configuration setting” as shown below:
<?xml version="1.0" encoding="utf-8"?><FutureSmartWorkflowSettings><Form name="DEFAULT"><config-setting userChangeable="true" limitValues=”value1 value2”>default value</config-setting></Form></FutureSmartWorkflowSettings>
Form Element and Name Attribute
The basic example above shows an attribute on the Form element called name. This attribute value may either be DEFAULT wherein the configuration settings are applicable to all workflow-forms or may correspond to the exact workflow-form name as specified in the DSS Configuration Utility’s Workflow tab. Multiple Form elements may be specified in the XML file, allowing custom configuration of default settings on a per-workflow-form basis. Note the example below where the LEGAL_PAPER_ONLY workflow-form may have a special configuration and the DEFAULT configuration is used by all other workflow-forms.
Figure : Example
Configuration Settings Element Attributes
Configuration settings elements have two attributes to supplement the default configuration settings value. As described previously, attributes are inserted within the start-tag of the element as shown here:
<config-setting userChangeable="true" limitValues=”value1 value2”>default value</config-setting>
The configuration element attributes are as follows:
userChangeable—All settings on the device application’s More Options pages are changeable by default. This attribute serves to allow or disallow the user from changing the default element value by setting the attribute to true or false. HP recommends that for clarity, this attribute always be used.
limitValues—This attribute is available on some configuration settings as will be indicated within each element description below. This attribute restricts the available values selectable by a user to a sub-set of the values normally available for a given configuration setting. Valid Limit Values entries correspond to the same list of available values as shown for each configuration settings element below. Limit Values entries cannot enable a value that is not otherwise available on the device. The userChangeable attribute value must be set to true when using this attribute.
Available Configuration Settings Elements
Now that the format of the settings file has been established, the following list of available configuration settings should be consulted to identify the name and available values used during construction of the configuration settings elements default values.
The element names and the element values must correspond exactly (including upper/lower case) to the references described here. These document scan configuration elements are all optional – if an element is not specified to override the default value, the device default will continue to be utilized. It is recommended to only override default values as necessary.
jobAssemblyMode—Also known as ‘Job Build’ mode - allows multiple scan operations such as multiple loads to the ADF tray to be performed by prompting the user for further pages before sending the job as opposed to the single scan/send operation usually performed when pressing the Start button.
Available values:
  • TRUE
  • FALSE
duplexMode—Indicates whether both sides of a document should be scanned.
Available values:
  • TRUE
  • FALSE
pageSize—Specifies the page size of the target document. If the scanned image page size differs from this target, the image will be adjusted to fit this target page size by reducing/enlarging or truncating if necessary. The limitValues attribute is available on this element.
Available values:
  • SEND_PAGESIZE_LETTER
  • SEND_PAGESIZE_LEGAL
  • SEND_PAGESIZE_EXEC
  • SEND_PAGESIZE_A4
  • SEND_PAGESIZE_A5
  • SEND_PAGESIZE_JB5
  • SEND_PAGESIZE_MIXED
  • SEND_PAGESIZE_LEDGER
  • SEND_PAGESIZE_A3
  • SEND_PAGESIZE_JB4
  • SEND_PAGESIZE_STATEMENT
  • SEND_PAGESIZE_8.5x13
pageOrientation—Specifies the page orientation of the target document. If the scanned image page orientation differs from this target, the image will be adjusted to fit this target page orientation by rotating the image 90 degrees clockwise.
Available values:
  • SEND_PAGE_ORIENTATION_PORTRAIT
  • SEND_PAGE_ORIENTATION_LANDSCAPE
colorMode—Specifies whether the target document should be rendered in color or in grayscale (mono).
Available values:
  • SEND_COLORMODE_MONO
  • SEND_COLORMODE_COLOR
resolution—Specifies the image resolution of the target document. Not all resolutions are available on all devices, so the configuration setting will be set to the closest available resolution if necessary. The limitValues attribute is available on this element.
Available values:
  • SEND_RESOLUTION_600x600
  • SEND_RESOLUTION_400x400
  • SEND_RESOLUTION_300x300
  • SEND_RESOLUTION_200x200
  • SEND_RESOLUTION_150x150
  • SEND_RESOLUTION_75x75
fileType—Specifies the file type of the target document. If an OCR file type is set as the default or listed in the limitValues, the Generate OCR File checkbox must be selected in the workflow form’s properties dialog. As just indicated, the limitValues attribute is available on this element.
Available values:
  • SEND_FILETYPE_PDF
  • SEND_FILETYPE_MTIFF
  • SEND_FILETYPE_TIFF
  • SEND_FILETYPE_JPEG
  • SEND_FILETYPE_TEXT_OCR
  • SEND_FILETYPE_PDF_OCR_TEXTUNDERIMAGE
  • SEND_FILETYPE_CSV_OCR
  • SEND_FILETYPE_RTF_OCR
  • SEND_FILETYPE_XML_OCR
  • SEND_FILETYPE_HTML_OCR
outputQuality—Specifies the output quality of the target document. The limitValues attribute is available on this element.
Available values:
  • SEND_OUTQUALITY_HIGH
  • SEND_OUTQUALITY_MEDIUM
  • SEND_OUTQUALITY_LOW
optimizeTextPhoto—Specifies the degree of bias that should be applied toward optimization of the target image towards text vs graphics quality. The limitValues attribute is available on this element.
Available values:
  • SEND_OPTIMIZETEXTPHOTO_TEXT
  • SEND_OPTIMIZETEXTPHOTO_MIXED_0
  • SEND_OPTIMIZETEXTPHOTO_MIXED_1
  • SEND_OPTIMIZETEXTPHOTO_MIXED_2
  • SEND_OPTIMIZETEXTPHOTO_MIXED_3
  • SEND_OPTIMIZETEXTPHOTO_MIXED_4
  • SEND_OPTIMIZETEXTPHOTO_GRAPHIC
imageAdjustDarkness—Specifies the darkness level to be applied on the target image. The limitValues attribute is available on this element.
Available values:
  • Integer values from 0 (light) to 8 (dark)
imageAdjustBackgroundCleanup—Specifies the degree to which cleanup of background flaws in the original image should be attempted. The limitValues attribute is available on this element.
Available values:
  • Integer values from 0 (no cleanup) to 8 (aggressive cleanup)
imageAdjustSharpness—Specifies the sharpness level to be applied on the target image. The limitValues attribute is available on this element.
Available values:
  • Integer values from 0 (soft) to 4 (sharp)
imageAdjustContrast—Specifies the contrast level to be applied on the target image. The limitValues attribute is available on this element.
Available values:
  • Integer values from 0 (low contrast) to 8 (high contrast)
Example
The following example sets the default page size of the target image to Legal and disallows the user from changing that default on the LEGAL_PAPER_ONLY form. It also sets a default file type of PDF for all forms but allows the user to choose either PDF or JPEG via the limitValues attribute. Note that the file type setting must be made in both the DEFAULT and LEGAL_PAPER_ONLY form configurations since the DEFAULT configuration settings are not inherited by other form configurations.
<?xml version="1.0" encoding="utf-8"?><FutureSmartWorkflowSettings><Form name="LEGAL_PAPER_ONLY"><pageSize userChangeable="false">SEND_PAGESIZE_LEGAL</pageSize><fileType userChangeable="true" limitValues="SEND_FILETYPE_PDF SEND_FILETYPE_JPEG">SEND_FILETYPE_PDF</fileType></Form><Form name="DEFAULT"><fileType userChangeable="true" limitValues="SEND_FILETYPE_PDF SEND_FILETYPE_JPEG">SEND_FILETYPE_PDF</fileType></Form></FutureSmartWorkflowSettings>
Usage
Once the FutureSmartWorkflowSettings.xml file is created, it should be placed in the DSS installation directory. When the Configuration Utility is opened and subsequent communications with bound devices occurs, FutureSmart devices for which workflows are enabled will have the configuration settings specified in this file applied to the device workflow application. If a configuration reflecting the one specified in the settings file is not seen on a tested FutureSmart device, in all likelihood there’s an error in the values or formatting of the file. Close the Configuration Utility, make any appropriate changes to FutureSmartWorkflowSettings.xml and re-open the Configuration Utility to push these new changes.
FutureSmartWorkflowSettingsSchema.xsd Schema File
For advanced users familiar with XML and XSD schemas, the schema file FutureSmartWorkflowSettingsSchema.xsd corresponding to the above configuration settings is included in the DSS installation directory for context-sensitive editing and validation of the FutureSmartWorkflowSettings.xml file.

hp-feedback-input-portlet

Actions
Loading...

hp-online-communities-portlet

Actions
Loading...

Ask the community!


Support Forum

Support Forum

Join the conversation! Find Solutions, ask questions, and share advice with other HP product owners. Visit now


hp-feedback-banner-portlet

Actions
Loading...

hp-country-locator-portlet

Actions
Loading...
Country: Flag Estonia

hp-detect-load-my-device-portlet

Actions
Loading...