Open APIs

Hello Experts , 

We have a requirement to place a lock on the customer products inventory / assets for certain long running transactions. This is to ensure that no further modifications are allowed on an asset until a certain usecase is executed. Since the product inventory modification are allowed via an Order as well as Inventory based operations we cannot just rely on an onging order transactions. Hence the ask is to introduce new 'Lock' fields on the TMF637 product resource and expose it in Get operations for the consumers to validate the state before triggering any transaction on the customer asset.

Seeking some advice / guidance if adding new Lock fields on the product resource is a viable option ?

We are also looking at enhancing the state model to introduce product lock status , however the business requirements states that a product can be in an Active and Lock status at the same time. So this approach me not be suitable to meet all requirements. 

Thanks in advance

Hi,

I don't know what a "long running transactions" means but maybe our use case can provide some suggestions:

at my company, "customers are allowed to perform AllowedProductAction on products from the Product Inventory under certain circumstances.

1 example: yesterday, customer has modified their existing product with a due date in 7 days.

today, they want to change that product again, and we will tell them to wait 7 days. They can still submit the 2nd order today (it depends what the order does) but the due date will have to be on or after the previous order's due date.

to control what customer can do on which product or product offering and when, you can use TMF679 (which also offer an alternate eligibility solution)

Hello,
the question is quite important, how to ensure that the product status in the inventory is being updated at the same time via various transactions/orders.

in our side, we use <Operational status> in the inventory, such that each product has a main status and operational status. 

operational status indicates that there is a process running possibly in the delivery orchestration that will impact the product status.
for example,
for <created> main status, we have: PendingActivation, LockedCreated
for <active> main status, we have: PendingTermination, PendingModificatoin, PendingMigration, LockedActive