currently the request from the document editor is the only thing being tested in this cycle.
in the document outcomes section. you can add outcomes. theses outcomes have a data-meta tag.
When they add a outcome. that outcome is added.
when they click save or publish
add of the data-meta tags in the #page element get posted to the server.
the server then adds these to the documentmeta database with a key starting with salsa
when a user builds a report, the documentmeta starting with salsa are collected and put into the reports .json file.
after that i think the client uses it to review the document outcomes. if so there should be a better way to do this.
currently the request from the document editor is the only thing being tested in this cycle.
in the document outcomes section. you can add outcomes. theses outcomes have a data-meta tag. When they add a outcome. that outcome is added. when they click save or publish add of the data-meta tags in the #page element get posted to the server. the server then adds these to the documentmeta database with a key starting with salsa when a user builds a report, the documentmeta starting with salsa are collected and put into the reports .json file.
after that i think the client uses it to review the document outcomes. if so there should be a better way to do this.