bring messages home

[burnettk]

Issues ticket #1626

build two process models using the messages branches. if that works, maybe we can ship it.

• [x] Restructure the message json
• [x] Update data setup service to new message json
• [x] Duplicated message data in process_group.js
• [x] New message dialog - can have duplicate messages
• [x] New message dialog - confirm dialog changes
• [x] Remove broken message models tab from UI. will follow back up later
• [x] Payload is missing in the properties panel
• [x] Data stores are dropped when editing a message
• [x] Selecting a message from the drop down does not set correlation properties in the xml
• [x] fabricate correlation keys so they will exist in bpmn xml
• [x] Hardcoded xml end to end
• [ ] avoid removing attributes on correlation properties when saving messages
• [x] avoid removing messages that are actually referenced by other tasks when updating a task that is associated with a message
• [x] End to end test
• [ ] User testing

DEFERRED

• [ ] delete message_triggerable_process_model entries when we delete their bpmn files - DEFER
• [ ] New api(s) to call instead of process_groups api - DEFER
• [ ] allow changing the location of an existing message - DEFER
• [ ] allow renaming an existing message - DEFER
• [ ] New message dialog - location, is it dropdownable - DEFER
• [ ] Move message edit temp button to permanent location - DEFER (just removed button for now)
• [ ] Receive message config for task data - DEFER?
• [ ] message models need collaborations because cor-keys. add validation? remove this requirement? - DEFER
• [ ] Add environment for new messages - DEFER