![\"\"](\"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.15 is a minor release that resolves several issues and includes the addition of the following functionality:<\/p>\n
<\/p>\n
Typically, users are expected to publish changes for each location as they complete the entries. In the standard Field Operator workflow, a user would:<\/p>\n
Even if offline, users should follow this approximate workflow and published changes will be pending until the device connects to the internet. Sometimes, users may close the Location Detail screen or enter directly from the Grid Summary without publishing. This leaves the possibility of forgetting to publish changes.<\/p>\n
In version 4.15, we\u2019ve rearranged and modified the icons on the main menu to make it more obvious that changes need to be published. The Sync icon is now at the highest level of the menu and the Journey Planner icon has moved to within the settings menu.<\/p>\n
When there are changes to publish, the Sync icon now changes to the upload image and changes colour.<\/p>\n As in previous versions, when the sync icon is clicked, the Sync screen shows which locations have changes and offers the option to Publish All<\/strong>.<\/p>\n This functionality is only available on Windows devices. When the user closes the application and there are changes that have not yet been published (and the device is connected to the internet), a prompt asks the user if these changes should be published.<\/p>\n Tapping Publish Changes<\/strong> will invoke the publish process for all changes and then close the app. Skip for now<\/strong> will simply close the app and Cancel<\/strong> will leave the app open.<\/p>\n This feature is meant to help users who \u201cfloat\u201d. On Monday, Bob may download routes A, B and C as he\u2019ll be in that area for the day. On Tuesday Bob may only need Route C. In previous versions, the app would download A, B and C as soon as it connected Tuesday morning. In 4.15, if 3 or more routes were downloaded previously, the user will be prompted to keep the same routes or select different routes when the app is opened for the first time for the day. Users may not notice this change to the sequence of events, when the app is first started on a given day.<\/p>\n On startup, if the device is connected to the internet, the user will see a Downloading\u2026 progress bar before the data is displayed. In previous versions, the screens would open and then the download process would begin as a background process.<\/p>\n Downloading before displaying the screens reduces total startup time and keeps the user from seeing a screen where data is expected but not yet downloaded.<\/p>\n In ProCount 4.15, analysts can edit and enter downtime events without the need to access Field Operator. In adding this functionality to ProCount, the settings for downtime events are now stored in the ProCount database and are now company wide.<\/p>\n In addtion, the ability to store more than one event on a day was added to both ProCount and Field Operator.<\/p>\n Although this is likely an unusual situation, if one downtime event is affecting a well or piece of equipment on a given day, the user can now add another event. For example, let\u2019s say one downtime event was entered that affected several wells for part of the day on April 29. Note that this electrical event ended at 1:00 PM on the 28th<\/sup>:<\/p>\n On the Location Detail screen, the 6 hours of downtime related to the electrical issues is displayed.<\/p>\n When the downtime cell on the 29th<\/sup> is tapped, the downtime event screen is opened. New to 4.15 is the + icon to add another event.<\/p>\n Let\u2019s say a Flow Line event affected this well (and others) from 10:00 AM through 10:00 PM:<\/p>\n Notice the previous \/ next buttons allow the user to toggle through the events that affect the well \/ day from which the screen was accessed.<\/p>\n Now that two events are affecting the well for the day, the system has calculated the total hours the well was down:<\/p>\n In this example, since the times of the events overlapped, the total hours are calculated accordingly. Event 1 had the well down until 1:00 PM (7:00 AM \u2013 1:00 PM). Event 2 affected the well from 10:00 AM till 10:00 PM. Since they overlapped, the well was down from 7:00 AM till 10:00 PM or 15 hours.<\/p>\n In P2 Explorer <\/strong>administrators can define pages that are available when a given entity is selected. For example, when a well completion is selected, a menu item can be defined to display a decline analysis page:<\/p>\n The P2 Explorer user should:<\/p>\n After these steps are complete, the page will display in the links section for any entity with the Template to which the Link was assigned. In the example, the Decline Analysis link will display for any Completion entity.<\/p>\n New to Field Operator 4.15, these links can be made available to Field Operator users.<\/p>\n Note:<\/strong> Links will only work on Field Operator devices if the device has access to the Explorer page. Users may need to log into a VPN to connect to P2 Explorer.<\/p>\n On the P2 Explorer<\/strong> tab of the Field Operator Options<\/strong> screen, select Show Explorer Links in Field Operator<\/strong> to enable this feature.<\/p>\n When enabled, the Grid View<\/strong> and Location Detail View<\/strong> in Field Operator will display the Links icon which shows all links defined for the entities for a given location.<\/p>\n When the user chooses to open a link, the native browser is launched with the URL. Along with the URL defined in P2 Explorer, the ?selectedEntity=xxxx query parameter is added in order to open the context of the entity.<\/p>\n Dashboard Links<\/p>\n When the Show Explorer Links in Field Operator option is selected, administrators can also add links to Explorer and other systems which are not related to a particular entity.<\/p>\n These links are available when the user selects the Dashboard Links<\/strong> option in Grid View.<\/p>\n Some customers would like to only allow admins to assign certain users in the User Authorization<\/strong> section of the configuration utility. In version 4.15, we\u2019ve added a new setting in the .config file that allows you to limit the list of users that\u2019s displayed.<\/p>\n Edit the P2.FieldOperator.Config.exe.config file and locate the appSettings section. Add a new key Allowed AD Group<\/strong>. For example:<\/p>\n When this app setting is set, only users in the specified Active Directory Group will display when admins choose to Add a user to the list of authorized users.<\/p>\n![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2024\/05\/image001.png\")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nClosing the App Reminds the User to Publish (UWP Only)<\/h2>\n
<\/a><\/p>\n
\nAsk the User Before Downloading a Large Number of Routes on App Startup<\/h2>\n
<\/a><\/p>\n
\nOn App Startup, Data Will Download First<\/h2>\n
\nAbility to Enter Multiple Downtime Events on a Day<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nLinks to P2 Explorer Pages<\/h2>\n
<\/a><\/p>\n\n
<\/a><\/li>\n<\/a><\/li>\n<\/a><\/li>\n<\/a><\/li>\n<\/a><\/li>\n<\/ol>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nAbility to Limit User Authorization List to an Active Directory Group<\/h2>\n
<\/a><\/p>\n