I was thinking about an RFE/Idea that I came across recently:
RFE: New Automation Script Launch Point to Support Roles
"Maximo automation scripts enable organizations to extend Maximo functionality without downtime and without having to write custom java classes. We'd like to see support added for an automation script launch point in the Roles application to replace custom java classes. Workflows and Communication Templates use roles to determine who should be notified/get assigned. Most of the time, this results in using database relationships to show data related to a record.
Some situations are more complicated and can't be handled with a SQL where clause. We'd like to be able to handle these situations without needing custom java classes so we can make changes without rebuilding and redeploying the ears."
Question:
Are there cases (possibly like the one above) where we might want to create custom database functions -- and use them in the relationship WHERE clauses?
- If the logic is too complicated/lengthy to put it directly into the relationship WHERE clause, then it might help to put it into a separate function. It might be easier to manage that way.
Or do WHERE clauses not use real SQL? (native database SQL)
#Maximo#AssetandFacilitiesManagement