![\"\"](\"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.11 is a minor release that resolves several issues and adds the following functionality:<\/p>\n
<\/p>\n
In versions before 4.11, users had to close the Run Ticket screen in order to access the Seals screen.\u00a0 If the current correct seal is not marked as Still On when entering a ticket, this could cause the user to navigate back and forth between the screens which could become cumbersome.<\/p>\n
In 4.11 the Ticket screen now has a button which allows the user to edit, add or clean up seals without interrupting the workflow of entering a ticket.\u00a0<\/p>\n
Note<\/strong>:\u00a0 Enable this functionality by selecting Access the Seals screen from the Ticket screen<\/strong> on the Field Operator Options<\/strong> screen in the configuration utility.<\/p>\n The following examples demonstrate the different ways the user might use the new screen interaction:<\/p>\n This workflow is the same as prior versions.\u00a0 So long as tickets are being entered in chronological order, the Seal Placed<\/strong> can be filled in on the Run Ticket screen and the Seal Removed<\/strong> defaults to the latest seal that\u2019s marked as Still On<\/em>.<\/p>\n Optionally, you can choose to enter the seal information using the seals screen.\u00a0 In this example, ticket number 483200<\/strong> is being entered and the user taps Seals Detail<\/strong> to enter the seal information.<\/p>\n Without closing the Run Ticket screen, the Seals screen is displayed where the new seal can be added, and the existing seal removed.\u00a0 When the Seals screen opens select the location and the + icon to add the new seal.<\/p>\n Once records are correct on the Seal screen click Close<\/strong> to return to the Ticket screen where the Seal Placed and Removed information will be updated.<\/p>\n Example 2 above might not be as realistic since the user visited the Seal Detail simply as an alternative to entering directly on the Run Ticket screen.\u00a0 More realistic is the scenario where the Seal Removed defaults to the wrong value on the ticket so you need to clean up the seals before proceeding.<\/p>\n In this example, ticket 483201<\/strong> is being entered.\u00a0\u00a0 On site, the seal currently installed on the load line is 169257<\/strong>, but the system has no record of that seal.\u00a0 The latest Still On seal on the load line in the system is 169152.<\/strong>\u00a0 During the normal flow of entering the ticket, the discrepancy must be accounted for by visiting the Seals screen.<\/p>\n In this case, since there is a missing seal, from the Seals screen, you could enter the missing seal by clicking the +<\/strong> icon.\u00a0 Remove the seal that the system has on record for the correct reason according to your administrator\u2019s policies.\u00a0 Then add the correct seal.\u00a0 The correct seal may or may not be associated with a run ticket depending on the reason that it is missing.<\/p>\n Once the missing seal has been entered, the system shows the correct seal that was installed when the user arrived on site to execute the run.\u00a0 Next, remove that seal and add the seal being placed with the run ticket in progress.<\/p>\n As you\u2019re adding and editing seals on the seals screen, the Run Ticket record is still in progress.\u00a0 Once the seal situation is corrected, click Close to return to the ticket screen and complete the entry.<\/p>\n The run ticket screen will reflect the Seal Placed and Seal Removed that were the result of the work on the seals screen.<\/p>\n Accessing the Seals screen while entering a ticket might also be helpful if multiple seals are being associated with one ticket. In this example, a seal was changed on the load line and the circulating line for a ticket.\u00a0<\/p>\n From the Run Ticket screen tap the Seals Detail button.\u00a0 Be sure to enter the ticket number on the ticket screen first in order that the right ticket number defaults on the seals screens.\u00a0 The ticket being entered is 483224<\/strong>.\u00a0 First tap the Load Line and the + icon to replace the seal at that location.<\/p>\n As each new seal is associated with the ticket, a green check shows on the seal locations list to indicate locations that have an associated seal.<\/p>\n Next switch to the Circulating Line and click the + icon to replace a seal at that location.<\/p>\n Now there are green checks at each location with seals associated with the ticket.<\/p>\n Since there are multiple seals associated with the ticket, the seals fields no longer display on the ticket screen, but the Seals Detail button indicates the count of associated seals records.<\/p>\n Version 4.11 of Field Operator allows admins to authorize Active Directory groups instead of just individual users as in previous versions.<\/p>\n On the User Authorization<\/strong> screen in the Field Operator Configuration<\/strong> utility, select the Authorized Groups<\/strong> tab to Add<\/strong> groups from your Active Directory.\u00a0 Once a group is added to the Authorized list, assign routes or route groups to grant access to all members of the AD group.<\/p>\n Now as your network administrators add members to the Active Directory group, they will automatically be authorized to the route or routes that you\u2019ve assigned.<\/p>\n Historically, administrators could capture custom records in the P2 Merrick system by adding Custom Business Components<\/strong> in the Merrick Metadata Configuration Utility<\/strong>.\u00a0 Many customers have utilized custom business components, but to do so required involvement of a DBA to add a new table structure to the database and an advanced understanding of how database structures should be designed.<\/p>\n P2 Explorer<\/strong> has a built-in concept called Entries<\/strong> which are customizable records that can be configured without adding tables to the database.\u00a0 Designing the forms to capture entries can be more straightforward than using P2 Merrick custom business components.<\/p>\n New to version 4.11 of Field Operator, administrators can include P2 Explorer forms within the same user experience as P2 Merrick forms.\u00a0\u00a0<\/p>\n Note<\/strong>:\u00a0 The Explorer Forms functionality within Field Operator is only available to customers with a license to the Route Surveillance software suite.\u00a0 Customers with Route Surveillance can add Case forms to Field Operator.\u00a0 Customers with Shift Log licensing can also use General Entry forms in Field Operator and the mobile version of the Shift Log Workbook experience within Field Operator. See Shift Log \u2013 (petroleumplace.com)<\/a> for information about Shift Log.<\/p>\n The first step to creating a custom form in P2 Explorer is to create Fields<\/strong>.\u00a0 A field can be re-used on multiple forms and includes such attributes as its data type, label, etc.<\/p>\n Next, a Form<\/strong> is designed by arranging selected Fields<\/strong> in the desired order.\u00a0<\/p>\n Finally, an Explorer Form is associated with a Merrick Production Entity<\/strong> on the new Explorer Forms<\/strong> tab in the Field Operator Configuration Utility<\/strong>.\u00a0 Select the Production Entity on the left and specify the Explorer Form(s) to be displayed.<\/p>\n Once the Explorer Form is connected to the Production Entity, the form displays in Field Operator on the Forms<\/strong> menu alongside the standard Merrick Forms such as Well Tests and Run Tickets.<\/p>\n Explorer Forms offer a few extra features that Merrick custom business components do not.\u00a0 One such feature is that an Explorer form can display Fields conditionally.\u00a0 For example, the Signs \u2013 Safety Comment field only displays if the Signs \u2013 Safety field is set to Unsatisfactory.<\/p>\n Explorer forms also have attachment functionality, so users can add photos if needed and as seen in the sample screen shots, pick lists (called Named Lists) can contain colors and icons.<\/p>\n Explorer forms also have attachment functionality, so users can add photos if needed and as seen in the sample screen shots, pick lists (called Named Lists) can contain colors and icons.<\/p>\n Please read more about Explorer Forms in the P2 Explorer help center: \u00a0Form Configuration \u2013 (petroleumplace.com)<\/a><\/p>\n We\u2019ve added \u201cuser\u201d fields on the TankRunTicketTb table.\u00a0 This will keep administrators from using additional queries or parameter data elements.\u00a0 Please upgrade your ProCount database using the Merrick 4.11 installer.<\/p>\n A new function has been added to allow administrators to send a one-time message to all users. In the Field Operator Configuration utility, select the Admin Messages button.<\/p>\n The next time the app syncs for each device, the user will see the message once and must Acknowledge the message to continue.\u00a0<\/p>\n Later, admins can return to the Admin Messages screen and double click on previously sent messages to see the list of users who\u2019ve Acknowledged the message.\u00a0 The expiration of the message is exactly the number of days from the time you entered it. For example, if you save the message at noon, it will expire X days from now at noon.\u00a0 A message can always be deleted if you want it to stop appearing for users who have not yet seen it.<\/p>\n The setup.exe program that installs the Field Operator server has been enhanced to include an upgrade<\/strong> parameter.\u00a0 This allows the software to be upgraded without user interaction.<\/p>\n In the Grid Summary View <\/strong>for Comments<\/strong>, previous versions would not display the name of the user\u2019s name for Daily Notes<\/strong>.\u00a0 Also searching by user did not return the daily notes entered by the user.\u00a0 Based on customer feedback, now Daily notes will display the user\u2019s name and return in searches.\u00a0 The user displayed is the last user who changed the text as Daily Notes allow users to edit one another\u2019s text.\u00a0 (Users are only allowed to edit their own formal comments and replies).<\/p>\n![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2023\/05\/image001.png\")
<\/a><\/p>\nExample 1:\u00a0 Prior Seal Information is Correct, and the User Enters Seal Information on the Ticket Screen.<\/h4>\n
<\/a><\/p>\nExample 2:\u00a0 Prior Seal Information is Correct, and the User Opts to Enter the Seal Information on the Seal Screen<\/h4>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nExample 3:\u00a0 Prior Seal Information is Incorrect, so the User Uses the Seal Screen to Clean up the Old Seals and Enter the New Seal Information<\/h4>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nExample 4:\u00a0 Associate Multiple Seals with One Run Ticket<\/h4>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nAuthorize Users Based on Active Directory (AD) Group Membership<\/h2>\n
<\/a><\/p>\n
\nCapture P2 Explorer Entries within the Field Operator Forms Menu<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nUser Number and String Fields Added to the Run Ticket Table<\/h2>\n
<\/a><\/p>\n
\nSend Administrative Messages to All Users Via Sync Process<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n
\nServer Upgrade Command Line Mode<\/h2>\n
<\/a><\/p>\n
\nDaily Notes Now Included When Searching Comments by User<\/h2>\n