This document discusses working with text items in Oracle Forms. It describes how to create text items, modify their appearance and properties, control their data and navigation behavior, and add functionality. Key topics covered include modifying font, color, and prompt properties; controlling data type, length, and initial values; and displaying help messages.
This document discusses how to create a basic form module in Oracle Forms. It covers creating an empty module, adding a data block using the Data Block Wizard and Layout Wizard, saving and compiling the form module, different file formats for storing modules, and deploying a form module to the application server. The key steps are to create an empty module, add a data block with the wizard, save and compile the form, move the files to the application server, and generate the module to run it in the browser.
This document discusses creating and modifying master-detail forms in Dynamics 365 Business Central. It covers creating relationships between data blocks, running a master-detail form with automatic linking and deletion rules, and modifying data blocks and their layouts using wizards in reentrant mode. The key points are that relationships can be set up manually or with a wizard, forms can be run with default coordination properties, and data blocks and layouts can be customized manually or with wizards in a non-destructive way.
This document discusses working with data blocks and frames in Oracle Forms. It covers identifying components of the Property Palette, managing object properties, creating and using Visual Attributes, controlling data block and frame properties, and creating and deleting data blocks. The key topics covered are using the Property Palette to modify object properties, setting properties to control data block behavior and appearance, setting frame properties, and creating and deleting data blocks.
This document provides an overview of LOVs (lists of values) and editors in Oracle Forms and describes how to create them. LOVs allow selecting a value for a text item from a dynamic list, and are created from a database query. Editors override the default editor for a text item and allow customizing the editing window. The document explains that LOVs are easiest to design using the LOV Wizard, which guides selecting columns and properties. Editors are created in the Object Navigator and associated with a text item's properties. Practice questions at the end involve creating an LOV attached to a text item and an Editor attached to another item.
Non-input items that can be created include display items, image items, buttons, calculated items, hierarchical tree items, and bean area items. Display items and image items show information without input, buttons initiate actions, calculated items use formulas or summaries, tree items show hierarchical data, and bean areas execute Java code. These item types are created by changing an existing item's type or using tools in the Layout Editor and setting properties specific to each item type.
This document discusses navigation in forms. It distinguishes between internal and external navigation, and describes how to control navigation with properties of the form, block, and item. It explains navigation triggers that fire during or after navigation, and navigation built-ins that can be used in triggers except those that fire during navigation. These include GO_FORM, GO_BLOCK, GO_RECORD, GO_ITEM, NEXT_BLOCK, and others. The document also provides examples of setting properties and using triggers and built-ins to control navigation flow.
This document describes how to run a Forms application using Oracle Application Server Containers for J2EE (OC4J). It explains that OC4J is used to run Forms applications on the development machine and test them in a web browser. When running a form, the Forms Client applet displays in the browser while the Forms Listener Servlet and Runtime Engine handle processing on the application server. Users can navigate forms and query, insert, update, and delete records in different operation modes.
This document discusses how to create a basic form module in Oracle Forms. It covers creating an empty module, adding a data block using the Data Block Wizard and Layout Wizard, saving and compiling the form module, different file formats for storing modules, and deploying a form module to the application server. The key steps are to create an empty module, add a data block with the wizard, save and compile the form, move the files to the application server, and generate the module to run it in the browser.
This document discusses creating and modifying master-detail forms in Dynamics 365 Business Central. It covers creating relationships between data blocks, running a master-detail form with automatic linking and deletion rules, and modifying data blocks and their layouts using wizards in reentrant mode. The key points are that relationships can be set up manually or with a wizard, forms can be run with default coordination properties, and data blocks and layouts can be customized manually or with wizards in a non-destructive way.
This document discusses working with data blocks and frames in Oracle Forms. It covers identifying components of the Property Palette, managing object properties, creating and using Visual Attributes, controlling data block and frame properties, and creating and deleting data blocks. The key topics covered are using the Property Palette to modify object properties, setting properties to control data block behavior and appearance, setting frame properties, and creating and deleting data blocks.
This document provides an overview of LOVs (lists of values) and editors in Oracle Forms and describes how to create them. LOVs allow selecting a value for a text item from a dynamic list, and are created from a database query. Editors override the default editor for a text item and allow customizing the editing window. The document explains that LOVs are easiest to design using the LOV Wizard, which guides selecting columns and properties. Editors are created in the Object Navigator and associated with a text item's properties. Practice questions at the end involve creating an LOV attached to a text item and an Editor attached to another item.
Non-input items that can be created include display items, image items, buttons, calculated items, hierarchical tree items, and bean area items. Display items and image items show information without input, buttons initiate actions, calculated items use formulas or summaries, tree items show hierarchical data, and bean areas execute Java code. These item types are created by changing an existing item's type or using tools in the Layout Editor and setting properties specific to each item type.
This document discusses navigation in forms. It distinguishes between internal and external navigation, and describes how to control navigation with properties of the form, block, and item. It explains navigation triggers that fire during or after navigation, and navigation built-ins that can be used in triggers except those that fire during navigation. These include GO_FORM, GO_BLOCK, GO_RECORD, GO_ITEM, NEXT_BLOCK, and others. The document also provides examples of setting properties and using triggers and built-ins to control navigation flow.
This document describes how to run a Forms application using Oracle Application Server Containers for J2EE (OC4J). It explains that OC4J is used to run Forms applications on the development machine and test them in a web browser. When running a form, the Forms Client applet displays in the browser while the Forms Listener Servlet and Runtime Engine handle processing on the application server. Users can navigate forms and query, insert, update, and delete records in different operation modes.
This document discusses various methods for reusing objects and code in Oracle Forms applications, including property classes, object groups, copying and subclassing objects, object libraries, SmartClasses, and reusing PL/SQL code through triggers, program units, and libraries. Property classes allow inheriting properties, object groups make related objects easy to reuse, and object libraries and SmartClasses simplify sharing reusable components. PL/SQL code can be reused by copying, subclassing, defining program units, or creating libraries.
The document discusses different types of canvases in Oracle Forms including stacked, toolbar, and tab canvases. It describes how stacked canvases overlay content canvases, toolbar canvases provide standard buttons and elements, and tab canvases organize information across pages. It provides instructions for creating these canvases, setting their properties, and placing items on tab pages.
This document discusses writing flexible code that is reusable, generic, and avoids hard-coded object names to make maintenance easier. It describes using system variables to reference the current context and status. Built-in subprograms like GET_ and SET_ can retrieve and set properties of objects. Objects can be referenced by internal ID found using functions like FIND_, or indirectly using COPY and NAME_IN to pass values without hard-coding names. Flexible code is more efficient and reusable across applications.
Windows display content canvases and allow viewing one canvas at a time. Content canvases are surfaces that display within a window. Each window must have at least one content canvas. You can create additional windows in the Object Navigator and display different canvases or the same form module across multiple windows and canvases. Properties of windows and canvases allow setting positions, sizes, names and other attributes.
Define triggers
Identify the different trigger categories
Plan the type and scope of triggers in a form
Describe the properties that affect the behavior of a trigger
Grid computing uses low-cost servers and modular storage to balance workloads and provide capacity on demand. Oracle's grid products include the Oracle Database, Application Server, and Enterprise Manager. Oracle Application Server provides services for building and deploying web applications. The Oracle Developer Suite includes tools for application development and business intelligence such as Forms Developer and Reports. Forms Services allows deployment of Forms applications to a web environment.
- Oracle Form Builder is a component of Oracle Developer/2000 that is used to create event-driven applications to enter, access, change, or delete data from an Oracle database.
- A Forms application consists of forms, menus, and libraries. Forms uses triggers, processes, and events to control user interactions and database transactions.
- The main components of a Forms application include windows, canvases, blocks, items, triggers, alerts, lists of values (LOVs), editors, parameters, program units, libraries, and object groups.
Is your engineering team doing whatever they want when creating 3D Models and Drawings? How do you get control and manage the chaos?
The goal of this session is to provide an overview of how standards can be imposed and managed by Autodesk Vault. Standards provide structure and guidance on how Engineers/Designers are to prepare and manage their engineering design data resulting in less mistakes, efficient workflows, accountability, and consistency within the team.
The document discusses creating a simple form module in Oracle Apps using form builder wizards. It describes using the data block wizard to create a data block and the layout wizard to design the form's presentation. It also covers creating a control block, setting data block properties, establishing master-detail relationships between blocks, and configuring block coordination and deletion behavior.
This document provides an overview of the speaker's background and experience with CAD software like AutoCAD and Inventor, as well as content center management. It then discusses best practices for setting up and managing an Inventor content center, including creating read/write libraries, defining categories and family tables, editing family tables, and publishing parts. The speaker offers to help customers develop customized Content Center implementation and training plans.
This document introduces Oracle9i and relational database concepts. It discusses Oracle9i features like scalability and reliability. It also explains that a relational database consists of tables related through primary and foreign keys that can be accessed using SQL. The Oracle database server allows storage and querying of data across these tables.
Introduction to the Standard Query Language (SQL) to access data in relational databases. More information can be found at https://www.spiraltrain.nl/course-sql-fundamentals/?lang=en
Advanced Queuing provides database-integrated message queuing functionality that allows asynchronous communication between applications. It allows producers to ENQUEUE messages into queues and consumers to DEQUEUE messages. Key features include persistence of messages, propagation between queues, priority ordering of messages, transformation of message formats, and access control. The document provides an overview of these features and how to configure and use Advanced Queuing through PL/SQL interfaces and APIs.
This document provides an overview of forms development in Oracle Applications. It discusses the major components of a form like the canvas, windows, blocks, items, and triggers. It explains how forms are developed using the Forms Designer tool, including laying out the interface, connecting to database tables via blocks, adding programming logic via triggers, and compiling the form. The document also briefly mentions other concepts like libraries, menus, and common issues encountered during forms development.
Using the Archivists' Toolkit: Hands-on practice and related toolsAudra Eagle Yun
The document provides an overview of the Archivists' Toolkit (AT), a free and open-source archival management application. It discusses the key functions of AT including recording accessions, describing archival materials and digital objects, managing locations, and exporting records. The document then demonstrates how to get started with AT by setting up a repository record and user accounts. It guides the user through activities like adding locations, creating accession and resource records, and linking them together. Finally, it discusses how to export finding aids from AT in EAD format and submit them to online archives like the Online Archive of California.
This document discusses working with data blocks and frames in Oracle Forms. It covers identifying components of the Property Palette, managing object properties, creating and using visual attributes, and controlling the behavior and appearance of data blocks and frame properties. Key points covered include using the Property Palette to modify forms objects, setting properties to control data block navigation, records, and database features, and deleting data blocks and their components.
ODBC (Open Database Connectivity) was Microsoft's first database access technology. It provided a C interface that allowed applications to access data from different database management systems (DBMS) using a standardized call level interface. While widely adopted, it had some drawbacks including requiring a C interface and putting a burden on drivers to emulate a relational database for non-relational data sources.
Content migration Part 1: TERMINALFOUR t44u 2013Terminalfour
TERMINALFOUR's Neil O'Neill discusses how T4 Site Manager comes with a number of tools to automatically migrate content, what migration approach is best for you, the steps involved in content migration and the systems we have migrated from.
WebUtil is a utility that enables client-side functionality on Win32 clients. It consists of Java classes, Forms objects, and a PL/SQL library. WebUtil provides benefits such as only requiring PL/SQL coding knowledge, free download, and easy integration into Forms applications. To integrate WebUtil, a developer attaches the WebUtil library and subclasses the WebUtil object group. Then WebUtil functions can be used to interact with the client, such as opening file dialogs, reading/writing files, executing commands, and automating applications.
The document discusses transaction processing in Oracle Forms. It explains that Forms uses transactions to apply changes to the database, which involves two phases - post and commit. During commit, it validates the form and blocks, performs the necessary DML operations like insert, update, delete, and fires various commit triggers. Forms supports supplementing the transaction processing using triggers at different stages. It also discusses getting and setting the commit status, and using array DML to reduce network traffic.
This document discusses various methods for reusing objects and code in Oracle Forms applications, including property classes, object groups, copying and subclassing objects, object libraries, SmartClasses, and reusing PL/SQL code through triggers, program units, and libraries. Property classes allow inheriting properties, object groups make related objects easy to reuse, and object libraries and SmartClasses simplify sharing reusable components. PL/SQL code can be reused by copying, subclassing, defining program units, or creating libraries.
The document discusses different types of canvases in Oracle Forms including stacked, toolbar, and tab canvases. It describes how stacked canvases overlay content canvases, toolbar canvases provide standard buttons and elements, and tab canvases organize information across pages. It provides instructions for creating these canvases, setting their properties, and placing items on tab pages.
This document discusses writing flexible code that is reusable, generic, and avoids hard-coded object names to make maintenance easier. It describes using system variables to reference the current context and status. Built-in subprograms like GET_ and SET_ can retrieve and set properties of objects. Objects can be referenced by internal ID found using functions like FIND_, or indirectly using COPY and NAME_IN to pass values without hard-coding names. Flexible code is more efficient and reusable across applications.
Windows display content canvases and allow viewing one canvas at a time. Content canvases are surfaces that display within a window. Each window must have at least one content canvas. You can create additional windows in the Object Navigator and display different canvases or the same form module across multiple windows and canvases. Properties of windows and canvases allow setting positions, sizes, names and other attributes.
Define triggers
Identify the different trigger categories
Plan the type and scope of triggers in a form
Describe the properties that affect the behavior of a trigger
Grid computing uses low-cost servers and modular storage to balance workloads and provide capacity on demand. Oracle's grid products include the Oracle Database, Application Server, and Enterprise Manager. Oracle Application Server provides services for building and deploying web applications. The Oracle Developer Suite includes tools for application development and business intelligence such as Forms Developer and Reports. Forms Services allows deployment of Forms applications to a web environment.
- Oracle Form Builder is a component of Oracle Developer/2000 that is used to create event-driven applications to enter, access, change, or delete data from an Oracle database.
- A Forms application consists of forms, menus, and libraries. Forms uses triggers, processes, and events to control user interactions and database transactions.
- The main components of a Forms application include windows, canvases, blocks, items, triggers, alerts, lists of values (LOVs), editors, parameters, program units, libraries, and object groups.
Is your engineering team doing whatever they want when creating 3D Models and Drawings? How do you get control and manage the chaos?
The goal of this session is to provide an overview of how standards can be imposed and managed by Autodesk Vault. Standards provide structure and guidance on how Engineers/Designers are to prepare and manage their engineering design data resulting in less mistakes, efficient workflows, accountability, and consistency within the team.
The document discusses creating a simple form module in Oracle Apps using form builder wizards. It describes using the data block wizard to create a data block and the layout wizard to design the form's presentation. It also covers creating a control block, setting data block properties, establishing master-detail relationships between blocks, and configuring block coordination and deletion behavior.
This document provides an overview of the speaker's background and experience with CAD software like AutoCAD and Inventor, as well as content center management. It then discusses best practices for setting up and managing an Inventor content center, including creating read/write libraries, defining categories and family tables, editing family tables, and publishing parts. The speaker offers to help customers develop customized Content Center implementation and training plans.
This document introduces Oracle9i and relational database concepts. It discusses Oracle9i features like scalability and reliability. It also explains that a relational database consists of tables related through primary and foreign keys that can be accessed using SQL. The Oracle database server allows storage and querying of data across these tables.
Introduction to the Standard Query Language (SQL) to access data in relational databases. More information can be found at https://www.spiraltrain.nl/course-sql-fundamentals/?lang=en
Advanced Queuing provides database-integrated message queuing functionality that allows asynchronous communication between applications. It allows producers to ENQUEUE messages into queues and consumers to DEQUEUE messages. Key features include persistence of messages, propagation between queues, priority ordering of messages, transformation of message formats, and access control. The document provides an overview of these features and how to configure and use Advanced Queuing through PL/SQL interfaces and APIs.
This document provides an overview of forms development in Oracle Applications. It discusses the major components of a form like the canvas, windows, blocks, items, and triggers. It explains how forms are developed using the Forms Designer tool, including laying out the interface, connecting to database tables via blocks, adding programming logic via triggers, and compiling the form. The document also briefly mentions other concepts like libraries, menus, and common issues encountered during forms development.
Using the Archivists' Toolkit: Hands-on practice and related toolsAudra Eagle Yun
The document provides an overview of the Archivists' Toolkit (AT), a free and open-source archival management application. It discusses the key functions of AT including recording accessions, describing archival materials and digital objects, managing locations, and exporting records. The document then demonstrates how to get started with AT by setting up a repository record and user accounts. It guides the user through activities like adding locations, creating accession and resource records, and linking them together. Finally, it discusses how to export finding aids from AT in EAD format and submit them to online archives like the Online Archive of California.
This document discusses working with data blocks and frames in Oracle Forms. It covers identifying components of the Property Palette, managing object properties, creating and using visual attributes, and controlling the behavior and appearance of data blocks and frame properties. Key points covered include using the Property Palette to modify forms objects, setting properties to control data block navigation, records, and database features, and deleting data blocks and their components.
ODBC (Open Database Connectivity) was Microsoft's first database access technology. It provided a C interface that allowed applications to access data from different database management systems (DBMS) using a standardized call level interface. While widely adopted, it had some drawbacks including requiring a C interface and putting a burden on drivers to emulate a relational database for non-relational data sources.
Content migration Part 1: TERMINALFOUR t44u 2013Terminalfour
TERMINALFOUR's Neil O'Neill discusses how T4 Site Manager comes with a number of tools to automatically migrate content, what migration approach is best for you, the steps involved in content migration and the systems we have migrated from.
WebUtil is a utility that enables client-side functionality on Win32 clients. It consists of Java classes, Forms objects, and a PL/SQL library. WebUtil provides benefits such as only requiring PL/SQL coding knowledge, free download, and easy integration into Forms applications. To integrate WebUtil, a developer attaches the WebUtil library and subclasses the WebUtil object group. Then WebUtil functions can be used to interact with the client, such as opening file dialogs, reading/writing files, executing commands, and automating applications.
The document discusses transaction processing in Oracle Forms. It explains that Forms uses transactions to apply changes to the database, which involves two phases - post and commit. During commit, it validates the form and blocks, performs the necessary DML operations like insert, update, delete, and fires various commit triggers. Forms supports supplementing the transaction processing using triggers at different stages. It also discusses getting and setting the commit status, and using array DML to reduce network traffic.
This document discusses windows and content canvases in Forms Builder. It describes windows as containers that display content canvases, which are surfaces that hold visual objects. It explains how to create new windows and canvases, set their properties, display a form module across multiple windows and canvases, and use windows and canvases to modularize form contents.
This document discusses triggers in Oracle Forms Builder. It defines triggers as event-activated program units. It describes different trigger categories including block processing, interface events, and validation triggers. It outlines the key components of a trigger as the event that fires it, the PL/SQL code that executes, and the scope level (form, block or item). It also addresses setting the execution hierarchy to control trigger firing order.
This document provides instructions on creating non-input items in Oracle Forms, including display items, image items, buttons, calculated items, hierarchical tree items, and bean area items. It describes the properties and functions of each item type, and provides steps for creating examples of each type. The goal is to teach the reader how to identify non-input item types and create various kinds of static and dynamic content displays within Oracle Forms applications.
This document discusses run-time messages and alerts in Oracle Forms. It describes how to handle errors from built-in subprograms, control system messages, create alerts, and handle database server errors. Key points covered include using FORM_SUCCESS to check for errors, the four types of Forms messages, and built-ins for controlling messages and alerts like SET_ALERT_PROPERTY and SHOW_ALERT. It also addresses trapping database errors using triggers or exception handlers.
This document discusses writing flexible code in Oracle Forms. It describes flexible code as code that is reusable, generic, avoids hardcoded object names, and makes maintenance easier. It recommends using system variables and built-in functions to reference objects by ID or indirectly. This allows code to be written that is more efficient and generic. Specific techniques covered include using system variables for context, GET/SET properties functions, and functions like FIND and COPY to work with object IDs.
This document discusses navigation in Oracle Forms applications. It describes internal and external navigation, controlling navigation with object properties, and using navigation triggers. Key points covered include setting the first navigation block or item properties, writing pre- and post-triggers for forms, blocks, records and items, and using built-in navigation functions like GO_FORM and NEXT_RECORD in triggers. The summary reiterates that navigation can be controlled through properties or triggers, and outlines the different types of navigation triggers and built-ins that can be used.
This document discusses list of values (LOVs) and editors in Oracle Forms Builder. It describes how to create LOVs and editors manually or using wizards, set their properties, and associate them with text items in a form. LOVs provide dynamic lists for text items, pulling from a supporting record group or query. Editors override the default editor for text items to allow for custom formatting and functionality.
This document discusses creating and using triggers in Oracle Forms Builder. It describes the steps to create a trigger, including selecting a scope, invoking the trigger list, defining code in the PL/SQL editor, and compiling. Common trigger types like When-Button-Pressed and When-Window-Closed are described. The document also covers using built-in subprograms and variables in trigger code and limitations on certain built-ins.
This document discusses different types of input items in Oracle Forms, including check boxes, list items, and radio groups. It describes how to create each type by converting an existing item or using tools in the Layout Editor. Properties specific to each input type can be set, such as list elements for a list item or radio buttons for a radio group. Mapping other values allows non-listed values to be assigned an item display value. The overall goal is to learn how to create different input items that accept user input in Oracle Forms.
This document discusses query triggers in Oracle Forms. It describes the query processing steps, the different types of query triggers (pre-query and post-query triggers), and how to write triggers to screen and supplement queries. It also covers obtaining query information at runtime, overriding default query processing, and controlling trigger actions based on the form's query status.
This document discusses how to create a master-detail form in Oracle Forms. It describes establishing relationships between data blocks, defining join conditions, setting deletion properties, and modifying block structure and layout. Key points covered include using the Data Block Wizard to create relationships, automatic block coordination when running the form, and using the Layout Wizard and Data Block Wizard in reentrant mode to modify existing blocks. The overall goal is to teach the reader how to build a basic master-detail form and manage the relationships between related data.
This document discusses validation in Oracle Forms. It explains that Forms validates data at the form, block, record, and item levels. Validation occurs when the enter key is pressed or when a trigger leaves a validation unit. The document also discusses controlling validation through properties, triggers, and pluggable Java components, as well as tracking validation status. It provides examples of validating user input and using client-side validation.
The document provides an overview of the Oracle Forms Builder development environment. It describes Forms Builder components like the Object Navigator and Layout Editor. It explains how to navigate the Forms Builder interface, identify main form objects, customize Forms Builder sessions, use online help, and run forms. It also covers Forms modules types, setting runtime environment variables, and testing forms using the Run Form button.
This document discusses various methods for reusing objects and code in Oracle Forms, including:
- Using property classes to inherit properties and standardize objects
- Grouping related objects into object groups for easy reuse
- Creating object libraries to share reusable components between forms
- Marking objects as SmartClasses for rapid, standardized application
It also covers reusing PL/SQL code through copying, subclassing, and defining library program units to call code from multiple places.
The document discusses debugging triggers in Oracle Forms Builder. It describes the components of the Debug Console used for debugging, including the stack, variables, watch, form values, PL/SQL packages, and breakpoints panels. It explains how to run a form in debug mode, set breakpoints in client and stored code, step through code, and view variable values while debugging.
This document discusses how to create multiple form applications in Oracle Forms. It covers calling one form from another, defining shared functionality between forms, and sharing data among open forms through global variables, parameter lists, global record groups, and shared PL/SQL variables. The key benefits of multiple form applications are modularity, easier debugging, and improved performance and scalability.
This document discusses adding functionality to items in Oracle Forms through triggers and built-in functions. It covers using triggers to interact with checkboxes, lists, buttons, images and trees. It also discusses populating items from databases, files and Java beans. Built-ins allow accessing properties, invoking methods and handling events of Java beans from Forms triggers. The overall aim is to supplement the functionality of both input and non-input items.
This document discusses how to create a basic form module in Oracle Forms. It covers creating an empty form module, adding a data block using the Data Block Wizard and Layout Wizard, saving and compiling the form module, and different file formats. The key steps are creating an empty module, adding a data block manually or with wizards, saving the module, compiling it, and deploying it to the middle tier to run in a browser.
This document introduces Oracle Database 10g and relational database concepts. It outlines the goals of the course as retrieving and manipulating data using SQL statements. Key features of Oracle 10g include its object relational capabilities and support for multimedia data. Relational databases are based on tables that can be logically related using primary and foreign keys.
This document discusses working with text items in a form application. It describes how to create, modify, and add functionality to text items. Key points covered include describing text items, modifying appearance properties like font and color, controlling data properties, altering navigational behavior, enhancing the database relationship, and adding functionality through properties. The document provides an overview of the different properties and groups that can be used to customize text items and their interaction with data and users.
This document discusses working with text items in a form application. It describes how to create, modify, and add functionality to text items. Key points covered include describing text items, modifying appearance properties like font and color, controlling data properties, altering navigational behavior, enhancing the database relationship, and adding functionality through properties. The document provides an overview of the different properties and groups that can be used to customize text items and their interaction with data and users.
This document discusses designing and running reports in Oracle. It describes understanding user requirements, common report styles like tabular, master-detail and matrix, best practices for designing reports, supported file types, and different methods for running reports. The objectives are to identify user needs, describe report structures, run prebuilt reports, and optimize database access and reuse.
This document discusses working with text items in a user interface. It describes how to create, modify the appearance, control the data and navigation, enhance the database relationship, add functionality to, and display helpful messages for text items. Key topics covered include the different properties that can be modified in the property palette to control various aspects of text items such as appearance, data, navigation, and functionality.
The document discusses various file formats used for large-scale ETL processing with Hadoop, including text, JSON, sequence files, RCFiles, Avro, Parquet, and ORC files. It provides details on the features of each format in terms of schema evolution, compression, storage optimization, and performance for write, partial read, and full read operations. Test results show that column-oriented formats like Parquet and ORC provide faster query performance, especially when filters are applied. The best choice of format depends on the use case requirements around data types, schema changes, speed of writing versus reading, and tool compatibility.
The document discusses Java web services and related technologies. It provides an overview of service-oriented architecture (SOA) and web services standards like XML, SOAP, WSDL and UDDI. It also covers Java tools for working with XML and implementing RESTful web services in Java, as well as the business needs and technical challenges that web services address.
This document provides an overview of schema objects and how to manage them in a database. It defines schema objects as the logical constraints that define how data is organized in a relational database, including tables, fields, data types, and relationships. It describes how to create and modify tables, define constraints, create indexes, and use temporary tables. The key objectives covered are defining schema objects and data types, creating and modifying tables, defining constraints, creating indexes, and explaining the use of temporary tables.
This document provides an overview of Apex and Force.com development. It covers Apex language basics, data types, collections, exceptions, asynchronous execution, database integration, triggers, debugging, limits, and unit testing. Key topics include the similarities between Apex and Java, SOQL, DML statements, polymorphism in Apex, and the requirements to deploy code changes to production.
This document outlines the objectives and content of an Oracle database administration course. The course will cover installing, configuring, backing up, and monitoring an Oracle Database 10g Enterprise Edition database. It will also discuss Oracle's product line, relational database concepts like tables and fields, the structured query language used to access databases, and the primary tasks of an Oracle database administrator.
Core Data is Apple's object graph and persistence framework that allows developers to save model objects to files and retrieve them later. It provides automatic support for undo/redo operations and maintaining relationships between objects. Core Data uses a schema to describe model classes and their attributes and relationships. It allows managing just a subset of model objects in memory at once to conserve resources. Core Data has components like the managed object context, persistent store coordinator, and persistent store that work together to fetch, save, and manage model objects in an application's data layer.
HTML 5 defines the fifth major revision of HTML and reflects efforts to study contemporary HTML implementations and deployed content. It aims to address issues with previous specifications and enhance HTML to better support web applications. New features include enhanced semantics, multimedia elements like video and audio, client-side storage, and geographic location detection. Compatibility is ensured through supporting older HTML parsing but some features require checking browser support through methods like feature detection libraries.
HTML 5 defines the fifth major revision of HTML and reflects efforts to study contemporary HTML implementations and deployed content. It aims to address issues with previous specifications and enhance HTML to better support web applications. New features include enhanced semantics, multimedia elements like video and audio, client-side storage, and geographic location detection. Compatibility is ensured through supporting older HTML parsing but some features require checking browser support through methods like feature detection libraries.
The document describes the CoFX data model, which is the data model for the Cockpit Framework (CoFX). It provides an overview of the key elements of the model including entities, properties, relations, validation rules, permissions, actions, entity views, sets, and triggers. The model uses a TCQL expression language to define things like calculated properties, validation rules, and permissions.
Apache Sling provides RESTful access to content stored in an Apache Jackrabbit content repository. Sling uses a resource-centric approach where everything is represented as a resource that can be rendered in different formats. Resources map directly to nodes in the Jackrabbit content tree. Sling supports scripting languages like JSP and uses selectors, extensions and resource types to determine how each resource should be rendered. It allows composing page resources from multiple child resources.
SQL Server 2008 is a relational database management system and enterprise data platform. It includes components like the database engine, integration services, analysis services, and reporting services. The database engine efficiently stores, retrieves, and manipulates relational and XML data. SQL Server 2008 allows databases to be partitioned across multiple files for large tables. Other database objects in SQL Server 2008 include indexes, triggers, constraints, diagrams, and views.
We plan to cover the following:
-- Deep Dive into Dataweave 2.x and its Modules. by Aravind Babu Ramadugu
-- Exploring ETL use cases for Salesforce as target system using Mulesoft's Bulk API connectors and batch processing by Amresh Kosuru
The document discusses strategies for scaling massive Elasticsearch clusters to handle large volumes of data and queries. It covers techniques such as controlling shard and replica placement, indexing thousands of documents per second, querying data in tens of milliseconds, handling multilingual content, and monitoring cluster performance. The key approaches include configuring indices, shards, and replicas; routing documents and queries for optimal distribution; tuning refresh intervals and merge factors; and using tools to monitor nodes, queries, caching, and garbage collection.
NoSQL and SQL - Why Choose? Enjoy the best of both worlds with MySQLAndrew Morgan
Theres a lot of excitement around NoSQL Data Stores with the promise of simple access patterns, flexible schemas, scalability and High Availability. The downside comes in the form of losing ACID transactions, consistency, flexible queries and data integrity checks. What if you could have the best of both worlds? This session shows how MySQL Cluster provides simultaneous SQL and native NoSQL access to your data whether a simple key-value API (Memcached), REST, JavaScript, Java or C++. You will hear how the MySQL Cluster architecture delivers in-memory real-time performance, 99.999% availability, on-line maintenance and linear, horizontal scalability through transparent auto-sharding.
Introduction
Overview
The default item type in an Oracle Forms Developer application is the text item or field. You have seen how creating a new data block based on a table creates text items for each selected column from that table. This lesson shows you how to customize text items to change their appearance and behavior.
Text Items
A text item is an interface object through which you can query, insert, update, and delete data. A text item usually corresponds to a column in the database table. When an item is first created, its default type is text.
The item type determines the properties available in the Property Palette. In this lesson you look at the properties of a text item. Remaining item types are covered in subsequent lessons.
Use the Property Palette to define, alter, or examine the characteristics of items.
Creating a Text Item
You can create a text item by doing one of the following:
Converting an existing item into a text item
Using the Text Item tool in the Layout Editor
Using the Create icon in the Object Navigator
Using the wizards
How to Create a Text Item in the Layout Editor
1.Invoke the Layout Editor.It is important to point to the correct data block where you want to create the text item. In the Layout Editor, select the data block from the Block pop-up list.
2.Click the Text Item tool.
3.Click the canvas.The text item appears.
4.Double-click the text item.The text item Property Palette appears.
5.Set the item properties as required.
Creating a Text Item (continued)
How to Create a Text Item in the Object Navigator
1.Locate the block in which you want to create the item.
2.Select the Items node.
3.Click the Create icon.A new item entry is displayed in the Object Navigator.
4.Double-click the icon to the left of the new item entry.The Property Palette appears.
5.Set all item properties as required, keeping the Type property set to Text Item.
Note: To display an item at run time, you must assign the item to a canvas. Do this in the Property Palette of the text item by setting the Canvas property to the desired canvas.
Modifying the Appearance of a Text Item
The properties of an item are divided into several groups.
You can affect the way the text item is displayed by altering its General, Physical, Records, Font, and Color group properties. To view descriptions of any of these properties, click the property in the Property Palette and press [F1]. Some of these properties are:
General:
Item type: Selects the type of item you want to create (pop-up list)
Physical:
Visible: Determines whether the item is displayed
Canvas: Determines the canvas on which the item is displayed. If left unspecified, the item is said to be a Null canvas item, and will not display at run time or in the Layout Editor.
X and Y Position: Sets the X and Y coordinates of the item relative to the canvas
Width and Height: Sets the width and height of the item in the current form coordinate units
Bevel: Controls appearance of bevel around the item; can also be set to Plain (flat) or None
Modifying the Appearance of a Text Item (continued)
Records:
Current Record Visual Attribute Group: Specifies the name of the visual attribute to use when the item is part of the current record
Distance between records: Specifies the amount of space between instances of the item in a multirecord block
Number of Items Displayed: Specifies the number of item instances that are displayed for the item when the item is in a multirecord block
Modifying the Appearance of a Text Item (continued)
Visual Attributes: You set the Visual Attribute Group for an item or its prompt to specify how the visual attributes are derived (select DEFAULT or a named Visual Attribute).
Color: The properties in this section specify the foreground color, background color, and fill pattern for the item. You select these from color and pattern pickers.
Font: The properties in this section determine the font used for the item, along with its size, weight, style, and spacing. You can double-click the Font group to display a Font dialog enabling you to set all these properties at once, or you can click the individual properties to select each from an appropriate control, such as a pop-up list or LOV.
Note: When the form module does not contain any named visual attribute objects, the pop-up list for the Visual Attribute Group property shows only Default or Unspecified. An item that has the Visual Attribute Group property set to default, or that has individual attribute settings left unspecified, inherits those settings from the canvas to which it is assigned.
Modifying the Appearance of a Text Item (continued)
You can control the appearance of the prompt, or label, of a text item using properties in the following groups:
Prompt: You can set the prompt text and other properties, such as:
Display Style: Pop-up list with choices of First Record, Hidden, and All Records
Attachment Edge: Specifies the item edge to which the prompt is attached
Attachment Offset: Specifies the distance between the item and its prompt
Prompt Color: The property in this section specifies the foreground color for the item prompt. You can select this from a color picker.
Prompt Font: The properties in this section determine the font that is used for the item prompt, along with its size, weight, style, and spacing. You can double-click the Prompt Font group to display a Font dialog enabling you to set all these properties at once, or you can click the individual properties to select each from an appropriate control, such as a pop-up list or LOV.
Associating Text with an Item Prompt
The Forms Builder Layout Editor has a tool called Associate Prompt which enables you to create a prompt for an item using any boilerplate text displayed in the editor. To create a prompt-item association using the Associate Prompt tool, perform the following steps:
1.Open the Layout Editor window.
2.Select the item and boilerplate text you want as the item’s prompt in the editor.
3.Click the Associate Prompt tool.
4.If you are replacing an existing prompt, answer Yes to the dialog box.
Controlling the Data of a Text Item
The properties in the Data group of the text item are used to control the way data is displayed and entered. You can see descriptions of any of these properties by clicking the property in the Property Palette, then pressing [F1]. Some of these properties are:
Data Type: Enables you to choose CHAR, DATE, DATETIME, and NUMBER; the others listed are for backward compatibility.
Data Length Semantics: You can set to Null, BYTE, or CHAR to be compatible with multiple character sets. If Data Length Semantics is CHAR, the correct amount of storage will be automatically allocated as required for the Maximum Length with either a single-byte or multi-byte character set.
Maximum Length: Specifies the maximum length of the data value that can be stored in an item. If the Maximum Length exceeds the display width of the item, Forms automatically enables the end user to scroll horizontally.
Note: In the example on the slide, whether the form operator is using a single-, double-, or variable-byte character set, the right amount of storage is allocated. To hold the same value if the Data Length Semantics had been set to BYTE, the Maximum Length would have needed to be 5 for single-byte, 10 for double-byte, and an unknown value for a variable-byte character set.
Controlling the Data of a Text Item (continued)
Format Mask: You can specify any format mask that is valid for the data type.Use the Format Mask property to specify the format in which the user sees the item value.
Use standard SQL formatting syntax for dates and numbers; for example, DD/MM/YY and $99,999.99.
Enclose non-SQL standard embedded characters in double quotes; for example, hyphen (-) and comma (,).
Note: It is recommended that you avoid creating individual masks if the general purpose masks (see Lesson 1) will suffice.
FX Format Mask: The FX format mask in a date value ensures that the date is entered exactly as defined in the mask. Element D is for decimal and G is a group (thousands) separator. Example: With a date format of DD/MM/YY, valid entries are: 10/12/00, 10 12 00, 10-DEC-00, or 101200. You can enter any character to represent the (/) in the value. Allow for the embedded characters of the format mask when defining the Width property. The embedded characters are used only for display purposes and are not stored in the database.
Controlling the Data of a Text Item (continued)
Required: Specifies whether Forms will allow the item to have a null value. When you create a data block, Forms derives this value from the existence of a NOT NULL constraint on the database column, but you can change the value.
Lowest/Highest Allowed Value: Specifies range of accepted values
Initial Value: Specifies default value assigned to an item whenever a record is created; can be set to select from a sequence. Must be compatible with the item data type. If the Lowest/Highest Allowed values are specified, the initial value cannot be outside the range.
Controlling the Data of a Text Item (continued)
Creating an Initial Value
You can use any one of the following values to issue an initial item value whenever a new record is created:
Raw valueExample: 340, RICHMOND
System variable
Variables giving current application server operating system date/time:
Variables giving current database date/time:
Global variableExample: :GLOBAL.CUSTOMER_ID
Form parameterExample: :PARAMETER.SALES_REP_ID
Form itemExample: :ORDERS.ORDER_ID
SequenceThe initial value can reference a sequence in the database. Forms automatically writes generated sequence numbers into the text item. To use a sequence, enter: :sequence.<sequence name>.nextval.Example: :SEQUENCE.ORDERS_SEQ.NEXTVAL
Controlling the Data of a Text Item (continued)
Copy Value from Item: Specifies the source of the value that Forms uses to populate the item. When you define a master-detail relation, Forms Builder sets this property automatically on the foreign key item(s) in the detail block. In such cases, the Copy Value from Item property names the primary key item in the master block whose value gets copied to the foreign key item in the detail block whenever a detail record is created or queried.Note: The text item should disable input; otherwise, the user could violate the foreign-key relationship. To prevent this, set the Enabled property to No for the foreign-key item, or do not display it at all.
Controlling the Data of a Text Item (continued)
Synchronize with Item: Specifies the name of the item from which the current item should derive its value and synchronizes the values of the two items, so that they effectively mirror each other. When the end user or the application changes the value of either item, the value of the other item changes also.
Controlling the Navigational Behavior of Text Items
You can see the default navigational sequence of items in the Object Navigator, as the item entries are displayed in the navigational order. However, you can also use the Navigation group properties to control the navigational behavior of a text item.
Note: The next or previous navigation item must be in the same data block as the current item.
Enhancing the Relationship Between Text Item and Database
You can alter or enhance the way in which a text item interacts with its corresponding database column by setting the Database group properties. Some of these are:
Database Item: Indicates whether the item is a database column
Query/Insert/Update Allowed: Controls whether DML operations are allowed
Query Length: Specifies the maximum length of query criterion in Enter Query mode
Case Insensitive Query: Controls whether case is recognized in query processing
Note: When you create an item in a data block, Forms Builder assumes that the item is a data item, sets its Database Item property to Yes, and automatically includes it in any SELECT, UPDATE, and INSERT statements issued to the database. If an item that you are creating is a control item, you must explicitly set its Database Item property to No.
Adding Functionality to a Text Item
Augment the default functionality of a text item by introducing some of the additional features you can set in the Functional group of the Property Palette. Some of these are depicted above or will be discussed in the next few pages. For descriptions of other properties in the Functional group, select the property in the Property Palette and press [F1].
Note
The Enabled property set to No grays out the item. If you want the item to appear normally but do not want the users to change it, do the following:
Set Insert Allowed to No.
Set Update Allowed to No.
Set Enabled to Yes.
A pop-up menu is a context-sensitive menu that enables users to access common functions and commands quickly. It is a top-level object in the Object Navigator and belongs to a form module (as opposed to a form menu, which belongs to a separate menu module).
Adding Functionality to a Text Item (continued)
Conceal Data: Hides characters that the operator types into the text item. This setting is typically used for password protection. Choose Yes to disable the echoing back of data entered by the operator; with this setting, the entered value displays as an asterisk for each character entered.Note: Conceal Data set to Yes is valid only for single-line text items.
Setting Keyboard Navigable and Enabled Properties
You can set the Keyboard Navigable and Enabled properties for items to specify whether operators can navigate to and interact with them. The Enabled property determines whether end users can use the mouse to manipulate an item. The following table describes the behavior of combinations of these settings:
Adding Functionality to a Text Item (continued)
Multi-Line: Determines whether the text item displays in a single-line or multi-line region. Use multi-line text items to display and/or edit such items as addresses, comments, or descriptions. The data in a multi-line text item must be of Char, Alpha, or Long datatype, not numeric or date.
Setting the Multi-Line property to Yes enables a text item to store multiple lines of text, but it does not automatically make the item large enough to display multiple lines. It is up to you to set the Width, Height, Font Size, and Maximum Length properties to ensure that the desired number of lines and characters are displayed.Note: Setting right or center justification for scrollable text items may result in values being hidden from the user.
Wrap Style: For multi-line text items, specifies how text is displayed when a line of text exceeds the width of a text item or editor window.
Displaying Helpful Messages
You can use the Help group properties to provide context-sensitive help to users:
Summary
This lesson showed you how to create and modify a text item that Forms Builder creates for each column flagged for inclusion in a data block.
Summary (continued)
In particular, text items have properties that enable you to do the following:
Modify their appearance
Control the data stored in the item
Alter navigational behavior
Enhance the relationship with the database
Add functionality
Include Help information
Practice 7 Overview
In this practice session you will create text items, alter the behavior and the appearance of text items, and delete text items.
Delete the region ID item in the CUSTOMERS form.
Using the Property Palette, change the properties of several text items in the CUSTOMERS data block to change their run-time appearance. Save and run the form after the changes are applied.
In the ORDERS form, create new text items to hold the customer name and sales rep name values in the ORDERS block, and set the suggested properties. Change additional text item properties in the ORDERS, ORDER_ITEMS, and INVENTORIES data blocks to change their run-time appearance and behavior. Save and run the form after the changes are applied.
Note: For solutions to this practice, see Practice 7 in Appendix A, “Practice Solutions.”
Practice 7
CUSTGXX Form
1.Remove the NLS_Language and NLS_Territory items.
2.Make sure that the Phone_Numbers item accepts multi-line text to display. The database column is long enough to accept two phone numbers if the second one is entered without “+1” in front of the number.
3.Automatically display a unique, new customer number for each new record and ensure that it cannot be changed. Use the CUSTOMERS_SEQ sequence.
4.In the CUSTGXX form, resize and reposition the items. Add the boilerplate text Customer Information. Reorder the items in the Object Navigator. Use the screenshot as a guide.
5.Save and compile your form.Click Run Form to run your form and test the changes. Note: The entire form may not be visible at this time. This will be addressed in a later lesson.
Practice 7 (continued)
ORDGXX Form
6.In the ORDERS block, create a new text item called Customer_Name.Ensure that Customer_Name is not associated with the ORDERS table.Do not allow insert, update, or query operations on this item, and make sure that navigation is possible only by means of the mouse. Set the Prompt text to Customer Name. Display this item on CV_ORDER canvas.
7.In the ORDERS block, create a new text item called Sales_Rep_Name.Ensure that Sales_Rep_Name is not associated with the ORDERS table.Do not allow insert, update, or query operations on this item and make sure that navigation is possible only by means of the mouse. Set the Prompt text to Sales Rep Name. Display this item on the CV_ORDER canvas.
8.Set the relevant property for Order_Date, so that it displays the current date whenever a new record is entered.
9.In the ORDER_ITEMS block, create a new text item called Item_Total.Ensure that Item_Total is not associated with the ORDER_ITEMS table.Do not allow insert, update, or query operations on this item and make sure that navigation is possible only by means of the mouse. Allow numeric data only and display it by using a format of 999G990D99.Set the Prompt text to Item Total. Display this item on the CV_ORDER canvas.
10.Justify the values of Unit_Price, Quantity, and Item_Total to the right.
11.Alter the Unit_Price item, so that navigation is possible only by means of the mouse, and updates are not allowed. Set its format mask to be the same as that used for Item_Total.
12.In the ORDGXX form, resize and reposition the items according to the screenshot and the following table.
Practice 7 (continued)
13.In the INVENTORIES block, alter the number of instances of the Product_ID, so that it is displayed just once. Make its prompt display to the left of the item.
14.Arrange the items and boilerplate on CV_INVENTORY, so that it resembles the screenshot.Hint: Set the Update Layout property for the frame to Manually.
15.Save, compile, and run the form to test the changes.