Updating dot-walked values using ATF Form steps can result in server side steps not showing the new value if the same value was previously accessed with server side steps - Known Error

Updating dot-walked values using ATF Form steps can result in server side steps not showing the new value if the same value was previously accessed with server side steps Description Different values are returned in ATF test for a field when dot-walked via reference compared to accessing the record directly. Use case test premises: - The dot-walked condition sc_request.active=false is defined in BR "set sc_task.active on insert" - before insert business rule. - The test starts with finding a request that is active, changes it to inactive and inserts sc_task records before and after the change. - The BR not triggering is expected for step 2, however not expected on step 8, after the associated sc_request is made inactive.

Steps to Reproduce

1. Load, preview and commit the attached update set sys_remote_update_set_2807a8da1bab40d09a110d03cd4bcba1.xml 2. Note the custom Business Rule being introduced 'set sc_task.active on insert' sys_script_eedc03151b7a40509a110d03cd4bcb16 3. Run the ATF test CS4553904 included in the same update set

Note that despite the request_item.active field being validated as false in step 7, the resulting record inserted in step 8 does not trigger the BR "set sc_task.active on insert".

Workaround This problem is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form.

As a workaround, remote all dot-walk references inside of form steps, add new test steps in the Server category, which most effectively query for, and then populate, the related records.