HiSo windows and iOS is working and only Android left. Are you using any loadbalancer or any other thing which also require a certificate? In android the certifcate chain need to be the same on all places, which iOS and Windows does not require. If I understood it correctly is though that you on the android device get the record, but not the notification about the record and usually when it is certification mismatch, then you will not receive the record either. But just asking the question, so we can rule that off completely.
HiReally good news then RegardsJohan
HiI checked in the latest version of IFS Cloud, 24R1, and the error you have got in Apps for Page Designer for Mobile Integration is not there in that version. I also checked in 22R1 environment and there we do have the error. I get the same error as you when going to that page. RegardsJohan
Hi JanIt should work with remote deployment as well. We are sending the messages fromm backend through the azure notification hub to the device. You should get a message on your device when you have a new notification. We had a report the other week around something that could be the cause for your experience. I have added it in the 24R1 documentation. I am not sure, but this could be the reason.-----Production environments restrict all outgoing calls except for IFS approved url's. For push notifications to work, backend should be able to communicate with Azure service bus. Depending on the app you are running there can be several servicebus. Namespace.servicebus.windows.net Example: mWorkOrder.servicebus.windows.net for Mobile Work Order ----RegardsJohan
HiWhat IFS Cloud version are you running on? RegardsJohan
HiYou say it works fine with Chinese tradisional on Android phones. Does that mean that you get everything translated for MWO, like logout buttons as well as e.g. work order related data? On iOS do you get some translations in Chinese tradisional?I am not sure it exist any work around for this problem, not without any changes from the iOS client.regardsJohan
HiHave you followed the steps from this page: https://docs.ifs.com/techdocs/23r1/070_remote_deploy/400_installation_options/030_aurena_native_apps/#setting_up_push_notification_hub I saw that you refrerred to the trouble shooting guide. Have you set up an own Azuer hub or used the default one? RegardsJohan
HiI am not 100% sure what you mean with your question, but you usually do not need to register the device or user. It gets registered for the app/user the first time you login as that user. RegardsJohan
HiI would say, yes, you shold retry to reprocess those two transactions. They have been caught in the failed trasnactions due to that the Mobile Sync Data table has been locked. And as this is rather transactional data I would suggest to re process them. RegardsJohan
HiSo is it so that it still doesn’t work for the end users? Which notifications are you trying with? As it can be different user permissions within the functionality as well, As an example. Supplier invoice have their on set of permissions within finance and Pucrhasing have theie own set of permissions as well. And both of them are tied to basic data. But if the user can do it in IFS Cloud that is not then the reason for the error. Also are you using any LTU licence for the end users? RegardsJohan
HiEA means Early Availability (Access) and that is given to some few customers that are involved in the pilot programs that IFS hase before the real release. GA means General Availability (Access) and that is the release that goes out for any customer to take. RegardsJohan
HiDoes the administrator also login via single sign on?Please double check that the end user really has Aurena_Native_Runtime granted to them. The security groups needs to be granted to a functional role. Does the user have that functional rule you have granted the security groups to? Again just to double check.
HiHow does the purchase requsition (PR) look like in the backend with regards to authorizers? What I mean is, do you have several different authorizers that needs to authorize the PR and should that go in a authorization sequence? Like user 1 need to authorize first and then user 2, who is above user 1 should authorize. It seems like several users get the authorization at the same time and then the rules for authentization that has been set up needs the first user to authorixe before the second one can authorize. It should not work in that way and if the rule is setup that first one user should authorize, then it should not be sent to the other authroizers before the first user has authorized. I think you will need to report this to IFS, so we can have a deeper look into this issue.RegardsJohan
HiThe links works fine for me and we do have a broken link test to see if this is working. I need to check up those pages as they might just be accesible if you are an IFS employee or should be moved so they are publically shown. Good catch as it was not covered by our tools and it works fine for me. I am not sure who is dealing with reporting and what devices can or cannot be used. I need to check a bit internally and come back. RegardsJohan
Hi AselaIt was the correct place, with the share poitn site, when I wrote it. But since then it has been moved into the technical documantation. Whewther customer can see this or not I do not know.This is the public site for 23R2: https://docs.ifs.com/techdocs/23r2/080_supported_platforms/For the app client we do not write anything about the reference devices we used to do in Apps9 and Apps10. With regards to printers, I do not know if we have that information or not. The part with Windows devices, I guess you refer to the windows mobile phone with the specific OS that was present some time back, We are not supporting those type of devices in IFS Cloud. We support Android, iOS and Windows (desktop). RegardsJohan
HiThere is not possible to process WOs offline without MWO and Touch App solution. The MWO app and the use of Touch Apps is the only place where offline support exists.IFS Applications is e.g. only working online. RegardsJohan
You should always try and be on the latest available version that exist on the app store. As Aleander Heinze mention, The apps in the app store is backwards compatible and we only do have one released app for all cloud versions, I also think you should download the apps prior to any upgrade of the IFS Cloud release on the server side. Then you will alwyas be sure it will work when you upgrade the IFS cloud server parts
HiWe are looking into this issue right now anc are checking what has gone wrong in this latest submission that was only to comply with Android API policy, to be on the latest api level available. My suspicion is that it has something to do with the certificate we have used and need to recheck that we have signed the android APK for notify me witht the same certificate as we signed the account manager.RegardsJohan
HiI think you should report this to IFS for further investigation. It is very hard to say what is going wrong just from the picture. You said this started to happen some few days ago. Did something special happen in the environment. Did anyone create a new custom field or did you get any new delivery to server sid?. It is also good to know which client version you are using as well as what Apps10 UPD release you are running on. It is also good to get the logs to see if those reveals anything more. RegardsJohan
HiYou cannot add a custom attributes for Notify Me using Page Designer. The only way to do that is to do a customization and include the custom attribute in what is sent to the app. It means coding and deploying the solution into the database.RegardsJohan
We have corrected one white screen issue and that is already included in Apps10 UPD20, which is the latest released client. In apps10 the login credentials and how often that should come is sather a setup issue in the environment. It depends how it is set up and if you are using SSO as well. I am not that good at that part of the setup though
We did this correction for Apps10 UPD17 in TAS. So your version of the TAS this correction does not exist in.
What client app version are you using? we did a correction on this and delivered this on Apps10.
HiPlease report this to IFS, so we can have a closer look at the issue. I guess this is in Apps10, but it is not stated in the message above. RegardsJohan
From practical point of view in 95% it is possible and quite easy. Of course it should be related to business functionality not Framework or any Binary patch. Yes that is true,.
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.
