Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error.

QueryLayout Object

PointsWell

Would anyone else find a QueryLayout Object useful?

What is this?

At the moment a query consists of two parts combined into one - FIND and then a UI Layout

Because this is encapsulated into a single object then minor modifications of that Query require completely new Queries

For example

FIND Car WHERE Car.Doors=4
FIND Car WHERE Car.Doors=4 AND Car.Wheels="Alloy" (* see below for disclaimer)

If both of these queries show a grid that contains

Panel Header Text
Car.Make, Car.Model, Car.Colour, Car.Doors, Car.Wheels | Operation on Record1, Operation Record2
Footer {Count Cars}

Then you decide that the order has to change and you want a new Panel Operation, then there are multiple touch points that have to be made. You can either copy the FIND statement modify one of the Grids and then copy the Query and then replace the FIND (which has to be done in a very specific order to prevent AIM correctly renaming things that reference the query) or manually touch every grid. This was covered in



hpl123

1+ for something like this.


PointsWell

Implemented as DISPLAY BO WHERE X,Y,Z USING QueryName


hpl123

PointsWell wrote

Implemented as DISPLAY BO WHERE X,Y,Z USING QueryName

What exactly is implemented? I can't remember the initial FR and now when reading it through, I don't fully understand what is implemented and how it works. Is this new functionality documented and possibly with an example somewhere?


PointsWell

hpl123 wrote
PointsWell wrote

Implemented as DISPLAY BO WHERE X,Y,Z USING QueryName

What exactly is implemented? I can't remember the initial FR and now when reading it through, I don't fully understand what is implemented and how it works. Is this new functionality documented and possibly with an example somewhere?

DISPLAY when used with a BO gives an arbitrary query output now you can define USING and refer to another query layout to display a defined layout. The documentation exists under PICK FROM as it works with both


hpl123

PointsWell wrote
hpl123 wrote
PointsWell wrote

Implemented as DISPLAY BO WHERE X,Y,Z USING QueryName

What exactly is implemented? I can't remember the initial FR and now when reading it through, I don't fully understand what is implemented and how it works. Is this new functionality documented and possibly with an example somewhere?

DISPLAY when used with a BO gives an arbitrary query output now you can define USING and refer to another query layout to display a defined layout. The documentation exists under PICK FROM as it works with both

Ok, now I understand, thanks.


nhofkes

It seems that the implementation on the basis of 'DISPLAY BO WHERE X,Y,Z USING QueryName' is not yet fully equal to defining a separate query that contains the same search criteria.

I found that any applicability conditions that are defined for row operations and (most likely) the presentation rules that may be defined for an attribute in the grid, are not evaluated when using DISPLAY BO USING QueryName. This is visible both in the output as well as in the Tomcat log file. So, to the extent that QueryName has such applicability conditions and/or presentation rules, those will be ignored when the query is used as the presentation for the data selected by the DISPLAY BO statement.

I hope that it is possible to incorporate this in a future update, so that the same grid will look exactly the same regardless whether it is displayed as the original query or by DISPLAY BO USING Query. This would bring us another step further towards decoupling the definition of the query data from the presentation thereof.