You are here

Alfresco Process Services 1.7 » Developer guide » Custom Logic

Hook points

A hook point is a place where custom logic can be added. Typically this is done by implementing a certain interface and putting the class implementing the interface on the classpath where it can be found by the classpath component scanning (package com.activiti.extension.bean for example).
  • Login/LogoutListenerinterface: com.activiti.api.security.LoginListener and com.activiti.api.security.LogoutListener
  • Process engine configuration configurerinterface: com.activiti.api.engine.ProcessEngineConfigurationConfigurer
  • Rule engine configuration configurerinterface: com.activiti.api.engine.DmnEngineConfigurationConfigurer
  • Process Engine event listeners It is possible to listen to events fired by the Process Engine. By default (and if enabled) there is a listener that captures these events, processes them before sending them to Elasticsearch (which is used for analytics). If the event data should be going somewhere else, for example an external BI warehouse, the following interface should be implemented and can be used to execute any logic when the event is fired.
  • Processing document generation variablesinterface: com.activiti.api.docgen.TemplateVariableProcessor
  • Business Calendar Use the business calendar when calculating due dates for tasks.
Parent topic: Custom Logic

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.