Data modeling workflows need to be predictable. Whether teams are importing models through the command line, running workflow scripts, applying Model Conversion Rules or editing multiple entity columns at once, they need confidence that every step can be monitored, controlled and completed – all without adding unnecessary friction.
That’s why WhereScape 3D 9.0.6.4 focuses on the operational layer.
We are calling this the ‘Workflow Control’ Release because it improves the way users manage automated model imports, monitor long-running scripts, apply Model Conversion Rules and work through everyday modeling edits.
This isn’t a landmark release but it addresses important areas such as: workflow reliability and usability improvements that help teams work with greater control and with fewer interruptions.
More Powerful CLI Model Import
What’s changed: The CLI model import command’s force overwrite option can now overwrite entity and attribute properties within a model.
This includes key fields such as:
- Label.
- Data type.
- Entity type.
- Other entity and attribute properties.
New attributes are added during import, while attributes that are absent from the import file are preserved.
Why it matters: Command-line model import is important for teams that want to standardize and automate repeatable modeling workflows. By extending force overwrite support to entity-level updates, 3D makes scripted model maintenance even more powerful and practical.
This is especially useful for teams working with automation, repeatable release processes or CI/CD-style workflows – all of those where models need to be updated consistently, without excessive manual intervention.
Practical impacts include:
- Automate more comprehensive model updates through the CLI.
- Update key entity and attribute properties with greater control.
- Preserve existing attributes that are not included in the import file.
- Support more reliable scripted model import and deployment workflows.
Real-Time Workflow Script Logging
What’s changed: Workflow script execution output is now streamed to the progress bar details window, all happening in real time.
Previously, script output appeared only after execution was complete. Now, users can see progress as workflow scripts are running.
Why it matters: Long-running workflow scripts are easier to monitor when users can see what is happening as it happens. Waiting until the end of execution can make troubleshooting harder, especially when a script takes time to complete or needs closer observation.
Real-time logging gives users immediate visibility into workflow progress, helping them understand whether a script is still running as expected or whether further investigation may be needed.
Practical impacts include:
- View workflow script progress in real time.
- Monitor long-running scripts more easily.
- Troubleshoot workflow execution with better visibility.
- Reduce uncertainty during script-driven operations.
More Reliable Model Conversion Workflows
What’s changed: This release includes fixes that improve the reliability of Model Conversion Rule workflows.
A NullPointerException that occurred when using the Validate template with Status = -2 in Apply Model Conversion has been resolved.
A separate issue has also been fixed where the application could hang when certain Model Conversion Rules accessed connection type through Pebble templates. This affected scenarios such as Set Load Table Properties and Collapse Source Mappings.
Why it matters: Model Conversion Rules are central to automated design workflows in 3D. When MCRs are used to apply standards, transform structures or prepare models for downstream work, users need them to complete reliably.
These fixes reduce the risk of interrupted conversion workflows and help users keep model automation moving without needing to force-close the application.
Practical impacts include:
- Apply affected Model Conversion Rules more reliably.
- Avoid hangs caused by MCR Pebble templates accessing connection type.
- Run Validate template scenarios with greater stability.
- Improve confidence in MCR-driven automation workflows.
Entity Editor Stability Improvements
What’s changed: An issue has been resolved where the entity editor window could fail to close after clicking OK or Apply when multiple columns were selected.
Although changes were being saved correctly, the user interface did not always reflect this, creating confusion.
The editor now closes as expected in multi-select scenarios.
Why it matters: Bulk column editing is a routine part of modeling work. When the UI does not respond as expected, even if the change has been saved correctly, users can lose time checking whether the operation worked.
This fix makes multi-column editing clearer and more predictable.
Practical impacts include:
- Apply bulk column edits with clearer feedback.
- Avoid confusion when clicking OK or Apply after selecting multiple columns.
- Work more smoothly in the entity editor.
- Reduce friction in everyday model editing tasks.
UI Housekeeping and Legacy Cleanup
What’s changed: The deprecated Define model conversion option has been removed from the repository tree contextual menu.
This legacy option was no longer functional, so removing it helps reduce clutter and avoid confusion.
Why it matters: Small interface improvements can have a meaningful effect on usability. Removing outdated options helps users focus on current, supported workflows instead of legacy features that no longer apply.
Practical impacts include:
- Reduce unnecessary UI clutter.
- Avoid confusion around deprecated model conversion options.
- Keep repository tree actions cleaner and more current.
Typical Scenario: More Controlled Model Automation
A typical workflow might look something like this:
- Import model updates through the CLI as part of a scripted process.
- Use force overwrite to update key entity and attribute properties.
- Run workflow scripts and monitor output in real time.
- Apply Model Conversion Rules with improved stability.
- Edit multiple entity columns and apply changes without UI uncertainty.
- Continue working in a cleaner interface with deprecated options removed.
The result is a more controlled and transparent modeling workflow, especially for teams using 3D as part of repeatable, automated or standards-driven data architecture processes.
Overall: Why This Release Matters
The ‘Workflow Control’ Release is about giving 3D users more confidence in the workflows that sit around modeling automation.
It improves how model imports are handled through the command line, how workflow scripts are monitored, how Model Conversion Rules complete, and how everyday entity editing behaves.
Key benefits include:
- Stronger CLI automation: Force overwrite now supports broader entity and attribute property updates.
- Better workflow visibility: Script output streams in real time during execution.
- More dependable MCR workflows: Fixes address conversion rule errors and application hangs.
- Smoother entity editing: Multi-select column edits now close correctly after OK or Apply.
- Cleaner user experience: Deprecated legacy options have been removed from the contextual menu.
Recap: Release Highlights
- CLI model import force overwrite now supports entity and attribute property overwriting.
- New attributes are added during import, while absent attributes are preserved.
- Workflow script execution output now streams in real time.
- Apply Model Conversion reliability has been improved.
- MCR hangs related to connection type access through Pebble templates have been fixed.
- Entity editor multi-select scenarios now close correctly after OK or Apply.
- The deprecated Define model conversion contextual menu option has been removed.
Ready to try WhereScape 3D 9.0.6.4 ‘Workflow Control’ features in your environment? Reach out to us for a demo.
