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

Open pdf not in webroot

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

    Open pdf not in webroot

    v12.4.5.4.6 Build 5447.

    Using the "Open a Web Page or PDF File in a Window or DIV" action js I can open a pdf if it is in the webroot. However I cannot open a pdf if it is stored outside the webroot even if I specify the full path like in this pic. The window opens but is blank. Am I missing something?

    aaopenpdf.PNG

    #2
    Re: Open pdf not in webroot

    Are you using IIS? Typically the process that is running the application pool does not have permission to access files outside of the published folder structure.

    Comment


      #3
      Re: Open pdf not in webroot

      No just the standard Alpha WAS. Given you can connect to databases in any folder outside of the webroot, or download files from any folder outside of the webroot, I couldn't figure out why PDF's need to be in the webroot (or a subfolder of webroot). Couldn't find any doco or videos saying so either.

      I'll just have to assume that webroot is a prerequisite and look to store them in a webroot subfolder.

      Thanks, Richard.

      Comment


        #4
        Re: Open pdf not in webroot

        In the browser ( a web page) c: does not exist you must reference the folder Test as in the webroot, on you server it would look like c:\webroot\test\aaa.pdf, to get to it you need https://mydomain/test/aaa.pdf in the browser.
        You also need to allow PDF's to referenced in the Project Properties.2018-11-29_1121_001.png
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #5
          Re: Open pdf not in webroot

          Thanks Pete, yes I get all of that and have it working fine when the file location is c:\webroot\test\aaa.pdf. I hoped that the Open a Web Page or PDF File in a Window or DIV action js would allow pdfs outside of the webroot to be viewed in an alpha popup window. In my case the pdf's are patient records and I know you in particular will appreciate the need for robust security hence my desire to store these outside of the webroot.

          I'll take steps to lock down the webroot subfolders that I will store the pdf's in.

          Comment


            #6
            Re: Open pdf not in webroot

            The Application Server has Directory Browsing turned off as a default, this means the Webroot is the safest place for the PDF as the only way it can only be be accessed is by using the the AA Security requirements via an application authorised to access the file. It should go without having to say it, but I will anyhow, reference to the PDF name should be in a documents table (containing the name and or the folder of the pdf - the name of the pdf would be the table id hosting it, never the Patient Name or MRN) via a relationship to either a visit or patient table, neither of which would contain the identity of the patient. This way the Patient PDF is without an identity unless viewed along with the identity data on the screen as a request is made. This ensures anyone viewing the PDF alone would have no idea what Patient the document relates to.

            Keep in mind if you server gets hacked you must ensure the only way to know what's what on the server, webroot or not, is via the database as it's needed to put all the pieces together.
            Last edited by peteconway; 11-29-2018, 08:19 PM.
            Insanity: doing the same thing over and over again and expecting different results.
            Albert Einstein, (attributed)
            US (German-born) physicist (1879 - 1955)

            Comment


              #7
              Re: Open pdf not in webroot

              Agree with your input around exposing patient ID, in my case though the PDF's are patient clinical notes (including the patient ID) created outside of Alpha and uploaded to be part of my application. Hence the need to ensure they cannot be accessed outside of Alpha.

              As you say, with directory browsing turned off files in the webroot are protected by AA security which is a reasonable solution given this scenario.

              Comment


                #8
                Re: Open pdf not in webroot

                In your system tables the PatientID should not be the same as the PatientID in the PDF, they should be joined by an intermediate table that contains A Primary KeyID and The Providers PatientID in the PDF - Your PatientID should point to that Primary KeyID in a view, there should at least one step between the two identities. HIPAA is tough for a reason, keep the identity of the Patient Identity unknown directly. Cheers.
                Insanity: doing the same thing over and over again and expecting different results.
                Albert Einstein, (attributed)
                US (German-born) physicist (1879 - 1955)

                Comment


                  #9
                  Re: Open pdf not in webroot

                  Yes I understand Pete, have worked in Healthcare IT for 25 years. By ID I meant any identifying information - eg the PDF comes from a 3rd party healthcare provider and contains patient name, address, DOB etc.

                  Exposing a patient name, address, DOB etc is actually worse than exposing a unique patient ID like a hospital's MRN. The MRN doesn't mean anything by itself unless it can be tied back to a patient.

                  HIPAA is of course a US act although many of it's guidelines apply elsewhere.

                  Cheers.

                  Comment


                    #10
                    Re: Open pdf not in webroot

                    How does the 3rd party get the PDF to you?
                    Insanity: doing the same thing over and over again and expecting different results.
                    Albert Einstein, (attributed)
                    US (German-born) physicist (1879 - 1955)

                    Comment


                      #11
                      Re: Open pdf not in webroot

                      Nothing fancy like HL7 interfaces - not an option in this case. Users of my app download the pdf from the 3rd party's portal and uploaded into my app.

                      Comment

                      Working...
                      X