| Foundation1 / Development Guide / Development Tools / Solution Developer / Customization Development / Normal Customization / |
This section describes standard customization development with ISD 2. Layered customization development is explained in Layered Customization Support.
In addition to a properly setup customer information file, .cifx file, that the developer should opened in the Solution Developer, Harvest Package for the customization should be created and available in Harvest. Creation of Harvest Packages should have been done from LCS Customization Projects.
When developer identifies the file that needs to be customized, he or she should make sure that the file is available in customer harvest environment. Developer can find this by looking in to the 'Harvest' column in ISD. If the file is not available, the first step would be to check in the file to customer harvest using the appropriate _STD* package. To do this, use RMB on the file -> Harvest -> Check in New menu option.
If an appropriate _STD* package cannot be located, developer can create one using the 'New' button in the package selection dialog. The correct naming for the package will be generated automatically. Clicking OK at the end will complete this process.
The next step would be to check out the file to update. This can be achieved by using RMB option Harvest -> Check Out for Update menu action. After selecting this, a dialog will appear to select the appropriate harvest package. Notice that this dialog is not listing _STD* packages and the new button stays disabled. Once the correct package got selected and OK button pressed, the required file with correct folder structure will get downloaded to workspace folder for update.
To open the file for editing using the associated application (based on the file extension), developer can RMB on the file -> Work Folder File -> and select 'Open' menu item. Bare in mind that this does not replace standard programming methods and tools, but simplifies doing smaller changes.
In order to start testing a customization, developers can deploy edited database files into Oracle database directly from the Solution Developer.
When checking out client files to update using Check Out for Update, following dialog will appear asking whether to download entire client project.
If the developer clicks Yes, all related files will be copied to the work folder as read only. And the check box is selected, this behavior will be persistent and the dialog will not be shown next time.
A drawback with having all files in the Work Folder is that the developer will not, during his or her development, see any changes made to the assembly by other developers unless he or she actively fetches these files from Harvest. A synchronization routine is needed.
When developing C# in Visual Studio it can sometimes be difficult to foresee exactly which files developer will be changing and need to check out for update. To prevent the developer from changing unreserved files, the Solution Developer always fetches required assembly files as Read Only. Visual Studio will always notify you if you are about to make changes to a Read Only file.
There will be situations where development cannot continue unless developer actually make a change to a not reserved file. The file may be reserved by someone else and will not be available for some time. If the developer now decides to overwrite the files, he or she must be able to synchronize/merge changes to these unreserved files with new versions in Harvest as soon as the files are available for reservation. Please refer to File Synchronization Support section.
Reports section in Virtual view provide a flat structure of reports. Report related files can be situated in many places but ISD will group them together and list them when a user clicks on a report.
