Building with Application Design

Loftware Enterprise SP's Application Design  allows you to do the following:

• Design complex, intelligent data entry form experiences for users.
• Link individual forms together and provide a dynamic path through them that varies based on data values or information entered by an end user.
• Link forms together to create a data set for use by a process An object in Loftware 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..
• Perform complex validation of data in data entry forms.

You can 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 Person or process that enters data into a form or other data entry view for a label that was configured by a Designer. A user acting as a Data Provider requires the DOCUMENT_PRINTER role or equivalent permissions. working in Applications  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 Design , you create an application that connects individual forms by using transitions. In an application, an action, rule, or business rule A 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 Application Design page and can be designed using the Configurator or programmed using XML. is run by a trigger A means of running an action, rule, or data service. 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.. In a form, a rule can also be run by a trigger. For data in a form, you can manually enter a value, or you can use a data map entry A name (key) and value pair in the data map for a job..