We are working on our Upgrade to Apps10 UPD9 (from Apps8). This post is related to mWO Service 10 - Aurena Native app and Mobile Surveys.We configured Surveys based on the very light documentation we were provided. Help Pages in Aurena don’t work, confirmed by IFS. If anyone has detailed documentation of any kind on this, it would be very much appreciated.The Survey and Workflow Config, as far as we can tell, is set up properly but reaching out for community input here, along with a formal, pending IFS support request. All Synchronized Entities syncs are up-to-date. I just filtered for anything with ‘Surv%’. Survey Configuration:The Survey is PublishedSurvey Workflow Type selected “Work Start”; this means the Survey should pop up when the user presses Start Work on the MWO. I did try other statuses for testing, but none of them worked and ultimately this is what we need.The Work Task Assignment in the mWO App is in ‘Work Started’ status. This was a new WO/Task/Assignment created and a
I’m hoping someone might have some experience that could get us to the next step in troubleshooting as we are at a bit of a standstill.Does anyone know how many customers are on Aurena Native, MWO?Issue: When I run the MWO Service 10 app, I am continuously getting a time-out error during sync at the point where it is “Waiting for Server”. Details:We are in the middle of our upgrade going from Apps8 to Apps10. Everything is IFS, not FSM, so IFS MWO only.TAS is installedWe intend to use Aurena Native, not RTMAll necessary System Parameter setup was done between our database architect and IFS’s TAS specialistThe setup for the user for my test case was verified by IFS SME as being correct (for both user setup and mobile user setup)Our url is internal only at this time and I am accessing it internallyThere are no errors in the logs.In the Mobile User Log, the last action is consistently “Initialize data Waiting for Grouped Push”. It is Type-Info, not Type-Error or Warning.I did a thorough t
I’m hoping I’m missing some easy, obvious option here. I did not find the details in F1.In Apps10, UPD9, how do I cancel a Work Assignment from IEE when it is transferred to mobile and in ‘Work Started’. In Apps8, we are able to go to Transferred to Mobile, rmb, and ‘Unassign Work Order’.I see the rmb option in Apps10 to ‘Cancel Work Assignment’ but it is grayed out when the Assignment is in Work Started status. I’m not sure in what status this feature becomes unavailable, but it seems to be so for at least Work Started. I am curious, is that also the case for Accepted?Also, looking for a way to manually advance the Work Assignment should the need arise. In Apps8, we are currently able to adjust the status from IEE and it keeps the id of the individual making the change neatly stored in the Journal.
We are moving from Apps 8 to Apps 10 (combination of IEE and Aurena that hasn’t been hashed out yet). For our National Field Service team, we are currently using Apps 8 IEE Work Order utilizing Resource Allocation Gantt, transferring to Mobile Work Order, and finishing in Apps 8 IEE. I was wondering if anyone out there has a similar experience and what your solution is? If you are using Maintenance Planning Board for Field Service, what your general opinion is? Figuring out our best practices with the big leap from 8 to 10/Aurena, especially with the new workflow. Thanks in advance for any insight!
We are on Apps10 UPD9 Enterprise Explorer, .NET Runtime 5.0.14. .NET Framework 4.8, Windows 10 Pro, build 19044. We are experiencing a high number of app crashes, specifically when users are navigating or utilizing Service-related areas. We tried multiple trouble-shooting steps initially, such as reducing cached pages to 5. We recently increased one of our units to 32GB of RAM. We are in the process of testing this now. Our standard is 8GB and generally works perfectly fine for all of our apps, including Apps8, which we were on previously. (just a few months ago). Event viewer often shows Event ID 1000 and Event ID 1026.Has anyone else experienced this issue? Any ideas on a potential fix, aside from the RAM increase or moving to a more recent UPD? Our systems meet the hardware/software/OS requirements set forth by IFS.Thanks.
We are currently on Apps8 going to Apps10. The workflow I describe below works in Apps 8, but not in Apps 10.Our installation workflow begins with a Customer Order (Sales) and ends with a Work Order (non-billed Service).The Customer Order is created and completed for one Site and the related Work Order is created and completed in a different Site. Also, Customer Order has one Customer Number (distributor) and Work Order has a different Customer Number (end-user). IFS 10 is requiring a matching Site and Customer Number between Customer Order and Work Order, but this won’t work for our business practices.Any suggestions or ideas? Open to IEE10 and Aurena for possible solutions.Thanks.
I was wondering if anyone out there integrated or is in the process of integrating utilizing RESTful API’s that would be open to sharing their experience and brief process? Thanks.
We are on Apps10 IEE, UPD9, fairly recently upgraded from Apps8.The inability to revise an ‘Accepted’ quote from Service Quotation is presenting quite an issue for us.Once the Estimate has been ‘Accepted’, there is no way to create a revision. This has been confirmed by IFS multiple times and we’ve received no communication that they have a plan to change this in the future in Apps10. Has anyone found a workaround for this restriction? Secondary issue, not having a Work Task or Work Order until ‘Accepted’ is creating multiple issues for us as well. Anyone happen to have run into the same issue and found a reasonable solution/workaround?Thanks.
We are in the process of upgrading from Apps8 to Apps10. In mWO, we have the standard Apps8 setup to allow mobile users to select the expense from the mobile device. We set up a Part Catalog Assortment which contains all of our non-inventory sales parts that we would like to use on the work orders for service and travel expenses, which are billed to the customer. The assortment is then assigned under Mobile Part Management > Mobile User Assortments to all mwo users as needed.We have been informed with the most recent changes in Apps10 mWO, there is no out-of-the-box solution for non-inventory sales parts. We have been directed to remote warehouse for inventory parts and given a possible work-around for non-inventory sales part. The viability of the work around is still being hashed out and involved several customizations.Business Need for Apps10: We would like to have the technician select the non-inventory sales part from expenses on the mobile device. When that part is selected, t
We are currently on Apps8, in the process of moving to Apps10.On occasion, an error is made and we don’t bill a customer enough for a physical product.They agree to be billed the correct amount.What is the best way to charge the additional amount, using the specific physical sales part from the original order (for reporting and accounting purposes), but not moving inventory?
We are mid-upgrade. We switched from DB Authentication method for login to Azure login. Now our mwo devices are not receiving new assignments. I can see existing assignments but newly assigned are not coming through. I am able to login to the app, but then I receive this message ‘The sync process has started failing’. I go to Details and it only takes me to the Sync page in the app where the normally spinning green initializing circle reads ‘idle’. I am not sure the sync’ing issue is related to the change from DB Authentication to Azure, but it was working without issue just previous to that change. No other changes were made at the time. So it may be something else and a coincidence, but I thought it was important to note as the major change.Any ideas?
We are currently running Apps8, mWO on-prem. This means we cannot use the app from the Microsoft Store (as we were informed from the very beginning it is intended for Cloud only) and instead we have to use the executable file from the TAS.Windows changed their rules for sideloaded apps. It used to be controlled with a simple setting in Developer Mode. We are no longer able to install the .exe file from our latest images which have a version that is after 1909.Is there an updated .exe file that accounts for this Microsoft change?
We are upgrading from Apps8 to Apps10. There is a customer and technician signature that exists in Apps8. Apps8 blob on table, HISTORICAL_SEPARATE, CUST_SIGNATURE. Apps10 table for mWO signatures is JT_TASK_SINGATURE.For historical reference and use on work order documentation, we need to migrate the Apps8 signature to Apps10.Anyone have suggestions on how we can accomplish this?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
