VBCS: Updating One DFF Default Value Expression Unexpectedly Overwrites Other DFF Expression
Summary:
Hello Oracle Community,
Has anyone experienced similar behavior when configuring Redwood HCM Assignment DFFs in Visual Builder Studio, where saving a default-value expression for one DFF unexpectedly changes the expressions of other DFFs?
We would appreciate guidance on the following:
- When multiple DFFs share the same underlying Assignment data object, is this behavior expected, or should each field retain its own default-value expression independently?
- What is the recommended approach to keep these expressions separate so that saving changes to one DFF does not affect others?
Issue Details:
We are encountering unexpected behavior when configuring the Workplace Environment Assignment DFF (PER_ASG_DF) on Redwood HCM pages using Visual Builder Studio.
Tagged:
0