properties field of the events. Here is an example for objects that used dynamic properties for URL parameters: The following event example in Apache Unomi 1.x: curl --location --request POST 'http://loc look up profiles by profile ID or aliases from the same cookie ( context-profile-id ) or body parameters ( profileId ) Verb Path Description GET /cxs/profiles/PROFILE_ID_OR_ALIAS Retrieves a profile following subsystems: context.json filters and personalization queries rule conditions and actions parameters Apache Unomi uses two integrated scripting languages to provide this functionality: OGNL and MVEL

] } EOF Apache Unomi 1.x - Documentation - 25 As you can see in this request, we have a few parameters that need explaining: • -k is used to accept any certificate as we are in this example using a if the action is hidden or not. It is usually used to hide objects in a UI. parameters List The parameters of the actions, also defined by annotations systemTags List A (reserved) @Action(id = "helloWorldGroovyAction", actionExecutor = "groovy:helloWorldAction", parameters = [@Parameter(id = "location", type = "string", multivalued = false)]) def execute() { logger

creates new actions based on the event data and the rule internal processes, providing values for parameters defined in the associated `ActionType. Example actions include: “Set user property x to value other conditions. A simple condition could be: “User is male”, while a more generic condition with parameters may test whether a given property has a specific value: “User property x has value y”. PERSONA executing the tests. Test parameteres are editable in the performance-tests/src/test/scala/unomi/Parameters.scala file. baseUrls should contains the URLs of all your cluster nodes Run the test by using