# ROB-EX property file
# Copyright (c) 2011 NOVOTEK PLANNING SYSTEMS

Misc



# Location of Gantt log file. If not specified it will be placed in
# users documents and settings area
# logfile.location=C\:\\temp\\robexlog

# Dateformat used for loading/saving of files
fileDateformat=dd-MM-yyyy HH:mm:ss

# Enable printing of user interface components
gui.dlgconfig.ConfPropStdTab.PrintPermissionFeaturePanel=false

# Enable/Disable progress mode
model.operation.progressModeEnabled=true

# Sets default start and end time for PrintDlg
printdlg.timeSelection.startHour=
printdlg.timeSelection.startMinute=
printdlg.timeSelection.endHour=
printdlg.timeSelection.endMinute=

# The max line length that the XML file should be written with
# Set to -1 means that there is no limit
# This attribute cannot have a value less than 100
maxXMLLineLength=-1

# Specifies how copied production data should be named.
# Default is with parantes : (1) etc = 1. Or with the same
# name = 2
copyProductiondataNaming=1


# is it allowed to use Ctrl-C to copy orders to the clipboard
allowCopyToClipboard=true

# is it allowed to use Ctrl-V to paste orders from the clipboard
allowPasteFromClipboard=true

# is it only allowed to copy express orders to the clipboard?
allowCopyExpressOrderOnlyToClipboard=false



# Should the man power factor and the operation efficiency always be the same?
SynchronizeManPowerFactorAndOprEfficiency=false

# How Manpower graph by default will sum for weeks and months
# Note that this setting can be overwritten individually per client in the Manpower settings dialog
# CALC_RULE_MAX = 2              : Max sum per day (the default)
# CALC_RULE_MAX_PER_RESOURCE = 5 : Sum of max per resource per week/month
manPlannerLongPeriodSumRule=2

# Where to locate the xml file with the customTable configuration
# If set to true, search for the file in the <installDir>\custom else
# search in the user home dir (Documents And Settings)
gantt.gui.utils.TableXml.readFromCustomDir=false

# Determine which kind of logging that should be used
# Standard or Log4Java. If true, log4j is used.
# Use Log4Java if the logfile should be saved in a longer period. If false is specified the file "gantt.log" is renamed to "gantt.log.1" (and so on) every time ROB-EX is startet or if the size exceeds 1MB.
# If true is specified a log file is created by each day (default max 10 days) -  named by the date. There will be no size limit of the log files.
gantt.DirectoryManager.log4j=false

# If log4j is enabled, this determines when log files expired.
# Default value is if the log file is more than 10 days old.
# Specifying a number below 1 causes log files to never expire  
gantt.DirectoryManager.log4j.days=10

# If log4j is enabled, this determines the layout pattern used in the log file. 
# For syntax see: http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
gantt.DirectoryManager.log4j.pattern=%d{HH:mm:ss} %-6p [%t] %m%n

# true  - This is the usual way of always splitting what has been selected (default)
# false - If an already splitted operation is selected, this will resplit the original split (TDC) 
gantt.gui.dlgsplitjoin.SplitJoinDialog.alwaysSplitAnew=true

# true  - Every splitted operation from same original must be on different resource (TDC)
# false - Operations are allowed to be on same resource (default)
gantt.gui.dlgsplitjoin.SplitJoinDialog.mustHaveDiffResources=false

# true - The parallel checkbox is always checked - and cannot be deselected.
# false - It's up to the user. The selection is stored.
gantt.gui.dlgsplitjoin.SplitJoinDialog.parallelAlwaysOn=false

# true - The split order checkbox is always checked - and cannot be deselected.
# false - It's up to the user. The selection is stored.
gantt.gui.dlgsplitjoin.SplitJoinDialog.splitOrderAlwaysOn=false

# true - Select the splitCollective tab by default when dialog opens.
# false - First tab is selected
gantt.gui.dlgsplitjoin.SplitJoinDialog.splitCollective=false

# true - The complete order will be joined
gantt.gui.splitjoin.joinOrder=false

# load the StandardViewLayout from local or remote location. Specify true in order to load it from a remote location (from the custom folder in the install dir, which might be on a remote PC).
# This is normally true. But if a userplugin overrides the standard view layout this should be set to false, in order to avoid an "update message" every time ROB-EX is started.
# Background: The various settings are stored in two locations, in the user's home dir and in the custom dir in the installation. A setting can be published to the custom dir
# Where all the users the next time they start ROB-EX will be asked if they want to update the concerned setting. However when the setting is overrided from a userplugin ROB-EX thinks that the setting is published every time it's started (in that case specify "false").
loadStandardViewLayout=true

# length of the default calendar vacation length, in days: 7
calendar.defaultVacationLength=7

# This is at present time used in the select Project combo box on the detail panel and the select resource combos. 
# These combos support "quick search" so items in the combos canbe filtered by typing while the combo is open.
# if true the items in the combo box must start with the typed filter.
# if false they must contain the typed filter.
CustomComboBox.FilterUtil.isStartsWith=false

# Commaseparated list of report ID's of reports which are to be shown in the print dialog combobox
# When pressing the print button on the DlgRawMaterialList
DlgRawMaterialList.defaultReportIDsToPrint=Material inventory

# Commaseparated list of report ID's of reports which are to be shown in the print dialog combobox
# When pressing the print button on the DlgEditRawMaterialTransactions
DlgEditRawMaterialTransactions.defaultReportIDsToPrint=Material transactions

#Take a std. capacity value and set on a new Campaign. Specify a layout item to take it from. A ProductFamily object will be passed to the layout item.
#DlgCreateCampaign.capacityFromProducFamLayoutItem=product_family_custom_double_1

# full path of the class configurating allowed state transitions
projectStateSetupClass=gantt.misc.DefaultProjectState
stateSetupClass=gantt.misc.DefaultOrderState
operationStateSetupClass=gantt.misc.DefaultOperationState
warehouseStateSetupClass=gantt.misc.DefaultWarehouseState

# Default setting of "Show warehouse sum" menu when right clicking on a material graph.
# True: When a warehouse is selected on a graph, inventory sum of all materials in that warehouse is shown
# False: Inventory of selected warehouse AND material is shown.
ShowWarehouseSum=true

