If, after upgrading Maximo Application Suite v9.1.x (patch version), you encounter the following error (please see error below) in Maximo Application Framework Configuration when attempting to save the app.xml file. It may indicate that the graphite-configuration deployment definition was not properly updated to the latest version.

Error Message:
XML code is invalid: app.xml
The property (...) is used for (...) but it is not defined in the registry. Valid properties are: (...) 

Example Error:

XML code is invalid: app.xml
The property 'on-drill-in' is used for 'lookup-with-filter' but it is not defined in the registry. Valid properties are: id, lookup-attributes, on-open-action, on-open-action-arg, on-primary-action, on-primary-action-arg, on-secondary-action, on-secondary-action-arg, on-item-click, on-item-click-arg, on-close-action, on-close-action-arg, show-search, search-placeholder, width, controller, datasource, lookup-heading, lookup-subheading, column-picker-label, show-count, on-close, on-close-arg, enable-barcode-scanner, enable-nfc-scanner, readers, timeout, hierarchy-drill-in, tree-name, tree-label-attribute, has-filter, child-attribute, reset-datasource, validate, file, slot, sigoption, license

In consequence you are using new MAS Mobile application version and revision but still old graphite-configuration (MAF Tool) version which doesn't contains new attributes property definition on-drill-in that is available for lookup-with-filter.

To verify if your graphite-configuration is using the correct image you can follow these steps:

1. In Red Hat OpenShift web console navigate to Operators -> Installed Operators
2. Find IBM Maximo Application Suite operator and open YAML
3. In YAML find section  spec.relatedImages and find image definition for graphite-configuration
   For example:
       - image: 'cp.icr.io/cp/mas/graphite-configuration:1.7.55-amd64@sha256:78e09392fd1c62163ae15ad0b913f332c12ccb6244d5988816827c0f580451c9'
      name: 'mas/graphite-configuration:1.7.55-amd64'
4. Take a note about image
5. GoTo Workloads -> Deployments and find deployment definition for graphite-configuration (<instanceid>-graphite-configuration)
6. Select deployment and open YAML definition.
7. In YAML definition find section spec.template.spec.containers.resources.image and check if SHA is the same as image in Operator definition (point 3). If it's not the same (as it was in my case) you can use image from operator definition and set it in deployment YAML and save changes. After that new graphite-configuration (MAF Tool) pod with the correct version will start.

I have opened an IBM support case regarding this issue, and it is currently under investigation. So far, IBM has not confirmed that this is a product defect; however, they have indicated that a similar scenario has been observed in other customer environments.

Further analysis of the entitymgr appcfg pod log is required to continue the investigation.

------------------------------
Bartosz Marchewka
IBM Maximo Consultant
AFRY
------------------------------