0.12.0

What's Changed

Breaking changes:

• Changed the names of the events and their classes, to be more consistent:

  • DocumentReleaseEvent -> DocumentReleasedEvent
  • PartReleaseEvent -> PartReleasedEvent
  • EngineeringChangeRelease -> EngineeringChangeReleasedEvent
  • EngineeringChangeCheck> EngineeringChangeCheckEvent

• Event data now consistently uses the attributes parts and documents instead of linked_parts or attached_parts

Full Changelog: 0.11.1...0.12.0

0.11.1

What's Changed

• Fix crash when using pydantic >=2.11

Full Changelog: 0.11.0...0.11.1

0.11.0

What's Changed

• Feat: Document and Part Field Calculation Events

Full Changelog: 0.10.0...0.11.0

0.10.0

What's Changed

• Feature: Added development server that can be used to run Functions locally for testing and development.

Full Changelog: 0.9.0...0.10.0

0.9.0

What's Changed

• Feat: Add create and modify check events for docs and parts

Full Changelog: 0.8.4...0.9.0

0.8.4

What's Changed

• Feat: Add MyPy support by @jens-kuerten in #20

Full Changelog: 0.8.3...0.8.4

0.8.3

What's Changed

• added the fields short_name, application and remark to Material

Full Changelog: 0.8.2...0.8.3

0.8.2

What's Changed

• add teilenummer and t_index to bom_item by @jens-kuerten in #15
• switch to ruff and upgrade bandit by @jens-kuerten in #16

Full Changelog: 0.8.1...0.8.2

0.8.1

• Fix: removed incorrect dependency to urllib3

0.8.0

Features:

• New "Release Check" events for Documents, Parts and Engineering Changes, which are triggered before an object is released and allow the release to be aborted by returning an Action.

• Actions can be returned by a Function to perform actions in CIM Database in response to an event. The first new Action AbortAndShowErrorAction can be used to abort the current operation in CIM Database, e.g. to abort a release process if certain conditions are not met.