# Raw material access rule: ACCESS_METHOD_NEXT_OPERATION_END, can enable/disable accesses
# if the status of next operation is start possible or above. In this case the access
# is disabled until the next operation is completed
accessMethodNextOperationEnd.disableUntilCompleted=false

# In the production order management dialog when selecting a route the fields 'Customer' and 'Product' can be auto-filled.
# It must be specified where to take the value from.
# In the below example the product value is fetched from the 'custom string 1' field on the route and the customer is fetched from 'custom string 2'
# For a list of the possible fields refer to the manual in the 'Variable list' section.
# SetProductOnRouteChange=operation_sequence_custom_string_1
# SetCustomerOnRouteChange=operation_sequence_custom_string_2

#Category valuetypes (class types)
numberOfCategoryValueTypes=3
categoryValueType0=java.lang.String
categoryValueType1=java.lang.Integer
categoryValueType2=java.lang.Double

# settings for inactivity timer.
#If this is enabled it will ignore client (user) specific settings!
InactivityMonitor.forced.enabled=false
InactivityMonitor.forced.timeout=600000
InactivityMonitor.forced.saveOnExit=false

# When calculate the workload contribution of an operation on the 
# workload graph, use the full amount of hours in a period when ever the
# operation intersects the period. 
# Ex: an operation intersects a day with 24 hours available time, with just 1 hour
# but the workload will calculate 24 hours of usage. 
workloadGraphCalculationRuleMax=false

# When adding new routes to a route network should they be added after last route or as a new root
DlgEditRouteNetwork.addNetworksAfterLast=true

# Custom colors for material graph text.
# Used when min./max. levels are violated.
# Below min. default #ff0000 - red
# Below min. warning default #0000ff - blue
# Above max. default #ff00ff - magenta
# Above max. warning default #00ff00 - green
material.graph.below.min=0xff0000
material.graph.below.minwarn=0x0000ff
material.graph.above.max=0xff00ff
material.graph.above.maxwarn=0x00ff00

#Java SSL keystore and truststore files used for secure network communication, please look in the manual under "Secure networking communication - SSL" for more information.
-Djavax.net.ssl.trustStore=./config/ssl/.truststore
-Djavax.net.ssl.trustStorePassword=
-Djavax.net.ssl.keyStore=./config/ssl/.keystore
-Djavax.net.ssl.keyStorePassword=
-Dsun.security.ssl.allowUnsafeRenegotiation=true
-Dhttps.protocols="TLSv1,TLSv1.1,TLSv1.2"

Appearance



# Custom logo to show in the tool bar
# This is a relative path from the gantt installation folder
# ex: .\custom\CustomLogo.gif
# Max height: 37 pixels to keep it right
customIconInToolbar=.\\custom\\CustomLogo.gif

# WarehouseState colors
warehouseStateOpen=#00ff00
warehouseStateClosed=#ff0000
warehouseStateQuarantine=#ffff00

# Width of time now line
gantt.timeNowWidth=2

# Triviality limit of the material graph.
# If the value is between trivialityLimit and -trivialityLimit the graph is not painted.
# Only the values are written.
PIndependentBarPanel.trivialityLimit=0.15

#This setting is used when material inventory or transaction sum is calculated.
#If true the old behavior is followed: If multiple categories are selected on graph, the inventory value will be summed for each selected category.
#When false multiple categories can be combined
RawMaterialManager.InventoryCalculationHelper.sumCategories=false

# Setting, if the TimeChooserPanel should always show zero minutes in the list,
# or show the actual minutes. 
gantt.gui.utils.TimeChooserPanel.alwaysZeroMinutes=true

# Colorcode (HTML) strings for standard java colors (the color object statics)
black=#000000
blue=#0000ff
cyan=#00ffff
darkgray=#404040
gray=#808080
green=#00ff00
lightgray=#c0c0c0
magenta=#ff00ff
orange=#ffc800
pink=#ffafaf
red=#ff0000
white=#ffffff
yellow=#ffff00

#Decides if material transaction constraints between orders should be painted as normal constraints or vertical lines
materialTransactionConstraint.paintAsVerticalLine=false

#Skip layout checkbox in Route network dialog, selected or not
DependencyPanel.jcbDirectLines.selected=true

#The default color of closed calendar periods
defaultClosedCalendarColor=#e6e6e6
#Default color of selected resource button. Light gray (rgb = 149, 149, 149)
resourcePanelSelectedResourceColor=#959595

Show or hide




# Always show waste rate field on all operations? 
dlgEditOperation.useWaste=false

# ** START OF DETAIL PANEL **

# Set the text fiels size (the minimum size is 7)
gui.detailPanel.productionOrder.productName.textFieldSize=15

# Show the production order priority
gui.detailPanel.productionOrder.priority.show=false

# Set the width of resource combobox in pixels
gui.detailPanel.operation.resource.pixelWidth=100

# Show the operation duration
gui.detailPanel.operation.duration.show=true

# Show the operation quantity left
gui.detailPanel.operation.quantityleft.show=false

# Show the operation capacity
gui.detailPanel.operation.capacity.show=false

# Show the operation price
gui.detailPanel.operation.price.show=true

# Show the operation capacity
gui.detailPanel.operation.capacity.show=false

# Show the operation target capacity
gui.detailPanel.operation.targetcapacity.show=false

# Show the operation target workload
gui.detailPanel.operation.targetworkload.show=false

# Show the operation target workload
gui.detailPanel.operation.editWorkloadOnMoreOperations=false

# Show the operation target workload
gui.detailPanel.operation.editOperationStartEndOnMoreOperations=false

# ** END OF DETAIL PANEL **


# ** START OF DLG ORDERLIST **

# Hide the delete production order button
dlgOrderList.showDeleteProductionOrderButton=true

# Hide the create new production order button
dlgOrderList.showNewProductionOrderButton=true

# Hide the edit production order button
dlgOrderList.showEditProductionOrderButton=true

# Enable/disable the pre condition table column edition
dlgOrderList.preConditionTableColumn.editable=true

# ** END OF DLG ORDERLIST **

# Attributes for the planning strategies
showPlanningStrategyDialog=true

# Show the production order details (customer, material date, delivery date...)
showProductionOrderDetails=true

# Show extra overlap control lines
gui.controlOverlap.showExtraLines=false

