Defining Objects and Loads that Do Not Affect the Solution State

You can create custom objects or loads that don’t affect the solution state. Any interactions with the object or load, such as inserting, suppressing, editing properties, or deleting, will keep the solution up-to-date. The feature can be used by setting the affectSolution attribute to false on the <object> or <load> tag:

<object name="objectName" version="1" caption="Object" icon="group" affectsSolution="false" > </object>

For example, if a load with the attribute affectSolution="false" is inserted in a solved analysis, the solution will stay up-to-date. If this attribute is not set, it will default to true. This feature also extends to the child entities. You can define a child entity with the same attribute and it will not affect the solution state.


Tip:  In Template2-GenericObjectCreation, you can see an example where this callback is implemented. To download all Mechanical templates, on the App Developer Resources page, click the ACT Templates tab and then click ACT Templates for Mechanical.