...
[10:57:41 CDT(-0500)] <JasonElwood> if Archna develops a UI for updating those values, go ahead and update the db directly? or do we want to tackle adding a service?
[10:58:29 CDT(-0500)] <JasonElwood> we discussed moving the configuration.js settings into the confg table
[10:58:30 CDT(-0500)] <dmccallum54> "tackle adding a service"… we're still going to need an API… i'm 100% OK with not publishing it
[10:59:03 CDT(-0500)] <dmccallum54> configuration.js and message_template… these are two separate issues in my mind
[10:59:09 CDT(-0500)] <JasonElwood> agreed
[10:59:31 CDT(-0500)] <JasonElwood> unless somebody is available to write the service and API for message_template, I'll ask her to directly update the db.
[11:02:12 CDT(-0500)] <dmccallum54> not sure what you mean. she's gunna need an API to write a ext.js UI for it
[11:06:25 CDT(-0500)] <dmccallum54> for the really simple level of support we've been talking about, a message template UI and API should probably look a lot like the confidentiality disclosure agreement UI and API
[11:08:28 CDT(-0500)] <JasonElwood> I'll write it up
[11:10:31 CDT(-0500)] <dmccallum54> hey look....
[11:10:32 CDT(-0500)] <dmccallum54> @Controller
[11:10:32 CDT(-0500)] <dmccallum54> @RequestMapping("/1/reference/messageTemplate")
[11:10:32 CDT(-0500)] <dmccallum54> public class MessageTemplateController
[11:10:39 CDT(-0500)] <dmccallum54> so there already is an API
[11:11:29 CDT(-0500)] <JasonElwood> sweet
[11:35:32 CDT(-0500)] <JasonElwood> SSP-188 is the issue for the message template if anybody is interested