# Special PAA feature for showing the edit order, in right-click menu in resview, but
# showing the expressorder dialog instead.
# Should default be set to false
resView.showEditExpressOrder=false
resView.editExpressOrderOnly=false

# Set if the edit->Operation Sequence option is available from menu
menu.edit.operationSequence.visible=true

# Set if the popupmenu->split operation option is available from menu
popupmenu.splitOperation.visible=true

# Set if the popupmenu->join operations option is available from menu
popupmenu.joinOperations.visible=true

# Show the account and price fields in express order dialog
dlgOrder.showEconomyFields=false

# Enable/disable the background popup menu
resView.backgroundPopupMenu.enable=true

# SplitJoinDialog table column settings
SplitJoinDialog.OperationList.Duration.Visible=true
SplitJoinDialog.OperationList.Capacity.Visible=true

# show the workload as column in the groupedit dialog
gui.dlggroupedit.showWorkload=false

# Show a customBoolean column in the material list table. Default false.
# Notice that it's possible to show JUST customBoolean1, or both. It's not possible to show only customBolean2!
rawMaterialTableModel.showCustomBoolean1=false;
rawMaterialTableModel.showCustomBoolean2=false;

#Layout items (table columns): Enable/disable if they are allowed to recurse on lower level objects. It is possible to control layout items individually - or per table (first have higher priority than the latter).
#Below two lines are examples for the "opr_resource" column (but all std. columns can be controlled). The third line will disable recurse for all columns on the Project overview table. Default is true.
#However PrjJTreeTable is default false (if not specified in this setup file, recurse is disabled on Project overview table - PrjJTreeTable)
#recurseOnlowerLevelObjects_layoutItem_opr_resource_table_dlgOrderList=false
#recurseOnlowerLevelObjects_layoutItem_opr_resource_table_PrjJTreeTable=false
recurseOnlowerLevelObjects_table_PrjJTreeTable=false

#Operation info icon. Show info icon on operations if there are text in the specified field(s). Comment out the line below if icon should never be showed
#showInfoIconForFields={opr_description},{opr_custom_text1}

#Show labes on resource reservation only when its selected
resourcereservation.showLabelWhenSelected=true
#Use the viewlayout "Campaign" for label rendering on resource reservations
resourcereservation.useViewLayout=false

Resource and calendar




# 0 - This will calculate in regard to current time
# 1 - This will calculate in regard to planned
gantt.gui.utils.ResourceAheadBehind.calculateAheadBehind=0

# if true the resource id will be showed after the name, separated by a blank. This will be visible when selecting resource
# on the detail panel and in the Split/Join dialog.
ResourceContainer.alsoShowIdInToString=false

# if true, the standard resourve layout will be used in the toString method
# on the Resource
ResourceContainer.useResourceLayoutInToString=false

# If enabled the check for overlap function, which will format text in red in the "change resource combobox" will be skipped.
# Also the function which will move "not relevant" resources to the bottom will be skipped.
# Use this to speed things up!
ResourceConstrants.isDeactivateCheckForOverlapAndMoveToBottom=false

# Activate/Inactivate the new resources in other views than standard when created
resView.activateNewResourceInAllViews=false

# If a view has option "hide resources in teams" set and a resource has planned
# operations this will affect if they are shown or not! 
resView.showHiddenResourcesInTeamsWithPlannedOperations=true

# Show the resource id as a column in the view property panel,
# where resources is selected for views.
resListView.showResourceIdColumnViewPropPanel=false

# model.period specifies settings for periods
# The following commands may be specified for "period"
# timeSelection.startHour
# timeSelection.startMinute
# timeSelection.endHour
# timeSelection.endMinute
#  Specifies the default start and end time for the time selection in the period definition
model.period.timeSelection.startHour=7
model.period.timeSelection.startMinute=0
model.period.timeSelection.endHour=15
model.period.timeSelection.endMinute=0

# Set if Gantt should use the calendar pool system to improve memory use but slow the program
model.useCalendarPool=true

# Set if Gantt should use the incremental availability system, this should speed the program but use memory
model.complexCalendar.useIncrementalAvailability=true
model.simpleCalendar.useIncrementalAvailability=true
model.recurrence.useIncrementalAvailability=true

# Set the number of times to try to extend the availability list of one week 
#	before giving up and calculating the operation start/end calendar as if the resource was always available.
# This should be at least equals to the number of weeks for the longuest operation 
# plus the longuest holidays period it can overlap with.
# - If you schedule with very long operations (many weeks or months) it will typically be 52 
# - If you schedule with short operations (typically less than 2 weeks length) it will typically be 10
model.resource.calculateStartOrEndCalendar.maxAvailabilityWeekNumber=50

Operation




# OperationState colors
oprationStatusCreated=#ffffff
oprationStatusForcalculated=#B67C00
oprationStatusPlanned=#c0c0c0
oprationStatusStartPossible=#0000ff
oprationStatusStarted=#00ff00
oprationStatusPaused=#ffff00
oprationStatusCancelled=#ff0000
oprationStatusComplete=#000000
oprationStatusDeleted=#000000

# OrderState colors
orderStatusReleasedColor=#00ffff
orderStatusIncompleteColor=#ffffff
orderStatusIncompletePatternColor=#ff0000

# model is the root for basic gantt behaviour
# model.status specifies settings dependend on order status
# The following commands may be specified for "model.status.XX.operation"
#
# moveEnable
#  Specifies if user may move an activity or not
# Status FORCALCULATED
model.orderstatus.15.moveEnable=true
# Status PLANNED
model.orderstatus.20.moveEnable=true
# Status RELEASED
model.orderstatus.30.moveEnable=true
# Status S_POSSIBLE
model.orderstatus.40.moveEnable=true
# Status STARTED
model.orderstatus.50.moveEnable=true
# Status PAUSED (Currently not used)
model.orderstatus.60.moveEnable=true
# Status CANCELLED
model.orderstatus.70.moveEnable=true
# Status COMPLETE
model.orderstatus.80.moveEnable=true
# Status DELETED
model.orderstatus.90.moveEnable=true

#
# Specifies if user may move an operation or not
# If set to true, a check on the activity state as made
#
# Status FORCALCULATED
model.operationstatus.15.moveEnable=true
# Status PLANNED
model.operationstatus.20.moveEnable=true
# Status S_POSSIBLE
model.operationstatus.30.moveEnable=true
# Status STARTED
model.operationstatus.40.moveEnable=true
# Status PAUSED
model.operationstatus.50.moveEnable=true
# Status CANCELLED
model.operationstatus.60.moveEnable=true
# Status COMPLETE
model.operationstatus.70.moveEnable=true
# Status DELETED
model.operationstatus.90.moveEnable=true

#MoveEnable with progress. Is move enabled for operations partly produced (progress reported)
# Status STARTED
model.operationstatus.40.moveEnableWithProgress=true
# Status PAUSED
model.operationstatus.50.moveEnableWithProgress=true
# Status CANCELLED
model.operationstatus.60.moveEnableWithProgress=true



# Require that order has state "Released" or higher in order to show operations
# in Gantt chart. If an operation is invisible it will not occupy any capacity
# and it will neither be shown in workload or manpower graphs.
# IMPORTANT: invisible operations still are taken into account on material graphs ! 
model.visibleRequireOrderReleased=false

# Control based on individual operation status if an operation should be visible or not in the gantt chart
# Usefull to hide completed operations without actually removing the operation from the route
# Only status values listed here are supported

# Status operation FORCALCULATED
model.oprstatus.15.visible=true
# Status operation PLANNED
model.oprstatus.20.visible=true
# Status operation PAUSED
model.oprstatus.50.visible=true
# Status operation CANCELLED
model.oprstatus.60.visible=true
# Status operation COMPLETE
model.oprstatus.70.visible=true

# Hide operations with total workload less than or equals to specified value (hours).
# Specify -1 to disable (all operations are visible).
minWorkloadForVisibleOperation=-1


# model.useCapacity specifies settings dependend on resource capacity for every operation
#  Specifies if we use capacity or not for every operation
model.useCapacity=true

# Attributes for the delete operation from operation sequence
showDeleteOperationDialog=true

# Enable the switching of operation status
gui.operation.status.change=true

# How the color by operationLocked should be
# true: locked=red unlocked=green
# false: locked=green unlocked=red 
operation.operationLockedColorGreenRed=true

# If operation is moved to a resource with autoUpdateOperationEfficiencyToResourceAvailabilityFactor=true
# prompt the user before change!
operation.promptAutoUpdateOperationEfficiencyToResourceAvailabilityFactor=true

# Override setting if progress should use percentage and ignore last progress time.
# PLEASE NOTE: Only ONE of the three following progress settings/properties should be set to true, and the two others should have value "user"!
# 
# Valid values are:
#   user  - default value, the user defined setting is used
#   true  - The settings it forced to true, user defined setting is ignored and cannot be changed
model.operation.progressModePercent=user

# Override setting if progress should use last progress time (the default mode where last progress is illustrated)
# Valid values are:
#   user  - default value, the user defined setting is used
#   true  - The settings it forced to true, user defined setting is ignored and cannot be changed
model.operation.progressModeProgressTime=user

# Override setting if progress should use last progress time and illustrate percentage.
# Valid values are:
#   user  - default value, the user defined setting is used
#   true  - The settings it forced to true, user defined setting is ignored and cannot be changed
model.operation.progressModePercentAndLastProgressTime=user

#Set if the operations in the operation group behave like a single operation with regard to the actual start/end time,pausing and status
operationGroup.common.actual.time.behavior=false

#Set if the operations in the operation group behave like a single operation with regard to the progress and spread the progress on all operations in group based on the workload quantity.
operationGroup.common.progress.behavior=false

# if WORKLOAD step is seen as 100% complete in case SWITCHOVER progress has been reported. By default true.
operation.progress.autoCompleteWorkloadStep=true

# if planned end for started operations should be automatically recalculated
# when resource calendar is changed.
operation.progress.recalculatePlannedEnd=true

# Apply resource efficiency to the progressTimeLeft calculation
operation.progress.removeResourceEfficiency=false

#Update efficiency upon progress update in order to retain existing end calendar on operation. Default false.
#Operation duration mode on resource must be set to "Adjust opr. efficiency".
#And "Use last progress time and show percentage progress reported" must be enabled in Edit parameters - on progress tab
operation.update.Efficiency.Upon.Progress.Changed=false

# set if the operation should be left untouched when the underlying resources calendars are changed in general
operation.leaveOperationUntouchedOnResourceCalendarChanged=false

# set if the operation should use hundredths of hours for setup, workload, switchover etc., worktime
# or worktime is a round number of minutes
operation.worktimeStepsHundredthsOfHours=false

# WorktimeStep settings
WorktimeStep.PRE_QUEUE.reserveCapacity=false
WorktimeStep.PRE_QUEUE.useResourceEfficiency=false
WorktimeStep.PRE_QUEUE.useOperationEfficiency=false
WorktimeStep.PRE_QUEUE.useCalendar=false
WorktimeStep.PRE_QUEUE.maxIdleByClosedPeriod=-1

WorktimeStep.SETUP.reserveCapacity=true
WorktimeStep.SETUP.useResourceEfficiency=false
WorktimeStep.SETUP.useOperationEfficiency=true
WorktimeStep.SETUP.useCalendar=true
WorktimeStep.SETUP.maxIdleByClosedPeriod=-1

WorktimeStep.FILLUP.reserveCapacity=true
WorktimeStep.FILLUP.useResourceEfficiency=false
WorktimeStep.FILLUP.useOperationEfficiency=true
WorktimeStep.FILLUP.useCalendar=true
WorktimeStep.FILLUP.maxIdleByClosedPeriod=-1

WorktimeStep.WORKLOAD.reserveCapacity=true
WorktimeStep.WORKLOAD.useResourceEfficiency=true
WorktimeStep.WORKLOAD.useOperationEfficiency=true
WorktimeStep.WORKLOAD.useCalendar=true
WorktimeStep.WORKLOAD.maxIdleByClosedPeriod=-1

WorktimeStep.EMPTYING.reserveCapacity=true
WorktimeStep.EMPTYING.useResourceEfficiency=false
WorktimeStep.EMPTYING.useOperationEfficiency=true
WorktimeStep.EMPTYING.useCalendar=true
WorktimeStep.EMPTYING.maxIdleByClosedPeriod=-1

