by VIKTOR
Learn how you (developer, engineer, end-user, domain expert, project manager, etc.) can contribute to the creation of apps that provide real value to your work.
We have heard your requests and listened: It’s now possible to change the options presented in a dynamic array row depending on the other input fields in the same row.
Previously, this was already possible for stand-alone option-, autocomplete-, or multiselectfielfds. Want to know more about implementing this feature in your apps? Visit the documentation to learn more!
Want to improve your development skills? Or looking for a specific guide, for example, on how to generate reports, set up a SCIA integration, or create (advanced) 3D models? The new Learn Page has information on all you need to know about getting started with VIKTOR and building awesome apps, so make sure to check it out in your environment! Still missing a specific tutorial? Let us know what you'd like to see in the community!
We have created a dedicated Grasshopper integration to make it easier to integrate your apps with Grasshopper! Some other benefits are: Improved error parsing informs you about where your code needs adjusting in case you made a mistake; All data provided by RhinoCompute is returned to you, providing the freedom to extract 3 DM files and other data.
Visit the documentation to set up your Grasshopper integration.
We've added a couple of ways in which admins can now better monitor the adoption and usage of tools:
Workspace admins can go to the user list of a workspace to see when a person has last visited the workspace. Environment admins can now see the email addresses of users in the activity dashboard to make it easier to identify the right people within your organization who are using apps.
Additionally, environment admins can see specifically which button or view name, including the corresponding Python function, is linked to the EDITOR.COMPUTE events. This makes it easier to gather information about computing time or errors in specific parts of the app code. Visit your environment to see all the details of your organization!
With Developer Token Expiration, tokens are automatically deactivated after one month of inactivity within SSO environments, unless you log in within this timeframe. This means that, from now on, admins don’t have to manually remove accounts to deactivate the token.
Last but not least, have you already spotted the 'What's new?' page in the documentation? Make sure to check it out for a quick overview of all the latest additions and updates of the previous months!
This month in the community spotlight, we have the Blue River application by Joris Bentvelsen. The app is an optimization model of the Blue River reservoir system, which supports multiple purposes such as flood control, minimum flow, and recreation.
Make sure to check it out and give it a try yourself!
SDK version v14.8.0 is now available: changelog
CLI version v0.33.4 is now available: changelog
Subscribe to our newsletter and get the latest industry insights