Field Service

Get Involved. Join the Conversation.

Topic

    Kimberly Phillips
    Using the list of Technicians to populate a combo box
    Topic posted October 31, 2016 by Kimberly PhillipsGreen Ribbon: 100+ Points 
    109 Views, 7 Comments
    Title:
    Using the list of Technicians to populate a combo box
    Content:

    I’m looking for a property that contains a list of technicians that I can add to a mobile form. Or, I would like to create a custom property  that uses the technician list as the source for the drop down.

    Much like the property “Activity Work Type” uses the Activity Type list as the source for that drop down.

     

    Comment

     

    • Graham Sawell

      Hi Kimberly,

      There's no 'simple' solution but it's definitely doable. You would need to populate and maintain an enumeration field in any case. However, with the new 16.8 functionality you are able to update and replace enumeration properties via the REST API metadata methods. You would need to control the logic outside of OFS that retrieves and inserts the data on a routine basis, but it's certainly achievable. Otherwise it is still doable, but you would need to manually populate and maintain this data in the enumeration field.

      Alternatively, you could create a plugin that calls the Get Resources REST API method and do something with HTML5, but you would be limited to doing this on a separate mobility tab, which may or may not suit your requirement.

      Hope this helps.

      Regards,

      Graham Sawell

    • Kimberly Phillips

      Thanks Graham that is helpful. Currently, our environment is 16.2, but 16.8 is coming in February for us.

      Can I update/append/remove an enumeration list to keep the list of technicians current, or would it be better to scrub the list each time an add/update occurs?

       

    • Hardik Gupta

      Hi Kimberly,

      Yes you can update/append an enumeration list. You will not be able to remove a value once created. You can deactivate the value.

      This can be done using Core Manage -> Properties page or via the REST API as mentioned by Graham. 

      Link for REST API : https://docs.oracle.com/cloud/latest/fieldservicecs_gs/CXFSC/api-Metadata-Properties.html

      If you can specify for what particular scenario is it needed then it will be easier to help out.

      Regards,

      Hardik Gupta

    • Kimberly Phillips

      Thank you Hardik.

      We have a group of Quality Control Inspectors whose job it is to review completed or in progress jobs dispatched to our Field Technicians.

      Their day is planned using ETA Managed. They find the jobs they intend to review and create an inspection activity on their route with key information and notes about that job.

      When they leave the office, they switch over to ETA Mobility and begin their route. When they start the inspection activity the form they fill out is custom to our “scorecard” questions about how the tech performed the tasks and how they interacted with the customer. The first field on the scorecard is Tech’s Name: ________. It is free key text and it is most often keyed wrong with nicknames, shortened names and many other things that are not the techs name.

      The rest of the scorecard questions are yes/no; an easy enumeration list to create once then done. We have 2,000 technician; not an easy enumeration list to maintain. 

      Reporting is difficult and associating the inspection back to the technician under review is nearly impossible.

      My goal is to turn this into a drop down list of the Technician user list in ETA Direct. I was hoping to do it however the "Activity Work Type" property in does it, but that seems to be a back end proprietary function. 

      From Graham’s advice, I was going to create a scheduled task that would re-populate the list every day to handle tech churn.  

    • Hardik Gupta

      Hi Kimberly,

      I would suggest that the Tech Name should get auto populated based on the activity id or work order that the Quality Control Inspector enters. Because searching the right person can also become difficult from a drop down list of 20 thousand technician. 

      If auto populating the tech name isnt possible then creating a scheduled task is the way to go.

      Regards,

      Hardik Gupta

    • Kimberly Phillips

      I like the direction you’re taking this Hardik, but I’m not sure I would know how to auto-populate base on the activity ID or work order the QC Inspector entered.

      First, they are keying the ID in as well (copy paste I think, but the inspection is more about the tech than the job. If it is typed incorrectly, it’s not as critical.) I am not aware of any other way to get the ID of another activity when creating an activity. Is that possible?

      Assuming it is keyed correctly how would one lookup the tech assigned to it?

    • Graham Sawell

      Hi Kimberly,

      I'd be tempted to remove the Tech Name completely, as the Inspector I assume is putting the activity ID in there anyway? If you know the activity ID then you know the associated resource. If you know the resource then when you come to report on it, just have the report join the activity ID the Inspector supplies to the activity ID of the job, removing the need for the Inspector to capture it. We have the data on OFS and whatever reporting system you are using already.

      If you need to have the tech name in OFS, you could do one better by having a routine API job that checks for any Inspector activity type, checks the activity ID field supplied by the Inspector and auto-populates a read-only Technican Name field based on that ID. To make it really smart you could then have that routine put "Tech not found" or similar in that read-only field when it can't find the activity, and have the form throw a validation error when the inspector tries to save which means you capture any time the Inspector enters a typo on the activity ID, helping your compliance.

      If that doesn't work because you have teams and you may be inspecting one member rather than the activity/teamholder, given your requirement I would advise going down the plugin route, you could have the 'scorecard' as a separate tab, and HTML5 will give you a lot more flexibility and allow you to create things like auto-complete search datalist fields using AJAX, storing the technician list as a json file on the web server which you could update/replace as you please.

      In this scenario, when the inspector starts typing in the name of a tech, the form will auto-complete the field or start dropping down options based on what they're typing. You could then validate to ensure that one has been selected or properly typed.

      Hardik is right, the requirement to deactivate enumeration values and the sheer number of technicians you have would make that solution very difficult to manage if relying on the OFS property alone.

      Regards,

      Graham