WorktimeStep.SWITCHOVER.reserveCapacity=true
WorktimeStep.SWITCHOVER.useResourceEfficiency=false
WorktimeStep.SWITCHOVER.useOperationEfficiency=true
WorktimeStep.SWITCHOVER.useCalendar=true
WorktimeStep.SWITCHOVER.maxIdleByClosedPeriod=-1

WorktimeStep.MAX_STORAGE.reserveCapacity=true
WorktimeStep.MAX_STORAGE.useResourceEfficiency=true
WorktimeStep.MAX_STORAGE.useOperationEfficiency=false
WorktimeStep.MAX_STORAGE.useCalendar=false
WorktimeStep.MAX_STORAGE.maxIdleByClosedPeriod=-1

WorktimeStep.CUSTOM.reserveCapacity=false
WorktimeStep.CUSTOM.useResourceEfficiency=false
WorktimeStep.CUSTOM.useOperationEfficiency=false
WorktimeStep.CUSTOM.useCalendar=true
WorktimeStep.CUSTOM.maxIdleByClosedPeriod=-1

WorktimeStep.OFFSET.reserveCapacity=true
WorktimeStep.OFFSET.useResourceEfficiency=true
WorktimeStep.OFFSET.useOperationEfficiency=true
WorktimeStep.OFFSET.useCalendar=true
WorktimeStep.OFFSET.maxIdleByClosedPeriod=-1

WorktimeStep.POST_QUEUE.reserveCapacity=false
WorktimeStep.POST_QUEUE.useResourceEfficiency=false
WorktimeStep.POST_QUEUE.useOperationEfficiency=false
WorktimeStep.POST_QUEUE.useCalendar=false
WorktimeStep.POST_QUEUE.maxIdleByClosedPeriod=-1

WorktimeStep.TRANSPORT.reserveCapacity=false
WorktimeStep.TRANSPORT.useResourceEfficiency=false
WorktimeStep.TRANSPORT.useOperationEfficiency=false
WorktimeStep.TRANSPORT.useCalendar=true
WorktimeStep.TRANSPORT.maxIdleByClosedPeriod=-1

WorktimeStep.CUSTOM.reserveCapacity=true
WorktimeStep.CUSTOM.useResourceEfficiency=true
WorktimeStep.CUSTOM.useOperationEfficiency=true
WorktimeStep.CUSTOM.useCalendar=true
WorktimeStep.CUSTOM.maxIdleByClosedPeriod=-1

# special settings for the No idle time workime chain
# value is hours (0.25 hours = 15 minutes)
WorktimeStep.noIdleChain.SETUP.maxIdleByClosedPeriod=0.25
WorktimeStep.noIdleChain.WORKLOAD.maxIdleByClosedPeriod=0.25
WorktimeStep.noIdleChain.SWITCHOVER.maxIdleByClosedPeriod=0.25

# Capacity factors - will be multiplied onto user supplied capacity values
# capacity.unitsPerTime specifies if capacity is specified as unitesPerTime
# (true) or as timePerUnit (false)
# Refer to key capacity.label.x in language property files. The index specified
# here must have a similar capacity.label.x index in the language file !!
# Custom factors may be added. Extra lines must start from index 6
# units per hour
capacity.factor.0=1.0
capacity.unitsPerTime.0=true
# units per minute
capacity.factor.1=60.0
capacity.unitsPerTime.1=true
# units per second
capacity.factor.2=3600.0
capacity.unitsPerTime.2=true
# hours per unit
capacity.factor.3=1.0
capacity.unitsPerTime.3=false
# minutes per unit
capacity.factor.4=60
capacity.unitsPerTime.4=false
# seconds per unit
capacity.factor.5=3600
capacity.unitsPerTime.5=false

# Should the price realized be calculated by default on new operations?
defaultCalculatePriceRealised=false

# when splitting operations and force them to be parallel then try to 
# find the longest operation and put it at the end of the splitted opr.
Operation.split.parallel.findLongest=false

# when splitting operations and force them to be parallel set this option to true 
# if the time fields should be replicated to all split members. Otherwise for instance setup time is only put on first split member and switch over on last.
Operation.split.parallel.replicateTimeFieldsWhenParallel=true

# when using percentage progress reported and not progress time reported, these settings
# will cause the painted progress on the operation in the gantt chart to never be grated
# than the given max value
operation.progress.isPaintMaxProgress=false
operation.progress.maxProgressValue=1.0

#Baseline. Settings below are used when baseline view is enabled on "Baseline" toggle button on the tool bar.
#If true revise the baseline1 dates on order state change from new to forcalculated. Default false.
operation.baseline1.reviseNewToForcalculated=false
#If true revise the baseline1 dates on order state change from forcalculated to planned. Default true.
operation.baseline1.reviseForcalculatedToPlanned=false
#If true revise the baseline1 dates on order state change from planned to released/start possible. Default false.
operation.baseline1.revisePlannedToReleased=true
#If true compare the actual start -and end date to the baseline1 dates instead of to the planned dates. Default false.
operation.baseline1.compareStartedToBaseline1=false
#If true show the baseline view on operations with ORDER state planned. Default true.
operation.baseline1.showBaselineOnPlanned=false
#If true show the baseline view on operations with ORDER state released. Default true.
operation.baseline1.showBaselineOnReleased=true
#If true show the baseline view on operations with OPERATION state start possible. Default true.
operation.baseline1.showBaselineOnStartPossible=true
#If true, reset the baseline start and end calendars. Used to be able to reset the values no matter what other settings used.
operation.baseline1.resetBaselineOnStatusNew=false

#BaselineWorkload view will by default have same end as current end, and thus calculate start - based on target workload (org.).
#But if this setting is enabled it will snap to start and thus calculate end based on target workload
operation.baselineWorkload.snapToStart=false

#Copy the current workload to targetWorkload, if operation status is below or equal to the user specified statusSetPoint
#Default is 20 (planned)
#Status list:
#CREATED = 10, 
#FORCALCULATED = 15,
#PLANNED = 20 
#S_POSSIBLE = 30, 
#STARTED = 40, 
#PAUSED = 50, 
#CANCELLED = 60, 
#COMPLETE = 70, 
operation.targetWorkload.statusSetpoint=20

#If true the last progress calender is illustrated on operations in progress (except completed) if setting "Use last progress time and show percentage progress reported" is enabled
#on progress settings in ROB-EX.
operation.show.lastProgress.on.started=true

