Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

XML and POST

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Re: XML and POST

    I'll echo/second Steve Wood's last suggestion. When I did this I had a lot of interaction with the programmer at the other end who could tell me

    a) that he was getting my post, and
    b) what was wrong from his point of view

    I would never have gotten mine to work without that help and feedback.
    -Steve
    sigpic

    Comment


    • #32
      Re: XML and POST

      I have also had a problem with http_post.
      Try define the post in a user defined function and see if it works interactively
      If it does maybe we have the same problem

      See my post...
      HTTP_Post problem


      thanks

      Comment


      • #33
        Re: XML and POST

        Hi Steve,

        I have been speaking to their technical support which has been difficult because they do not know alpha.

        But it seems now that I need to submit a header, which you had mentioned above.

        But how do I do that? Do I stick it in to the xml or what?
        Gary S. Traub, Ph.D.

        Comment


        • #34
          Re: XML and POST

          They don't need to know Alpha to know what they need in the xml file. And, they should be able to tell you what they want in the xml header, which is simply the top part of our xml output.

          Here's an example.
          -Steve
          sigpic

          Comment


          • #35
            Re: XML and POST

            Steve,

            Here's what they want:

            Content-Type: text/xml


            So all I do is put that as the first line of the xml?

            Do I enclose in brackets?
            Gary S. Traub, Ph.D.

            Comment


            • #36
              Re: XML and POST

              This is the error response I get back:

              <?xml version="1.0" encoding="UTF-8" ?><api-response><errorCode>1</errorCode><errorMessage><![CDATA[Fatal Error: URI=null Line=-1: Premature end of file.]]></errorMessage><time>1277400343188</time></api-response>
              Gary S. Traub, Ph.D.

              Comment


              • #37
                Re: XML and POST

                and this is the xml that I sent:

                <?xml version='1.0' encoding='UTF-8'?>
                <Content-Type: text/xml>
                <api-request>
                <verification>
                <merchantId>1482</merchantId>
                <merchantKey>5bbwted9j9u9jfk7p1vjabhl</merchantKey>
                </verification>
                <command>add-patient</command>


                <request>
                <patientAccountNumber>0000003293</patientAccountNumber>
                <firstName>Nicole</firstName>
                <middleName></middleName>
                <lastName>Kidman</lastName>
                <address1>6261 Dorman Way</address1>
                <address2></address2>
                <city>Atlantic Beach</city>
                <state>FL</state>
                <zip>32284</zip>
                <phone>(531) 459-6634</phone>
                <email>[email protected]</email>
                <dob>03/15/1976</dob>
                <ssn>111-22-3421</ssn>
                <sex>M</sex>
                <medicalRecordNumber></medicalRecordNumber>
                <familyAccountNumber></familyAccountNumber>
                <policyNumber>XJWH372763</policyNumber>
                <groupNumber>XJWH346253</groupNumber>
                <relationshipType>Self</relationshipType>
                <alternateMemberIdType></alternateMemberIdType>
                <alternateMemberId></alternateMemberId>
                <payerProgramName>Nicole</payerProgramName>
                </request>
                </api-request>
                Gary S. Traub, Ph.D.

                Comment


                • #38
                  Re: XML and POST

                  Any syntax example I find uses double quotes in that first line, not single quotes. Have you tried that or other variations?
                  -Steve
                  sigpic

                  Comment


                  • #39
                    Re: XML and POST

                    Steve,

                    How can I put the double quotes given that the entire line has to be double quoted at beginning and end. I know it can be done, but I have not used the syntax. Could you help with that?
                    Gary S. Traub, Ph.D.

                    Comment


                    • #40
                      Re: XML and POST

                      OK. I figured out the double quotes. But, still does not work. Same error message. Arghhhh!
                      Gary S. Traub, Ph.D.

                      Comment


                      • #41
                        Re: XML and POST

                        The xsd document starts off like so
                        <?xml version="1.0" encoding="UTF-8"?>
                        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
                        <xs:element name="address">
                        <xs:simpleType>
                        <xs:restriction base="xs:string">
                        <xs:maxLength value="128"/>
                        <xs:whiteSpace value="collapse"/>
                        </xs:restriction>
                        </xs:simpleType>
                        </xs:element>
                        .......
                        .......
                        You have not included the line in blue. Since the error message says that the URI line is null, that could be the problem.
                        URI is another name (but slightly different) for URL. The values on the left side of the equal sign may need to be adjusted slightly for your message.

                        I do not have a lot of experience with this kind of thing but the one project I have worked on used SOAP messages and there were lots of examples for each type of transaction. I would have thought that the tech support of the destination would have provided you with an example transaction.
                        Tim Kiebert
                        Eagle Creek Citrus
                        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                        Comment


                        • #42
                          Re: XML and POST

                          Gary - can you ask them for a complete sample/example of what they want to see? Seems like much of what you're doing is shooting in the dark.
                          -Steve
                          sigpic

                          Comment


                          • #43
                            Re: XML and POST

                            Hi guys,

                            Well, I am getting very close. Here is the latest email from their tech support dept:

                            ----------------------------------------------------------------
                            You are getting a valid response from the server which is great. Please make the following changes and resubmit.

                            1- remove the header: <Content-Type: text/xml> from the xml string. This needs to be part of the HTTP headers not part of the body.
                            ----------------------------------------------------------------

                            So, my question now is how do I do what they are asking? I thought the header was supposed to be in the xml string but they are saying no. What do I do?
                            Gary S. Traub, Ph.D.

                            Comment


                            • #44
                              Re: XML and POST

                              Gary,

                              No promises, but I signed up as a merchant with this gateway and will attempt to connect, including adding the headers. I use http_fetch() rather than http_post() because it has a specific property for sending headers.

                              This company is not quite on the ball. Their API document online has the WRONG URL for testing which is why all my tests failed so far. I also asked, and you don't have to test from a SSL site, normal site will do.
                              Steve Wood
                              Join the ALPHA DEVELOPERS NETWORK
                              There is no Cloud. It's just someone else's computer.
                              Web - Mobile - Hosting - Products - Frameworks - Developer Resources
                              AlphaToGo | IADN (100% Alpha Anywhere Websites)

                              Comment


                              • #45
                                Re: XML and POST

                                I've done probably a half-dozen gateways like this. So far I haven't found accurate documentation even once.
                                -Steve
                                sigpic

                                Comment

                                Working...
                                X