Difference between revisions of "Pandora Functions Descriptions"
From SmartWiki
| Line 14: | Line 14: | ||
Unless a function is established, no functionality is available. | Unless a function is established, no functionality is available. | ||
| − | {| border="1" cellpadding=" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
| Line 42: | Line 42: | ||
*Pref - | *Pref - | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
| Line 72: | Line 72: | ||
==='''Recordset Retrieval Functions'''=== | ==='''Recordset Retrieval Functions'''=== | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
| Line 92: | Line 92: | ||
The following functions are used to update an existing record or create a new record. These functions only work with a single record. | The following functions are used to update an existing record or create a new record. These functions only work with a single record. | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
| Line 122: | Line 122: | ||
The following function is used to trigger a message. | The following function is used to trigger a message. | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
| Line 133: | Line 133: | ||
The following functions are used for specific purposes. | The following functions are used for specific purposes. | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
| Line 148: | Line 148: | ||
==='''Transaction Functions'''=== | ==='''Transaction Functions'''=== | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" |
!Function | !Function | ||
!Description | !Description | ||
|- | |- | ||
| − | |[[Pandora - Update Transaction Intersection to Level 1 Entity|translink_add(flag ,callbackfunc,translinkid,transid,objectid,linktype,recordset)]]||Updates intersection table between Transactions and Level 1 | + | |[[Pandora - Update Transaction Intersection to Level 1 or Level 2 Entity|translink_add(flag ,callbackfunc,translinkid,transid,objectid,linktype,recordset)]]||Updates intersection table between Transactions and Level 1 or Level 2 records. |
|} | |} | ||
Revision as of 22:37, 30 September 2010
Contents
Function Overview
Pandora functions are are divided into a number of types.
- Session Level Functions – these functions are used to manage the session associated with the processing being performed.
- Information Finding Functions – these functions are used to retrieve multi-record recordsets based on provided criteria.
- List functions
- Update Functions – these functions are used to create new entities within the system.
- Utility functions – these functions provide additional general functionality to the API.
Session Level Functions
These functions are used to enable a valid session in which process can be performed and once created, determine user and related organisation attributes. Unless a function is established, no functionality is available.
| Function | Description |
|---|---|
| Session_Login (Find) | Enables Login to the instance. |
| session_logout(flag,callbackfunc) | Enables logout of the instance. |
| session_islogin(flag,callbackfunc) | Retrieve active user information. |
| Session_getCurrentUser (Find) | Retrieve the current user information. |
| Session_getCurrentCompany (Find) | Retrieve the current user’s organisational information. |
Information Finding Functions
These functions return record sets containing multiple records based on the filter passed to the functions. Each of these functions uses the following parameters:
- Fields – the fields list to be retrieved and created in the recordset. Notes an ID field will be prefixed onto the user specified field list providing the unique identifier for each record.
- Filter – the criteria by which fields should be retrieved.
- Order – the field list to control the sort sequence of the records set.
- Start – the starting record to be returned. The default is 0.
- End – the end record to be returned. The default is 200.
- Pref -
Recordset Retrieval Functions
| Function | Description |
|---|---|
| contact_list(flag,callbackfunc,fields,filter,html,order,start,end,cfidused) | Enables creation of a contact recordset. |
| webform_list(flag/callbackfunc,actionname,formid,scoreid,filter,order) | Enables return of all webforms recordset. |
| company_list(flag,callbackfunc,fields,filter,html,order,start,end,cfidused) | Enables return of an organisation recordset. |
| levelone_list(flag,callbackfunc,appid,fields,filter,html,order,start,end,cfidused) | Enables return of UTA Level 1 recordset. |
| level23_list(flag,callbackfunc,appid,level,fields,filter,html,order,start,end,cfidused) | Enables return of UTA Level 2 or 3 Recordset |
Information Update Functions
The following functions are used to update an existing record or create a new record. These functions only work with a single record.
| Function | Description |
|---|---|
| contact_update(flag,callbackfunc,rset,loginfornew) | Enables update of single contact or creation of new user. |
| company_update(flag,callbackfunc,rset) | Enables update of single organisation or creation of new organisation. |
| category_update(flag,callbackfunc,recordset) | Enables update of a category list of a company or creation of a new category list. |
| levelone_update(flag,callbackfunc,appid,rset) | Enables update of single UTA level one entity or creation of new UTA level one entity. |
| level23_update(flag,callbackfunc,appid,rset) | Enables update of single UTA level 2 or 3 entity or creation of new UTA level 2 or 3 entity. |
| invoiceitem_update(flag,callbackfunc,appid,rset) | Enables update of single invoice line items or creation of new invoice line items. |
| invoice_update(flag,callbackfunc,appid,rset) | Enables update of single invoice record or creation of new invoice record. |
| utarole_add(flag,callbackfunc,parenttype,parentobject,childtype,childoject,roleid) | Enables ability to associate an organisation or contact with a UTA level 1, 2 or 3 record. |
| utarole_remove(flag,callbackfunc,parenttype,parentobject,childtype,childoject,roleid) | Enables ability to remove an organisation or contact with a UTA level 1, 2 or 3 record. |
| leveloneskills_update(flag,callbackfunc,objectid,rs) | Enables access to Level 1 skills. |
Messaging Functions
The following function is used to trigger a message.
| Function | Description |
|---|---|
| send_msg(flag,callbackfunc,msgtype,format,fromadd,touserid,cc,subject,body) | Enables sending a message (email or quick message). |
Utility Functions
The following functions are used for specific purposes.
| Function | Description |
|---|---|
| format_date(d) | Enables date formatting. |
| variables_replace(flag,callbackfunc,objecttype,objectid,content) | Invokes the variable processor and returns formatted content. |
| trigger_workflow(objectid,wfid,objecttype) | Triggers a workflow. |
| variables_replace(flag,callbackfunction,40,userid,variable) | Obtains System Variables or other values. |
Transaction Functions
| Function | Description |
|---|---|
| translink_add(flag ,callbackfunc,translinkid,transid,objectid,linktype,recordset) | Updates intersection table between Transactions and Level 1 or Level 2 records. |
General Guidelines
The following guides are common to all function calls.
Referencing Fields
- Standard fields are referenced by name as 'firstname,lastname'. (see Database Field Names)
- Custom fields should be referenced by field name as '$fieldname1$,$fieldname2$' (recommended)
- Custom fields can also be reference by field ID as 'cf_123456'
- Fields specified will be the fields returned to the recordset
- When referencing the fields in the recordset, the first parameter is always the record index.
- If the fieldlist parameter is empty the Standard fields will be returned.