#By default when changing to alternate route and searching for matching oprs to put prod refs and mat links on match only on the first 8 chars instead of the whole operation name.
#Specify -1 to disable this and thus it must match on complete opr names.
AlternateRouteResourceCollector.first.chars.match.length=8

#If enabled an operation milestone will always be visible in the Gantt chart even though the order is not selected.
alwaysShowOperationMilestone=true

Order




# Enable to change production order state from new to start possible
gantt.productionOrder.status.allowChange.newToStartPossible=true

# Disable to allow change from new to start possible without preconditions required
gantt.productionOrder.status.allowChange.newToStartPossible.requirePrecondition=true

# Enable to change production order state from forcalculated to start possible
gantt.productionOrder.status.allowChange.forcalculatedToStartPossible=true

# Disable to allow change from forcalculated to start possible without preconditions required
gantt.productionOrder.status.allowChange.forcalculatedToStartPossible.requirePrecondition=true

# Enable to change production order state from start possible to forcalculated
gantt.productionOrder.status.allowChange.startPossibleToForcalculated=true

# If set to false, the normal backwards status change is not allowed e.g. if an order is changed to started, it cannot be changed back to start possible
gantt.productionOrder.status.allowChange.backwards=true

# If true, allow operation status change from completed to paused
gantt.operation.status.allowChange.completedToPaused=false

# If set to false, the normal backwards status change is not allowed e.g. if an operations is changed to started, it cannot be changed back to start possible
gantt.operation.status.allowChange.backwards=true

# If set to false, the normal backwards status change is not allowed e.g. if an operations is changed to started, it cannot be changed back to start possible
gantt.project.status.allowChange.backwards=true

# default start when creating a new order.
defaultStartTime=8

# default delivery time when creating a new order
# OBS: This setting will only have an effect for first time users. After that change the setting from Functions->Settings->General->Standard-tab
defaultEndTime=19

# default material time when creating a new order
# OBS: This setting will only have an effect for first time users. After that change the setting from Functions->Settings->General->Standard-tab
defaultMaterialTime=15

#When creating an express order, a name is suggested. It normally consist of G + a number (e.g. 'G2363').
#Blank string for no prefix. Default is 'G'
gantt.gui.dlgorder.DlgOrder_expressOrderNamePrefix=G

Project




# Use the start calendar of the project for material date of production orders that are attached
useProjectStartCalendarAsMaterialDate=false

# Use the end calendar of the project for delivery date of production orders that are attached
useProjectEndCalendarAsDeliveryDate=false

# Use the customer of the project for customer on production orders that are attached
useProjectCustomerAsCustomer=false

# Lock the project structure
# This means that no one can add/remove a production order to/from a project
model.project.lockProjectStructure=false

# Synchronize the project status with the production orders status
# The project gets the same status as the lowest status for the production orders
gantt.project.status.reflectOrdersStatus=false

# true - The hard link checkbox is always checked - and cannot be deselected.
# false - It's up to the user. The selection is stored.
gantt.gui.dlgsplitjoin.SplitJoinDialog.hardlinkAlwaysOn=false

# load the StandardViewLayout form local or remote location
loadStandardViewLayout=true

# Synchronize the production order status when project state is set
# Production orders state is only moved forward to same state as the project
gantt.project.status.moveOrderstateForward=false

# How express orders are colored in project coloring mode
# If 0 (the default) project color is used
# If 1 operation coloring is used
operation.expressOrderProjectColor=0

# This is used in the select project combo box on the detail panel. This combo supports "quick search", so items can be filtered by typing while the combo is open.
# Always filter by the specified value i.e. if specifying "127" the combobox will only contain items wich contains (or starts with) the text "127".
# It's dependent of the setting "CustomComboBox.FilterUtil.isStartsWith=" whether the filter value must be contained in the text or must start with.
OverviewDetailInfo.jcbProjectNumber.prefilterValue=

# Use advanced project search
# If true an extra "browse" button will appear on the right side of the project combo box.
OverviewDetailInfo.useAdvancedProjectSearch=false

Integration




# if XML import should delete express orders when deleting orders that are
# not mentioned in the latest import file
xmlImport.deleteExpressOrders=true

# if the <ResAlloc> tag is not supplied during XML import and this
# setting is true, then the import will automatically assign the first priority
# resource from the template operation as resource for the operation. In case an
# operation does not have a template operation (either specified in the XML on
# Operation.templateOprId or secondary has a template operation with same name) then
# an error will be raised if this value is true.
#
# In the GanttERP SQL interface an empty <ResAlloc> tag is generated by
# 1. removing any referential integrity contraints between the Operation and Resource table in the database
#    Removing a named referential contraint is done in Transact SQL using:
#    ALTER TABLE [dbo].[Operation] DROP CONSTRAINT [FK_Operation_Resource]
#    To allow NULL to be inserted as resId use the following Transact SQL:
#    ALTER TABLE Operation ALTER COLUMN resId NVARCHAR(40) NULL 
# 2. Next simply specify null in column Operation.resourceId 
xmlImport.allowOperationEmptyResource=true

# set import/export permissions for individual attributes. The key name
# has the form io.<xml tag>.<xml attribute>, where "xml tag" and "xml attribute"
# can be looked up from the XML integration document. Note that only selected
# attibures can be specified and that case spelling matters !
# Possible values are 'read', 'write' or 'both'
io.resource.specs=both

# Used to determine if status on productionorders and operations 
# should be exported even though status has been set backward and changed made in 
# ERP systems then will be lost.
dbSetup.ExportConf.statusExportEnable=false

# If xml plugin should export custom properties (i.e. Manpower staffing on operation etc.)
xmlplugin.exportCustomProperties=false

# If xml plugin should export order custTextX
xmlplugin.export.order.custText1=true
xmlplugin.export.order.custText2=true
xmlplugin.export.order.custText3=true
xmlplugin.export.order.custText4=true

# If xml plugin should export operation custTextX
xmlplugin.export.opr.custText1=true
xmlplugin.export.opr.custText2=true
xmlplugin.export.opr.custText3=true
xmlplugin.export.opr.custText4=true

