INDEX
Documentation Library
Search for information on Hornbill Documentation.
{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}
-
{{resultItem.title}}
{{resultItem.url}}
Have questions about this site?
What is this site?
- This website is Hornbill's new product documentation website and is currently under development.
- It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
- Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
- Please feel free to have a look around at any time.
Why has Hornbill created this site?
- Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
- Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
- We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
- We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
- We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at docs@hornbill.com.
What will this site be good for?
- Community contribution will be facilitated, encouraged, and most welcome.
- High quality documentation, will be kept up to date as rapidly as our products evolve.
- Real-time content search and discovery.
- Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
- Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
- Documentation available in browser as well as printable/viewable as PDF on demand.
- Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
- Almost all publicly available documentation on docs.hornbill.com will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.
What is the timeline for this site?
- We have taken the decision to publish and make available early, there is very little content at this time.
- As and when we have completed/usable documentation, it will be published here.
- We have a host of additional features we wish to add over time, so please watch this space.
- We expect most of our existing documentation should be reviewed/migrated to docs.hornbill.com over the coming months.
- The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Change Reporting, Handling, and Management
- Article
- Mon Oct 02 2023
- 2 minutes to read
- 1 contributors
Change management
Changes are logged in Hornbill Technologies’ own Hornbill instance. The originator obtains sufficient information to complete the Change Request form and obtains the Chief Technical Officer’s or Cloud Service Manager’s approval for the change, taking into account any technical considerations, the costs of the exercise, the potential benefits, etc.
Copies of all change requests are retained to provide an audit trail.
The Cloud service Manager is then responsible for reviewing and/or carrying out a risk assessment to identify potential risks, and their impacts and then to identify and cost the required controls in line with Hornbill Technologies’ risk management framework.
The Chief Technical Officer or Cloud service Manager in consultation with Managers is responsible then for authorizing the change to go ahead. No change implementation work is done until the change is agreed upon. Where required by the risk assessment, fallback procedures or a rollback strategy must be prepared.
If necessary, the testing plan can include a dry run of the change. Where the change is significant, a testing plan, complete with clear acceptance criteria [including business, technical, and load criteria] must be documented prior to commencing the change testing. The individual responsible for testing the change must be briefed.
Once the change is proved to be effective the Cloud service Manager authorizes its transfer to the operational environment, ensuring that business processes are not disturbed and that business continuity plans are updated if appropriate. Authorization may be granted by e-mail as appropriate which should be retained and appended to the relevant Change Request Form.
Test, development, and operational facilities
All testing is conducted in a test environment that is configured for that specific test requirement. It is separated from operational facilities by logical means and requires a password for access, which is issued by the Cloud Team.
All testing for core platform changes is performed in Dev\BETA environments with https://wiki.hornbill.com/index.php/Continuous_Delivery being used to ensure problems are found\rectified before Live.
No data from the live environment is ever used for testing and all test data used by developers is pseudo-generated.
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}