Asset subscribed

Feature
1

Rational

Some kind of subscriptions involve an asset of the company (ex: cars, building etc.). In such case it may be required to know which asset is rent to who. Also we should ensure that the same asset is not rent twice over the same period. And we must provide a way to let the user select available assets for the subscription period.

Proposal

  • Add a Man2Many pointing to stock lots of assets on subscription service.
  • Add a Many2One pointing to a serial lot number on the subscription line. It must be a lot number from the subscription service.
  • Add on serial lot number a Function field “Subscribed” for the contextual date which point to the current subscription line.
  • Add a constraint on subscription line with a lot number to not overlap.
  • Add a Many2Many readonly fields on the subscription service which shows the available and not available lots for the current date (using filter).

The lot must be removed from the lines when the subscription is canceled.
The lot will be required for a running subscription with a service linked to lots.

Implementation

Future Improvement

  • Create customer shipment for the rent assets.
2

For performance, it will be good to implement the feature exclude with range.

3

Here’s the implementation: RFC: Asset subscribed (#7486) · Issues · Tryton / Tryton · GitLab

4

This topic was automatically closed after 14 days. New replies are no longer allowed.