Search Knowledge Base and Documentation
|Support Plan Feature||Standard|
|Phone Support *|
As determined by support technician only.
Level 1 - 1 hour
8 x 5
* Depending on issue complexity, issues may not be resolved in one phone call. For faster problem resolution, iSymphony engineers may also need to replicate certain problems locally and call customers back upon further diagnosis.
*** Number of license technical contacts that may contact iSymphony Support.
While iSymphony attempts to respond to all issues in a timely manner, critical issues i.e. issues that hurt our customers' production applications (Level 1, Level 2) do take priority. "Production" is defined as an instance of iSymphony software actively used by the customer's business.
Level of Severity
Description of Severity
|Response SLA||Standard Support|
Production application down or major malfunction resulting in majority of users unable to perform their normal functions.
8 x 5
Critical loss of application functionality or performance resulting in high number of users unable to perform their normal functions.
Moderate loss of application functionality or performance resulting in multiple users impacted in their normal functions.
Minor loss of application functionality or product feature question.
You can have confidence that our supported platforms are well tested and we will work to correct issues. iSymphony will not provide assistance with configuration in unsupported environments. See the pages below for detailed information on what platforms are supported with iSymphony products:
Supported Platforms are version specific. When checking the documentation, make sure you're viewing the correct version for your platform.
Please read our Security Policies page for information about iSymphony's approach to handling security issues.
*Critical priority is defined as "production application down or major malfunction causing business revenue loss or high numbers of staff unable to perform their normal functions." This includes security issues.
For more detailed information, please visit these policy pages:
iSymphony supports major version releases for two years after the last minor iteration of that version was released (for example, we support iSymphony 2.8 for 2 years after the date it was released). This policy excludes security patch iterations (please refer to the Security Patch Policy).
|3.1.x||June 22, 2017|
|3.0.x||August 17, 2015|
|2.8||May 14, 2015|
|< 2.8||End of Lifed|
Software maintenance covers access to support and software product updates for the corresponding software license. Refer to the End User License Agreement for specific terms of agreement. After the active maintenance period expires, the software will continue to function, but you will no longer be able to access support or software updates (including security patches).
Support is open to system administrators and account holders. End-users will be redirected to a system administrator.
Administering iSymphony products requires a baseline technical skill set, including but not limited to:
Customers are responsible for administering and upgrading their own installations. iSymphony Support will provide guidance on how to do this, but we will not be able to provide step by step maintenance and installation. If you require further assistance with this level of implementation, please consider the following resources:
If you need additional help, contact one us for a paid support quote.
iSymphony products interface with a variety of technologies.
iSymphony will endeavour to provide documentation for integration with these 3rd party applications but does not provide support for 3rd party applications. We are unable to provide support when a failure in a 3rd party application occurs.
iSymphony does not offer support for milestone or beta releases, but we do support release candidates. These will be tracked with the terminology 'BETA' or 'RC' in the version title.
Servlet Containers and Databases are integral technologies; without them iSymphony products cannot function. We provide integration instructions for getting our products to work on supported platforms, but we do not support configurations that differ from the procedures described in our product documentation.
There are many ways to customise and extend our products. We provide source access, APIs, remote interfaces, and tools that allow users to add or change the way the product functions. However, our support for use of these customization options is limited.
If you're working to extend or customize our products and encounter a problem, iSymphony support are happy to help document the problem and relay information to our development teams as follows:
iSymphony does not support direct database INSERT, UPDATE or DELETE queries, as they can easily lead to data integrity problems. If we encounter customisations at this level, we may ask customers to restore data from their last known working state, or to engage an Expert to help recover their instance to a supportable state. If you are confident your UPDATE or INSERT is safe and your change management system is reliable, refer to the specific product's database documentation.
In the event that there are data integrity problems due to defects in a product, iSymphony will provide workarounds or solutions to these problems that may involve SQL queries. We use SQL-based solutions as a last resort.
Using SQL for business intelligence is beyond the scope of iSymphony Support.
Planning for rolling out our products or capacity planning for large instances is better suited for service offerings than iSymphony Support. We will refer these requests internally to the correct department. This includes establishing specific upgrade and deployment plans for existing installations.
See Implementation of New Features Policy for a detailed discussion.