First time here? Check out the Help page!
1 | initial version |
When we needed this with OpenStudio server we created a file named "resource.json" in the lib directory. We made a helper method to read and write to this file that measures had access to. This allowed us to pass information across measures. If you tried to do this on local runs in the OpenStudio application you would need to use an absolute path to the resource file, while on the server we use a relative path.
You can file a user voice request to allow direct access to log messages from earlier measures in the workflow.
2 | No.2 Revision |
When we needed this with OpenStudio server we created a file named "resource.json" in the lib directory. We made a helper method to read and write to this file that measures had access to. This allowed us to pass information across measures. If you tried to do this on local runs in the On OpenStudio application you would need to use an absolute path to the resource file, while on the server we use a relative path.path to the resource file. For a local run with OS app or PAT you might need an absolute path, but I haven't tested this.
You can file a user voice request to allow direct access to log messages from earlier measures in the workflow.