This article has been updated to correct links
In the above image you will see a couple of the rows marked to indicate that there are further notes. Also a feature marked N/A indicates that the method or property is not applicable within that coding environment. It does not however mean that it can't be invoked nor does it mean that sometimes it can't be used for 'tricks'. 1)
Although Self Service is a COM based API like the main ASP API for building application extensions it is actually separate and the usage of the blocks can be quite different.
The Self Service environment lacks a 'logon' that generates a CRM SID (Session ID). Because we are not using a session and we therefore also lack context we can't use any API objects/methods that rely on this for building URLs. So we can't use eWare.Button(), eWare.GetTabs() eWare.URL() etc.
For a discussion of Search Select Advanced Fields in Self Service Pages please see the article "Search Select Advanced Fields and the Self Service COM API
There are compromises that have to be made to security in order to publish files via Self Service that are stored in the Sage CRM and associated with solutions. This is mentioned in the article "Publishing Library Items in Self Service
The use of the MessageBlock has been discussed in the article "Sending Emails in ASP COM API
".COM Objects not available within the Self Service API General Observations about Self Service
I have discussed Self Service in the context of a Web Services based system here: