I like to display a description of what a workspace does in annotation. The workspace parameters already have a place to input a description (e.g. Overview property in 2017.1), but that is not nearly as visible as annotation. It would be helpful if annotation could be created that is dynamically linked to workspace parameters, such that if I update the text in the annotation the corresponding workspace parameter is updated, and vice versa.
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It's a great idea to make the Workspace Parameters more explicit on the canvas... Filling the workspace parameters is of great importance when it comes to documenting your workspace so others can make use of it. It could look like this....
'
To expand the breadth of the idea, this same feature would be helpful with transformers also. For instance, I sometimes like to put in annotation attached to a Bufferer transformer the buffer amount, i.e. "Buffer by 5 feet". It would be nice if that transformer parameter could be embedded in annotation, thus dynamically updated.
Hi,
To expand more on _trent_ , and on other previous suggestions. It would be great to have a kind of annotation somehow linked to the global variable setter I would say. It's useful for testing purpose, because such a variable can specify a state of the workbench, exactly as a parameter, but from a more programmatic style (just as an example : "print debug on" or "... off" could be done inline this way - granted you have a writter dedicated to each case...).
Moreover, it could be even a little more sophisticated if we could have such a annotation-like variable setter, be wired to a parameter value from any transformer. In this case we could do a fanout based on this kind of internals (name the directory of the final output according to) and so on. This allow the developper to exhibit any particular case he needs to underline at a given time.
So in one word, for me a new workbench annotation-like global variable setter, from a testing and developping point of view, would do great. The advantage in term of documentation is in fact in the same line and has been already pointed out before - and today is almost very well done by the ability to show a table of the transformer settings, just missing how to grab some value from this table the way discussed here.
+15- Safer
Updated idea statusGathering Interest→Archived
Idea merged into:
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.