• [In the explorer]
  • Select the object for which you want to watch certain events.
• [In the explorer]
  • Using its icon, drag and drop this object on the corresponding table section (Configuration Process, Form, Form Properties) table.
• [In the event table]
  • Check the box corresponding to the Event Type you want to associate to the container (see table below to have details on the possible Event Types).
• [In the menu toolbar]
  • Execute the Save function
    • A new box corresponding to the association Container-EventType is created in the Map section of the working area

The description of the event types is given by the following table:

In order to remove all events of a certain type for a certain object or object class, proceed as follows:

• [In the event table]
  • Select the line for which you want to remove the events of a certain type
• [In the event table]
  • For that line, empty the checkbox corresponding to the event type you want to remove
• [In the menu toolbar]
  • Execute the Save function  The event map is updated and the associated “box” is removed.

In order to remove a specific event for a certain object or object class, proceed as follows:

• [In the event map]
  • Click on the box corresponding to the object/event
    • The event details are shown
• [In the event toolbar]
  • Execute the Delete function after having selected the event to be removed
• [In the menu toolbar]
  • Execute the Save function
    • If only one event was defined, the event logic matrix is shown again

• [In the event map]
  • Click on the box corresponding to the object/event
    • The event details are shown
• [In the event section]

  Update the event properties:

  • Event name: enter a unique name for the event
  • Event container: read-only, generated by the previous step
    • Event CPE: this is the event pattern you want to listen to. This event can be a specialization of the CPE mentioned in the event container.
• Define the actions:
  • For each action to be added, a line needs to be inserted using the insert line function
  • Depending on the action that you added, you may have to specify some parameters
• [In the menu toolbar]
  • Execute the Save function
    • The event map is updated.

In order to add a subsequent event definition for an already existing event type/object in the event map, proceed as follows:

• [In the event map]
  • Click on the box corresponding to the object/event
    The event details are shown:

    [In the Explorer toolbar]

    Execute the Add event function

    [In the popup]

    Enter the event name and click on “OK

    Proceed by defining the new event

The event CPE, as mentioned before, is the eventual CPE that the CPQ engine will listen to. The following CPE formats are supported:

• Absolute CPE, like CPE.rootCP.wks/FO/myForm.FP/myFP.value
• CPE using wildcards, like CPE.wks/CP/myCP.FO/*.FP/fp1.value
  Warning: In the event definition, CPE containing relative keywords (such as currentCP, currentForm or currentFP) or the nearest keyword cannot be used because they don’t make any sense (the event logic is always executed in the context of the root CP). The keyword rootCP however is supported.

  Moreover, instances can be targeted specifically using [1], [2] or [last]. The [current] instance is not supported.

  Warning: When the configuration engine is working on a certain CPE, it will basically look in the event definition table to all event CPE. As the event CPE is actually an event pattern (not necessarily a complete and valid CPE), the engine will actually verify if the event pattern matches the CPE it is working on.

As seen before, certain event types will typically target a complete object, and others will target an attribute. Currently, only the onChange event will target a specific attribute; all other events will target an object (a Configuration Process, a form or a form property).

will be triggered throughout the configuration and will potentially have a severe impact on performance.

In order to better understand this, let’s have a look at the following example:

Suppose that you want to execute an action whenever a form is successfully completed. In order to do this, you could use the following syntax:

onComplete(CPE./FO/)

Indeed, in this case, when the engine reaches the following form: CPE.rootCP.FO/myForm

It will clearly state that the event CPE pattern matches the current CPE. However, when the user completes the form property CPE.rootCP.FO/anotherForm.FP/aFormProperty

The engine will also see that this CPE matches the pattern used by the event CPE.

The following actions can be defined:

• [Via the ‘Event Map’ section]
  • Click on the box corresponding to the association EventType-Container you want to manipulate. You are redirected to a new working area where you can find the associated actions.
• [Via the ‘Action Parameters’ table]
  • Select the line corresponding to the action you want to delete.
• [Via the Table Toolbar]
  • Click on ‘Delete Line’
• Save