The table is used to identify a problem set group used to differentiate between different problem types. It is typically used to define the problem for Background optimization, planning, and dispatch.
Attribute Name |
Type |
Field Size |
Description |
Required |
int |
4 |
Unique internal DB Identifier of the DataSetGroup record. |
Required | |
nvarchar |
50 |
Business key to identify the activity this DataSetGroup refers to. |
Required | |
nvarchar |
50 |
Business key to identify the Area this DataSetGroup refers to. Must exist on the FWArea table. |
Required | |
nvarchar |
50 |
This attribute is assigned a specific string value by the user when created. Valid values must be validated against a predefined list of valid values on the FWCode table. Fixed values: · BGO = Background Optimizer · DEDICATED_BGO = Background optimizer fixed on one group · PLANNER = Route Planner · DISPATCH = Dispatch |
Required | |
nvarchar |
255 |
The service name is set to ”r;-None-” when the status is set to ”r;Free.” It is system assigned to a service name of the service receiving the dataset for processing. It is typically set to a unique service scheduler machine name and port. |
Required | |
nvarchar |
50 |
This attribute is assigned a specific string value by the system. It is not modifiable by the user. Valid values must be validated against a predefined list of valid values. The predefined list needs to be externalized for possible extension during implementations. Fixed values: System Assigned · Planning · Dispatching · Frozen · Optimizing · Free · Busy · Done |
Required | |
datetime |
8 |
When the status is set to ”r;Processing” or ”r;Done.” Should be blank when the status is set to ”r;Free.” |
| |
nvarchar |
500 |
See Comment. |
| |
int |
4 |
See CreatedBy. |
| |
datetime |
8 |
See CreatedDate. |
| |
int |
4 |
See ModifiedBy. |
| |
datetime |
8 |
See ModifyDate. |
| |
datetime |
8 |
Last time the record is retrieved. |
| |
UseDipatchBGO |
bit |
1 |
Specifies whether or not this data slice selects from a Dispatching schedule |
|
Active |
bit |
1 |
When this setting is enabled, the BGO will optimize the data slice. This functionality applies to both types of data slices: dedicated and dynamic. The Active setting is disabled by default in order to allow users to configure the data slice first and then activate it when configuration is complete. In cases where the data slice is active and being optimized and this setting is turned off, the system will behave as follows:
com.descartes.escheduler.optimizer.refresh_lnosfw_data |
|
nvarchar |
50 |
See Company. |
|