Last updated on SEPTEMBER 06, 2016
Applies to:
Oracle Depot Repair - Version 12.1.3 to 12.1.3 [Release 12.1]Information in this document applies to any platform.
Symptoms
On : 12.1.3 version, Service Request
ACTUAL BEHAVIOR
---------------
A forms personalization on WHEN-NEW-BLOCK-INSTANCE trigger and block UPDATE-STATUS does not open the DFF window even when the personalization is set to GO_ITEM REPAIRS_DF.
EXPECTED BEHAVIOR
-----------------------
This personalization worked ok in 11.5.10, but it does not in 12.1.3
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create DFF 'Repair Orders' using ATTRIBUTE1 for a segment (free text)
2. Create a personalization on the Repair Workbench as follows
Seq: 1
Description: item revision mandatory - no save without it
Level: Function
Enabled: True
Condition(Tab):
Trigger Event: WHEN-NEW-BLOCK
Trigger Object: UPDATE_STATUS (note - on 11.5.10 this should be CONTROL_UPDATE_STATUS)
Condition: :REPAIRS.ATTRIBUTE1 is NULL
Processing Mode: Not in Enter-Query Mode
Context:
Level: Site
Actions (Tab):
Seq: 10
Type: Builtin
Description: open DFF
Language: All
Enabled: True
Builtin Type: GO_ITEM
Argument: REPAIRS.DF
3. Close repair workbench and open it again
4. create a repair order without entering the DFF data
5. click Update Status; the DFF does not open. Instead it opens the update status window
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users can change the status without updating the DFF attributes that are mandatory before changing status.
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