Your manager has disapproved your vacation request for ${numberOfDays} days.
Reason: ${managerMotivation}
</documentation>
<extensionElements>
<activiti:formPropertyid="numberOfDays"name="Number of days"value="${numberOfDays}"type="long"required="true"/>
<activiti:formPropertyid="startDate"name="First day of holiday (dd-MM-yyy)"value="${startDate}"datePattern="dd-MM-yyyy hh:mm"type="date"required="true"/>
<para><emphasisrole="bold">identity:</emphasis> optional tables, when using the default identity management as shipped with the engine.</para>
</listitem>
<listitem>
<para><emphasisrole="bold">history:</emphasis> contain the history and audit information. Optional: not needed when history level is set to <emphasis>none</emphasis></para>
<para><emphasisrole="bold">history:</emphasis> contain the history and audit information. Optional: not needed when history level is set to <emphasis>none</emphasis>
Note that this will also disable some features such as commenting on tasks which store the data in the history database.</para>
</listitem>
</itemizedlist>
</para>
</section>
<sectionid="database.tables.explained">
<title>Database table names explained</title>
<para>
The database names of Activiti all start with <emphasisrole="bold">ACT_</emphasis>. The
second part is a two-character identification of use case of the table. This use case
will also roughly match the service API.
<itemizedlist>
<listitem>
<para>
<emphasisrole="bold">ACT_RE_*</emphasis>: 'RE' stands for <literal>repository</literal>.
Tables with this prefix will contain 'static'' information such as process definitions and,
process resources (images, rules, etc.).
</para>
</listitem>
<listitem>
<para>
<emphasisrole="bold">ACT_RU_*</emphasis>: 'RU' stands for <literal>runtime</literal>.
These are the runtime tables, that contain the runtime data of process instances,
user tasks,variables, jobs, etc. Activiti only stores the runtime data during process instance
execution, and removes the records when a process instance ends. This keeps
the runtime tables small and fast.
</para>
</listitem>
<listitem>
<para>
<emphasisrole="bold">ACT_ID_*</emphasis>: 'ID' stands for <literal>identity</literal>.
These tables contain identity information, such as users, groups, etc.
</para>
</listitem>
<listitem>
<para>
<emphasisrole="bold">ACT_HI_*</emphasis>: 'HI' stands for <literal>history</literal>.
These are the tables that contain historic data, such as past process instances,
variables, tasks, etc.
</para>
</listitem>
<listitem>
<para>
<emphasisrole="bold">ACT_GE_*</emphasis>: <literal>general</literal> data, which is used
in various use cases.
</para>
</listitem>
</itemizedlist>
</para>
</section>
<sectionid="databaseUpgrade">
<title>Database upgrade</title>
<para>Make sure you make a backup of your database
attribute you provide should contain the canonical name of the runtime class. This is a class that implements
Activiti's <literal>JavaDelegate</literal> interface. You should implement this class in the same manner as any
other <literal>JavaDelegate</literal>. Documentation for this is provided in the <linklinkend="bpmnJavaServiceTaskImplementation">userguide here</link>.
</para>
<para>
The user's property values will be injected into the <literal>delegationClass</literal> runtime class
if you provide members in the class for Activiti to inject into. The names should match the names of the members
in your <literal>CustomServiceTask</literal>. For more information, consult <linklinkend="serviceTaskFieldInjection">this part</link>
of the userguide.
</para>
<para>
Note that the runtime class shouldn't be in your extension JAR, as it's dependent on the Activiti
libraries. Activiti needs to be able to find it at runtime, so it needs to be on the Activiti engine's