Last updated on MARCH 02, 2017
Applies to:Siebel Field Service - Version 184.108.40.206.10 [IP2013] and later
Information in this document applies to any platform.
Request your help in understanding if OOTB class functionality with Status=Done and Actual End Date can be tweaked or not.
As per vanilla functionality in Action BC, when status is updated to 'Done', Actual End Date field (TODO_ACTL_END_DT) gets updated with time stamp. This looks to be class functionality.
We have a requirement, where when status is changed to 'Done', an error message must pop up requesting the user to fill the 'Actual End Date' field.
To avoid this OOTB behavior, we have written a browser script to throw an alert message using SWEAlert and we are returning CancelOperation, hence OOTB behavior is being bypassed and it doesnt populate Actual End Date with timestamp.
Another OOTB functionality is, when Actual End Date is populated, system automatically sets status to 'Done'. We are unable to control this behavior. Once system populates the status to Done, we are populating status to the old value in the script itself, so when the user gets back control, he would see the old status value.
Once the user fills the 'Actual End Date' field and changes the status to 'Done', system should create another activity (as per our requirement).
Currently, the issue we are facing is, system is not behaving as expected when Status is changed to 'Done' or when Actual End Date is being populated. System is not behaving consistently. We are attaching log file, BC, Business Service SIFs along.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms