Abstract: A thumbnail preview of a file enables a user to recognize the file without opening it. An algorithmic approach to generating simulated thumbnail previews is provided. This approach includes executing rules for determining and implementing one or more rendering schemas to simulate different content types within a portion of a file. A simulated thumbnail preview is generated from the simulated content types based on a file structure. Since users may rely on the general structure and distinguishing content elements of a thumbnail for recognizing a file, these distinguishing elements are maintained based on different rendering schemas used to create a simulated thumbnail. Moreover, the algorithmic approach promotes consistent simulated thumbnails across clients, regardless of client processing capabilities, form factors, customized theming, or the like. Based on the rules for rendering various content types, the simulated thumbnails are also consistently generated across documents.

Abstract: A thumbnail preview of a file enables a user to recognize the file without opening it. An algorithmic approach to generating simulated thumbnail previews is provided. This approach includes executing rules for determining and implementing one or more rendering schemas to simulate different content types within a portion of a file. A simulated thumbnail preview is generated from the simulated content types based on a file structure. Since users may rely on the general structure and distinguishing content elements of a thumbnail for recognizing a file, these distinguishing elements are maintained based on different rendering schemas used to create a simulated thumbnail. Moreover, the algorithmic approach promotes consistent simulated thumbnails across clients, regardless of client processing capabilities, form factors, customized theming, or the like. Based on the rules for rendering various content types, the simulated thumbnails are also consistently generated across documents.

Abstract: Systems and methods for creating and updating digital notes. One system includes an electronic processor configured to receive an electronic message from a user to an electronic messaging address, the electronic message including content and determine whether the electronic messaging address is associated with the user. In response to the electronic messaging address being associated with the user, the electronic processor is configured to automatically create a digital note including at least a portion of the content included in the electronic message. The electronic processor is also configured to receive a reply to the electronic message from the user and automatically update the digital note based on the reply.

Abstract: Systems and methods for creating and updating digital notes. One system includes an electronic processor configured to receive an electronic message from a user to an electronic messaging address, the electronic message including content and determine whether the electronic messaging address is associated with the user. In response to the electronic messaging address being associated with the user, the electronic processor is configured to automatically create a digital note including at least a portion of the content included in the electronic message. The electronic processor is also configured to receive a reply to the electronic message from the user and automatically update the digital note based on the reply.

Abstract: Embodiments are provided for creating and reusing custom data types in a database. A selection of a field or group of fields may be received from a database table in the database by a database software application executing on a computer system. Each selected field may include a set of field properties. The application may further receive a user input to initiate saving the selected field or group of fields as a custom data type. In response to receiving the input, the application may be configured to generate a dialog for receiving custom data type information for the selected field or group of fields and save the selected field or group of fields as a custom data type. The custom data type may then be reused by the application in the database.

Abstract: Embodiments are provided for creating and reusing custom data types in a database. A selection of a field or group of fields may be received from a database table in the database by a database software application executing on a computer system. Each selected field may include a set of field properties. The application may further receive a user input to initiate saving the selected field or group of fields as a custom data type. In response to receiving the input, the application may be configured to generate a dialog for receiving custom data type information for the selected field or group of fields and save the selected field or group of fields as a custom data type. The custom data type may then be reused by the application in the database.

Abstract: Embodiments provide a distributed file fuzzing environment. In an embodiment, a number of computing devices can be used as part of a distributing fuzzing system. Fuzzing operations can be distributed to the number of computing devices and processed accordingly. A group or team can be defined to process particular fuzzing operations that may be best suited to the group. The time required to perform a fuzzing operation can be reduced by distributing the fuzzing work to the number of computing devices. A client can be associated with each computing device and used in conjunction with fuzzing operations.

Abstract: Embodiments are provided for creating and reusing database forms and reports. A selection of an object may be received from a database by a database software application executing on a computer system. The object may include a form or a report. The application may further receive an input to initiate saving the selected object as a new form template or a new report template. In response to receiving the input, the application may be configured to generate a dialog for receiving the selected object and save the selected object as a new form template or a new report template. Any controls, sub-forms, sub-reports, properties, macros, code, and object model references which may be included in the selected object are persisted in the newly created templates for reuse.

Abstract: Embodiments are provided for creating and reusing custom data types in a database. A selection of a field or group of fields may be received from a database table in the database by a database software application executing on a computer system. Each selected field may include a set of field properties. The application may further receive a user input to initiate saving the selected field or group of fields as a custom data type. In response to receiving the input, the application may be configured to generate a dialog for receiving custom data type information for the selected field or group of fields and save the selected field or group of fields as a custom data type. The custom data type may then be reused by the application in the database.