Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Last revision Both sides next revision
devel:documentation:architecture:dev:events [2020/03/30 12:49]
tomiskar 		devel:documentation:architecture:dev:events [2021/06/29 09:52]
127.0.0.1 external edit
Line 126: Line 126:
     * ''IdmIdentityProjectionDto'' - identity form projections     * ''IdmIdentityProjectionDto'' - identity form projections
       * supports base event types ''CREATE'', ''UPDATE''       * supports base event types ''CREATE'', ''UPDATE''
 +    * ''ModuleDescriptorDto'' - application modules
 +      * supports base event types ''INIT'', ''ENABLE'', ''DISABLE''
 +    * ''IdmScripDto'' - groovy scripts
 +      * supports base event types ''CREATE'', ''UPDATE'', ''DELETE'' 
 +    * ''IdmMonitoringDto'' - monitoring evaluators
 +      * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''
 +      * adds event type ''EXECUTE'' - run monitoring evaluator
 +    * ''IdmMonitoringResultDto'' - monitoring results (returned from evaluator)
 +      * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''
   * ''acc'':   * ''acc'':
     * ''AccAccountDto'' - Accounts on target system     * ''AccAccountDto'' - Accounts on target system
Line 133: Line 142:
       * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''       * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''
     * ''SysSystemDto'' - System in ACC module     * ''SysSystemDto'' - System in ACC module
 +      * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''
 +    * ''SysRemoteServerDto'' - Remote server in ACC module
       * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''       * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''
     * ''SysSystemMappingDto'' - Mapping between system and his mapping of provisioning or sync     * ''SysSystemMappingDto'' - Mapping between system and his mapping of provisioning or sync
Line 144: Line 155:
       * adds event type ''CANCEL'' - cancels provisioning operation       * adds event type ''CANCEL'' - cancels provisioning operation
     * ''AbstractSysSyncConfigDto'' (''SysSyncConfigDto'', ''SysSyncContractConfigDto'', ''SysSyncIdentityConfigDto'') - synchronization     * ''AbstractSysSyncConfigDto'' (''SysSyncConfigDto'', ''SysSyncContractConfigDto'', ''SysSyncIdentityConfigDto'') - synchronization
 +      * supports base event types ''CREATE'', ''UPDATE'', ''DELETE''
       * adds event type ''START'' - starts synchronization       * adds event type ''START'' - starts synchronization
       * adds event type ''START\_ITEM'' - starts synchronization of one item (~entity)       * adds event type ''START\_ITEM'' - starts synchronization of one item (~entity)
Line 161: Line 173:
  
  
-The default order for listeners (''-'' => before, ''+'' => after): +The [[#predefined_processors_order|default order]] for listeners (''-'' => before, ''+'' => after).
-  * ''core'': **0** +
-  * ''provisioning'': **1000** +
-  * ''delete / archivate processed'': **5000**+
  
 ===== Basic interfaces ===== ===== Basic interfaces =====
Line 207: Line 216:
  
  * ''getPriority(event)'' - Registered async processor can vote about priority of processing for given event. Returns ''null'' by default => processor doesn't vote about priority - preserve original event priority. Use ''IMMEDIATE'' to execute whole event synchronously. All registered processors votes about event priority - whole event will be processed with the highest priority.  * ''getPriority(event)'' - Registered async processor can vote about priority of processing for given event. Returns ''null'' by default => processor doesn't vote about priority - preserve original event priority. Use ''IMMEDIATE'' to execute whole event synchronously. All registered processors votes about event priority - whole event will be processed with the highest priority.
 +
 +==== AbstractInitApplicationProcessor====
 +
 +Use this super class for providing application and module [[.events:init-data|init data]].
 +
 +
  
 ===== Transactions ===== ===== Transactions =====
Line 341: Line 356:
 ===== Implemented processors ===== ===== Implemented processors =====
  
-Basic save and delete processors are not listed.+**Basic processors for simple operations (e.g. save, delete) are not listed.** All registered processors can be listed in agenda (Settings - Modules - Processors). 
 + 
 ==== Automatic roles processors ==== ==== Automatic roles processors ====
 <code properties> <code properties>
  • by tomiskar