Difference between revisions of "System Call"
From SmartWiki
Line 10: | Line 10: | ||
− | < | + | <pre><!--SysCall_updatestatus(@objtype@,@objid@,'StatusName')--> |
− | + | <!--SysCall_workflow(@objtype@,@objid@,'myworkflow')@--> | |
− | + | <!--SysCall_workflow(23,@parent.objid@,'myworkflow')@--> | |
− | |||
− | |||
+ | <!--SysCall_workflow(levelone,@parent.objid@,'myworkflow')@--> | ||
+ | </pre> | ||
<br/>**@objtype@ and @objid@ are reserved words | <br/>**@objtype@ and @objid@ are reserved words | ||
<br/>**Objtype can be integer or constants {levelone,level1,leveltwo,level2,levelthree,level3,contact,people,company} | <br/>**Objtype can be integer or constants {levelone,level1,leveltwo,level2,levelthree,level3,contact,people,company} |
Revision as of 13:55, 12 September 2012
System Call ( embedded in browser script custom field type )
Trigger Type
on Load - SysCall is carried out by server when page is loaded(no javascript is required)
on Page - SysCall is trigger by clicking a button on page
on Save - SysCall is carried out by server when page is saved(no javascript is required)
Example :
<!--SysCall_updatestatus(@objtype@,@objid@,'StatusName')--> <!--SysCall_workflow(@objtype@,@objid@,'myworkflow')@--> <!--SysCall_workflow(23,@parent.objid@,'myworkflow')@--> <!--SysCall_workflow(levelone,@parent.objid@,'myworkflow')@-->
**@objtype@ and @objid@ are reserved words
**Objtype can be integer or constants {levelone,level1,leveltwo,level2,levelthree,level3,contact,people,company}