User1971,
Have you noticed that when you populate the start time and you enter the hours it calculates the end time? and yes this is constructed and built this way. Please if you can provide for me the usual and normal use case scenario you are trying to support (i.e. not the edge case).
Most clients will simply enter the hours on a manual labor transaction. Capturing the start and end times on a manual labor transaction is of much less concern that the actual start and end times. So again please provide the usual and normal use case scenario that stipulates the need to capture times.
I ask for this to help you convey back to the business owners the cost benefit for building this capability. What you ask is not a cheap investment in the product. It can be done but is costly. If the need of the business is paramount to have start and end times on ALL transactions, and they are willing to invest in the cost of development of the custom code then they have the responsibility of understanding that cost and bearing it, given the value of have ALL labor transaction have start end time. My guess is that the business does not really NEED to have EVERY transaction have start and end time on them, and the cost of getting that is not economical for the business benefit on back-end analytics.
------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA
------------------------------
Original Message:
Sent: Tue April 06, 2021 09:53 AM
From: User1971
Subject: Anywhere Actuals: start/stop time FIELDS; number of hours
Anywhere Work Technician 7.6.4:
Note: this question pertains to the start/stop time fields, not the timer.
In Anywhere, if I create an Actual by entering the start/stop time manually in the start/stop time fields, Anywhere doesn't automatically populate the Hours field (unlike Maximo Desktop, which does auto-populate the Hours field correctly).
Does anyone have any ideas how to get the Hours field to populate automatically in this scenario?
IBM:
"This is working as designed, The reason the calculation does not happen in Anywhere is because of a limitation in how javascript can be used."
Thanks.