So I am guessing that you do not have the MWO module installed in your environment. The MWO Maintenance App requires this module to function. You can check to see if this module exists by checking the Module report or querying the records in the module view via a SQL statement. Cheers James
It looks like everything is configured correctly as you can pass through the login page via Account Manager. Could you check that the end user has access to the Scan It App security - you can generate a role script via the Touch Apps Server Customer Portal. If the User has the correct access then I suggest you raise a Case with IFS Support to investigate further Cheers James
The new MWO Maintenance App will only work with IFS Applications 10 UPD4 onwards. On top of this you must have the MWO Maintenance projection installed. You can check to see if the projection is available to grant to your mobile users by looking in Permission Sets > Activities and look for a folder named “TouchApp MaintEngApp 1” Cheers James
For the MWO Maintenance Touch App the redirect URI is: ifs-mworkorder10nextgeneam://auth Cheers James
The Touch Apps Server in Apps 10 is delivered in each Update. When you install an Apps 10 UPD you should also install the delivered Touch Apps Server. The Touch Apps Server can be found in the manualdeploy\install folder in your Build Home.
Looks like you need to upgrade the Touch Apps Server to the 10.6 version. The TAS installer is delivered as part of the IFS delivery and you can find it in the manualdeploy\install folder of your Build Home. Please follow the installation guidelines in F1 Technical Documentation under IFS Installation Guide > Additional Installation Options > Touch Apps > IFS Touch Apps Server Installation Cheers James
The redirect should be ifs-ifsaurenanotifyme10://auth You can find this in the F1 Technical Documentation under IFS Administration & Configuration Guide > Touch Apps > Touch Apps Business Components > Notify Me on Aurena Native
@Maithree The SMS is not the problem here. Its the exposing of the local database and the potential exposing of IFS Applications based on updating the local database.
From a security point of view this is difficult to do. We encrypt the local database and to do something like this we would have to open this up to allow updates from the outside. This would pose a security risk as it could be used to hack the local database and therefore expose IFS Applications.
Already have an account? Login
No account yet? Create an account
Enter your 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.