{"action":"opened","issue":{"url":"https://api.github.com/repos/e2ebridge/bpmn/issues/28","repository_url":"https://api.github.com/repos/e2ebridge/bpmn","labels_url":"https://api.github.com/repos/e2ebridge/bpmn/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/e2ebridge/bpmn/issues/28/comments","events_url":"https://api.github.com/repos/e2ebridge/bpmn/issues/28/events","html_url":"https://github.com/e2ebridge/bpmn/issues/28","id":136741041,"number":28,"title":"Persisting of modified properties","user":{"login":"lindleycb","id":5908831,"avatar_url":"https://avatars.githubusercontent.com/u/5908831?v=3","gravatar_id":"","url":"https://api.github.com/users/lindleycb","html_url":"https://github.com/lindleycb","followers_url":"https://api.github.com/users/lindleycb/followers","following_url":"https://api.github.com/users/lindleycb/following{/other_user}","gists_url":"https://api.github.com/users/lindleycb/gists{/gist_id}","starred_url":"https://api.github.com/users/lindleycb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lindleycb/subscriptions","organizations_url":"https://api.github.com/users/lindleycb/orgs","repos_url":"https://api.github.com/users/lindleycb/repos","events_url":"https://api.github.com/users/lindleycb/events{/privacy}","received_events_url":"https://api.github.com/users/lindleycb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-26T16:15:15Z","updated_at":"2016-02-26T16:15:15Z","closed_at":null,"body":"Possibly related to https://github.com/e2ebridge/bpmn/issues/16 and https://github.com/e2ebridge/bpmn/issues/17, we've been using your BPMN engine successfully now for a number of months with no glitches, but we recently had a requirement to modify rather than add one of the properties on a process instance.  When we do this using setProperty, it shows as modified when using getProperties, but is left unchanged in the database.  If there is a simple fix for this, we'd very much appreciate a patch."}}