Maximo Anywhere supports the OSLC WHERE clause.
The criteria in an OSLCWHERE clause have a standard format that comprises an attribute,
an operator,
and a constant. For example, the following WHERE clause can be added to the additionallocations lookup resource to retrieve locations in SITE A only:
The where clause includes the following items:
siteidAn attribute of the additionallocations lookup resource.
=
A comparison operator that expresses equality. No spaces are allowed before or after comparison operators.
SITE AA constant that expresses the site value criteria for matching location records.
The criteria in a WHERE clause are typically based on attributes of the lookup resource to which the WHERE clause applies. However, a WHERE clause can also include criteria that are based on system resource attributes. For example, the following WHERE clause finds the mylaborcraftrate resource for the labor record that is associated with the current user. The labor record for the current user is given as [${
mylabor.
laborcode}], where
laborcode is
an attribute of the mylabor system resource. spi:defaultcraft is an attribute of the mylaborcraftrate system resource:
You must not create circular references in WHERE clauses that use attributes from other resources. For example, if the WHERE clause for resource A uses
an attribute from resource B, the where clause for resource B must not use an attribute from resource A.
The application XSD cannot validate the content of the
element. If you add WHERE clauses to the lookup resources in an application definition file,
you must test the updated runtime application before you deploy it to a production environment.
Share with your friends: