Glossary of Terms

GLOSSARY: FILEMAKER PLATFORM

• Authentication – The process of checking the validity of an account and password (if one is defined) before assigning privileges and allowing access to a system or a file. An account authenticated via FileMaker Pro or FileMaker Server is referred to as a FileMaker account. (FileMaker Server can also authenticate an account via External Server — an external authentication system such as Apple Open Directory, or a Windows domain.)
• Commit – To save changes to a file. Certain actions such as navigating between records, finding, and sorting do not change the file’s modification date. Other actions such as changing data in a record or changing a layout do change the file’s modification date.
• Client – A user that opens a file that is shared on a network, published in a browser, or shared via ODBC/JDBC. FileMaker Network settings and privileges determine how FileMaker Pro and FileMaker Go clients interact with files hosted through FileMaker Pro, and FileMaker Server.
• Client Application – The application that requests data (using SQL) from a data source (using ODBC or JDBC). Also, FileMaker Pro is a client application when it accesses a file hosted by FileMaker Server.
• Database – The arrangement of tables and fields and their interrelationships in a file.
• Database Encryption – A form of encryption that protects “data at rest.” For FileMaker, data at rest is a FileMaker Pro file, and its temporary files, while it is being stored on disk (and not open). An encrypted file is protected from unauthorized access with an encryption password. FileMaker Pro Advanced is required to encrypt files. Encrypted files can be decrypted and re-encrypted as needed.
• Field – The basic unit of data in a record. You define a field to hold a specific, discrete category of data, such as Last Name, Employee Photo, or to display the result of a calculation. You can define text, number, date, time, timestamp, container, calculation, and summary fields. Field can also refer to the object on a layout that displays the data, such as an edit box, checkbox set, or pop-up menu.
• FileMaker WebDirect – A web application for accessing layouts from files in a web browser. Web clients use FileMaker WebDirect to access layouts from files hosted by FileMaker Server.
• Full Access privilege set – One of the three predefined privilege sets that appear in every file. The Full Access privilege set allows complete read/write access to a file, including making changes to privileges for the file.
• Function – A predefined, named formula that performs a specific calculation and returns a single, specific value.
• Global Field – A field defined with the global storage option can contain one value that’s used for all records in a file. Use the value of a global field as a fixed value in calculations, to declare variables in If or Loop script steps, or for fields that rarely need to be updated (for example, a company logo in a container field). A global field can be any field type except summary. A global field can’t be indexed.
• Host – After a file has been opened and enabled for sharing, the host is either the first FileMaker Pro user to share the file, or the host is FileMaker Server. Once the host opens the file, other users (clients) can access and change the file. All changes are stored in the file on the computer or device where the file resides. FileMaker Network settings and privileges determine how FileMaker Pro and FileMaker Go clients interact with files hosted through FileMaker Pro or FileMaker Server.
• Layout – An arrangement of fields, objects, pictures, and layout parts that represents the way information is organized and presented when you browse, preview, or print records. You can design different layouts for entering data, printing reports and mailing labels, displaying web pages, and so on.
• Layout Theme – A collection of coordinated styles that determine the color, object, part, and background attributes, and the fonts used on a layout. Themes also enhance the appearance of a layout or report and give all your layouts a consistent look. A theme does not control the placement or behavior of fields or objects on a layout. A theme is assigned when you create a new layout, but you can change the theme in Layout mode. You can also create a theme by changing the styles used for the layout, and then saving the theme with a new name.
• Layout Types – FileMaker Pro includes several predefined types of layouts and reports to display on different types of devices (such as laptop computer screens or touch device screens), for different purposes (such as browsing records, entering data, or printing reports, mailing labels, or envelopes). After you choose a layout type, you can make additional choices.
• Popover – A layout object that can contain other layout objects. Popovers include a content area (where objects are placed) and can include a title. You open a popover by clicking a popover button. Popovers reposition on the screen as needed to stay in view.
• Relationship – Relationships provide access to data from one table to another. Relationships can join one record in one table to one record in another table, one record to many other records, or all records in one table to all records in another table, depending on the criteria you specify when you create the relationship in the relationships graph.
• Schema – In database terminology, a schema is the organization of the tables, the fields in each table, and the relationships between fields and tables.
• Script – One or more instructions (script steps) that you define to automate repetitive or difficult tasks. You create and manage scripts using the Script Workspace window. You run a script by clicking its button, choosing its menu command, calling it from another script or a plug-in, or running it at startup or when a file closes.
• Security – The protection that’s placed on a file. Security includes various types of accounts to authenticate users, levels of privilege sets to determine what can be done with a file, and authorization of other files to create references to the current file (including its tables, layouts, scripts, and value lists). Security also includes extended privileges, which determine the data sharing options that are permitted by a privilege set.
• Solution – A file or a set of files containing database tables, layouts, scripts, and associated data. A solution solves one or more specific problems, such as tracking customers or invoices.
• Value List – To save time and ensure accuracy during data entry, define frequently used text, number, date, or time values as a value list. When you enter data, you can choose from the list of defined values. You can format value lists to display in a drop-down list or pop-up menu, or as checkboxes or option (radio) buttons. The values in a value list can be user-defined or based on the values in a field in the same file or in a different file. You can also define relationships for use with value lists, to access and display particular related values. Another option is to use a value list from another file.
• View – An arrangement of your data primarily useful for onscreen manipulation. In Browse mode, Find mode, or Preview mode, Form View displays individual records, List View displays records in a list, and Table View displays records in a spreadsheet-like table format.
• Web Server – A computer that is connected to the Internet or an intranet and has a web server application installed on it. Web server applications deliver web pages and associated files to web browsers.

