Abstract: An integrated development environment (IDE) leverages a generative AI model to generate industrial control code in accordance with specified functional requirements, which can be provided to the industrial IDE system as intuitive natural language spoken or written text. The industrial IDE can also analyze written code in response to natural language prompts submitted against the code, generate answers to user-submitted questions about the code, and offer recommendations for improving the code in response to specific questions or requests submitted by the user.

Abstract: Generating a report involves phases such as (a) database queries or other raw data accesses, (b) calculations such as data grouping, sorting, filtering, aggregation, (c) data presentation layout, (d) data formatting, and (e) rendering. When generating a modified version of a report, reusable interim results for phases (b), (c), and (d) are identified and retrieved from a cache instead of being recalculated. Newly calculated interim results are also cached for possible future use.

Abstract: User values and selections are collected and provided to a report server that customizes a generically defined report pursuant to the user values and selections. An ordered set of report parameters is declared in the definition of a report and then this parameter definition is used to drive user prompting and execution of the report. As parameter values are collected in sequence order, a value retrieved or specified by the user for one parameter may be used to generate the set of the allowed values or default value of a parameter later in the sequence. Parameters are dynamically presented to the user. After values for all parameters been retrieved or specified, a report is generated by the report server.

Abstract: Various technologies for processing a selection on an item on a report. In one implementation, a request to perform an action on the item may be received. Whether one or more actions corresponding to the item exist based on one or more parameters and one or more values of the parameters associated with the item may be dynamically determined. A list of one or more actions may be displayed if the one or more actions exist.

Abstract: Various technologies and techniques are disclosed that improve the retrieval or interaction with data in databases. A database has one or more tables with compound keys. An entity key that is a single composite key of each of the compound keys is generated via an invertible composition transformation. The composite entity key is a binary serialization of the respective compound keys. The composite entity key is used by separate applications to interact with the database instead of the respective underlying compound keys. The composite entity key is decomposed into the underlying compound keys when a particular database operation needs to be performed. The results are then returned to the separate application with the composite entity key.

Abstract: Grouping and regrouping of data using aggregation is disclosed. In one aspect of this disclosure, data can be grouped based on some expressions, and then this result can be regrouped based on other expressions which may utilize aggregates computed in the context of the first group. Such regrouping is performed on a group basis—as opposed to being regrouped, for example, on a row basis. The grouping and regrouping can employ various logical expressions that may incorporate the aggregates. Moreover, regrouping of regrouping can be performed, and the mentioned logical expressions can be based on groups of various scopes.

Abstract: Mechanisms are provided for completing partially specified paths. For example, users can partially specify paths by specifying some preferred entities and roles along the paths so that these paths have to incorporate these preferred entities and roles. From then, queries can automatically complete the paths, unless more specification information is needed. In completing these paths, numerous restrictions can be used, such as a role and its inverse cannot be used in a path, and no role may be traversed more than once in a path.

Abstract: End user sorting and filtering of data extracted for report processing can be performed. That is, data can be filtered or sorted subsequent to the execution of underlying queries performed to extract data from a data source. A user can sort or filter data by selecting a set of data values using a filter or sort control attached to a header or to a data field. The scope of effect of the filter or sort within the report may be specified. That is, a specified filter or sort may act locally or may apply globally. Filtering or sorting may apply to other regions of data linked to the filtered or sorted data region according to the specified scope of the filter. A filter or sort may apply to each row of data in the data set, to each row of data in the data region, to each instance of a group or to one or more sets of data.

Abstract: A preferred path between two selected entities is determined. Initially, there is provided a representation of the data structure in the form of a plurality of entities having relations between them indicative of roles and the relations reflecting a cardinality of one of a one-to-one, one-to-many and a many-to-one relationship between the entities. A query is entered that provides an indication of a first selected entity and a second selected entity. A preferred path is selected through the entities and relations that couples the first selected entity to the second selected entity. The preferred path is selected from a plurality of paths as a function of the number of changes in cardinality along the plurality of paths and a indicator indicative of a preferred role relating two entities.

Abstract: Systems and methods for declaratively controlling the visual state of items in a report allow the visual state of any report item to be toggled from any other item. A set of declarative metadata may be associated with a report item. The declarative metadata may identify an initial visual state of the item, whether the item is a control item, and if so which other items are controlled from the item. The declarative metadata may further identify an initial visual state of a control image associated with a control item. Report processing software can initially display a report in accordance with the initial visual state specified in the declarative metadata. When a control item is activated, the software can change the visual state of identified items, as well as the visual state of the corresponding control image.

Abstract: Systems and methods for supporting custom report layouts allow features that may be available to supported report layouts to also be made available to custom layouts. A custom layout definition may first meet a set of report definition criteria so that it is recognizable to report processing software. A design tool is provided that may be used to create such a custom layout definition. The custom layout may then be passed to report processing software. The report processing software can initially process the custom layout, and provide it with any features available in the initial processing stage. The reporting software may provide an interface for custom processing of the custom layout. The interface may be accessible to custom layout builder objects. Custom layout builder objects can be designed to use the report building components provided through the interface to build a custom report layout.

Abstract: A plurality of scope declarations can be provided to delineate various portions of any data structure, such as a matrix, a table, or a chart. Some scope declarations may correspond to portions of a horizontal axis, or columns, while other scope declarations may correspond to portions of a vertical axis, or rows. Thus, the aggregate scope at any given location within a data structure may vary, depending on which scope declarations overlap at the given location. Properties can be set for a location of a data structure based on this aggregate scope, thereby providing increased control flexibility.

Abstract: On-line or computer based document generation and consumption has become as common, or more so, than paper based document generation and consumption. With the move away from paper there is no longer the physical restriction of the paper on which a document may be printed. It is still desirable, however, to break documents into readable pages. We allow a selection of logical page breaks at locations that are deemed convenient, also allow for selection of approximate page dimensions for pages within each logical section. Because these pages are approximate, pagination is less computationally expensive than fixed pagination. Moreover, many of the appearance problems that plague fixed pagination dissolve.

Abstract: Columns and/or rows of a report can be declaratively defined as either dynamic or static. The declarative definition can be represented by any marking. If a column or row is declaratively designated as dynamic, it can be expanded into a plurality of columns or rows. If a column or row is designated as static, it remains as a single column or row to represent only the specified column or row data. Subgroups of columns and rows can also be declaratively defined as dynamic or static. A static column or row may contain no sub-columns/rows, or it may contain a plurality of static columns/rows, a plurality of dynamic columns/rows, or any combination of both. Similarly, a dynamic column or row may also contain the above combinations.

Abstract: User values and selections are collected and provided to a report server that customizes a generically defined report pursuant to the user values and selections. An ordered set of report parameters is declared in the definition of a report and then this parameter definition is used to drive user prompting and execution of the report. As parameter values are collected in sequence order, a value retrieved or specified by the user for one parameter may be used to generate the set of the allowed values or default value of a parameter later in the sequence. Parameters are dynamically presented to the user. After values for all parameters been retrieved or specified, a report is generated by the report server.