sections in the article
Inriver's ambition is to collaborate with our partners in providing our customers as safe and secure a PIM system as possible. With that in mind, inriver is introducing improved information on our Community to help implementation partners ensure quality, optimise implementations, and avoid pitfalls.
Â
Through quality-assured knowledge, partners can now find additional Notice where inriver provides clarity on how to implement in a stable and well-performing way. These also highlight bad practices and unrecommended development methods so that implementation partners can avoid issues from the outset. 
This information is also introduced in our academy to ensure that quality is in sync with the guidelines and to keep customer satisfaction as high as possible.
How will Implementation Standards guide you?
Notices will be added to our articles to highlight important areas where other implementations have struggled in the past. This will help you make the most out of your current implementation, and we encourage you to review your previous implementations. For example, you may encounter a warning about a method that you have used extensively in the past. By reviewing your previous implementations, you can help your customer improve the solution by making it faster, more stable, and incorporate any new features added after the implementation was completed.
The different Notices we use, and what they mean
We use three different Notice types in our community articles. Some of them are considered as information or guidance and others will warn you against using a specific implementation method. We either know from experience that they can cause complications, or we have known items in our backlog preventing use of certain implementation methods (avoid now instead of making urgent changes later).
Â
Methods you must not use when implementing or configuring inriver. This is a warning that the approach can cause severe issues or errors during or after implementation that negatively impact customers.
Ignoring a warning is expected to negatively impact your customer either at the time of implementation or later, as the solution provided might stop working at a later date or can cause severe performance issues when scaling up a solution. Using such approaches in a design is not supported.
Â
Proceed with caution if considering this method in your solution as there are specific design and usage considerations that must be taken into account to avoid implementation or later issues.
Extensive use of these methods have the potential to cause severe issues in your implementation or cause performance issues when scaling up a solution such as moving from a test to production environment.
If such a method is the only available approach that achieves your goal, you must first consult with inriver for guidance, as this approach has a high risk of negatively impacting customers.
Â
These notices contain supporting information and guidelines to implement a function successfully, with the Expert Services team available to also assist with your solution.
You will find implementation guides and links to other Community articles to support your projects and decisions as you grow with the inriver solution.
When working on large scale projects, we always advise you to contact inriver to assist with your solution.
Optimize your implementations
We recommend you read our articles below on how you can optimize your implementations by using our implementation standards. The articles are categorized by topic and we have helped you by linking to articles on the Community where in-depth reading about how the various components work can help you succeed with your implementations.
Optimizing inriver performance
Implementation Checklist
Make sure your implementation follows the Implementation Standards by using our Implementation Checklist, which is based on the Implementation Standards we've described in the articles above. By understanding the Implementation Standards and then using the checklist to ensure that the standards are followed both during the project and at launch, you are one step closer to a successful implementation with future-proof scalability, and where your customer remains satisfied.
Implementation checklist – inriver community
Â
Comments
0 comments
Please sign in to leave a comment.