GLOSSARY: CUSTOM APP DEVELOPMENT TERMS

• Bug – a coding error in a computer program.
• Change Request – a request for a modification of an existing software feature.
• Debugging – the process of locating and fixing or bypassing bugs (errors) in computer program code or the engineering of a hardware device.
• Delivery – a document, service, or product that provided to client– often fulfilling the terms of a work-order or contract.
• Demo – a meeting or presentation of a software program or process (partial or complete).
• Development Environment – the system of software and hardware assets used for developing a software product/system. Usually constructed to simulate the Production Environment where a similar system of software and hardware are actively used by an organization to do their work.
• Double Entry Testing – a method of software testing where users simultaneously enter and process data in two software applications (usually an established/old software program and a new software program that will replace the old version).
• Go Live – the process of preparing and releasing a new version of software.
• Hackathon – A hackathon, also known as a codefest, is a social coding event that brings computer programmers and other interested people together to improve upon or build a new software program.
• Milestone – a point in the development process used to track progress.
• Product Scope – the functions and features that characterize a software product or service.
• Production Environment – the system of software and hardware assets used by an organization to service it’s clients/staff IT needs
• Project Kick-off – The formally recognised start of a project. Usually accompanied by a meeting to present the development plan, schedule, and to set expectations.
• Project Scope – the common understanding among stakeholders about what goes into a project and what factors define its success. A project’s scope is made up of the functionalities or specifications outlined in the requirements.
• Quality Assurance (aka QA) – product testing to ensure that a program or process is working as expected.
• Release – A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.
• Screenshot – a digital image capture of a computer display.
• Software Testing – Software testing is a method of assessing the functionality of a software program. There are many different types of software testing but the two main categories are dynamic testing and static testing.
• Staging Environment – the environment or software assets used to simulate the production environment (pre-release).
• Stakeholder Interview – Conversations with the key contacts in the client organisation funding, selling, or driving the product.
• Test Case – an example scenario of the expected & correct outcome of a particular process.
• User Interface – everything designed into an information device with which a human being may interact — including display screen, keyboard, mouse, light pen, the appearance of a desktop, illuminated characters, help messages, and how an application program or a Web site invites interaction and responds to it.
• Use Case – A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. In this context, the term “system” refers to something being developed or operated, such as a mail-order product sales and service Web site. Use case diagrams are employed in UML (Unified Modeling Language), a standard notation for the modeling of real-world objects and systems.
• Wireframe – A rough guide for the layout of a website or app, either done with pen and paper or with wireframing software.
• Workflow Diagram – A graphical representation of activities and actions conducted by users of a system. (Sometimes called an activity diagram.)