auto_stories Knowledge Base chevron_right Actions chevron_right Article

Print

This is the type of operation that allows the printing of the information created on the form. Form design as output design can be printed out.

mceclip0.png

Print operation at Property Panel

 

Properties

Description: A description of the action is written.

Heading: Specifies the name in the action list when added as a Form Action.

Design File: The name of the design file is written or found with the SQL query.

Form: The form for printing is selected.

Linked List: If printing from records in a list, the corresponding list is selected.

List-ID Field: The UserTableID field in the list is selected.

List Type Field: The FormTypeID field in the list is selected.

Print Preview: It is decided whether the print preview can be made. (In the absence of a print preview, printing is done on the server-side active printer.)

Run Condition: If the value in the query entered in this field is ‘0′, the corresponding action will not run.

Request Confirmation: Select whether to ask for confirmation before running the action. If Request Confirmation is activated, the Confirmation Message feature is turned on and the message that will be displayed when requesting confirmation is written.

 

Example Used

Firstly, run the client screen of the related form and then click the Form button in the bottom right of the screen. Write a form name for design and adjust the form design. After the design form is saved, go to the Studio screen for the related form.

mceclip1.png

Add a button for print. Create an operation as Print with When clicked event. Write your design name in the Design File area. Choose the related form. Switch the Print Preview as Yes to view the print page.

mceclip2.png

When you click the Print button, Print Page will be opened as fullscreen.

mceclip3.png

Client view on-screen with Print page

Dynamic Use of Design Names in Print Actions

To enable multiple outputs created via Studio or Client to be generated through a single Print Action based on specific conditions, the output names must be written into a textbox field on the form screen.

In the example below, this textbox field is defined as DesignName.

Two sample outputs are used: DynamicDesignFirst and DynamicDesignSecond.

undefined

In the Design File field within the Print Action, the textbox containing the dynamic design name is added using a SELECT query as follows:

SELECT '$PDesignName$'

Note: $PDesignName$ represents the name of the textbox field on the screen where the dynamic design name is stored.

undefined

On the Client screen (as shown in the visual), the design name is dynamically written into the textbox named DesignName. When the button associated with the Print Action is clicked, the corresponding design file (e.g., DynamicDesignFirst) is executed automatically.

undefined