Feature Requests

If you are in Work Days - Time Pairs Module and you want to navigate to the employee, you have to navigate from TimePairs to WorkDays and then to Employees. It would be helpful if a direct navigation is possible. Also from Employee to Time Pairs directly would be beneficial

Add Button "Apply Workday Modification" in TimePair-Cockpit Add a function to apply workday modifications for multiple workdays/timepairs at once -Enabled when 1 or more TimePairs are selected. -select Workdays (Maximum 1000 items) -Needs Edit Workday Right & check Write-Restrictions -Question: Are you sure? -Adding Serverside Method, which checks all workdays and applys the current modification. -Presenting the result to the User (e.g. 5 Added, 1 Edited, 10 Deleted) -Reload the selected items.

Material issues, requests, and returns and the corresponding material handling items are moved to their own database tables. Moreover, several fields on those entities are renamed to better emphasize their meaning, including the following. UserAssignedDate CompanyPerson Quantity Additionally, the field "RequestedQuantity" is added to the MaterialIssueItem entity to indicate the originally requested quantity.

Just like we currently have the Deactivate Projects option, we would also like to have the ability to deactivate companies, removing them from user visibility and use within the system. Deleting a company simply is not possible anymore after it has been used in some projects.

In the past, there have been misunderstandings about whether filters were applied or why certain data was not displayed. This was often caused by hidden columns. To prevent such issues, it will no longer be possible to hide columns that are used for filtering, grouping, or sorting in the desktop and web clients.

Moving containers into a new container table Container Types: Container Types are now stored in it's own table ContainerType table Per Container Type you can define default measurements, which will be considered when selecting a container type New Fields: Ownership (Shipper / Carrier) Seal No Commodity Code ECCN Number Export Value (considered in Shipment.TotalExportValue) New Container Status: Packed, Shipped, Delivered, Inspected, Unloading, Unloading Finished, Returned. Unloading and Unloading Finished will be calculated based on the packages, similar to the shipment status. All existing "Completed" containers will be migrated to "Returned" Weights: Container Net Weight is now a calculated field, automatically summarizing the Gross Weight of all Packages Container Tare Weight: This value ist stored physically in the database Container Gross Weight: This is Net Weight + Tare Weight. The Gross Weight is still editable, but if you change it, the Tare Weight is adjusted accordingly

Currently, it is only possible to link items of a single reference type to deviations, e.g. either packages, shipments, or site progress items. We want to resolve this restriction and support references of different types for deviations, i.e. to reference both packages AND shipments, for example.

Since we have the unique chance with the next release (due to the Container Rework) to rename tables and properties, we are reviewing the whole database. For example we will rename tables: PackagePosition to PackageItem Equipment to SiteProgressItem SubAssembly to BillOfMaterials Issue to Deviation and many more Rename single properties: PackagePosition.PositionNo to PackageItem.PackageItemNo QuantityExpected to QuantityPacked and many more the complete list of changes will be published here: https://docs.insitelms.net/general-information/updates/version-10-database-changes We will migrate reports, views, dashboards, import configurations as good as we can

In Global Forms and Project Forms complete lists can be managed. But it is not possible, to use the same list on different fields. Therefore it is suggested, to move the management of lists out of the forms editor and new modules with Global and Project lists should be created. Lists will have a name, and this name can be associated in the forms

When copying Deviations, all Deviation References and Notification Subscriptions should be copied to the new item as well. Additionally, Notification Subscriptions should also be copied for all other relevant items, that are Tasks, Cost Impacts, and Project Documents.