Announcement

Collapse
No announcement yet.

Hijack the Business Monitor Servlet to Run Custom Saved Queries as Menu Links

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hijack the Business Monitor Servlet to Run Custom Saved Queries as Menu Links

    To design process-driven user experiences, we often configure menu structures using 'Results First' Screen Sets having Default Criteria which limit the display of results to specific business objects (e.g. "Unplanned Order Releases").

    This works very well as long as there is a simple set of selection criteria with all of the fields to be checked in the primary table of the queried object.

    But what to do when you encounter a more complex set of selection criteria, requiring additional tables to be queried or conditional logic?

    Here we can exploit the functionality of the Servlet used to display Business Monitor Query results which allows for the specification of custom, non-Finder Saved Queries for the display of a result set.

    The setup is really easy. When defining the Menu Link, select 'External URL' as the link type and use the following formatting to enter the value in the External URL field:
    glog.webserver.businessmonitor.LaunchSavedQuerySer vlet?saved_query_gid=<SAVED_QUERY_XID>&finder_set_gid=<FINDER_SET_GID>&query_table_gid=<OBJECT_TABLE_NAME>

    Here is an example of an entry:
    glog.webserver.businessmonitor.LaunchSavedQuerySer vlet?saved_query_gid=SELECT_TARGET_ORDER_RELEASES& finder_set_gid=DOMAIN.CUSTOMER_ORDER_RELEASE&query _table_gid=ORDER_RELEASE

    And that's it-- your own custom SELECT statements run from a Menu Link!

  • #2
    Re: Hijack the Business Monitor Servlet to Run Custom Saved Queries as Menu Links

    Two things to be take notice of, if using the above.

    1. The otmfaq forum software is strangely inserting a space in the URL segment ("LaunchSavedQuerySer vlet" should be "LaunchSavedQueryServlet"). Copy-pasters beware!

    2. The url parameter named "saved_query_gid" actually requires the Saved Query XID (no Domain specification). Looks like a developer error.

    Comment

    Working...
    X