We frequently have work tasks where we issue Purchase Orders against them and send the parts to the techs directly from the vendor instead of going through any depots. This occurs prior to scheduling due to the desire to have the parts in hand prior to scheduling work.However, our techs in the field are using mWO. If the PO is connected to a Work Task, and the work task has not been transferred to mobile, the techs are unable to see the PO at all. This is even when the PO has the tech’s warehouse and location listed on the PO correctly.Is there something we are doing incorrectly? Or is this as designed? If as designed, then why was it designed that way and is there a way around it?
We are aware how to utilize the “Exclude from Scheduling” checkbox at the Work Task level to prevent the entire work task from being sent to PSO. However we have a need to exclude only specific work assignments from scheduling, while other work assignments on the same work task get sent to PSO. Is this possible?
We currently have approximately 90 different workflow configurations intended to drive different eforms being presented to technicians based on specific criteria. All of these workfows are “Work Task” configuration type. This is currently working as intended. However, we have come up with certain scenarios that require some items be mandatory that cannot be properly made mandatory utilizing current system capabilities.We are therefore looking to experiment with the Workflow Type of “Configured Work Task”. But I seem to be having an issue getting these to trigger inside of mWO. I have mirrored one of the workflows that we currently have as far as the filters and sites are concerned, then disabled any of our workflows that may overwrite this one.But for some reason, the system would rather choose no workfow config at all rather than choose my Configured one. Is there something I am missing somewhere? I cannot seem to find any real documentation on how to properly utilize this feat
During the creation of a Service Quotation in mWO, we only create them from a Work Assignment, we never create them raw from the home screen. When doing this, the default value of the Service Quotation Work Type is equal to the Work Type of the Work Task from which it was generated.For our purposes, we wish the Work Type field to always have one specific value. Currently we wish this in every scenario that we will come across without fail. But, these will be generated from as many as five different work types. If the technician does not change the value on the initial creation screen, then he is required to change it on both the Work Order and any Work Tasks on the Service Quotation prior to submitting. If either of these is missed, and the estimators miss it as well, then pricing is incorrect in the end.That scenario does require a minimum two different people missing this value, but if the value should always be the same anyway, then I should be able to default that field to that
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.
