Scribd
Upload
290 views2 pages

Uniface Learnings

1. The retrieve statement without the /e switch activates the read trigger of the outermost entity on the component, while with /e it activates the read trigger of the current entity. 2. Using new_instance allows creating multiple instances of the same component, each with its own instance name, and determines if instances are created on client or server. 3. The init operation is executed before a new instance is created.

Uploaded by

Neha Agarwal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
290 views2 pages

Uniface Learnings

1. The retrieve statement without the /e switch activates the read trigger of the outermost entity on the component, while with /e it activates the read trigger of the current entity. 2. Using new_instance allows creating multiple instances of the same component, each with its own instance name, and determines if instances are created on client or server. 3. The init operation is executed before a new instance is created.

Uploaded by

Neha Agarwal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Without the /e switch the retrieve statement activates the Read trigger of the first outermost entity on the

e component. With /e switch It activates the Read trigger of the current entity ($entname) or of Entity. E.g. Retrieve EMP ( EMP is an entity) Error : field EMP not available, it goes into read trigger of outermost entity on the component.

Using new_instance allows you to start several instances of the same component, each known by its own instance name. If the component is a service or report, assignments in the [SERVICES_EXEC] or [REPORTS_EXEC] section of the assignment file determine if the instance is created on the client or server machine. (Instances of form components are always created on the client machine.)

ULANA.DICT or USYSANA.TEXT, URR

Init operation is executed before the new instance is created.

Locating the called module When resolving a call statement, the called module is searched for in this order: 1. 2. 3. 4. In In In In the the the the triggers of the component (for a local Proc module). library specified in the component properties (for a global Proc). library specified in the start-up shell properties (for a global Proc). library SYSTEM_LIBRARY (for a global Proc).

Further information about call resolution and binding can be found in The compilation process. Never use the clear/e statement in the Occurrence Gets Focus or Start Modification triggers. This can cause UNIFACE to enter an infinite loop. The process flow for the <Erase> trigger is as follows: 1. The ^ERASE structure editor function activates the <Erase> trigger. 2. If <Erase> trigger contains the erase statement, the Lock trigger is activated for each occurrence retrieved from a database. 3. If the Lock trigger contains the lock statement, all occurrences are locked in the database. 4. UNIFACE activates the Delete trigger for each occurrence retrieved from the database.

5. Per occurrence, the delete statement in the Delete trigger deletes the occurrence from the database. Most developers disable the <Erase> trigger. Compare the functionality of ^ERASE with the ^CLEAR function which is used to clear the form of data, but does not delete data stored in the database. Next field: This trigger is not activated when the cursor is moved with arrow keys or mouse clicks or by setting $prompt.

Leave Object group of triggers (Leave Field, Leave Modified Key, and Leave Modified Occurrence) Validate -> leave -> next

Model and design applications


Application development with UNIFACE is driven by the business model. Business models capture the rules and processes of the business of organizations. Abstraction is high in business model-driven development. Developers can concentrate on solving business issues rather than computing problems, regardless of the intended deployment technologies and architectures. UNIFACE captures the business model as follows: The logical data model and business rules are defined in the application model. The application logic and functional requirements are captured in the component model. Business objects are components. UNIFACE application components are services, forms, reports, and server pages. Business processes are the operations carried out by the components

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy