User Tools
development:applications:ebonding:howto:commonissues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:ebonding:howto:commonissues [2017/02/08 12:49] – bcoffey | development:applications:ebonding:howto:commonissues [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== Common Issues ===== | ||
| + | Author : Brian Coffey | ||
| + | \\ Date : 2017-02-07 | ||
| + | |||
| + | |||
| + | Below are a list of common issues the support team may face with eBonding. These includes the actual issue, the cause and the resolution | ||
| + | |||
| + | |||
| + | ==== No form field value in the Ticketer Ticket ==== | ||
| + | |||
| + | Cause: The form fields are populated using CustomerMessageMappings which link an XPath to and errigalKey (i.e the form field database name), therefore either the errigalKey or the XPath location within the XML is incorrect | ||
| + | |||
| + | Solution: CustomerMessageMappings can be updated via the eBonding GUI. Firstly you need to investigate which value is incorrect on the mappings, the logs will help with this as they print out information obtained from the incoming message. Once the problem is found the CustomerMessageMapping can simply be edited with the correct information. If a new CustomerMessageMapping needs to be created make sure it links correctly with parent and children. | ||
| + | |||
| + | |||
| + | ==== REPLACE_WITH still present in response message sent to customer ==== | ||
| + | |||
| + | Cause: This issue is caused by not having a CustomerMessageResponseMappings assigned to a CustomerMessageResponseTemplate/ | ||
| + | |||
| + | Solution: The particular CustomerMessageResponseTemplate/ | ||
| + | |||
| + | ==== INJECT_WITH still present in response message sent to customer ==== | ||
| + | |||
| + | Cause: This issue is caused by not having a CustomerMessageResponseSubTemplate assigned to a CustomerMessageResponseTemplate for that INJECT_WITH statement. | ||
| + | |||
| + | Solution: The particular CustomerMessageResponseSubTemplate can be assigned the correct CustomerMessageResponseTemplate via the GUI. Please note some subTemplates use the REPLACE_WITH rather than INJECT_WITH. | ||
| + | |||
| + | |||
| + | ==== Value in response sent back to customer is blank ==== | ||
| + | |||
| + | Cause: This issue is caused when the CustomerMessageResponseMapping being used has the incorrect 'With This' value. If this value doesn' | ||
| + | |||
| + | Solution: The 'With This' value of the CustomerMessageResponseMapping can be updated via the GUI. If a new CustomerMessageResponseMapping needs to be created make sure it links correctly with parent and children. | ||
| + | |||
| + | ==== Access Denied - Invalid Credentials Exception ==== | ||
| + | |||
| + | Cause: This occurs when the incorrect basic authentication username and password are set. | ||
| + | |||
| + | Solution: Check password safe for the correct username and password and ensure the customer in question has these values for ' | ||
Page Tools
