Changes

SmartConnect - RESTful API

213 bytes added, 20:15, 22 June 2018
no edit summary
|-
||cf_''CustomFieldName''
||Custom fields are denoted by their field name, preceded by a prefix of 'cf_'. While it is best practice to reference the field name, you may also reference the field ID. ||cf_My Custom Field cf_fieldid 
|-
||;;
* Any existing and applicable template formulas will be triggered and run after a record update.
* Any existing and applicable workflows will be triggered and run after a record update.
* Any existing and applicable status-triggers will run for any status change after a record update.
=Configuration - Advanced=
=Appendix=
==Creating SmartConnect functions==
SmartConnect functions are created for each individual instance of SmartSimple. You can create multiple functions of the same action if needed, depending on the field list returned.
For a more detailed look at creating functions, see See [[Creating JSON functions|Creating and Managing SmartConnect Functions]] for a more detailed look at creating functions.
==Standard Field Names==
For a list of available Standard Fields that you can reference along with update restrictions, see See [[JSON API (SmartConnect) Standard Field Names|SmartConnect Standard Field Names]] for a list of available Standard Fields that you can reference along with update restrictions.
The standard fields available for reference varies on the Record Type selected in the API call.
==Options and Settings==
<!--Explain all applicable misc options and settings that shouldn't be explained above here...-->
===Available Record Types===
{| class="wikitable"
0
edits