| # Versions The parameters for your modeling environment are defined and you created the components that can be used in the modeling process. The next step is to define one or more versions in which you can create the model items you need to build a business model. To make enterprise structure models, business models, and related repository model items uniquely identifiable, you must model them in a specific, user-definable version. Versions can be derived from other versions. A new version, which is derived from a source version, includes all the models and model items of the source version without copying them to the new version. Therefore, any modifications made in the source version, even after the derived-from structure has been defined, will apply to the new version. However, modifications in the new version will only apply to that version.
Version dependency of model items.
Version-dependent model items | Version-independent model items
--- | ---
Business control diagrams | Responsibility codes
Business functions | AO documents
Business processes | All categories
Wizards | Employees
Reference models | Employee group types
Project models |
Roles |
Static conditions |
Dynamic conditions |
Rules |
Utilities |
Employees (through project models) |
Employee groups |
Versions (tgbrg1500m000) To create new versions or to maintain existing ones, use the Versions (tgbrg1500m000) session. You can also use this session to define data such as the version from which the new version was derived, the status, and the owner. To define a version, complete these steps: Click New In the Version field, specify a name for the version In the Status field, select the status for the version Choose one of the following statuses: Developing One or more model items in this version are still being worked on. Finished All model items in this version have been developed and can be used. Expired All model items in this version can no longer be used. In the Owner field, select the ERP Enterprise user who has created the version, or is responsible for the version. Click Save
Key fields for the Versions (tgbrg1500m000) session
Field | Description
--- | ---
Derived-From Version | If applicable, select a version from which the version you are creating is derived.
Effective Date | The date when the version becomes effective.
Finish Date | The date when the version can no longer be used.
Expiry Date | The date when the status of the version was set to Expired.
License Expiry Date | Displays the expiration date of the license code. After this date, a new license key must be acquired from Infor.
Standard | If this check box is selected, the version is developed for a customer. If this version is for internal use only, clear this check box.
Note The dates you specify in the Effective date field and the Finish Date field are purely informative. If a new version is created, a message appears with the question whether the authorization mechanism should be used for this new version. If you answer: Yes, you are authorized for this new version. No, version authorization is not generated at this point. At a later point, you can still generate authorizations. Until then, everybody is authorized for that version. For more information on version authorizations, see the version authorization section. These are the options to view the version tree structure in a browser: Click Browser. Click Version Tree on the appropriate menu In this browser you can see which versions are interrelated, and for which versions you are authorized.
Color descriptions in version browser
Color | Description
--- | ---
Green | Normal version for which you are authorized.
Blue | Your current modeling version.
Red | Version for which you are not authorized.
Magenta | Your current modeling version, for which you are not authorized.