The encountered scenario:
Containers were booked out in some past projects and never booked back in Rentman, but they did return to the warehouse. However, if I try to scan them out on a project now, I am blocked with an error that says: “Combination X is booked on project Y”.
Rentman’s development team has worked on a way to increase flexibility in packing combinations left on previous projects. To achieve this, we are looking whether a combination is sealed or unsealed and whether a combination is empty or has content. Let us look at the options, using an old Project A, and an upcoming project B.
What the system does:
If the combination is empty (both, sealed or unsealed):
Books the combination as returned on project A, and books it out on project B. Since the combination is empty, no content has to follow.
If the combination has content and is sealed:
Books it as returned on project A, including all the content, and books it out on project B with that content.
If the combination has content and is not sealed
Unlinks all of the combination's content on project A, so that it becomes loose equipment, but lets it stay in the combination as actual content.
Books the combination as returned on project A.
Opens a screen prompting you to match the equipment on project B with the content of the previous project in it.
We have also implemented an additional filter in the warehouse Warehouse that shows all projects that are "done" (project status is Returned) but still have equipment out on one of the warehouse statuses.
What you have to do:
The fix will be in version 441.
Nothing. Once released, this fix will allow you to simply scan combinations that have been left behind, which will cause them to return and be booked into your upcoming project.
In the meantime you can go back to the project they were on and book the containers back.
There is also a new filter