Procedural user component property/connection point synchronization should have an option to ignore them from synchronization
Problematic case in Apros:
- A procedural user component generates components that have default attribute values defined in the ontology for all attributes
- The procedural SCL code does not and cannot define correct values for every single Property in the generated components
- Synchronization will use the ontology-defined default values for the properties that are not defined by the procedural UC SCL code
- This means those default values will always overwrite also all of those undefined properties from the solver
What we would want:
- There should be a way in the procedural UC definition generated by the SCL code to specify that synchronization should ignore a property, not overwrite it
This means making changes to Procedural.scl but in a backwards compatible fashion. A new option for the value of Property would be needed which would signify ignoring the value in synchronization.
Edited by Tuukka Lehtonen