| http://redstack.wordpress.com/ |
| http://venkatnagabhushanam.wordpress.com/2013/09/23/oracle-sales-cloud-fusion-crm-groovy-editor-accomplish-more-by-doing-less/ http://docs.oracle.com/cloud/latest/salescs_gs/FACMI/F1071274AN104B3.htm http://www.rittmanmead.com/2014/02/groovy-jmx/ |
| Feature | Most Common Use Case | Groovy |
| Field Triggers | React to run-time data changes. Only fired when the field is changed and upon submit. | Y |
| Object Triggers | To extend the standard processing logic for an object, based on record creation, updates and deletes. There is a split between these firing events, with some related to UI/ADF actions and others originating in the database.
UI Trigger Points:
Database Trigger Points:
| Y |
| Field Validation | Displays a user entered error message based groovy logic validating the field value. The message is shown only when the validation logic returns false, and the logic is triggered only when tabbing out of the field on the user interface. | Y |
| Object Validation | Commonly used where validation is needed across multiple related fields on the object. Triggered on the submit UI action. | Y |
| Object Workflows | All Object Workflows are fired upon either record creation or update, along with the option of adding a custom groovy firing condition. | Y |
| Field Updates - change another field when a specified one changes. Intended as an easy way to set different run-time values (e.g. pick values for LOV's) plus the value field permits groovy logic entry. | Y | |
| E-Mail Notification - sends an email notification to specified users/roles. Templates support using run-time value tokens and rich text. | N | |
| Task Creation - for adding standard tasks for use in the worklist functionality. | N | |
| Outbound Message - will create and send an XML payload of the related object SDO to a specified endpoint. | N | |
| Business Process Flow - intended for approval using the seeded process, however can also trigger custom BPMN flows. | N | |
| Global Functions | Utility functions that can be called from any groovy code in Application Composer (across applications). | Y |
| Object Functions | Utility functions that are local to the parent object. Usually triggered from within 'Buttons and Actions' definitions in Application Composer, although can be called from other code for that object (e.g. from a trigger). | Y |
| Add Custom Fields | When adding custom fields there are a few places you can include groovy logic. | Y |
| Default Value - to add logic within setting the default value when new records are entered. | Y | |
| Conditionally Updateable - to add logic to set the field to read-only or not. | Y | |
| Conditionally Required - to add logic to set the field to required or not. | Y | |
| Formula Field - Used to provide a new aggregate field that is entirely based on groovy logic and other field values. | Y | |
| Simplified UI Layouts - Advanced Expressions | Used for creating dynamic layouts for simplified UI pages where fields and regions show/hide based on run-time context values and logic. Also includes support for the depends-on feature as a trigger. | Y |
|  |
| |
Data Type
|
Attributes
|
|---|---|
VARCHAR2 (240 CHAR)
|
ATTRIBUTE1 - ATTRIBUTE150
|
NUMBER
|
ATTRIBUTE_NUMBER1 -- ATTRIBUTE_NUMBER50
|
 | Why did my flexfield changes not appear in the runtime UI? | |
|
The ADF business components or artifacts of a flexfield, which are generated into an metadata services (MDS) repository when the flexfield is deployed, are cached within a user session. You must sign out and sign back in again to view flexfield definition changes reflected in the runtime application user interface page.
A flexfield's deployment status indicates whether the flexfield segments as currently defined in the metadata are available to end users. The flexfield segments seen by end users in the runtime correspond to the flexfield definition that was last deployed successfully.
=================
deployment status indicates how the flexfield metadata definition in the Oracle Fusion Applications database relates to the Application Development Framework (ADF) business components generated into a Metadata Services (MDS) repository.
The following aspects are important in understanding how flexfield deployment status is calculated:
Settings That Affect
If you have made a change to a flexfield and expect a changed deployment status, be sure you have saved your changes. No settings affect flexfield deployment status.
How Is Calculated
If the flexfield definition has been edited through the Define Flexfields activity task flows, the status is Edited. The latest flexfield metadata definition in the Oracle Fusion application diverges from the latest deployed flexfield definition. Any change, including if a value set used in a flexfield changes, changes the deployment status to Edited. If a flexfield has never been deployed, its status is Edited.
=================
|
