I think I would have done this:

ID=what you want to call it

Event Class Key= what your eventclasskey will be, probably empty in your test case.

regex: *test*

example: test

transform:

if evt.summary.find('test') >= 0:

   evt.summary="Event Successfully Mapped"

So - your eventClassKey is mapping as well as the name?  Typically, the eventClassKey would be set to some other field of the event - often it is the component field though it doesn't have to be.  So I, personally, would not have a mapping name or eventClassKey of "mapping" - I would find that confusing.

You don't say what event class you are mapping to??  You need to start with an event class - either a product-supplied one or create your own.  Once you have a class, then create the mapping.  The function of a mapping is to determine whether your event is going to be of this class, or not.

Rather than creating your own mapping next, the easiest way is to generate a test event.  Not sure whether you have actually been specifying an event class of /Unknown?  Don't - leave that event class field blank - that is what the mapping is all about.  Your event should come through as /Unknown anyway.  Once you see your event, use the class mapping icon in the Event Console (the one that looks like a data tree) and map it to your /Skills event class.  This AUTOMATICALLY creates a mapping for you and copies the event summary field into the mapping example field - which may come in handy later.

Now you can work on that mapping.  You could add a rule of evt.summary == "test" and you could add a transform as you have done.

Another tip is to always close previous test events before generating a new test event - otherwise it adds to the repeat count of an earlier event and may cause confusion.

When you get bored with using the GUI to generate events, you may find swapping to a command window and using zensendevent is faster.

Cheers,

Jane

The /Unknown "class" is a special case that catches everything that doesn't map to anything else.  The documentation may not be over-bright about it but I don't really think it's a bug.

Glad you got going

Cheers,

Jane