Function prototype	event_set ( session, event )
API Version	ALL

API Version	Changes respect to previous version
2.7.3	Added support for multiple comments XML structure changed (see change details)
0.0.0	Initial version
IMPORTANT: Remember to call session_init() indicating the appropriate API Version

API Version

Changes respect to previous version

2.7.3

Added support for multiple comments

XML structure changed (see change details)

0.0.0

Initial version

IMPORTANT: Remember to call session_init() indicating the appropriate API Version

Sets information of an event
Input parameters:	session: is the session id obtained in the session_init call event: is an event XML object. See more on event_get() function
Output parameters:	result: empty if all the process it’s ok ErrorMsg: any fault in the call, either in the validation of input parameters, errors in the connection to the database or any other error, this parameter returns the error message produced ErrorCode
Request sample:	event_set(“LC000000000000”, “ <?xml version="1.0" encoding="UTF-8"?> <event> <version>2.7.3</version> <ref>10017</ref> <type> <id>#EVENT:CARE</id> <description>EVENTO SANITARIO</description> </type> <status>OPEN</status> <date>2017-11-21 00:00:00</date> <follow_report>N</follow_report> <phone_poster>615235656</phone_poster> <priority>HIGH</priority> <comments> <comment> <order>1</order> <text>This is the text of the first comment</text> <date>2018-05-28 00:00:00</date> <channel> <type>email</type> </channel> <user> <ref>123123</ref> </user> <assigned_to> <user> <ref>123123</ref> </user> <team> <ref>1</ref> </team> <role> <ref>24</ref> </role> </assigned_to> </comment> <comment>...</comment> </comments> <call_type>IN/OUT/VOID</call_type> <issued_by> <type>OTHER</type> <ref></ref> <date>2011-03-28 17:05:00</date> <channel>PHONE</channel> <phone></phone> </issued_by> <admission> <ref>6903</ref> </admission> <case> <ref>4741</ref> </case> </event> “);
Response sample:	<?xml version="1.0" encoding="utf-8" standalone="yes"?> <result></result> <ErrorMsg></ErrorMsg>
Notes:	This method will send an email using the EMAIL TEMPLATE to the EVENT's ASSIGNTO_USER (if informed and User's preferred contact channels are selected)

2.7.3	0.0.0	Comments
`<event>`	`<event>`
`<version>2.7.3</version>`		If this node is specifically included, the specified XML version format will be used. Otherwise the version used will be the one provided in session_init()
`<ref>10017</ref>`	`<ref>10017</ref>`
`<type>`	`<type>`
`<id>#EVENT:CARE</id>`	`<id>#EVENT:CARE</id>`
`<description>EVENTO SANITARIO</description>`	`<description>EVENTO SANITARIO</description>`
`</type>`	`</type>`
`<status>OPEN</status>`	`<status>OPEN</status>`
`<date>2017-11-21 00:00:00</date>`		Date assigned to the EVENT. This value was previously informed in node `posted_by/date`
`<follow_report>false</follow_report>`	`<follow_report>N</follow_report>`	Contents changed from S/N to true/false
`<phone_poster>615235656</phone_poster>`	`<phone_poster>615235656</phone_poster>`
`<priority>HIGH</priority>`	`<priority>HIGH</priority>`
`<comments>`	`<comments>`
	`<open>comments for open the event</open>`
	`<close>comments for closet he event</close>`
`<comment>`
`<order>1</order>`
`<text>This is the text of the first comment</text>`
`<date>2018-05-28 00:00:00</date>`
`<channel>`
`<type>email</type>`
`</channel>`
`<user>`
`<ref>123123</ref>`
`</user>`
`<assigned_to>`
`<user>`
`<ref>123123</ref>`
`</user>`
`<team>`
`<ref>1</ref>`
`</team>`
`<role>`
`<ref>24</ref>`
`</role>`
`</assigned_to>`
`</comment>`
`</comments>`	`</comments>`
	`<team>`
	`<ref>1</ref>`
	`</team>`
`<call_type>IN/OUT/VOID</call_type>`	`<call_type>IN/OUT/VOID</call_type>`
	`<posted_by>`	`posted_by` information is now enclosed in the first `comment`node
	`<role>`
	`<id>23</id>`
	`<description>Enfermero</description>`
	`</role>`
	`<id>5282</id>`
	`<nickname>Call C.</nickname>`
	`<name_complete>Call Center</name_complete>`
	`<date>2011-03-28 17:05:00</date>`
	`<minutes>10</minutes>`
	`<channel>`
	`<type>email</type>`
	`</channel>`
	`</posted_by>`
	`<assigned_to>`	`assigned_to` information is enclosed in the comment/assigned_to information. Note that now there can be multiple comments and each one can be assigned to a different role/team/user
	`<role>`
	`<id/>`
	`<description/>`
	`</role>`
	`<id>5282</id>`
	`<nickname>Call C.</nickname>`
	`<name_complete>Call Center</name_complete>`
	`<date>2011-03-28 17:05:00</date>`
	`<minutes/>`
	`<channel>`
	`<type></type>`
	`</channel>`
	`</assigned_to>`
`<issued_by>`	`<issued_by>`
`<ref></ref>`		Moved from node `person/id`
`<type>OTHER</type>`	`<type>OTHER</type>`
	`<person>`
	`<id/>`	Moved to node `issued_by/ref`
	`</person>`
`</issued_by>`	`</issued_by>`
`<admission>`	`<admission>`
`<ref>6903</ref>`	`<ref>6903</ref>`
`</admission>`	`</admission>`
`<case>`	`<case>`
`<ref>4741</ref>`	`<ref>4741</ref>`
`</case>`	`</case>`
`</event>`	`</event>`

XML changes in API version 2.7.3 respect version 0.0.0

Browser not supported