We are not planning on adding the IQA capabilities to the FSM 6 web client. This decision was based on the level of effort to implement that vs value it is adding. Here the effort far outweighed the value as there are very few, if any, customers utilizing the IQA capabilities. Since there is such a large overlap in capabilities between IQA and surveys, my question would be are there unique business requirements here that can only be solved with IQA or would a solution involving some combination of surveys and business rules also work?
Documentation for Dynamic Scheduling can be found in the embedded help files, which are accessible through the help menu in the application. Regarding the service_hours_response_type app param, this parameter allows you to use a special time commitment record on your task to define non-standard calendar hours (e.g. outside of the customer’s normal working hours). It is an optional feature and is not necessary unless you have cases where you want to override the customer’s normal availability hours. If desired to use this, then you would want to define a new (i.e. do not reuse your existing Accepted of Arrival response types) response type code that you would use on the time commitment for these special hours. Then the calendar that is defined on that time commitment (as identified by task id and response code) will be used to determine availability for the job. The time commitments for these exceptional cases would typically be created through the standard time commit generation b
Hi @qquac - that is not a core capability of the baseline FSM 6 Mobile application. If it was previously delivered as a customization, then it’s possible that customization would need to be uplifted and the mobile app be rebuilt and redistributed when you take subsequent baseline application updates. I see that you’ve added an Idea now to have this be in baseline product. We will review that Idea along with the previously delivered customization and consider for inclusion in a future product update, but it is not currently part of a planned release.
Who/when log levels are modified are not currently tracked.
I’m not aware of a way to accomplish this with OOB functionality. To do so via client scripts, you would need some new events to hook into - namely LostFocus and/or CloseScreen events for the screen. Even so, this may be difficult as the use could have several screens open on different tabs and conceivably you would only want to track their time while they were actively using a certain screen. Likewise, they could have multiple tabs open for the same screen, which would further complicate things.Easy enough to track the date/time that a particular screen instance is opened or navigated to, but not possible when closing or navigating from.
IFS publishes product roadmaps twice annually. The Product Roadmap is intended to cover only the current and next product releases. This is done to ensure a high likelihood of delivering what we have published in the roadmap. We will be publishing a new roadmap which will be for the 24R1 and 24R2 releases very shortly.For longer term areas of investment beyond that period of time, the Statement of Direction will give some insight into that, but with a lower level of detail and focus on areas of investment rather than features. A new Statement of Direction will be published very shortly as well.The latest versions of the Product Roadmap and Statement of Direction are always accessible right here in Community in the Product Updates section.https://community.ifs.com/p/productreleasenotes?
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.