Subvar Update push to Essbase
Summary: When subvar is updated it does not update the essbase at the backend. And to get it to work right first from the point the point of update, you either need to do refresh database or restart DB, the later being simple and lite weight process, i am in favour of taking it. But it would have been good if subvar update method does this at the backend in the rest call or give a rest resource or method to stop the database it would help. Anyone has any thoughts around this ?
Content (required): Subvar update through groovy - Changes push to essbase.