create XML submit to webservice and parse the return XML and put in database
Budget: $30 – $250 USD
A customer will enter a Florida professional code, and a complete license number. This code and number will be part of an XML file/string that will be submitted to an XML service which will then return an XML file/string. This result will need to be parsed to get the first and last names [put in the customer table] and the license state (lic_state), professional code (lic_prof), and license number (license) and the result of the submission (true or false in validated field), and the date-time stamp when the validation, if true, was completed, all put in the [license table] and linked via the cust_id. SEE Excel file attache for professional codes and database tables and fields information.
The customer should be prompted for their state (through a drop down - this will eventually be expanded to other states), and then the professional code (list via drop down based on the professional codes of the state), and the complete license number.
They will click to look up their license number of CEBroker webservices. If the result is valid = true, then the data will be displayed and the user will be prompted to click an accept button, and the data will be entered into the database. And the form below will appear filed in. In the two fields preferred customer first (c_first_name and c_last_name - the way the customer prefers their name to appear on the certificate). the first and last name will be placed. If the customer wants to change them they can, all other fields should be read only.
If the result is valid = false, then a form will appear with fields as follows: legal customer first and last names (names as they appear on the license), preferred customer first and last names (how the customer wants name on certificate), license state (two letter code manually entered), lic_prof (manually entered) and license number manually entered, then the user will be given the opportunity to correct the data, or enter their own data with the caveat that this means that the customer must submit all completion data to CEBroker manually themselves.
Finally, the user should be presented with an ACCEPT button to submit and put info in the database and clear form to allow them to enter another license number. And a REJECT button which will clear the form and allow the user to begin with an empty form.
Here are some links to CEBroker pages to explain the system:
https://help.cebroker.com/en/articles/2169328-reporting-via-web-services-system-to-system
https://help.cebroker.com/en/articles/2169575-xml-license-validation-examples
the code mu st be WELL DOCUMENTED so that more functionality can be added down the road as the business grows. The database queries MUST use PDO and parameterized queries. Errors should be caught and sent to an email (can put made up email address for the code and comment it out, but it MUST work and when the correct email address is put in the code, it should send the all the relevant data that the user entered and the error information the system reported, and send email). This is only when the code fails, not when the XML is returned as not valid.
The customer should be prompted for their state (through a drop down - this will eventually be expanded to other states), and then the professional code (list via drop down based on the professional codes of the state), and the complete license number.
They will click to look up their license number of CEBroker webservices. If the result is valid = true, then the data will be displayed and the user will be prompted to click an accept button, and the data will be entered into the database. And the form below will appear filed in. In the two fields preferred customer first (c_first_name and c_last_name - the way the customer prefers their name to appear on the certificate). the first and last name will be placed. If the customer wants to change them they can, all other fields should be read only.
If the result is valid = false, then a form will appear with fields as follows: legal customer first and last names (names as they appear on the license), preferred customer first and last names (how the customer wants name on certificate), license state (two letter code manually entered), lic_prof (manually entered) and license number manually entered, then the user will be given the opportunity to correct the data, or enter their own data with the caveat that this means that the customer must submit all completion data to CEBroker manually themselves.
Finally, the user should be presented with an ACCEPT button to submit and put info in the database and clear form to allow them to enter another license number. And a REJECT button which will clear the form and allow the user to begin with an empty form.
Here are some links to CEBroker pages to explain the system:
https://help.cebroker.com/en/articles/2169328-reporting-via-web-services-system-to-system
https://help.cebroker.com/en/articles/2169575-xml-license-validation-examples
the code mu st be WELL DOCUMENTED so that more functionality can be added down the road as the business grows. The database queries MUST use PDO and parameterized queries. Errors should be caught and sent to an email (can put made up email address for the code and comment it out, but it MUST work and when the correct email address is put in the code, it should send the all the relevant data that the user entered and the error information the system reported, and send email). This is only when the code fails, not when the XML is returned as not valid.