Events & Actions on ScipioERP

EECAs

Mon, 06 Jun 2016 00:00:00 +0000

Entity Event Condition Actions (EECAs) are actions that are triggered by events on the database level. You can be quite specific as to what the event actually is (like before during or after an update has been performed on a particular row of a table) and how the action is going to be:

Annotation

 
 
 
 java
 
@Eeca(
 entity = "MyEntity",
 operation = "create-store",
 event = "return",
 condition = "!empty(myParameter)",
 actions = {
 @EecaAction(service = "checkUpdateQuoteStatus", mode = "sync")
 }
)
public interface MyEntityReturnEeca {}

XML

SECAs

Mon, 06 Jun 2016 00:00:00 +0000

Just like entity event condition actions , services can be interlinked by the event condition action model. On the service level these are referred to as Service Event Condition Actions (SECAs). SECAs are defined inside service-eca definition files:

Annotation

 
 
 
 java
 
@Seca(
 service = "myService",
 event = "return",
 condition = "myField == 'TEST'",
 actions = {
 @SecaAction(service = "testService", mode = "sync", runAsUser = "system")
 }
)
public interface MyServiceReturnSeca {}

XML

Controller Events

Mon, 06 Jun 2016 00:00:00 +0000

Requests can be used as to trigger events. Like all request definitions, these are defined within the Controller . Controller events are either request-specific or generic. The difference is that generic events are validated on each request without validating the request path itself.

Annotation

 
 
 
 java
 
@Event(name = "test", type = "java", path = "org.ofbiz.webapp.event.TestEvent", invoke = "test",
 section = "postprocessor")
public interface PostprocessorTestEvent {}

@Request(
 uri = "view",
 secure = "false",
 auth = "false"
)
@Event(name = "test", type = "java", path = "org.ofbiz.webapp.event.TestEvent", invoke = "test")
@Response(name = "success", type = "request", value = "main")
public interface View {}

XML

JobSandbox

Mon, 06 Jun 2016 00:00:00 +0000

JobSandbox works like a time-based scheduler. It is used to schedule Tasks periodically at fixed times, dates or intervals. Within Scipio ERP the scheduler is based on Quartz . JobSandbox makes use of the service engine for all operations. A similar concept on the entity level can be achieved by the use of EntitySync. The concept itself differs slightly, however, as the use of EntitySync is mostly designed around the scheduled synchronisation of databases (as in POS systems) and not for maintenance in general.