Methods handling

2008-09-19T07:29:02Z

Zjz: /* Parameters handling */

__NOTOC__
[[Category:Customizations]]
[[Category:r6]]
[[Category:r11]]
[[Category:Spel Code]]
{{Global Header}}
{{Global Announcement}}
== Method calling ==
Methods can be called from [[Object_Triggers|triggers]] or using [[Send_wait]] function.

Here is an example of trigger (call method ''convert_request'' with one parameter):
<source lang="text">
POST_VALIDATE convert_request( persistent_id ) 96 FILTER(EVENT("INSERT"));
</source>

== Method definition ==
You can define new methods on every object. This definition must be in file with SPL extension in [[$NX_ROOT]]/site/mods/majic folder. In one file you can define more than one method and even for more than one class.

Here is the base structure of new method called '''newMethod''' on object '''cr''' with variable number of parameters:
<source lang="javascript">
void cr::newMethod (...)
{

}
</source>
Use method definition with ''(...)'' even if no parameters are expected.

=== Parameters handling ===
Parameters are passed into the method in '''argv''' array. Each parameters are in triplets. Here is the explanation of argv values:
*argv[0] - number of parameters
*argv[1] - name of the first parameter
*argv[2] - previous value of the first parameter
*argv[3] - actual value of the first parameter
*argv[4] - name of the second parameter
*argv[5] - previous value of the second parameter
*argv[6] - actual value of the second parameter
and so on

== Overriding methods ==
If you want to override some built-in method, simply define method with the same name (object::methodName) and write your new body.

Attachments Library

2008-07-18T15:52:40Z

Zjz: /* Tips */

[[Category:Configuration]]
On a fresh install of r11, the attachment repositories of Knowledge and Service Desk are already configured and operational. Additional work is required when performing a migration.

== Facts ==
[[Image:r11_default_repositories.jpg|thumb|r11 Default Repositories Screenshot]]

The attachment functionality uses Tomcat exclusively.

The attachment functionality resides on the Primary Server exclusively, even though the Repositories can exist anywhere.

Knowledge Tools and Service Desk utilize the same attachment mechanism, but have their own distinct requirements. In particular, every Knowledge Repository ''must'' contain a folder, while the Service Desk Repository does not.

== Tips ==

Ensure your default Tomcat port (usually 8080) has firewall access for users outside of the firewall. Just because they have Service Desk access, which is usually the default port 80 used by IIS and Apache, do not assume they have access to attachments.

If directing users outside the firewall to a Secondary Server, ensure they have access to the Primary Server tomcat port
or
Add a repository deamon to your secondary server using pdm_edit and change your repositories to point to the secondary server (recommanded solution for external users as no additional port need to be open on the firewall).
Note that the physical folders for the repositories need to located on the secondary server too.

== See Also ==

[[Configure Java Client to Use Web Client for Uploading Attachments]]

----
<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>

SDU - User contributions [en]

Methods handling

Attachments Library