Different Method Using VRC Management

The procedure begins with the creation of a new package combination and new package VRCs.  The developers and their company number are linked to the new package combination.  Runtime help information for the new VRCs are created, and the developer data is modified.  Next, the normal users are linked to the former development package combination.  Their company numbers are also linked to this new package combination.  Finally, the changes in user data are converted to runtime.
The result of this procedure is a new development package combination, which is used by the developers.  The former development package combination has become the new live package combination, which is used by the normal users.

Software components can be exported from one VRC and imported into another.  In this procedure, software components of a certain development VRC are released by exporting them to sequential files.  These files can be imported into a different VRC.  Next, the copied software components are compiled, dumped, or converted to runtime.  Finally, the runtime help of the copied components must be dumped.

Customized software components are normally created in a development environment.  Normal users cannot use these software components, because these users are linked to a package combination, which contains other package VRCs than the development environment.  After testing, the customized components are released for use by normal users.

Related Posts:

• Package VRC
• Version Release Customization

Read More

Package VRC

A Package VRC is a package, which is indicated by a VRC. Within each PVRC, various components can be created and/or modified. The advantages of using PVRCs are:

• standard software cannot be overwritten
• new software components can be developed and tested in a protected environment before releasing them to production
• a PVRC does not contain all software components, only new or changed components
• development authorizations can be set by PVRC

The software components that can be created and/or modified within PVRCs are:

• Labels
• Forms
• Menus
• Reports
• Sessions
• Functions (Include Files)
• Program Scripts
• Messages
• Questions
• Domains
• Table Definitions
• Dynamic Link Libraries
• Charts

Package Combination

A Package Combination is a combination of individual PVRCs, but only one VRC from each package.

A working environment is determined by:

• package combination code
• various PVRCs
• company number(s)
• users

Assigning a Package combination to a user in a company:

Example

This slide depicts two environments: a Production environment (OPER) and a Design Environment (DSGN). The Design Environment is based on the Production Environment because of the derived from structure of the Package VRCs. Everything that is created in the Design Environment will not affect the production environment unless it is released. 

Users are linked to a Package Combination in order to find the software components at runtime. 

Developers will create/modify software components. To be able to run the software components, the developer is linked to a package combination like the user. But in order to create new software components, the developer needs a Current Package VRC.  If authorized, the developer can switch between Package VRCs.


Related Posts:

• Version Release Customization
• Different Method Using VRC Management

Read More

Version Release Customization(VRC) in BAAN ERP

Introduction
Unlike conventional products, such as cars or furniture, computer software is dynamic in nature. Rapid technological advancement, changing customer requirements, bug fixes, etc., make it imperative for software houses to regularly introduce newer versions of their software. Failure to do so would be disastrous for customers as well as the software house.
However, managing these different versions, their corresponding releases, and all the different customizations performed on them becomes a nightmarish task.


Different kinds of Software

BAAN software is divided into packages. There can be:

• Standard Software
• Localizations
• Line of Business
• Customizations
• Own 

The bshell usually searches for a software component from the outside to the inside (see Figure ) .  First, the bshell searches for any own customization for that component.  If there is no own customization, the bshell searches for a customer-specific customization, and so on.  The search path, however, is not the same for all users depending on the package combination to which the user is linked.

Components of a Package VRC

V (Version) - indicates a major change in the software

R (Release) - indicates a minor change or new enhancement

C (Customization) - indicates a customer extension, which uses the customer’s initials

Types of Software:

VRC management can be used to distinguish between various types of software. Baan delivers standard and localization packages. The customer has the option to customize the software to meet their specific needs.

A VRC should be coded using the following legend:

• L:  Localization
• B:  Line of business specific
• C: Customization developed by a third party
• O:  In-house customization

Rules: When creating a new package VRC that is derived from a standard or localization VRC, you must include one of the letters from the previous legend.

For example:

Existing VRC = tiB40a

New VRC = tiB40Ca cus

Package VRC Deviation Structure

Related Posts:

• Package VRC
• Different Method using VRC Management

Read More