I am in the process of creating a design for a customer using FSM6 update 25. I need to add a new custom screen but when trying to add the screen, the drop down list for the “Screen Type” field is missing the “Standard” option. All others however exist. The message_id ‘Standard’ (message_type=CODE) exists in the metrix_message_def table. Also, the table metrix_code_table does include the row code_name=’MM_SCREEN_TYPE”, code_value = ‘STANDARD’ and active=’Y’.Any ideas what is missing?
I have a screen which I am hiding a Longtext field via client script in the refresh script with the following: setControlRequired("c_collected_sample", "reason", false); setControlVisibility("c_collected_sample", "reason", false); Then I have a list field which has a value changed script attached to it which makes the field required and visible when a certain value is selected via: setControlVisibility("c_collected_sample", "reason", true); setControlRequired("c_collected_sample", "reason", true);However, what is happeneing is that the field is being shown but has the word Required in bold (rather than grey) and it cannot be overwritten - any text added is appended.What is also strange is that if I turn the iPhone to landscape and then back to portrait the field goes grey as expected. I have other screens where the above works as expected so can’t see why this is happeneing.The device is an iPhone (iOS 15) and FSM 6 update 17
Does any one know of any issues with using the password_stretch app param in FSM 6 update 6 and mobile? I have had an email from a customer asking this as when they have set the app param to 1 then mobile fails to activate and the mobile person_id gets locked out. They are not using SSO and mobile is running on iOS. I have seen a number of previous cases around this topic but they don’t seem to match exactly.
A customer is having problems when using OIDC to access the FSM Web Client. The customer has checked their SSO environment and believes it to be correct. However, we are getting a 403 error when trying to use OIDC.From outside their network, I can get to the FSM web client landing page: If I use FSM authentication, I can log in OK: However, if I select “Use OIDC Login” on the landing page, I briefly see the redirect to the Microsoft page: before being bounced back to the root page of the server with a 403 error: Does anyone have ideas/suggestions as to what might be wrong or how to troubleshoot this further?Steve
What is the minimum version of TLS can that can be used between FSM Mobile service and FSM service (FSM6)?
Think I know the answer to this but just want to make sure!The new Attachment API List Screen has a heading of “Attachments” is there any way of changing this? I can’t use a message translation because I have two attachment list screens and need different headers.
Does anyone have information on what size the images for the Home screen should be?
I have an issue whereby when the owner of a task is changed in FSM, the task appears on the new owners device but also remains on the device of the original owner.Any guidance as to what might becausing this would be most welcome as I cannot see anything wrong. This is FSM 6 update 6
I am being asked by a customer if we (IFS) have any statement/certificate that shows that FSM 6 is GDPR compliant?
Before I log this in LCS, I thought I’d post it here in case someone has also seen this and has a solution!I have been getting the attached error on both FSM6 update 7 and update 8 (I have not seen it on update 6). I have created a new mobile design and have created a couple of non related client scripts. The sequence is as follows:Install app on mobile (iOS or Android - fails on both) and activate (or initialise an existing installation)From Home screen tap Jobs to go to the JobList screen - all OK - no errorsGo to Design Screen (JobList)Refresh ScriptsPreviewFrom Home Screen tap Jobs to go to the JobList screen - get the attached errorThis now always happens until an init as above.Note the error is referencing the baseline script although if I replace the script with a custom version with the same code, then the same error occurs. If the Field Service baseline design is used, the same thing happens.
I am seeing a large number of these errors in the Mobile error log (FSM 6u7) for each replicated table - As far as I can see all the user/passwords are correct. Anyone have any ideas what might be wrong?
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.