Solution settings can be accessed from scripts and are available to the LDD administrator through LMC during and after solution deployment. A solution setting is accessed from a script by name, just like a constant or variable.
Solution settings may be global or local. The following table lists the differences between global and local solution settings:
Setting type | Scope | Location in LMC | Time of first configuration | Common uses |
|---|---|---|---|---|
Global | All device groups that use the solution | Configuration task on the Solutions tab | The solution is uploaded to LDD. |
|
Local | A single device group that uses the solution | Solutions task on the Device Groups tab; dialog during deployment to a device group | The solution is added to a device group. |
|
Solution settings are generally configured throughout the solution development process as the need arises for each setting.
To create solution settings, double-click solutionSettings.ldd in the src\conf\ folder of the Package Explorer list. The Solution Settings Editor appears in the Editor pane. Separate lists of local and global solution settings are shown.
To edit an existing setting, select an item in the Local Solution Settings list or Global Solution Settings list.
To add a setting, click New beside the associated list.
To delete the current selection, click Remove beside the associated list.
To change the position of the current selection in LMC, click Up or Down beside the associated list.
Modify the properties of the selected or new setting using the fields on the right side of the window. While editing properties, click Clear to revert to the last saved properties for the setting, or click Save to save the new properties.
Property | Description |
|---|---|
Key | The name used to access the property from a solution script. |
Name | The name used for the property in LMC. |
Read-Only (local solution settings only) | Determines whether the property is read-only. A read-only property cannot be modified using a script or in LMC. |
Type | The type assignment for the property. See the following table of property types for a description of each type. |
Type | Shown in LMC | Properties |
|---|---|---|
Check | Check box | Values:
|
Content Type | List of predefined content type settings |
|
Text | Value field | Any character Note: The Value field can be left blank. |
Number | Value field | Any character Note: The Value field should not be left blank, even if the minimum value is set to zero. |
Password | Value field | Any character |
Darkness | List of predefined darkness values | Values:
|
Depth | List of predefined color depth settings | Values:
|
Duplex | List of predefined duplex settings | Values:
|
File Type | List of predefined file type settings | Values:
|
Media Size | List of predefined media-size settings | Values:
|
Resolution | List of predefined resolution settings | Values:
|
Display Type | List of predefined printer standard prompt settings | Values:
|
The device policy developed within the solution determines the profiles that are made available to a printer or software client when the solution is deployed. Each profile is associated with a script within the solution. The policy also manages the default profile buttons, shortcut number, access control number, scan settings, and eSF applications associated with each profile. The device policy is generally configured near the end of the solution development process, since existing scripts are assigned to profiles.
To manage the device policy associated with the solution, double-click devicePolicy.ldd in the src\conf\ folder of the project in the Package Explorer pane. The Device Policy Editor appears in the Editor pane.
To add a profile, click New, type the key for the new profile, and then click Create.
To edit a profile, select it in the Device Profiles list.
To delete a profile, select it in the Device Profiles list, and then click Remove.
A device policy contains a separate sub-policy for each device class and for software clients. Select a device class from the Device Group list to access the sub-policy for each, or select Software to access the sub-policy for software clients.
Notes:
To reset all settings for a sub-policy, click Reset beside the Device Group list. While editing properties, click Clear to revert to the last saved properties for the profile, or Save to save the new properties.
The following table shows the properties available for each device profile:
Property | Description |
|---|---|
Key | This property is the name used to access the profile from a script. The key applies to the policy as a whole and does not vary for sub-policies. |
Device Group | This property allows the solution developer to select which device subtypes are in the profile. The device group can be any of the following:
|
Name | This property is the name used for the profile in Lexmark Management Console. Note: For a profile used with a Lexmark Document Server Port, the name must be 14 or fewer characters. |
Task | This property is the script associated with the policy. |
No Scan (e-Task and e-Task 2) | This property indicates whether a scan task is part of the solution. A profile can be deployed to a single-function printer only when No Scan is selected. |
No Prompt | This property is a control added to note indicating that the profile does not contain prompting. It helps improve the performance of the LDD printer ports for print servers that do not support prompting. This setting is also active for device groups which are set to Software. Select this setting for any existing Software solutions, such as print release, to improve the LDD printer port performance for print servers. |
Setting (e-Task and e-Task 2) | This property is the setting type to add to or edit in the list of settings. See the following table of setting types for a description of each type and available values. |
Mapped (e-Task and e-Task 2) | This property determines whether the setting is mapped to a solution setting defined in solutionSettings.ldd. |
Value (e-Task and e-Task 2) | This property is the value of the setting to add to or edit in the list of settings. See the following table of setting types for the available values for each setting type. |
Overrideable (e-Task and e-Task 2) | This property determines whether the user at the printer can override the setting when the solution is run. |
Shortcut Number | This property is the shortcut number by which a user can access the profile from the printer. |
Access Control Number | This property is the number used to assign access controls specifically to the profile, using one of the Solution 1–10 settings in the printer Embedded Web Server. |
The following table shows the setting types available for device profiles:
Type | Available values |
|---|---|
Content Type |
|
Darkness |
|
Depth |
|
Duplex |
|
File Type |
|
Media Size |
|
Orientation |
|
Resolution |
|
You can package profile buttons to appear on the home screen as part of the device policy for e-Task and e-Task 2 devices. When e-Task or e-Task 2 is selected in the Device Group list, the Profile Button(s) section appears. Additionally, when e-Task 2 is selected, a selection appears for e-Task 2 or e-Task 2+ profile buttons, representing older and newer e-Task 2 printers, respectively. You can determine which setting to use by matching the preview of the default image with the look of the existing buttons on the printer display.
You can load separate images for Up Image and Down Image. The Up Image shows when the button is in default state, and the Down Image shows while the user is pressing the button. If no Down Image is specified, then the Up Image is used for both conditions.
Images selected are resized to the following dimensions for each device class. For best results, resize or crop source images to the correct size before use.
e-Task 5—140 x 140 pixels
e-Task 3 and e-Task 4—172 x 254 pixels
e-Task 2 and e-Task 2+, SFP e-Task 2+—120 x 75 pixels
e-Task—120 x 80 pixels
X642—120 x 55 pixels
To associate an eSF application with the e-Task 2 sub-policy for a hybrid solution, click Import beside the eSF Applications list, and then locate an eSF application. Select the newly imported application in the list, and then make sure that e-Task2 is selected in the Device Group list. To remove a previously imported eSF application, select it from the list, and then click Remove.
To manage the settings associated with the eSF application and allow configuration in LMC, import and configure the descriptor file for the eSF application.
Notes:
Select the eSF application from the eSF Application list.
Click Descriptor.
Locate the XML descriptor file for the eSF application. The file name should be the same as the file name of the eSF application, with an ”.xml” extension and “_desc” appended before the extension.
Click Open.
Select the eSF application from the eSF Application list.
Click the eSF Descriptor Editor tab at the bottom of the Device Policy Editor.
Modify the settings if necessary, and then click Save.
You can use forms merge in a solution by including formsets created with Lexmark Forms Composer. Formsets included in a workflow solution project are uploaded to the LDD system when the workflow solution is installed.
Formsets are added as needed throughout the solution development process. To manage formsets, double-click forms.ldd in the src\conf\ folder of the Package Explorer list. The Forms List Editor appears in the Editor pane. The list of included formsets is shown.
To add a formset that will be installed with a workflow solution:
In the Forms List Editor, click Import.
Browse to a formset (.sdd or .fdd) file.
Click Open.
When uploaded, formsets may be shared among workflow solutions, and the administrator selects whether to remove associated formsets when removing solutions. To create a link with a formset included in another workflow solution:
In the Forms List Editor, click Link.
In the Form Name field, type the name of the formset.
Click Create.
To remove a formset from the project, select it from the Forms List, and then click Remove.
LDD uses JasperReports for custom reports, which can be included with a workflow solution during development. You can create custom reports using the open source application iReport 3.5.2. For more information about overall report design, see the documentation for iReport, and for specific information about developing custom reports for LDD, see the Lexmark Document Distributor Administrator's Guide.
Custom reports are added as needed throughout the solution development process. To manage custom reports, double-click reports.ldd in the src\conf\ folder of the Package Explorer list. The Reports List Editor appears in the Editor pane. The list of included reports is shown.
To add a report that will be installed with a workflow solution:
In the Reports List Editor, click Import.
Browse to a compiled JasperReports (.jasper) file.
Click Open.
To edit the settings of a report after it is imported:
Select the report file from the Reports list.
Type a descriptive report name.
Select an output format.
Select Database from the Datasource drop-down menu.
Select Monitor from the Source Choice drop-down menu.
If you are using auto-configure to schedule the report, then select the period for the report to cover.
Add a custom parameter for either a query parameter defined in the custom report file:
In the Key field, type the name of the parameter defined within the report.
Select the parameter type to identify the type of data contained in the parameter.
Type a default value for the parameter.
Notes:
Click Save.