Custom Object Creation With Webservice Failed In Error
(Doc ID 2330967.1)
Last updated on DECEMBER 20, 2017
Applies to:Oracle Fusion Sales Cloud Service - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Opportunities
Custom object creation via webservice
there is a business requirement to make a button from Opportunities, which would send a notification to the owner with some information about the current status of the opportunity.
So to send an email you need a workflow. It can be triggered either via object update or creation. To change an existing object there are two ways of doing it:
> to edit a field (this would require the user to press "Save" button after the "Send notification button")
> to edit it via a webservice (this would prevent user to continue working on that object and would require him/her to close it and open again, losing all the unsaved changes).
Therefore a solution with new object creation has been chosen.
You are using a custom object CustomLog_c and creating an object with a webservice adf.webServices.CustomObject.createEntity. (Then the workflow is getting triggered after object creation). However few of the desired technical fields are never triggered.
The createEntity web service method call should create a custom object record with all detail attributes.
The issue can be reproduced at will with the following steps:
1. Create a custom object using App Composer
2. Update and or Create a new record via web service using Groovy
3. Few of the object attributes are not being passed and updated on the created record
The issue has the following business impact:
Due to this issue, users cannot see few of the important attributes for the custom object record created.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document