Maximo

• Unburden the user of having to provide information the organisation should already have (frustration)
• Speed up the entry of SR  (efficency)
• Provide more details to those that need to manage and resolve the issue (communication)
• Allow for feedback through the SR proces. (verificaiton)

• Unburden the user of having to provide information the organisation should already have (frustration)
• Speed up the entry of SR  (efficency)
• Provide more details to those that need to manage and resolve the issue (communication)
• Allow for feedback through the SR proces. (verificaiton)

Setting fields as required can be done at the UI level or at the database level.  If you need this just for SRs created via Work Centers, then you could do this at the UI level on the Work Centers.  I'm not on version 7612, so I'm not sure if the editing tools for Work Centers would allow you to make that change visually.  You may have to go into the coding itself and change it.  Not necessarily easy.

Alternatively, you can set it at the database level.  However, that means it will be required for every way an SR could be created (e.g., Work Center, the self-service application, from Work Order Tracking's Create --> Service Request action, integration, etc.)  To do this, go into the Database Configuration application, retrieve the SR object, find the reportedphone and reportedemail attributes and check the Required? checkbox.  Apply the changes.

Or you could write an Object Launch Point Automation Script with a Validate Application event that would make sure those fields have a value.  (And if you wanted to get a little fancier, you could also include something that would try to make sure the phone numbers and email addresses at least have a valid format.)

• Unburden the user of having to provide information the organisation should already have (frustration)
• Speed up the entry of SR  (efficency)
• Provide more details to those that need to manage and resolve the issue (communication)
• Allow for feedback through the SR proces. (verificaiton)

Setting fields as required can be done at the UI level or at the database level.  If you need this just for SRs created via Work Centers, then you could do this at the UI level on the Work Centers.  I'm not on version 7612, so I'm not sure if the editing tools for Work Centers would allow you to make that change visually.  You may have to go into the coding itself and change it.  Not necessarily easy.

Alternatively, you can set it at the database level.  However, that means it will be required for every way an SR could be created (e.g., Work Center, the self-service application, from Work Order Tracking's Create --> Service Request action, integration, etc.)  To do this, go into the Database Configuration application, retrieve the SR object, find the reportedphone and reportedemail attributes and check the Required? checkbox.  Apply the changes.

Or you could write an Object Launch Point Automation Script with a Validate Application event that would make sure those fields have a value.  (And if you wanted to get a little fancier, you could also include something that would try to make sure the phone numbers and email addresses at least have a valid format.)

• Unburden the user of having to provide information the organisation should already have (frustration)
• Speed up the entry of SR  (efficency)
• Provide more details to those that need to manage and resolve the issue (communication)
• Allow for feedback through the SR proces. (verificaiton)