FieldStack settings for all devices and locations can be managed by administrators by choosing the Options tab on the main form and clicking [Configuration Management] button.

This action will open up the Configuration Management form.

General Overview of Settings:

There are 3 levels of settings: Company, Location and Machine.  

  • Company settings are pushed down to every location and machine.  
  • Location settings are settings that apply to all machines in the location.  
  • Machine settings are those that can be changed on a machine by machine basis.  

Default vs. Modified:

If a setting is bold, that indicates that the setting has been modificed from the FieldStack Default.

Keyword Search:

Want to search for a particular setting?  Type the name in the filter search field to quickly navigate by keyword.

Machine-specific Configurations:

1. Select the location or machine you want to configure using the navigation tree on the left.


2. If you are on a computer that needs settings verified or changed, click on [Select this machine proto] and you will be taken directly to that machine without having to navigate the tree.

3. To view current version, last seen and other machine attributes, click on [Set Tree List Column Options].  A fly-out panel will appear.  Choose the additional columns you'd like to view from the panel. 


Default Settings:

We strongly recommend that  you set-up location and machine defaults.   In doing so, it makes future administration faster, easier and more consistent.

Bulk Changes/Scheduling Updates:

A. Updates can be scheduled at the company, location or machine level.  At the location and machine level, one or more locations or machines can be updated.

  • To schedule a company level update, select the company
  • To schedule a location level update, select a location
  • To schedule a machine level update, select a machine

  • Then click on the [Access Company or Location Set Defaults] button to open up a fly out panel.  


    When the fly-out panel appears, click the [Schedule Updates] button. The Schedule Updates dialog box will appear. 


    Note that the Schedule Update dialog box should display the correct level of update:

    FA-780-ScheduledUpdateCompanyWithRedOutlines.png  FA-780-ScheduledUpdateLocationWithRedOutline.pngFA-780-ScheduledUpdateMachineWithRedOutline.png

    B. Once the Schedule Updates dialog box appears, use the tree list to select what should be affected by the change.(1)  

    C. Next, edit the setting you want to change in the normal editor (2), and press [enter].  That change should pop up on the dialog box.  

    D. Once the Scheduled Updates dialog box has the settings you want changed in it and the machines or locations you want to change, select a date and time to apply the change (3).  

    • If you want it to go out immediately, choose a past date.
    • If you want it to go out at a future time, choose a future date.  
      • The date-time picker will allow you to select the date-time in local time only (3).  Local time means local to the computer that you are using to do the scheduling.
      • It will then translate and display the selected date-time in UTC to the left (4).  
      • Note 1: The Bulk Changes/Scheduled updates can apply changes for stores in different time zones.  That is why changes are scheduled in local time of the scheduler's computer then saved in UTC time.
      • Note 2: UTC time helps people in different time zones communicate efficiently and clearly with each other about the timing of an event by always referring to a common, standardized time zone (UTC).  If we did not use UTC and an event was scheduled to occur simply at 9 pm, then the time zone is implied.  People in different time zones will have to find out the implied time zone of that 9 pm from the person that scheduled the event.  Over time, this implied time zone can change if the next person doing the scheduling is in another time zone, introducing more confusion. In contrast, if events were always stored in UTC time, a user in any time zone can quickly determine when an event will occur in his or her local time by knowing the UTC time offset for his or her local time zone.
      • For example: Portland, ME is UTC-5 when not in daylight savings time and UTC-4 when in daylight savings time.  Phoenix, AZ is UTC-7 (it doesn't use daylight savings time).  So if an event were to occur on October 18th at 3 am UTC, a store in New York, NY (on daylight saving, -4 hours) can expect it to occur on October 17th at 11 pm local time and a store in Phoenix, AZ (-7 hours) can expect it to occur on October 17th at 8 pm local time.

    Configuration Management

    Below is a screen shot of a completed scheduled update prior to the [Save] button being pushed.  Notice that both the local time from the computer used to schedule the update (4) and the UTC time (5) are displayed.


    Click [Save] to commit the scheduled update.