0056349: [Distribution Order API]: IsAutomaticallyIssueStock parameter is kept between sessions

Description

If a request includes IsAutomaticallyIssueStock=Y at least one time then this configuration is randomly used for other requests that doesn't include this parameter.

Steps To Reproduce

1.- Create a distribution order receipt using the back-end
2.- Book it
3.- Using Postman or any REST testing tool send to the Distribution Order API (https://livebuilds.openbravo.com/context/retail_modules_pgsql_pi/api?urls.primaryName=Business%20API%20-%20Transactional%20Data#/DistributionOrder/Import_DistributionOrder [^]) an update for the previously created distribution order issue
Example JSON:
[
  {
    "organization": "The White Valley Group",
    "documentNo": "1000112",
    "isIssue": true,
    "description": "test",
    "IsAutomaticallyIssueStock": true,
    "lines": [
      {
        "lineNo": 10,
        "product": "DX58ORT-F9913",
        "qtyConfirmed": 3
      }
    ]
  }
]
4.- Create another distribution order issue and book it
5.- Update the distribution order issue using the API:
[
  {
    "organization": "The White Valley Group",
    "documentNo": "1000114",
    "isIssue": true,
    "description": "test",
    "lines": [
      {
        "lineNo": 10,
        "product": "DX58ORT-F9913",
        "qtyConfirmed": 3
      }
    ]
  }
]

RESULT: The system is trying to automatically issue the distribution order regardless the IsAutomaticallyIssueStock property is not passed in the request. Note that this might be randomly reproduced.

Proposed Solution

Revise how the IsAutomaticallyIssueStock is passed to ensure only this request can be seen. This might require discussing with the Platform team

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0168694) vmromanos (developer) 2024-09-03 12:35	For the developer fixing it: The usage of SessionInfo to save the ISSUEQTYMAP is not working as designed, because it is kept outside of the request scope. This hack was developed in a moment where the API framework was very primitive. We should check with Platform a best way to cover this feature (because I think it is now possible).

Issue History
Date Modified	Username	Field	Change
2024-09-03 12:20	kchoperena	New Issue
2024-09-03 12:20	kchoperena	Assigned To	=> Triage Platform Conn
2024-09-03 12:20	kchoperena	Triggers an Emergency Pack	=> No
2024-09-03 12:31	vmromanos	Steps to Reproduce Updated	View Revisions
2024-09-03 12:35	vmromanos	Note Added: 0168694
2024-09-03 12:53	kchoperena	Assigned To	Triage Platform Conn => Triage Omni WMS