Intelligent Regeneration › Processing Logic

Processing Logic

You can request Intelligent Regeneration for a model, a business system, or a load module. You can further restrict the scope of the request by specifying changes that are made during a specific time frame, by a specific user ID, or select to ignore changes that are made to the target environment and construction libraries. If the scope is restricted by these parameters, the results of the analysis are not saved for future work sessions. When the scope of the request is defined, the Intelligent Regeneration process:

• Determines all application components included in the scope of the request: a business system has load modules; load modules have procedure steps; procedure steps have action diagrams and screens; procedure step action diagrams have action blocks, derivation algorithms, referential integrity triggers, or both.
• Records the earliest timestamp that a component was generated.
• Identifies the sessions and the associated aggregate objects that occurred since the earliest component timestamp and, if requested, within the specified time frame and by the specified user ID.
• Reviews each generation object, according to the Intelligent Regeneration Rules, to mark the appropriate components as changed.
• Flags the components for regeneration if an aggregate object change affects that component, and if the aggregate object's session timestamp is later than the component's generation timestamp.

Regeneration occurs for the flagged components.