![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2021\/05\/P2-Field-Explorer-Icon-RGB200.png\"){kind=icon}
<\/p>\n<\/p>\n
P2 Field Operator: Explorer Edition version 4.12 is a minor release that resolves several issues and adds the following functionality:<\/p>\n
<\/p>\n
As you probably know, the Merrick software, including Field Operator, has the ability to switch screens based on Production Entity<\/strong>.\u00a0 In the Merrick configuration utility, Production Entities defined on the Reading Types tab can be assigned different screens.\u00a0 For example, if you want a specific well test screen for Gas Lift wells, define a Production Entity and then Specify a screen for that Production Entity.<\/p>\n This did not work for Run Ticket and Water Draw screens in prior versions.\u00a0<\/p>\n Run Ticket screens have an increased complexity in that they employ the \u201cSwitch Screens based on Reading Type<\/strong>\u201d functionality on the Merrick Business Component<\/strong>.\u00a0 This functionality is necessary because a tank can have multiple types of ticket records.\u00a0 The Switch Screens based on Reading Type setting allows admins to specify which types of tickets are available to each type of tank and which screen should be used for each type.\u00a0 For example, an oil tank can have run tickets, water draws and transfer tickets, while a water tank can only have water draws and transfers.\u00a0 The menu system knows what to display based on these settings.<\/p>\n Due to this complexity, extra steps are necessary to display different ticket screens for different user groups.\u00a0 For example, to have a different water draw screen for tanks in a given area, perform the following steps.<\/p>\n Walkthrough:<\/p>\n To create a separate screen for water draws in an area, first create a Production Entity<\/strong> for water tanks in the area.\u00a0 This is the standard first step to create a separate screen for any screen type.\u00a0 In the Criteria section of the screen, fill in something like \u201cAND Area Is In xxx\u201d.\u00a0 You might also need to adjust the standard Water Tank to specify \u201cAND Area Is Not In xxx\u201d to ensure that the system selects the right Production Entity for each tank.\u00a0 The screen shots below use \u201cALT\u201d as a descriptor, but please use something more descriptive like \u201cEagleford Water Tanks\u201d, etc.<\/p>\n Next, specific to the Run Ticket workflow, create a new Reading Type<\/strong> by clicking \u201cSwitch Screens based on Reading Type\u201d on the Business Component screen.\u00a0 Set the reading type to be valid for the new Production Entity and be sure to set the Calculation to use for this Reading Type<\/strong>.<\/p>\n Finally, on the Screens editor, specify a screen to be used for the Production Entity \/ Reading Type.\u00a0<\/p>\n ProCount and Field Operator will respond to these settings in a slightly different manner, but users can access the specified screen in both systems. In ProCount, users will see the name of the Reading Type in (the example Alt Water Draw) when adding a new record.\u00a0 In Field Operator, users will still utilize the \u201cWater Draw\u201d menu, but the override screen or the standard screen will show based on the Production Entity criteria of the selected tank.\u00a0<\/p>\n New to version 4.12 is the ability to choose which Daily Notes are synced to Explorer.\u00a0 Each organization makes decisions about how Daily Notes are used versus Formal Comments.\u00a0 Depending on the data entered in Daily Notes, it may not make sense to display them in Explorer.<\/p>\n Daily Notes are always stored by Field Operator in ProCount\u2019s CommentsTb table.\u00a0 Formal Comments are always stored in Explorer\u2019s com.Comment table.\u00a0 Depending on the settings on the Commentary tab of the Field Operator options screen Daily Notes may be stored in Explorer.<\/p>\n In Version 4.12 is the ability to choose whether the Formal Commentary icon will display in Field Operator for Route Surveillance users.\u00a0 (The commentary icon is hidden if Field Operator is not connected to P2 Explorer.)\u00a0 Control this on the Field Operator Options screen, Commentary tab.\u00a0\u00a0 This option is set to true by default.<\/p>\n \u00a0<\/p>\n New to Field Operator version 4.12 and Explorer version 4.13 is the ability to include a reference to a Merrick Form on a Case by filling in a Merrick Form in Field Operator.\u00a0 For example, a Case can be defined that asks the user to enter a Well Test record in Field Operator. \u00a0<\/p>\n This could be used in many different workflows.\u00a0 For example:<\/p>\n The first step to implementing this functionality is to set up a Field in P2 Server Management with the Merrick Form data type.<\/p>\n Next, create a Case Form and include the Field:<\/p>\n Next, users (or Sentinel) can create new cases using this Form for a given entity.<\/p>\n The new Case will sync to Field Operator for users who have downloaded the route to which the entity is assigned.\u00a0 Also, if the Case is assigned to a particular user, the location will download to that user\u2019s device even if the route has not been selected to be download.<\/p>\n In Field Operator, the user will open the case and either select an existing form or create a new one by tapping the + icon.\u00a0 Once the new form is saved it displays on the case form and the user should save the case and publish the changes.<\/p>\n Now in P2 Explorer, the case is updated with the date and user who filled out the form in Field Operator.\u00a0 The case can now be closed in P2 Explorer (or it could be automatically closed by using a rule).<\/p>\n![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2023\/08\/image001-3.png\")
<\/a><\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nNew Configuration Setting: Sync Daily Notes to Explorer<\/h2>\n
<\/a><\/p>\n
\nNew Configuration Setting: Show Formal Commentary<\/h2>\n
<\/a><\/p>\n
\nLaunch a Merrick Form from an Explorer Case<\/h2>\n
\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n