Profiles may now have alias IDs, which is a new way to reference profiles using multiple IDs. The Unomi ID still exists, but a new index with aliases can reference a single Unomi profile. This enables more "contextServerCookieName": "context-profile-id", "activateWem": true, "trackerSessionIdCookieName": "unomi-tracker-test-session-id", "trackerProfileIdCookieName": "trackerProfileIdCookieName": "unomi-tracker-test-profile-id" } } // generate a new session if (unomiWebTracker.getCookie(unomiTrackerTestConf.wemInitConfig.trac

\ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "metadata": { "id": "setContactInfo", "name": "Copy the received contact info to the current profile", "description": "comparisonOperator" : "equals", "propertyValue" : "PROFILE_ID" } } } EOF Apache Unomi 1.x - Documentation - 11 where PROFILE_ID is a profile identifier. This will indeed retrieve all the events \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "metadata": { "id": "exampleEventCopy", "name": "Example Copy Event to Profile", "description": "Copy event properties

definition: { "itemId": "tweetNb", "itemType": "propertyType", "metadata": { "id": "tweetNb", "name": "tweetNb", "tags": ["social"] }, "target": "profiles" elementToCreate, id) { var js, fjs = document.getElementsByTagName(elementToCreate)[0]; if (document.getElementById(id)) return; js = document.createElement(elementToCreate); js.id = id; js errorCallback, payload) { var data = JSON.stringify(payload); // if we don't already have a session id, generate one var sessionId = cxs.sessionId || generateUUID(); var url = 'http://localhost:8181/context