MAM 7.6.1.2:

Is there a way to use an object formula as a "dynamic non­-persistent attribute" in Application Designer? Just like we can do with the REST API?

For example, I have an object formula called OBJECT_FORMULA_TEST.

• The object formula could be used by an attribute formula to populate a custom field (persistent or non-persistent): exp$OBJECT_FORMULA_TEST
• Or, the object formula could be used in the REST API without the need for a custom field (persistent or non-persistent): exp.OBJECT_FORMULA_TEST

But I want to use the object formula directly in the UI -- without needing to create a custom field.
For example, in the Classifications application, I want to add a field to the application that uses the object formula as the attribute.

Unfortunately, when I try to enter exp$OBJECT_FORMULA_TEST or exp.OBJECT_FORMULA_TEST  as an attribute in Application Designer, the field doesn’t work; I get a "invalid binding" error.

Does anyone know of a way to use an object formula directly in Application Designer?

Thanks.


RFE / Idea: 
Use object formula as "dynamic non­-persistent attribute" in Application Designer
https://ibm-ai-apps.ideas.ibm.com/ideas/MASM-I-546

Here’s some background info from the docs:


Object Formulas:

"An object formula is a formula that is not associated with any Mbo attribute but is just associated with the Mbo itself. These are often known as dynamic non­persistent attributes because these expressions can be evaluated for a Mbo and their values used as input to other formulas, just like you would use an attribute value in other formulas. The difference being, we do not need to explicitly create these Mbo non­persistent attributes (using DB config app+Admin mode etc) just to store a calculation.

If say we defined that overbudgetcost as a formula instead of a non­persistent Mbo attribute, we could have used that as part of another formula like below:

exp$overbudgetcost + someothermboattr

The key thing here is, we can use the key word "exp$", append the object formula name to it and then use it as part of any other calculation."

REST API (page 14):

"You can select calculated values without creating non-persistent attributes by using the integration between the REST APIs and the object formula feature, which was included in Maximo Asset Management 7.6.0.5.

For example, you create a object formula called MYREPLACECOST for asset object by using the Object Formula action in the Database Configuration application. The formula is purchaseprice/NVL(priority,1). You can then select that formula property that is associated with the asset object by using the following API select clause:

GET /oslc/os/mxasset?oslc.select=assetnum,status,exp.myreplacecost,assetmeter{…}

The response is as if myreplacecost was an attribute of the asset MBO.

Note that this can be considered as a great alternative to defining non-persistent attributes just for the sake of holding calculated values. This acts like a dynamic attribute that does not need db config or admin mode."