Look into the Move/Swap/Modify. When a WO is going to change the specs on an Asset/Location/CI, this is a supported way out of the box to queue those changes up. Then when the work is completed the plan gets executed (or you can manually execute it if desired).
You can display values from other records without much concern because everyone (above self-service) is granted read-only access to the system. However, you need to be careful about adding ways to modify records outside of the apps where they're allowed to be modified out of box. Beyond potential technical issues such as missing bean class references that are required to support it, it could become a licensing issue in an audit if it's identified. For example, most changes to a Location require SAVE access to the Locations application. That access would bump a user from Express to Limited and Limited to Authorized (if that caused them to go from 3 to 4 modules). That's why adding ways to modify a record (outside of the ways we provide out of box) can be a licensing issue.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Tue October 11, 2022 06:15 PM
From: Steven Kelly
Subject: Modify/Edit Location Specifications (Attributes) from Work Orders?
Hello everybody,
I've configured a relationship to display two Location Spec/Attributes (LOCATIONSPEC.ALNVALUE) in work orders based on the WORKORDER.LOCATION and LOCATIONSPEC.ASSETATTRIDs.This is displaying LOCATIONSPEC.ALNVALUES perfectly in WOs.
Received a request for the ability to modify/update the Location Spec/Attributes within Work Orders. What is the best practice to support updating existing Location Spec/Attributes from Work Orders?
Many thanks!
------------------------------
Steven K., Business System Analyst
------------------------------
#AssetandFacilitiesManagement
#Maximo