Enable getLookupName for Attribute Automation Script

Automation scripts in Maximo have a lot of functionality, especially in relation to attributes. We can add our own custom logic to most of the common methods/functions (validate, action, getList(), etc.), and make changes to this custom logic (including disabling) without any downtime. We'd like to see support for getLookupName() in addition to the other events.

In most cases in Maximo, an attribute will only have a single object that the field relates to (ex: storing REFWO on PRLINE where it corresponds to the WORKORDER object WONUM attribute). In some cases, an attribute will correspond to multiple objects (ex: TABLEVALUE on ASSETSPEC). In either scenario, we can handle the logic to relate the objects and crossover the values with the Retrieve List (getList()) Automation Script launch point.

We can easily associate a lookup in Application Designer when it corresponds to a single object, but when it corresponds to many it's really required to implement getLookupName() on the attribute where you can return the appropriate lookup based on the record. This also simplifies when you have a field referenced in many applications where you want to define which lookup is used. Instead of modifying a bunch of screens (which then has to be deployed to all the JVMs in the cluster), you can change it in the code and have it everywhere.

It may make sense to implement similar to how integrations work where we have a single automation script that we define which methods to support that we can put our custom logic. This would make it similar to a single field class. We can accomplish the one script today (and do) by determining the launch point name, but it'd still be cleaner (especially when you want to use the same script for more than one field) to have one launch point per attribute.

This could also add support for getAppLink(), which isn't necessary for us in this scenario but could be useful for others.