Hello,I am currently working on a FSM/PSO solution where the tasks creation is done by backend systems and sent to FSM via API. FSM/PSO is only responsible for task assignment, scheduling and task status updates to the backends.The problem is to do with two scenarios and their relation:-Multi-day tasks: tasks with a duration longer than a technicians shift, taking more than 1 day. For example, a multi-day task with a duration of 20 hours is gonna be split into tasks (5 in this case) of duration of maximum 4 hours before being sent to PSO.-Interrupted tasks: when a technician puts a task "ON HOLD", a copy of the task is created to get reassigned. It can get reassigned to the same technician. This interruption comes from the legacy mobile app.The work order id's in the back-end systems have a 1-to-1 relation to the task id's in FSM. What is the best approach to ensure the task status for a given work order is correctly updated in the back end system? The problem here is how can I ensure
Hello everyone,We're working on a FSM+PSO solution where the creation/update of objects (task, person, place, etc.) is done through the FSM API and the customer need to adapt it's backend system to receive and process messages following the FSM API structure so we would like to know if it's possible to extract the schema and WSDL files from the MetrixIntegration Service of the FSM XML API. Thank you,José Pereira
Hello,We have a scenario with a client that currently they click in a button in their legacy system and they "fetch" for example 1000 tasks and related objects from a shared queue and create them in their own system. Is it possible to do something similar in FSM with Monitor Schedule Jobs and XML maps configuration?This communication is done through FTP communication. Thanks
Hello,I am currently working on a FSM-PSO solution where the field technicians of the client work on an external custom app. The field tech is gonna have a number of tasks pre-allocated sent by PSO at the start of the day and as he completes one, more are sent. Everything is fine until the field tech may get sent to a place with no service (no internet and/or no phone service) for several hours and complete all the tasks assigned without being possible to communicate with PSO.In this case, there is also a scenario in which he could complete a given task(change its status offline) and go to the next one he has in his phone (previously sent). Because he is without coverage, the updates won't go to from that external legacy app to FSM and as a result PSO won't be updated with the right status therefore for PSO it would mean that he is still doing the second task and once the app goes online he will receive all the updates but potentially this will have an impact on the optimization since
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.
