{"_id":"574c0348281b010e00008f71","user":{"_id":"574bfb9290d8b32000864973","username":"","name":"Tigermoth Support"},"initVersion":{"_id":"574a3bc0d1d1381900b73fae","version":"3517"},"__v":0,"project":"574a3bc0d1d1381900b73fab","metadata":{"title":"","description":"","image":[]},"createdAt":"2016-05-30T09:09:28.715Z","changelog":[{"_id":"574c0348281b010e00008f77","update":"- A constraint type called 'SCHEDULED' has been added for use on the 'Harvesting' worksheet. This constraint will force plunits that are defined as being part of the constraint to be harvested during the period of the constraint. In addition, the plunits are prevented from being harvested outside of the period of the scheduling constraint. Importantly the plunits will be harvested irrespective of their age, i.e. a SCHEDULED constraint will override any minimum or maximum age of harvest otherwise defined in the forest description. If a plunit has been scheduled at an age for which a yield has not been defined then the plunit area will be harvested without generating a yield, and an infeasibility will not be generated.","type":"added"},{"_id":"574c0348281b010e00008f76","update":"- All charts have had the option to group and filter by 'Plunit' added. This enables an understanding of the results of harvest planning using the scheduling constraints to be better understood and interpreted.","type":"improved"},{"_id":"574c0348281b010e00008f75","update":"- Regular expressions are now able to be used on the data definition worksheets 'Tending', 'Regime', 'Croptype' and 'Cost'. This greatly simplifies data definition because new products can be quickly defined for any grouping of the existing data classes. For example, to create a new cost product called 'Harvesting Management Fee' and have it apply to every plunit via the 'Cost' worksheet, use the expression { LIKE '%' } as the cost class of the product. In this example the new product would apply to every plunit because the '%' acts as a catch-all wild-card across the worksheet and is achieved using a single line. Boolean logic is also supported to enable more efficient and complicated data definition if required. The use of regular expressions for data definition requires the use of the parallel processed data access routines for SQL Server.","type":"added"},{"_id":"574c0348281b010e00008f74","update":"- The parallel processed data access routines for SQL Server will no longer allow the use of the 'Origin/All' grouping on either the 'Allocation' or the 'Balancing' worksheets. This historic grouping should be replaced with the standard generic grouping of 'All Plunits/All' (or similar). The historic 'Origin/All' grouping is still able to be used if the original data processing routines are selected.","type":"improved"},{"_id":"574c0348281b010e00008f73","update":"- The parallel processed data access routines for SQL Server will now also check that two Groups with the same name do not exist.","type":"improved"},{"_id":"574c0348281b010e00008f72","update":"","type":"added"}],"body":"Additions, changes and corrections available in this build:","slug":"3517100295596-1","title":"3517.10029.5596"}

3517.10029.5596


Additions, changes and corrections available in this build:
added
- A constraint type called 'SCHEDULED' has been added for use on the 'Harvesting' worksheet. This constraint will force plunits that are defined as being part of the constraint to be harvested during the period of the constraint. In addition, the plunits are prevented from being harvested outside of the period of the scheduling constraint. Importantly the plunits will be harvested irrespective of their age, i.e. a SCHEDULED constraint will override any minimum or maximum age of harvest otherwise defined in the forest description. If a plunit has been scheduled at an age for which a yield has not been defined then the plunit area will be harvested without generating a yield, and an infeasibility will not be generated.
improved
- All charts have had the option to group and filter by 'Plunit' added. This enables an understanding of the results of harvest planning using the scheduling constraints to be better understood and interpreted.
added
- Regular expressions are now able to be used on the data definition worksheets 'Tending', 'Regime', 'Croptype' and 'Cost'. This greatly simplifies data definition because new products can be quickly defined for any grouping of the existing data classes. For example, to create a new cost product called 'Harvesting Management Fee' and have it apply to every plunit via the 'Cost' worksheet, use the expression { LIKE '%' } as the cost class of the product. In this example the new product would apply to every plunit because the '%' acts as a catch-all wild-card across the worksheet and is achieved using a single line. Boolean logic is also supported to enable more efficient and complicated data definition if required. The use of regular expressions for data definition requires the use of the parallel processed data access routines for SQL Server.
improved
- The parallel processed data access routines for SQL Server will no longer allow the use of the 'Origin/All' grouping on either the 'Allocation' or the 'Balancing' worksheets. This historic grouping should be replaced with the standard generic grouping of 'All Plunits/All' (or similar). The historic 'Origin/All' grouping is still able to be used if the original data processing routines are selected.
improved
- The parallel processed data access routines for SQL Server will now also check that two Groups with the same name do not exist.