Hello all. I am starting this blog to provide the TRIRIGA user community with insight into how to help improve your experiences with the TRIRIGA Support team.
Today, I would like to talk about your TRIRIGA environments. Most companies create 3 different environments, development, test/uat, and production. Having worked with enterprise application similar to TRIRIGA, I have found that another environment should be set up specifically to verify that a particular issue is due to something in the base product versus something in a custom object. If at all possible, companies should consider setting up an As Delivered environment. This environment should not contain any customizations of any kind and should be used by the corporate internal support team to validate whether an issue can be replicated without the customizations in place.
With this environment in place, customers can provide unambiguous steps to replicate to the support team. This will, in turn, lead to a faster turnaround to the development team for remediation. Ultimately, this should decrease the time it takes to get a resolution to a problem.
If you have concerns regarding the resources required to set up this As Delivered environment, consider that this will not be used to address questions of performance. Performance questions really require the environment to be as close to your production environment. This As Delivered environment can be small in size and can even be set up on something as simple as a laptop computer. Keep in mind, the purpose of this environment would only be to identify whether an issue is in the base code and not in anything that has been customized. This environment would be especially suited for finding issues that are at the platform level as that is code that really cannot be modified by the customer.