TrustedCode

Special services, e. g., to access email, EDI?, HBCI? etc.

These services are defined at system startup by entries in a table at the place configured in $trustedcode-oid.

The place holds a table (in HTML syntax) with an id attribute value of TrustedCode. Each line (tr element) enables one trusted code function. The first cell hold the OID of the only place, which is allowed to execute the code. The second cell contains the name of the function to enable. The third cell is either the literal read or write and defines whether the function can be called from within a transaction (write operation) only or also from read operations.

Those places allowed to executed the code can return an additional element in their reply (see CoreAPI). This new element has an gi of TrustedCode and a name attribute equal to the configured service.

Example

Definition table at $trustedcode-oid

 <table border="1" id="TrustedCode">
  <tr>
   <td>OID</td>
   <td>sendmail</td>
   <td>write</td>
  </tr>
 </table>

Beware: there must not be any space characters in the table cells. They don't harm, but disturb the operation (no effect anymore).

Application at OID

<reply xmlns="mind">
 <TrustedCode name="sendmail">
...
 </TrustedCode>
</reply>

Spezialdienste zum Beispiel zur Anbindung an eMail, EDI? etc., werden durch "trusted code" (beim Systemstart an vordefiniertem Platz definiert) implementiert.

Ursprünglicher Plan: Sie transformieren ein Slotset (ggf. außer "urkundlichen").