Service (Touch Apps, MWO, MRO)

I’ve searched this forum and it seems several users have requested/suggested the functionality to allow multiple photos to be added to a single survey response in MWO vs the cumbersome process of introducing looping questions/child surveys. Most threads seem to go cold a while back so would be great if someone could confirm if this has been implemented or if not where this is on the development track. Feels like this is pretty basic/standard expectation of an end user in 2026 (ie select multiple images and hit ‘upload’) 

Hi,What is the best way to keep the Material Line visible in the MWO app while disabling all edit-related actions such as Issue, Un-Issue, Edit, and Delete?I have already tried removing the relevant options from the workflow configuration, but these actions are still visible in the application.Could you advise if there is another configuration, permission set, or projection setting that controls the visibility of these options or can this be a bug? Cloud version - 25.2.4 /Indika

Good Morning, We are in the early stages of our IFS Cloud Upgrade. I am having issues where 2 users can log into IFS Cloud Web Version with their user name and password.When they attempt to log into MWO Service App they get ‘Invalid Username or Password’They have the same permissions sets granted as a user that can log into MWO. What else would prevent a user from logging into MWO Service App? I have managed the details via Resource Structure, they are ticked as MWO User but they do not appear in Mobile App User Details, they cannot log in etc. I am sure it is a setting I have missed but I cannot work it out. Thanks,Lisa

Hi,maybe someone can consult what actions should be done to activate mobile user?:In is not allowed to activate it manually. The field is inactive when switching on the function to edit data.

Hi,  With the transition to the MAUI platform, it has been observed that the current mobile applications (MWO, Notify Me, and Scan IT) do not provide the same level of Insight Logs that were available in the MWO Classic (Xamarin) application. This limitation makes it challenging to clearly understand user actions and accurately identify issues encountered during application usage.Although the application parameter EXTENDED_CLIENT_LOGGING can be enabled, it currently captures only a limited set of logs, which is often insufficient for effective troubleshooting and root cause analysis.Proposed ImprovementsTo enhance observability and support efficient diagnostics, the following improvements are recommended: Enhance Device Log Coverage Introduce more comprehensive client-side logging to better capture user interactions, application flows, and er

Hi all,I believe this behavior is an issue and does not match the expected result.IFS CLOUD Version:I’m following these steps:Navigate to MWO Maintenance Use Additional Work on a Task or Task-Steps Select Copy Information from Task = Yes Click on Report additional work that I have done Select a task template Click on FinishExpected result:A new Work Task should be automatically created under Work Order with status Work DoneActual result:A new row is created under Job and Templates with originating system MWO. No Work Task is generated f

Hi everyone,I wanted to reach out to the community to get some clarity and perspective on a topic that recently came up in a discussion with IFS.During a recent conversation, I heard a statement that “Nexus Black Resolve is intended to be the long-term replacement for MWO.” But i did not hear any specifics - it sounded bit vague, however it could just be me and plans may be in place. I’m Seeking some Clarifications as this raised a few important questions, and I’m hoping the community can help me to clarify these: Has this direction been formally defined? Is Nexus Black Resolve officially positioned as the successor / replacement for MWO, or is this still early-stage direction or regional guidance? Is Resolve included in the official roadmap? If so, where can we find formal roadmap visibility or release

Hi,I am looking for the following options in MWO - Service Classic but they do not appear. I have added all the security grants for ServiceEngApp 25 but it only gives me view to add new service request which is linked the request management. Is there anything I am missing? Thanks,George.

Hi All, When we enter a new cost to a Resource Group, the below error pops up. However, there is no such costs defined for the Resource Group. This has happened even after we creating a new resource group. This behavior is there in one of our environment. Entering cost works fine in our another environment.   Anyone, have seen this error?

Hi,   I would like to know why is it important to timely clear error messages from Maintenance Posting Analysis. What impact does it have if we dont do it timely.

Hi,We have an assortment with parts that are set to be refilled with Shipment Order:  If we select “Receive into Inventory” for the Remote Warehouse in the Receive Case, it works fine, but obviously, the parts arrived in the picking inventory location as soon as the shipment is delivered.The business would prefer it if the parts were first in a sort of transit state as they want the remote warehouse operator (the remote warehouses are typically work vans and the operators are the van drivers and they use IFS MWO Service) to confirm receipt of the delivery (this must happen in the mobile device) before the parts are made available in the remote warehouse.We cannot use Transport Tasks with move to transit option as the main warehouse absolutely requires the use of “Pick by Choice” which is only available from a

Is there a separate permission set for IFS NotifyMe (IFS Cloud 25R2 SU3)? When trying to connect i’m getting an error ODATA_PROVIDER_ERROR. 

Hi All,We need to use Region attribute in request management to use in several places such as Selection Rules, Task Regions etc.However, it seems that region alone does not work and we need to tie it with a location to make it usable. Since we get requests from different locations almost every time saving locations may not be that useful. Address and Region combination would be ideal for our work. If we use dummy location per region then that will make exception in PSO with invalid location.Can anyone give any input on this?

Our company uses work order and work task processes. We typically use one work order with one work task. A user has changed the work task status to Work Started and is now unable to change back to Released (it was changed in error and for our flow needs to be in Released status and update a value in the Work Stage which is how we’ve overcome the lack of work task status). The work task in question has a connected Maintenance Purchase Requisition which is Closed Status. This was used to create a part requisition line for an external service purchase order which is in released status. This error message is received when attempting to change the status back on the Work Task or Work Order. ERROR: It is not possible to initiate a Tender flow when one of more connected Work Tasks are in status Released or above.Turned on debug console and found the error is due to WORK_ORDER_REQUIS_HEADER_API starting at line 1379 where it’s attempting to

Added custom fields to the Service Eng App in time clocking screen. However, the same is not visible in the mobile app. apps page designer has Service engineer and Maint Eng Screens only. The fields are visible in the time clocking screen in Service engineer Screens. However, cannot see it in the mobile.Same was done for MWO screen (MaintEngApp) and it works.In the page Configuration screen we cannot see ServiceEngApp What are we missing?

MWO Demystified has been updated to 24R2. As usual, headlines are tagged with “24R2­🌟” for new capabilities, “24R2↗” for improved features, and “⁠🖊” for new chapters on existing functionality. You will also find numerous configuration examples.If you find this document helpful, please consider leaving a 👍 LIKE. And ⭐ SUBSCRIBE to get updates.295 pages cover:MWO Service with Work Order Management vs. Request Management Work Execution Process Work Crew work Bundle tasks in MWO Work Status My Misc. Allocations Set attention on/off Scope Review Work to Prepare Mobile Integration New Service Request / New Wor

Hello,I’m trying to add a navigation command from an Online screen ‘ServiceEquipmentDetailOnlinePage’ in MWO to a standard entity ‘TechnicalObjectReference’ and existing screen ‘TechnicalReqPage’. The screen works fine when I try in Cloud but in MWO it displays a blank screen without any data. I’m in 25R1 IFS Cloud version and also have the latest MWO Service app installed. Is this a limitation through configuration or am I missing something? Please advice. MWO 

Hi All, When we complete an assignment of a Request Task, an assistant appear to Clock Out. There we can give a comment.But, this comment cannot be found anywhere in Assignments tab or Events.Anyone has idea on this behavior? Is this a bug or am I missing something? Respective screens are shown below.   TIA.

Hi All,I created an additional on call shift and MRA to a resource. Those two appear in dispatch console.  However, not visible in PSO. It’s empty.The MRA category is marked as “Use in Scheduling”. SEND_MRA_DESCRIPTION=Yes in Scheduling Configurations. What else need to be done? TIA.

Hi All, We are experiencing an issue with generating SLA commitments from SLA Templates connected to Service and Request Contracts. SLA commitments are created when an Urgency is defined for a Request. The Service Catalog item was created as shown below. SLA Template that is attached to a Service item Different SLA Template is attached if the Urgency is 1 Creation of service request are show in below. First, without an urgency.No urgency used. Normal SLA template is fetched from

Hi all,In 25R1 mobile work order (via maintenance app), when trying to enter a new measurement, I have below error.function<GetNewmeasurementInfo>: Failed to read value from EquipmentObjectTestPntRec.descriptionNew measurementError Also noticed the description inEquipmentObjectTestPntRec looks like below.EquipmentObjectTestPntRecA colleague checking on a different environment verified the same issue in their environment as well.

MWO Demystified  describes changes and additional capabilities related to MWO (Mobile Work Order) in IFS Cloud 25R2. People with experience in 25R1 should focus on chapters marked with 25R2☀️ and 25R2↗️.Chapters with 🖋️ provide new or additional details for features that were already available in previous releases.To clearly point out where something can be found in the application, navigation paths are now highlighted with 📁 path to page (IFS Cloud), ☰ MWO (left-hand panel) and 𝍖 MWO (home page dashboard).If you find this document helpful, please consider leaving a 👍 LIKE. And ⭐ SUBSCRIBE to get updates.

MWO Demystified  describes changes and additional capabilities related to MWO (Mobile Work Order) in IFS Cloud 26R1. People with experience in 25R2 should focus on chapters marked with 26R1☀️ and 26R1↗️.Chapters with 🖋️ provide new or additional details for features that were already available in previous releases.Features that rely on AI are marked with ✨.If you find this document helpful, please consider leaving a 👍 LIKE. And ⭐ SUBSCRIBE to get updates. 428 pages cover:Terminology Getting Started Work Execution by Individual Resources Work Execution by Crews Work Execution by Contractor Resources Bundle tasks in MWO Core Functionalities Service Objects Stock and Inventory Management Purchase Handling Documents, Media, and Attachments Tec

Hi,  With the transition to the MAUI platform, it has been observed that the current mobile applications (MWO, Notify Me, and Scan IT) do not provide the same level of Insight Logs that were available in the MWO Classic (Xamarin) application. This limitation makes it challenging to clearly understand user actions and accurately identify issues encountered during application usage.Although the application parameter EXTENDED_CLIENT_LOGGING can be enabled, it currently captures only a limited set of logs, which is often insufficient for effective troubleshooting and root cause analysis.Proposed ImprovementsTo enhance observability and support efficient diagnostics, the following improvements are recommended: Enhance Device Log Coverage Introduce more comprehensive client-side logging to better capture user interactions, application flows, and error scenarios. This wi