Sage 300 Web SDK
The Sage 300 Web SDK (SDK) includes productivity tools (wizards) for the generation of Web UIs in an MVC framework, documentation, samples and utilities.
The Sage 300 ISV and Business Partner community has applications, add-ons, and plug-ins to the Sage 300 application. These are very exciting and are the life blood to the community and were built with the Sage 300 SDK (non-web) in order to ensure compatibility with Sage frameworks and the Sage 300 application.
These applications will need to be re-written for Sage 300’s web screens. The SDK will provide assistance in getting screens developed quicker by creating a Visual Studio solution based upon the structures which Sage 300 uses internally. It will also generate code for a screen or report based upon a business view or a report or a dynamic query.
All tools can only be so much to everyone in order to consider everyone’s base needs while providing functionality that is easy to use. The open sourcing of the SDK will allow the community to extend, enhance and tailor this SDK to their specific needs.
Sage wants this community to be successful in the conversion of their applications to the web paradigm. The open sourcing of the SDK will allow those who wish to contribute to the SDK to do so in a way that not only addresses their needs, but potentially the needs of others as well. With this participation, Sage hopes to have a couple of outcomes:
- Engagement and Excitement
- Get ISVs and Partners involved by allowing an ownership stake
- Generate excitement not only for themselves, but as an example for others to participate and contribute as well
- The community can make the SDK more robust
- Faster Pace to Improve/Enhance/Extend the SDK
- Everyone benefits (Sage too!)
- The SDK potentially gets uncompleted sections and areas to be completed
Folders and Contents
The bin folder contains the assembly (binary) files which have already been compiled and for the SDK utilities and wizards. The folder contains the following sub-folders in order to segregate the files:
The docs folder contains the documentation for the SDK and contains the following sub- folders in order to segregate the documentation:
The help folder contains CHM files
Only the Common and Core assemblies for web screens are documented at this time
The following sub-folder contains help files for the Classic (Desktop) SDK:
The maps folder contains the Visual Studio Code Maps for certain entities, controllers, utilities and helper classes and contains the following sub-folders in order to segregate the code maps:
The patch folder contains any patches which may be required to be applied to:
- Generated solutions
- Generated projects
A README.md file in the patch folder will explain the patch, the reason for the patch and the action to be taken.
The samples folder contains sample projects, which are stand-alone, runnable versions of different screens and reports within the Sage 300 application as well as customization samples. These samples are to provide implementation knowledge.
The README file in the samples folder is important and contains prerequisites for running samples.
The settings folder contains an AccpacDotNetVersion.props file, which is used by the samples to
reference the correct version of the Accpac libraries. Prior to 2018.2, every sample had this file local to the sample. This single version of the files will allow for an easier upgrade between releases as only the single file will need to be modified for correct references.
A generated solution by the Solution Wizard will still contain a local AccpacDotNetVersion.props file .
The src folder contains the source files which comprise the SDK and contains the following sub-folders in order to segregate the source:
A read-only file for displaying the MIT Copyright notice
A read-only version for displaying SDK information (this page!)
A read-only file for displaying Development Partner Program Support information
A read-only version for displaying the current version of the SDK
This section will discuss management and the collaboration model of the repository
The administration of the repository is performed by Sage’s DevOps team located in Richmond BC.
The repository is read-only for anonymous users which means that these users cannot “push” any changes into the repository.
Collaborators are Sage assigned developers and personnel which have write/push access to the repository.
Collaboration Model (Fork and Pull)
In the Fork and Pull Model, any GitHub member (anonymous user) can fork this public repository, which will create another repository where modifications can be applied to the forked repository without the changes affecting the original repository until a pull-request is submitted and evaluated by a collaborator who may or may not merge the changes.
See the article on Forking.
Forking and Branches
This section describes the branches for the repository and the fork procedures for an anonymous user.
While a collaborator uses a forked repository for making changes to the public branches, an anonymous user can only submit changes to the public repository via a pull-request.
Therefore, an anonymous user will:
- Fork the public repository in GitHub
- Clone the fork down to their local machine
- Make changes locally
- Commit to the local repository
- Push everything up to the fork on GitHub
- Submit a pull-request, which is evaluated by Sage Collaborators for inclusion into the public repository.
The development branch, develop, is just what the name implies as it contains the in-progress contents of the SDK that is being worked on for the next release.
Sage collaborators are pushing changes and potentially merging anonymous user pull-requests for the next version of the SDK.
Only Sage collaborators can make changes to this branch
This is the branch to be accessed based upon the question “Get me the in-progress version of the SDK that is not ready for release, but is to be released with the next version of the SDK”.
The current branch, master, is the branch which holds the current release/version of the SDK.
This is the branch to be accessed based upon the question “Get me the current version of the SDK”.
Sage collaborators may push changes to this branch in response to defects or issues either discovered internally or externally. Any changes to this branch are also made in the develop branch
Only Sage collaborators can make changes to this branch
The release branches (i.e. release-2018, release-2018.1, etc.) contains the contents for that particular release/version of the SDK.
When the next version of the SDK is released, the master branch is copied into, for example, the release-2018 branch, the develop branch is copied to master and the develop branch then becomes the basis for the next release.
develop --> master --> release-…
There is only one in-progress version branch: develop
There is only one current version branch: master
There are to be numerous version branches: release-2018, release-2018.1, release-2018.2, etc.
Only Sage collaborators can make changes to these branches
The approval process for changes submitted by anonymous users are performed by Sage collaborators who review any changes for inclusion into the SDK based upon the value added to the SDK for the benefit of all users.
Therefore, it is extremely important to provide as much useful information and rational to support the request being added into the SDK. And, not all requests may be added to the SDK. But, the good news with open source software is that the submitter can still enjoy their version of the SDK which includes the modification being requested.
Depending upon the SDK roadmap, Sage collaborators are working throughout the development cycle on changes and enhancements in the roadmap and will want to potentially include any requests and issues that are discovered and presented by anonymous users.
Sage collaborators review any pull requests or issues submitted to the Repository on a bi-weekly basis.
The SDK follows the release cycle established in the roadmap for the Sage 300 Application. Therefore, new versions of the SDK are released when the Sage 300 Application is released.
Please refer to the README files in the bin\wizards and src\wizards folders for details on topics such as building, installing, uninstalling, and debugging of the wizards.
See the LICENSE.md file