Hello @rroges, have you tried reducing the MaxLength of the survey field using Page Designer to restrict the input?I tried this just now on the Task Details screen by setting the Description and Long Description fields to MaxLength of 10 and 20 respectively (they default too 60 and 4000 respectively).Once I save, publish and (re)initialize MWO, I can see this reflected in the app where I can’t type more than the MaxLength number of characters.The one downside compared with the mask approach is that your user doesn’t see in advance how much they can enter - instead, the field stops accepting input, but it might still work in your case, once the technicians get used to the behaviour.Best regards,Rukmal
Hi @eduardo.sm, the Camera is dependent on two things:Camera permissions need to be granted to Trip Tracker on the device. From your screenshots though, it looks a bit like you’re running on the same device and connecting to both env’s. Am I right? if so, this should be fine. We also do check for Media permissions. I couldn’t find all the details, but I believe this is the Media Library configurations on the environment. Can you check the Media Library permissions and configuration on the test and prod environments please?Best regards,Rukmal
@eduardo.sm glad to hear you seem to have a way forward.To clarify my previous answer and tie it to your last comment about availability - IFS Notify Me 10 was last updated in January 2021 and that’s because there were no functional changes nor any Support Tickets reported requiring an app update.However, the “unavailability” that you experienced came into effect only from 1st November 2023 when Google Play Store changed their policy and required apps to target the latest Android OS versions in order to be discoverable for “new users” (i.e.: a Google account that hasn’t installed it before) via the Play Store, but users who have installed it before can continue to install it on any device. This connects to my suggestion #1. This policy change only applies to installs via the Play Store app, and it can be sideloaded and installed on any device with no restrictions (suggestion #3), so this isn’t really an “unavailability”.Unfortunately, aligning with this Google Play Store policy change
Hi @eduardo.sm, Notify Me on Apps10 is indeed supported on Android 13.From what you’re saying though, I guess that you’re on “IFS Notify Me 10”, where due to a recent Google Play Store policy change, you are currently unable to install IFS Notify Me 10 via the Play Store. This is likely because you are on an Android 13 device and your Google account has not previously been used to install IFS Notify Me 10 on any other device, am I correct?If so, you have 4 options:Use your Google account on an older Android device (Android 12 or older) to first install IFS Notify Me 10. This should now make it possible for you to also install it on your Android 13 device using the same Google account. Wait until mid-December - there is a planned update to IFS Notify Me 10 which is expected to be released by mid-December and should align with the Google Play Story updated policy and allow you to install it as with our other apps Obtain the APK file directly and sideload IFS Notify Me 10 - you can report
@Priyanka Cecilia V the second scenario is a limitation that we’ve not been able to investigate deep into yet. Once we look into it, if we find a workaround, we will share that too on both the documentation and on this thread.
@gianni.neves following up on this, do you still experience the issue, and if so, have you been able to report it? Please do remember to also include the additional information I pointed out above.We’ve also identified a couple of areas that could contribute to this sort of behaviour in certain environments and are working on some candidate fixes. If you can send us a Support Ticket, we can work together to try out a pre-release version to see how it behaves in your environments.Thanks,Rukmal
@bdoucette what SU are you on now, and what were you on before the update that seemed to break it?
This is indeed possible on MWO with IFS Cloud 23R2 and up as Configuration only!It’s called Conditional Fields. See the documentation for the Web here: https://docs.ifs.com/techdocs/23r2/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/#conditional_attributeIt translates almost directly into Mobile, with the only difference being that you’d do this using Solution Manager > Mobile Apps > Configuration > Apps for Page Designer > Service Engineer(Or Maintenance Engineer).Best regards,Rukmal
@Priyanka Cecilia V I think you’re referring to the scenario we discussed previously, of setting a field from JtTask to be conditionally visible/editable/required based on a reference to JtExecutionInstance right?We concluded the technical investigation on that literally today, and that specific scenario is unfortunately not something we can handle. The reason is that we came to realize that even though the projection has a reference from JtTask to JtExecutionInstance, in reality, a single JtTask instance will effectively be a wrapper for multiple JtExecutionInstance instances, so there is no logical reference from JtTask to JtExecutionInstance. The reference we tried to use is one that has been added to make some functional implementation easier.The right way to approach references is to look at the Entity definition. Any associations defined between entities and also reflected as references on the Projection level can still be used.I hope the above is clear and is some help, and we
Hi @gianni.neves, we’ve heard of a similar issue from one other customer, but we’ve found it difficult to investigate it properly as we have not been able to recreate it in-house. Could you report a Support Ticket and ask your support contacts to expedite it to the Mobile Framework team please, so that we could take a look?Any additional information you can share is likely to help us a lot, for example:please include the Device Logs (Settings > Send Device Logs) if you can, please try to get the logcat output as well have you seen any patterns in where it crashes? e.g.: is it the same screen or action? do you have any lists with large amounts of data, and are the crashes associated with those? do your devices have internet access or are they on a completely isolated intranet? how many users do you have? do they all see the crashes or only some? if not everyone, what is different about those who see the crash and the others? you mentioned that it all worked okay for a while. What cha
@Priyanka Cecilia V in general, yes, just like the example we looked at together, we can use references to refer to related entities.However, you might recall one instance where the referred entity had multiple records and we were evaluating against the incorrect one, and that’s turned out to be rather complex so we’re still working on that.
@Alexander Heinze yes, they are now supported on MWO with 23R2.
Thanks @Dario Zani it does!@Anthony D are you in 23R1 on an SU between GA and SU2? If so, this is a know issue. Can you check with the instructions linked below please?Best regards,Rukmal
@EILCTHOMPSON for Scan It on Android, it’s likely that your new certificate has an incomplete certificate chain. If your SSL endpoint is externally accessible and on port 443, you can use https://www.ssllabs.com/ssltest/analyze.html to check for this.If it’s internal and/or on any other port, you might have to use another tool like SSLScan (https://github.com/rbsec/sslscan/releases).Either way, I suggest that you ensure the certificate chain is complete, because Android devices are quite picky about this.Hope this helps!Rukmal
@ISD it’s hard to say anything without knowing details, but if you consistently get failed transactions from the Revise Document setting and our Support Team have not been able to help you resolve it, it’s probably worth sending a Support Issue so that we can dig a bit deeper.In terms of hiding the Revise option, that is a built-in screen, so it’s not possible to hide that option via Page Designer for example. If your users have Edit access for Documents, the Revise option will also be shown as per design.Best regards,Rukmal
@ISD do you have any reference to the bug you mentioned please?
@meshfemi we’ve been looking into very similar errors (more in line with what @SHAUN_KERSLAKE shared) for a while now but they have been very hard to recreate and therefore investigate. Can you report a support ticket on this please? Hopefully that will give us more insight on what’s going on here. Please remember to include device logs and other relevant information like device information, update level etc.Thanks,Rukmal
@Janith we saw this some time ago in the central environments, but then it resolved itself. Can you DM me the environment details please, so that we can take a look?That said, my experience was that it did not prevent me from doing configuration changes.Thanks,Rukmal
Hi @OmnLorreZ, we’ve seen in the past that Android tends to be stricter about SSL certificate chains than iOS and Windows, so that’s quite likely here.Here’s a quick check you can do. If your Test site is running on the standard HTTPS port (i.e.: you don’t have a custom port, like for example this URL → acme-test.acme.com:4242), you can use Qualys’ SSL Labs to check that the SSL Certificate Chain is complete.https://www.ssllabs.com/ssltest/analyze.htmlIf you have the site running on a non-standard port, please DM me your site details and I can try to take a look.Best regards,Rukmal
Hi @LevSupunS, can you share the UPD level the customer is on as well as the exact version of Scan It 10 they are running please?Thanks,Rukmal
@HubertZ I believe this is related to how the browser shares the report content with the email app. Can I know what browser you’re using? and would you be able to install an additional browser (e.g.: Chrome, Firefox etc.), set that as default and try again please?Thanks,Rukmal
@SimoK and @lnilsson I came across this by chance, and I believe you’ve both had resolutions for these, am I right?thanks,Rukmal
@ISD among other things, an MDM solution will allow you to manage which apps are automatically deployed on to your “managed” devices, and control the version of software, so that you can control when updates that we publish to the Store get rolled out to different users.While this is not an endorsement, some of the MDM solutions we’ve seen some of our customers use include Microsoft Intune, SOTI MobiControl and Citrix XenMobile.I hope this helps!Rukmal
@ISD I don’t see the need to logout from the app, but perhaps others who’ve seen this first hand in actual usage scenarios would have some suggestions 🙂When it comes to updating MWO for 50 users, if you want to do it from a backoffice perspective, you’d probably have to look at an MDM solution. Sounds like you’re not using an MDM right now, so in that case, the users would have to trigger the update.Hope this helps!Rukmal
Hi @ISD, initialization is required only if the underlying database structure has changed and we aim to avoid such changes. So I’d expect that a re-init is not needed. That said, you seem to be jumping 7 updates, so there might be such changes.Perhaps you can try to update a single device and see how it goes. Given that re-init can be an expensive operation, you’d then know if you should plan for all users to re-init.Can you elaborate more on the second part of your question, of keeping devices on idle mode or disconnected please?Best regards,Rukmal
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.
