Base actions help identify some technology-specific properties automatically to send as part of the webhook. There are currently base actions for the technologies listed below. Each technology will list which action values will be defaulted based on page content in the current browser window. See the Sample Webhook Functions page for ideas on actions to trigger for each technology.
...
When using the APEX base action, the default match pattern is .*\/apex\/f.*, matching any pages within APEX. Another option would be to set this based on your APEX server host name, which would be better if you’re sending different webhook actions from each APEX server. (Ex. https:\/\/apexhostname:8181\/apex\/f.*)
Properties
Name | Description |
|---|---|
Application Names | List of APEX application names |
Workspace | APEX workspace name |
...
When using the ORDS base action, the default match pattern is .*\/apex\/f.*, matching any pages within APEX. Another option would be to set this based on your server host name, which would be better if you’re sending different webhook actions from each APEX server. (Ex. https:\/\/apexhostname:8181\/apex\/f.*). If you sending webhooks for both APEX and ORDS, it’s best to remove the match pattern for whichever action is used less frequently, as there’s no indication in the URL to differentiate between App Builder and ORDS.
...
The default match pattern for the OIC base action is .*integration\.ocp\.oraclecloud\.com.*.
Properties
Name | Description |
|---|---|
Integration IDs | List of Oracle cloud integration IDs found on current page |
...
No match pattern is set for the OBI base action, but you can easily add one based on host name. (Ex. http:\/\/obihost:9704\/analytics.*)
Properties
Name | Description |
|---|---|
Object Names | List of object names found on current page |
Current Folder | Full path of current folder, starting with /shared. This property value generally can’t be identified while viewing/editing a specific object within the catalog. |
...