# Additional layout item variables to include on the <ProdOrder> tag
# As value specify a comma separated list of layout item variable names (look up valid names from
# variable list client online users manual). It is supported to enclose each variable
# in qoute " characters. Note in case layout value is null, the corresponding attribute is excluded from the export.
# Example values: order_locked, order_series_id
# Will result in export like <ProdOrder order_locked="false" order_series_id="" />
xmlplugin.export.layoutitems.order=

# Additional operation level layout items to export
# Refer to documentation above of xmlplugin.export.layoutitems.order for further details
# Example values: opr_locked, opr_planning_factor
# Will result in export like <Opr opr_locked="false" opr_planning_factor="2.00" /> 
xmlplugin.export.layoutitems.operation=

# Additional resource level layout items to export
# Refer to documentation above of xmlplugin.export.layoutitems.order for further details
# Example values: resource_efficiency
# Will result in export like <Res resource_efficiency="1.00" />
xmlplugin.export.layoutitems.resource=

# Additional route level layout items to export
# Refer to documentation above of xmlplugin.export.layoutitems.order for further details
# Example values: operation_sequence_lotsize, operation_sequence_is_cip
# Will result in export like <Route operation_sequence_lotsize="500.00" operation_sequence_is_cip="false" />
xmlplugin.export.layoutitems.route=


# If orders are spread over multiple rows and each row defines an operation in the order
# and operations should be created specify this one to true.
textio.createOperationMultipleRows=false

# Normally the route is only created if a template route with same name exists.
# Specify true in order to create a route even no template route exists with the specified name.
textio.createRouteEvenNoTemplate=false

# ** START OF Transfer settings from opr template to imported operation **

# When importing a new operation into ROB-EX the values not specified during import can be transferred
# from an existing template operation. This transfer mechanism only applies the first time an operation
# is imported, not on subsequent updates of the same operation.
# As an example only the workload of an operation is specified on the import. During import a fixed switch
# over and/or setup time are copied from a template operation onto the newly imported operation.
# All values from the template are copied, except for those specifically set on the imported operation.
# xmlImport.createOperationFromTemplate: Specify true to make ROB-EX find operation templates with same name
#                                        as the imported operation and copy selected parameters from this template
#                                        If no mappings (see below) are specified ROB-EX will look for a template
#                                        operations with same name for all imported operations.
xmlImport.createOperationFromTemplate=false

# Transfer Mappings:
# If 'xmlImport.createOperationFromTemplate' is true mappings can be specified to refine what operations
# will be created based on values from the template operation.
# Specify the pattern of the imported operation which should copy values from a template operation.
# Regular expressions are supported (case insensitive). Uncomment line below.
# xmlImport.mapping.importedOperationName.1=Cutting 1
# 
# Specify the name of the template operation where values are copied from. Regular expressions are supported
# (case insensitive). Uncomment line below.
# xmlImport.mapping.operationTemplateName.1=Cut*
#
# Mapping no. 2. More mappings can be created, just copy the two lines below and rename to '.2' to '.3' etc.
# xmlImport.mapping.importedOperationName.2=Cutting 2
# xmlImport.mapping.operationTemplateName.2=Cut*

# ** END OF Transfer settings from opr template to imported operation **

#Define the timeout in seconds - how long time should ROB-EX wait for data from the Visma service.
soaintegrationClient.soaVisma.Timeout=600

# Setting this setting to false will disable the cleanup manager. The role of the cleanup manager
# is to store information about orders, operations etc. being deleted. This way plugins can query the cleanup
# manager for deleted objects and update external systems about what has been deleted. In applications
# where this functionality is not needed, performance and memory consumption may be improved by disabling
# the cleanup manager
cleanupManagerEnable=true

# If the client should "flatten" events sent from the server into
# a single event where only the newest values are retained in the final event.
multiuserFlattenReceivedEvents=true

# If true 00:00 will be exported as 24:00.
# April 2 at 00:00 will be exported as April 1 24:00.
# Default false. Visma will not accept 24:00. XAL expects 24:00 (at least in the old days).
xmlplugin.export.midnight.as.24=false

Booker




# ** This concerns the Booker edition of ROB-EX **

# BookingState colors
bookStatusCreated=#ffffff
bookStatusReady=#B67C00
bookStatusReserved=#c0c0c0
bookStatusCheckedOut=#0000ff
bookStatusService=#00ff00
bookStatusSold=#ffff00
bookStatusScrapped=#ff0000
bookStatusStolen=#000000
bookStatusDeleted=#000000
bookStatusSubHiredCreated=#ffffff
bookStatusSubHiredReceived=#ffff00
bookStatusSubHiredReturned=#000000
bookStatusSupplyer=#00ff00

# full path of the class configurating allowed state transitions
bookingOperationStateSetupClass=gantt.misc.DefaultBookingOperationState
bookingStateSetupClass=gantt.misc.DefaultBookingState

Scheduling



# When scheduling hardlinked operations the algorithm should try to place the 
# hardlinked operations a maximum of this many times before giving up!
scheduler.hardLink.maxAdjustmentsBeforeFail=100

Database Connection Pool



# Database connection pool setting.
# Number of Connections a pool will try to acquire upon startup. Should be between <code>minPoolSize</code> and <code>maxPoolSize</code>.
dbpool.initialPoolSize=0

# Database connection pool setting.
# Minimum number of Connections a pool will maintain at any given time.
dbpool.minPoolSize=0

# Database connection pool setting.
# Determines how many connections at a time c3p0 will try to acquire when the pool is exhausted.
dbpool.acquireIncrement=1

# Database connection pool setting.
# Maximum number of Connections a pool will maintain at any given time.
dbpool.maxPoolSize=3

# Database connection pool setting.
# Seconds a Connection can remain pooled but unused before being discarded. Zero means idle connections never expire.
dbpool.maxIdleTime=3600

# Database connection pool setting.
# Seconds. If set, if an application checks out but then fails to check-in [i.e. close()] a Connection within the
# specified period of time, the pool will unceremoniously destroy() the Connection. This permits applications with
# occasional Connection leaks to survive, rather than eventually exhausting the Connection pool. And that's a shame.
# Zero means no timeout, applications are expected to close() their own Connections. Obviously, if a non-zero value is
# set, it should be to a value longer than any Connection should reasonably be checked-out. Otherwise, the pool will
# occasionally kill Connections in active use, which is bad. <b>This is basically a bad idea, but it's a commonly requested feature.
# Fix your $%!@% applications so they don't leak Connections! Use this temporarily in combination with
# debugUnreturnedConnectionStackTraces to figure out where Connections are being checked-out that don't make it back into the pool!</b>
dbpool.unreturnedConnectionTimeout=7200

# Database connection pool setting.
# Number of seconds that Connections in excess of <code>minPoolSize</code> should be permitted to remain idle in the pool before being culled.
# Intended for applications that wish to aggressively minimize the number of open Connections, shrinking the pool back towards
# minPoolSize if, following a spike, the load level diminishes and Connections acquired are no longer needed.
# If <code>maxIdleTime</code> is set, <code>maxIdleTimeExcessConnections</code> should be smaller if the parameter is to have any effect.
# Zero means no enforcement, excess Connections are not idled out.
dbpool.maxIdleTimeExcessConnections=300

# Database connection pool setting.
# The number of PreparedStatements c3p0 will cache for a single pooled Connection. If both maxStatements and maxStatementsPerConnection
# are zero, statement caching will not be enabled. If <code>maxStatementsPerConnection</code> is zero but <code>maxStatements</code> is a
# non-zero value, statement caching will be enabled, and a global limit enforced, but otherwise no limit will be set on the number of cached
# statements for a single Connection. If set, <code>maxStatementsPerConnection</code> should be set to about the number distinct
# PreparedStatements that are used frequently in your application, plus two or three extra so infrequently statements don't force the more
# common cached statements to be culled. Though maxStatements is the JDBC standard parameter for controlling statement caching, users may find
# maxStatementsPerConnection more intuitive to use.
dbpool.maxStatementsPerConnection=3600

# Database connection pool setting.
# c3p0 is very asynchronous. Slow JDBC operations are generally performed by helper threads that don't hold contended locks.
# Spreading these operations over multiple threads can significantly improve performance by allowing multiple operations to be
# performed simultaneously.
dbpool.numHelperThreads=2

# Database connection pool setting.
# Set the query used to test the pool connection. Default query is "SELECT GETDATE()". Please note that this is not
# a valid Oracle query. In case of an Oracle database use "SELECT 1 FROM DUAL".
dbpool.preferredTestQuery=select getdate()

# Database connection pool setting.
# Test the connection on checkout using the preferredTestQuery.
dbpool.testConnectionOnCheckout=true

ROB-EX in headless mode



#In headless mode GUI for accepting changes cannot be shown. If true changes are always loaded.
XMLVersionControl.alwaysLoadChanges=true

BOM



#Is a warehouse considered empty if there is a small amount left in it? Use this to handle rounding issues. Default value is zero.
warehouse.empty.tolerance.in.SI.unit=0

#Set the default status on purchases if status is not set (null)
#Choices:
#Received, Confirmed and UnConfirmed 
purchase.default.status=Received

#Precision for material shortage color scheme. Find a good balance between precision and performance.
#When an opr have linear material accesses - how often should we check inventory during the duration of the opr?
#Default each 30 minute. It will of course always check on opr end and start.
material.shortage.precision.in.minutes=30

#Material shortage color scheme will only focus on a certain horizon to improve performance. Default 30 days from now.
material.shortage.horizon.in.days.after.now=30

#Ignore safety stock and just check if stock level will get negative - when applying mat. shortage color scheme.
ignore.SafetyStock.Material.Shortage.Colors=false

#Related to material inventory calculations and wether countings should be adjusted by unconfirmed BOM lines.
#If the BOM line state is set to 'Unconfirmed' a possibly subsequent counting will get adjusted by the BOM line quantity.
#Possible values = 'On' or 'material'
#If 'on' the state will be checked on all BOM lines - regardless of setting on master material.
#if 'material':
#The field on master material 'Use BOM line status' must be enabled - this is the most optimal setting performance wise! 
#Default = 'Material'
bom.line.confirmation.active=material

#Related to above setting bom_line_confirmation_active
#Possible values: 'None' or 'status-rule'
#Default = 'status-rule'
#If set to status-rule the state on BOM lines will be set to 'Confirmed' upon order or operation completion (when order/operation state is set to complete)
bom.line.confirmation.action=status-rule

#Possible rules: 'on-order-completion' or 'on-operation-completion'
#Default = 'on-order-completion'
bom.line.confirmation.status.rule=on-order-completion

#Comma separated list of browser where we enable direct edit of files.
#Possible values are: IE, EDGE
shopFloorDirectEditSupportedBrowsers=IE,EDGE

#Comma separated list of file extensions for which we enable direct edit.
shopFloorDirectEditFileExtensions=pdf,xls,xlsx,doc,docx

# Block access to the rest api if not logged into a mutiuser database
rest.blockAccessIfNotLoggedIntoMultiuser=false

# Should "Read from other plan" keep existing id's for production data (Projects, orders, operations, (not template!!))
readFromOtherPlan.keepExistingProductionOrderIds=false

#disable adjustment of cuantity on certain statuses
disableQuantityChangeWhenStatus=

#Colors for the material shortage/excess color view
#Dark slate gray
colorView.materialShortage.aboveMax = 0x000000
#light slate gray
colorView.materialShortage.aboveMaxWarning = 0xA0522D

# The number of suborder constraints to draw from the selection (default -1, means draw all)
order.constraint.draw.depth=-1

# Used for layoutitems project_delivery_on_time_state and order_delivery_on_time_state. Defines the number of days an order can be early,
# relative to the delivery date, before the state switches from "On time risk" to "On time".
onTimeDeliveryState.onTimeRisk.breakpoint = -1

# Used for layoutitems project_delivery_on_time_state and order_delivery_on_time_state. Defines the number of days an order can be early,
# relative to the delivery date, before the state switches from "On time" to "On time early".
onTimeDeliveryState.onTime.breakpoint = -4

# Used for layoutitems project_delivery_on_time_state and order_delivery_on_time_state. Defines the number of days an order can be late,
# relative to the delivery date, before the state switches from "late" to "very late".
onTimeDeliveryState.late.breakpoint = 2

# Draw constraints with shapes indicating the src and destination (rhombus and arrow respectivly)
constraints.route.visualizeDirections=true
constraints.prodref.visualizeDirections=true
constraints.material.visualizeDirections=true

#The default scaling factor to apply
dlgprint.ganttchart.textScale=0.9

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment