Maximo Open Forum

Seems like you could use a Script without a launchpoint, as long as you name the script WORKORDER.NEW --- see IBM Maximo Autoscripting Guide – OBJECTNAME.NEW Script

I'm guessing you wouldn't want that literally every time. . .I mean, do you want that to run against every Work Order created via PM?  Child task Work Orders created because a Job Plan was utilized?

If you have a true static default (IE it's not based on something from another record), the database configuration default value is the proper approach. For example, if you wanted the description to be "Change This"



If you need to do it programmatically for some reason (getting something from the person record for example that isn't supported as a substitution variable), then Travis is spot on that the .NEW script is the most efficient way to do it. This will fire only once per record and will be immediate so users will see it as soon as they click new row. Object save with only the Add option enabled is also efficient but is after the users attempt to save. If you require the field for example, this won't work because Maximo will prevent the save prior to your default. Object init is the absolute worst option because it fires every time the MBO is initialized (on the list tab, on a REST API request, etc.). 

Hi Anudeep,

Easiest is very subjective.  The answer also depends on where the record is being created.  I assume that this is for a new record.

Here are some ways that a field default could be applied:

• Automation Script - Covers all scenarios
• DB Config - Covers all scenarios
• APPFIELDDEFAULTS - Covers all scenarios Ref: Defaulting a value for a user with APPFIELDDEFAULTS table
• Application Designer - Screen only
• Database triggers - Covers all scenarios, not recommended
• Java customisations - UI and Importing Data
• Integration - Importing Data

Ref: MaximoDev - How to set the default value of a field in Maximo

I agree with the answer that Steven has also give.