Below you will find the Mobile Settings that you can use for the supervisors in the field. See Instructions on how to enter MobileManager Settings here.
Default Values will be used if the Entry does not exist.
Possible Values <Value>(<Description>)
|AllowContactMethodOverride||Boolean||Whether the user is allowed to override the default contact method for a given supplier when scheduling a task||TRUE||TRUE||TRUE/FALSE|
|BaselineInterval||int||Hours before another baseline can be downloaded on a particular contract.||1||1||Integers|
|ForecastInterval||int||Hours before another forecast can be downloaded on a particular contract.||24||24||Integers|
|CACUserCanChange||Boolean||Not yet implemented.||TRUE||TRUE||TRUE/FALSE|
|CACPhoneConf||Char||Whether to enforce, prompt or do nothing for using Call & Confirm when scheduling a key task with a phone supplier.|
A - Always uses C&C for phone callups
P - Prompts the user and asks them if they want to use C&C for phone callups
N - No automated use of C&C. The user can still select it via the drop down list
If you delete the Validation entry then the user is able to use their preference.
|CACOtherConf||Char||Whether to enforce, prompt or do nothing for using Call & Confirm when scheduling a key task with any non-phone supplier.|
A - Always uses C&C for normal callups
P - Prompts the user and asks them if they want to use C&C for normal callups
N - No automated use of C&C. The user can still select it via the drop down list
If you delete the Validation entry then the user is able to use their preference.
|CACWarningHours||Int||The maximum expected time for a C&C to be confirmed, in hours. If this time is exceeded, the C&C appears on the home screen as a late confirmation.||4||4||An integer representing hours|
|CompactView||Boolean||Whether to display the callsheet in Compact mode. Only set this if you want to enforce the supervisors to view the call sheet in a particular mode.||FALSE||FALSE||TRUE/FALSE|
|CompleteView||Boolean||Whether to display the callsheet in Compete (IE Expand All) mode.Only set this if you want to enforce the supervisors to view the call sheet in a particular mode.||FALSE||FALSE||TRUE/FALSE|
|ContractSortOrder||String||The order that the joblist will be sorted in. Generally I'd recommend leaving this blank, unless you for some reason want to restrict the supevisors to ordering their list in a particular way|| || ||The field name(s) to sort by|
|CopyTaskCostCode||String||Gives the option of copying the cost code from a task when creating a requisition against the task.||EDIT||EDIT: Blank cost code to be entered manually|
COPY: cost code is copied and cannot be edited
BOTH: cost code is copied but can be edited
|DDDeliveryListNameX||String||This setting specifies the name for the particular delivery instruction list.There are up to 4 delivery lists, replace the X with the number you want to use. There is a built in list already assigned to 1, so if you want to use that list along with custom lists then start at 2.|| || ||A string containing the Delivery List Name. It's best to keep this concise|
|DDDeliveryListX||String||This setting specifies the values in a for the particular delivery instruction list.There are up to 4 delivery lists, replace the X with the number you want to use. There is a built in list already assigned to 1, so if you want to use that list along with custom lists then start at 2.|| || ||A pipe (|) delimited list containing each item to have in the drop down. For example, "Left hand side|Right hand side|On verge"|
|DRUserCanChange||Boolean||Whether the user is allowed to manually change their date ranges. This is basically the limits that prevent scheduling too far into the future and so on. This refers to all other settings starting with DR||FALSE||FALSE||TRUE/FALSE|
|DRPlannedBehind||int||Number of days before today's date that a work item can be planned|
This restricts the date planned field on the Schedule Screen. The default value of 1 means that the Planned date can be set to yesterday, but not the day before and not any earlier. Changing this to a large value means that the Supervisor can set the Planned date to many days in the past which is both inaccurate and provides a way of enabling the Supervisor to not doing anything for a long time and then update the system to 'pretend' they were using it properly.
|DRPlannedAhead||int||Number of days after today's date that a work item can be planned|
This restricts the date planned field on the Schedule Screen. The default value of 40 means that the Planned date can be set up to 40 days in the future. A low value means that the Supervisor is restricted from being proactive, but at the same time prevents them from a 'Set-and-Forget' mentallity. Additionally, this prevents dates from mistakenly being way to far in advance such as the same day and month of next year.
|DRDueBehind||int||Number of days before today's date that a work item can be due (ie estimated complete)|
This restricts the date due field on the Schedule Screen. The default value of 0 means that the Supervisor cannot insert a Due Date before today. If the Supervisor 'expects' the task to be completed yesterday, he should be able to update the Actual Completed, and not worry about providing an Expected value.
|DRDueAhead||int||Number of days after today's date that a work item can be due (ie estimated complete)|
This restricts the date due field on the Schedule Screen. The default value of 5 means that the Supervisor cannot insert a Due Date for farther out than 5 days from today. A large value means that the Supervisor cannot 'speculate' too far out into the future. A low value means that the Supervisor is restricted to only providing estimates for tasks where there is a high degree of control over their input.
|DRStartedBehind||int||Number of days before today's date that a work item can be started|
This restricts the date started field in the Wizard and in the Complete Task Screen. The default value of 4 means that the Supervisor can input a value for Actually started up to 4 days in the past. This provides a means of updating the system where the supervisor forgot. Additionally, the assumption here is that since it is a true date, representing something the Supervisor knows to have happened, it can be reasonably accurate. A large value, or too large a value allows the Supervisor to fudge and be forgetful.
|DRStartedAhead||int||Number of days after today's date that a work item can be started (generally 0)|
This restricts the date started field in the Wizard and in the Complete Task Screen. The default value of 0 means that the Supervisor can input a value for Actually started until the task has Actually started. Using a value larger than 0 will lead to inaccuracy.
|DRCompletedBehind||int||Number of days before today's date that a work item can be completed|
This restricts the date completed in the Wizard and in the Complete Task Screen. The default value of 1 means that the Supervisor can input a value for Actually completed up to 1 days in the past. This provides a means of updating the system where the supervisor forgot. Additionally, the assumption here is that since it is a true date, representing something the Supervisor knows to have happened, it can be reasonably accurate. A large value, or too large a value allows the Supervisor to fudge and be forgetful.
|DRCompletedAhead||int||Number of days after today's date that a work item can be completed (generally 0)|
This restricts the date completed field on the Wizard and in the Complete Task Screen. The default value of 0 means that the Supervisor can input a value for Actually Completed until the task has Actually Completed. Using a value larger than 0 will lead to inaccuracy.
|LocalPhonePrefix||int||The prefix automatically attached to phone numbers that don't already have a prefix. This only needs to be set if the supervisors are using the PDAs as a phone||8||8||Any valid phone prefix|
|MaxSyncUpload||int||The maximum number of synchronous items that can be uploaded in one batch. Synchronous items are basically everything apart from schedules. Best kept under 30.||5||10||An integer representing the max number of items|
|MaxSyncUpload||int||The maximum number of asynchronous items that can be uploaded in one batch. Asynchronous items are basically just schedules. Best kept under 30.||15||20||An integer representing the max number of items|
|NOTIFICATIONUserCanChange||Boolean||Whether the user is allowed to change their notification Settings (related to NOTIFICATIONUserCanChange, NOTIFICATIONDisplayMethod, NOTIFICATIONRejectMessage, NOTIFICATIONScheduleMessage)||TRUE||TRUE||TRUE/FALSE|
|NOTIFICATIONDisplayMethod||String||The method used to display notifications.|
None - Don't display notifications at all
Popup - Uses a standard message box to display them (ugly + annoying)
Notification - Uses the notification popup that stays at the top of the screen, but can't be used on Windows Mobile 2005 devices
|NOTIFICATIONRejectMessage||Boolean||Whether to display a message when there is a rejected task for a contract||TRUE||TRUE||TRUE/FALSE|
|NOTIFICATIONScheduleMessage||Boolean||Whether to display a message to the user after a schedule, which shows the details of what they've just called up||TRUE||TRUE||TRUE/FALSE|
|JOBPositiveDaysIsDaysAhead||Boolean||This determines the way days ahead/behind are displayed on the Job List and CallSheet. If this is set to true, then positive days mean the job is ahead, so 1 would mean the job is running 1 day ahead of schedule, -5 would mean 5 days behind schedule.|
If this is set to false then negative days mean the job is ahead, so 1 would mean the job is running 1 day behind schedule, -5 would mean 5 days ahead of schedule.
|JOBVisitExpire||int||This determines how long a job in the Job List will stay highlighted in blue after it has had an action performed on it.||1||1||an int representing days|
|PHOTONewPhotoAge||int||How long (in minutes) after a photo is taken that it's considered 'New', and thus appears in the list of photos to upload||5||5||an int representing minutes|
|PHOTOStoreFolder||string||The file path that photos are stored in||photos||photos||A string representing a folder name|
|PHOTOStoreLocation||int||Whether the photos are stored on the device, or a memory card||1||1||1 - Device|
2 - Memory Card
|PHOTODeleteAfterUpload||Boolean||Whether the photos are removed from the device after being uploaded to the server||TRUE||TRUE||TRUE/FALSE|
|REMUserCanChange||Boolean||Whether the user is allowed to change their reminder settings. (Related to RemDeliveryNotes and RemLinkedTasks). If this is false, the settings remain on their default value, unless they're set explicitly as a MobileManager setting||TRUE||TRUE||TRUE/FALSE|
|REMDeliveryNotes||Boolean||Whether to remind the user to enter delivery instructions if they haven't already been to the delivery tab.||TRUE||TRUE||TRUE/FALSE|
|REMLinkedTasks||Boolean||Whether to remind the user to review linked tasks if they haven't been to the linked tasks tab.||TRUE||TRUE||TRUE/FALSE|
|ReqMoreMandFlds||Boolean||GST inclusive label is set to be optional on Requisition screens. To add this label and make fields mandatory in requisition screen.||FALSE||TRUE||TRUE/FALSE|
|SCHEDYellowWarningDayDifference||int||The maximum number of days that a task can be scheduled before its estimated start date before a yellow warning is shown.||6||6||1and above for warning days, -1 for no yellow warnings ever|
|SCHEDRedWarningDayDifference||int||The maximum number of days that a task can be scheduled before its estimated start date before a red warning is shown.||12||12||1and above for warning days, -1 for no red warnings ever|
|SCHEDPromptForLinkedSupplier||Char||This setting affects the schedule screen. If scheduling a key task (not via the wizard), and linked tasks are ticked, but have no supplier, then this setting allows the linked task to be called up manually.|
A - Automatically opens up any linked tasks that have no supplier
P - It prompts the user and asks them if they want to schedule the linked tasks with no supplier manually
N - No manual scheduling happens
|SCHEDWizardCloseAction||Char||This setting affects the schedule screen when in wizard mode. It defines what happens if there are items left to process in the wizard and the the close button at the top right is pressed.|
C - Close down the wizard as per usual.
P - Prompt the user, asking them whether they want to close the wizard or move onto the next task
N - Automatically move on to the next task
|ServiceTimeout||int||Affects how long a webservice will wait for a response from the server before timing out||60||60||The number of seconds before a webservice request times out. Increase this value if you're getting transport connection errors.|
|TASKCanSplitTasks||boolean||This setting affects where the user is able to manually split tasks on the PDA|
True - The user can manually split tasks
False - The user won't even see the option to manually split tasks
|TASKLateTaskLimit||int||The maximum age that a late task can be. If it's more working days late than this number then we don't show the task as late anymore, just assume it isn't happening. -1 for no maximum age||10||10||Any positive number for a limit, -1 for no limit|
|TASKForceBranchSelection||char||This setting affects the schedule screen. If scheduling a task with a supplier that has branches then this allows us to prompt or force them to change the supplier.|
N - Never. The system works the same as before
Q - Prompt If Online. If the supplier we're scheduling for has branches and an online contact method prompt the user
P - Prompt Always. If the supplier has branches we always prompt
O - Force if Online. If the supplier we're scheduling for ahs branches and an online contact method force the user to change it.
F - Force Always. If the supplier has branches we always force the user to change it
Q(Prompt if Online)
O (Force if Online)
|CALLUPAllowedContactMethods||char||Defines what methods are allowed to be used for the supplier contacts||EFIMW||EFIMSW||S (SMS)|
W (Work Phone)
|NONWORKINGDAYSRangeDaysBefore||int||Defines the range of non-working days to bring down to the PDA. This setting defines the lower bound - how many days before the current date we should bring down||60||60||Any integer|
|NONWORKINGDAYSRangeDaysAfter||int||Defines the range of non-working days to bring down to the PDA. This setting defines the upper bound - how many days after the current date we should bring down||60||60||Any integer|
|SYNCNotSyncedWarningHours||int||Defines after how many hours we warn the supervisor that they need to sync||24||24||Any integer|
|maintenanceImgSize||int||Defines Maintenance image size||0||1||0=best, 150 = 150KB ,1= 1mb, 2= 2mb, 4=4mb|
|taskImgSize||int||Defines normal Task/Contract image size||0||2||0=best, 150 = 150KB ,1= 1mb, 2= 2mb, 4=4mb|
|inspectionImgSize||int||Defines Inspection Image Size||0||4||0=best, 150 = 150KB ,1= 1mb, 2= 2mb, 4=4mb|
|TimeStampPhotos||char|| Automatically adds a timestamp to each photo||FALSE||TRUE|| TRUE/FALSE/TOP/BOTTOM/LEFT/RIGHT|
|AdminKey||char||Must be entered if the user can clicks on the buttons 'Export Database' or 'Export Logfile'||NULL||Short Text field example: 123456|
|AdminEmail||char||If the user clicks on Export Database or Export Logfile this email address is the location of where it will be sent to.||NULL||it Support email address||Text1 field|
|RebuildKey||char||Must be entered if the user clicks on the 'Perform test rebuild' or 'Perform Full Rebuild'||NULL||Short Text field example: 123456|
|DefaultAutoupdateScheduleStatusopenCallSheet||char||Prompts user if scheduling is complete when a job is opened.|
(Automatically turns house to green from brown indicating full file prep is done).
|YES||YES / NO|
|MaintenanceScreenStatus||char||Ability to show Maintenance Acknowledgement and Maintenance issues for different job statuses (eg M= Maintenance, A= Active, P=Pending etc)||M||MAPCFH|
|JOBFILTER||char||Ability to see Maintenance jobs and active jobs in one list (new current jobs filter)||ActiveMaintenance|AM;FinalizeMaintenance|FM;|
|UpdateLatLong||char||Ability to capture current location of the job site||TRUE|
|MMISSUEDELIVERYINSTRU||char||Add issue comments as delivery instructions against the task.||TRUE|
|ETSCostCode||char||To modify the cost code field selection in the requisition screen||FALSE|| 'List', 'Text' or 'Both'|
To create custom list create validation setting CHCOSTCODE (sgvalue = code, display = long text)
|AllowAnyReqSupplier||char||To list all the suppliers in the requisition screen||FALSE||TRUE||TRUE/FALSE|
| HideCompleteAllTask||Char||Hide the complete all tasks option from the calendar screen.||FALSE||TRUE/FALSE|
| ReqMoreMandFlds||Char||GST inclusive label to be optional on Requisition screens.||False||True/False|
|TentativeOptions||Char||Menus and functions to Start, Progress or Complete a Task on status Tentative is disabled.||FALSE||True/False|
|ScheduleNormal||Char||Allows you to schedule all tasks as tentative by default (if False is chosen) if True is chosen all tasks are scheduled normal by default||FALSE||True/False|
|SkipContractNotification||When set to TRUE it ignores CNS notifications during sync process||TRUE||TRUE or FALSE|
|HideTrgtDate||Boolean||When set to TRUE it will hide the Trgt / Durn column on the callsheet.||FALSE||TRUE or FALSE|
|PHOTOMaxSize||char||set max photo upload size (used fortablet manager)||2048|
|DefalutCallsheetView (sic)||char||whether the callsheet should list the tasks grouped by stage, or in one large list - sgText1 (sgValue must be null)||Normal||Callsheet with Stage Name||Normal/Callsheet with Stage Name|