The Ansys Minerva connector allows you to:
Overwrite mode
When uploading files, the Ansys Minerva connector has several overwrite options for how to handle files when the file is already present in Ansys Minerva:
Overwrite: Silently overwrite any existing files with the new files.
Append: Keep the existing files and download the remote files with appended names.
Ignore: Do not transfer the conflicting files.
Snapshot: Create a minor version for unreleased files of the same name. Create a major version for released files.
Note: For more details about overwrite modes, refer to the Ansys Minerva generic connector documentation.
Example: Run optiSLang in batch mode with data send/receive to/from Ansys Minerva
Create an optiSLang workflow with data send and receive to/from Ansys Minerva.
Create a data send/receive node with registered files that will be sent to Ansys Minerva.
Execute the project in optiSLang batch mode.
View the uploaded files under Data view in Ansys Minerva.
Limitations
Once the stored refresh token expires, the associated project or workflow becomes invalid for data transmission (send/receive). To restore functionality, In the same project/workflow, you must browse the filesystem within Ansys Minerva at least once to update the refresh token for that project.
It is important to note that validity of a project utilizing the Ansys Minerva connector is directly linked to the lifecycle of the refresh token from Ansys Minerva.