Improved creation of object headers

 

TE Core has always had two ways of creating or adjusting object headers:

  • Dragging a type from the selection list makes the header display all objects of that type
  • Dragging a single object from the object list and dropping it on the header adds the object to the header. Right-clicking an object in the header provides the option to remove it

In TE Core 2.275, we are making it much easier to create a header with a certain set of objects.

Ska_rmavbild_2020-12-07_kl._08.33.19.png

When the active calendar has an object header, an extra button appears next to the object list.

Ska_rmavbild_2020-12-07_kl._08.34.19.png

 

This button allows you to send all the objects currently in the object list to the object header. Clicking it, you get the option of either setting the object header to display the set of objects, or to add the objects to the set currently being displayed.

 

Ska_rmavbild_2020-12-07_kl._08.36.08.png

Ska_rmavbild_2020-12-07_kl._08.37.30.png

This, in turn, means that you can make an object header reflect whichever search you can create in the object list with just two clicks. And, you can easily build an even more complex header by adding the result of multiple searches to the same header.

 

Limitations

Sending more than a hundred objects to a header is not recommended, mainly for performance reasons. If you absolutely must send a list of, say, 300 objects to a header, scrolling through the list before sending can improve results (by giving them a chance to load before being sent to the header).

 

If  creating headers with this many objects is something you would frequently like to do, please tell us in a support ticket so we can take it into account when planning future development.

 

This feature doesn’t support calendars with multiple object headers - the objects will be sent to all object headers at once which is most likely not what you expect. Again, please tell us in a support ticket if this is a use case you would like to see supported in the future.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.