Through our network of 25,000 people in 1,000 laboratories and offices in 100 countries, Intertek provides quality and safety solutions to a wide range of industries around the world. Learn more...
A career with Intertek offers rewarding opportunities to help companies around the world develop products that are used safely by millions of people every day. Learn more...
BMC Software Validation Program Guide Downloads
BMC Service Desk Express Validation Guide (298 kb DOC)
BMC Service Desk Express Validation Guide (157 kb PDF)
BMC Remedy Validation Guide (532 kb DOC)
BMC Remedy Validation Guide (352 kb PDF)
1. The integration note is missing steps required to complete the integration. For example, steps may be missing for configuring the Technology Alliance member's application. A good method for ensuring all the steps are included would be for someone other than the person who wrote the integration note to test the integration note.
2. The steps in the integration note do not correspond with the AR System, nor do they correspond with the Technology Alliance member application. As with reason number one, having the integration performed by someone other than the author of the integration note, increases your chances of passing this test.
3. The integration note does not explain the process for creating AR System objects that are necessary for the integration.
4. Data was not transferred correctly to the AR System. In some cases this could be a result of incorrect configuration in the AR System or the Technology Alliance member application. In other cases, the Technology Alliance member application is transferring user ID's to the Technology Alliance member application that do not correspond with the correct users in the AR System. If it is assumed that specific data (i.e. users) exist on the AR System, the integration must either provide the data, or instruct the user to create the data.
5. The Remedy User client does not start when launched from the Technology Alliance member application. In many cases this is a result of an incomplete or incorrect configuration. Verify that macros, parameters, and login instructions function as documented. The integration note must give the user correct instructions for configuring the Technology Alliance member application to launch the Remedy User tool.
6. The integration note does not explain the steps to set up permissions. If it is necessary to create or modify permissions relating either to the AR System, or the Technology Alliance member application, the integration note should explain the process for making these modifications. An example from the AR System is when ARAdmin needs to be dbowner of a third-party database.
7. The Technology Alliance member application does not start correctly. When starting the Technology Alliance member application from the Remedy User client, the integration note must instruct the user to enter the correct path and syntax for starting the Technology Alliance member application.
8. The integration note refers to existing objects that are not available. The objects referenced in the integration note need to exist in the basic AR System or be provided in the distribution. Document sample objects and explain changes in detail.
9. The integration note contains incomplete system requirements. Any hardware necessary for the integration must be included in the integration note. Also versions specified are not correct according to the product supplied. It is important to indicate ALL system requirements prior to submission.
10. The integration note does not explain the steps to configure the application. For completeness, configuration on both the AR System and the Technology Alliance member's application must be explained in full detail.
