An object generator creates a related business object from an existing one and copies the data across. Classic example: a quote becomes an order with all line items. Nuclosian sets up these follow-up documents. Jobs are the scheduled runs that go with them.

What the generator does in the process

Source and target are defined, as is when the generator is visible (state, action, single or batch). Attributes and subforms to copy define the data handoff. Optionally the system links target to source. When mapping and copy are not enough, rules hang on the generator. The follow-up document appears without retyping and without spreadsheet transfer.

For leadership that means fewer media breaks in quote-to-cash and similar chains. For business teams it means a clear action on the record. For IT it means configurable handoff instead of a one-off script.

What Nuclosian takes on

Keep Objektgenerator, source, and target in the prompt. Nuclosian writes mapping and creation directly into the instance. There is no diff for that. Then check generation of the follow-up in application mode. Overview: First steps.

Technical reference in the wiki

Tabs, attributes, subforms, and rules: Objektgenerator in the Nuclos wiki. The wiki is the configuration guide. This page explains the process value.

What to clarify next

• Which follow-up documents are created manually today?
• Which fields and lines must copy one-to-one?
• Which generations need extra rules or jobs?