Item Status Change Requiring Multiple Saves (Doc ID 1989761.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Product Hub - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version,

ACTUAL BEHAVIOR
---------------
When changing the item status from "Active" to "Future Delete", the status had to be saved twice in order to be applied to the item.

This issue has also been reported as: Attribute values from new template are not applying first time.


EXPECTED BEHAVIOR
-----------------------
Expect to save changes first time correctly

STEPS
-----------------------
1. Navigate to an item in "Active" status
2. Click "Update"
3. Change the Item Status to "Future Delete" and Apply
4. Note that the item status is still "Active" after the page refreshes
5. If Steps 2-3 are repeated, the item status is then changed to "Future Delete"


Note: Standard Oracle functionality is in place to "Default Value" of Purchasable to "No" when an item status changes to Future Delete.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms