When using Configuration Spaces, the Space Action Event is always generated. By default, 
logs some preset actions. The events for these actions are notified by default to the System Log. For further information on these preset actions, see the Configuration Spaces.
You can also configure space action events to be notified when a space has been created, copied or removed using Event Notification.
Filtering
In the Event Setup tab, the values for all the event fields are set by default to All in the Match Value(s) column, which generate event notifications every time a Space Action event is generated. Double click on the field to open the Match Values dialog where you can click on the Add button to add which values you want to filter on. If there are specific values available, these will appear in a drop-down list. Alternatively, you can enter a hard coded string or a regular expression.
Space Action event specific fields
The following fields are available to filter Space Action events in the Event Setup tab:
actionType- With this field you can configure notifications to be sent for certain space actions. You select the action type from the drop-down list:spacecreate done,spacecopy doneandspaceremove done.destinationSpaceName- The name of the destination space to which the content of the source space is copied when aspacecopycommand has been executed. To choose a specific space or spaces, select the space from the drop-down box which includes all of your spaces.spaceName- The name of the space for which an action has occurred.To choose a specific space or spaces, select the space from the drop-down box which includes all of your spaces.
Fields inherited from the Base event
The following fields are inherited from the Base event, and described in more detail in 4.3.1 Base Event:
category- If you have configured any Space Action categories, you can select to only generate notifications for Space Action events with the selected categories.contents- This field contains a string with event specific information. If you want to use this field for filtering you can enter a part of the contents as a hard coded string.eventName- This field can be used for specifying which event types you want to generate notific ations for. This may be useful if the selected event type is a parent to other event types.origin- If you only want to generate notifications for events that are issued from certain Execution Contexts, you can specify the IP addresses of these Execution Contexts in this field.receiveTimeStamp- This field contains the date and time for when the event was inserted into the Platform database. If you want to use timeStamp for filtering, it may be a good idea to enter a regular expression, for example, "2014-11.*" for catching all Space Action events from 1st of November, 2014, to 30th of November, 2014.severity- With this field you can determine to only generate notifications for events with a certain severity; Information, Warning, Error or Disaster.timeStamp- This field contains the date and time for when the Execution Context generated the event. If you want to use timeStamp for filtering, it may be a good idea to enter a regular expression, for example, "2014-11-13 09:.*" for catching all the Space Action events from 9:00 to 9:59 on the 13th of November, 2014.
Note
The values of these fields may also be included in the notifications according to your configurations in the Notifier Setup tab.
Example Space Action Event Configuration
Example - Space Action event notification saved in a database
This configuration will give you the following notification setup:
- When a space action is performed on any of your spaces, a notification will be generated.
- When a space action event is generated, an entry is added to the spaceactions table in the configured database, containing the following data:
- The action performed i e spacecopy, spacecreate, or spaceremove
- The name of the space for which the action has occurred