IBM Ticket GPAT-2960 – Functional Defect Service Request can be saved without Asset or Location (missing blocking validation)

1. General Information Title Service Request creation allowed without Asset or Location – missing blocking validation Type Functional defect Application Mobility – Service Request 2. Business Requirement A Service Request must not be saved if neither an Asset nor a Location is specified. At least one of the two fields (Asset or Location) must be mandatory in order to ensure proper functional linkage and data quality within the CMMS. Currently, the application allows a Service Request to be saved without any of these values, which is not compliant with the expected business rules. 3. Test Context Site / Facility None User profile National admin Assignment None Application Mobility – Service Request Usage context Training / demonstration 4. Reproduction Steps 1. Open the Mobility – Service Request application. 2. Create a new Service Request. 3. Fill in the standard mandatory fields (title, description, etc.). 4. Do not select any Asset. 5. Do not select any Location. 6. Save the Service Request. 5. Results 5.1 Actual Result The Service Request is saved successfully even though no Asset or Location is specified. No error message or blocking control is displayed. 5.2 Expected Result Saving the Service Request must be blocked when both Asset and Location fields are empty. An explicit error message must be displayed indicating that at least one of the two fields is mandatory. 6. Business Impact • Creation of unlinked Service Requests. • Degradation of data quality. • Difficulties in maintenance assignment and operational processing. 1 • Inconsistency with business rules presented during training. • Risk of reproducing this behavior in production environments. 7. Suggested Priority Medium to high, considering the impact on data quality and business usage.