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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Submitting a UX when fields are dirty

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Submitting a UX when fields are dirty

    I've got a web app UX that I want to be able to be submitted with certain specified fields dirty. Anyone know how to do this?
    Tags: None
    #2
    Re: Submitting a UX when fields are dirty

    Put something like this in the Dialog Validate server-side area.
    e.dirtyColumns = e.dirtyColumns + crlf() + "YOUR_FIELDNAME" + crlf() "ANOTHER_FIELD"
    this will set the fields to "dirty"

    Now on the other hand, if your trying to CLOSE the UX with the field dirty and not get a warning thats a different answer.
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment

      #3
      Re: Submitting a UX when fields are dirty

      yes, that's what I'm trying to do. Close with certain fields dirty and not get a warning.

      Comment

        #4
        Re: Submitting a UX when fields are dirty

        If you are opening the UX from another using the action javascript "open a UX component" in a window to do it you will want to uncheck the Warn if UX is dirty option - that will get rid of it in that case. How are you opening this UX? is it in a tabbed UI pane? Is it a list control? Is it on a page in a tabbedui pane? Is it just on a page by itself?
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment

          #5
          Re: Submitting a UX when fields are dirty

          Opening from a Grid. Yes, I can uncheck the 'Warn' box, but I want it to warn on all except a few specified fields.

          Comment

            #6
            Re: Submitting a UX when fields are dirty

            Just opening a UX from a Grid.

            Comment

              #7
              Re: Submitting a UX when fields are dirty

              Ok so you will want to ignore those fields, that's a bit different and can be done but it is definitely more custom and you will need to figure out WHEN they should be dirty and saved vs when you don't care if they are since it's ONLY certain fields that you want a warning for. Perhaps a better way would be to turn the warning off for ALL fields as suggested BUT make certain fields required via the validation rules. This would allow people to just exit out if they want to but if they submit the UX they will have to have filled out the fields that you really care about - the rest wouldn't matter.
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment

                #8
                Re: Submitting a UX when fields are dirty

                Also - you really need to say if your CLOSING the UX or Submitting the UX - Closing it means your not saving crap so all you want to do is exit and thats what the check box untick will do. If your submitting you wouldn't hit "Close" you would hit "Submit" and then there wouldn't be an issue - I still feel like I am missing something here.
                NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                Comment

                  #9
                  Re: Submitting a UX when fields are dirty

                  The scenario is an inventory list.

                  The Grid contains the list of inventory.
                  The UX opens from the Grid which edits the current record. Submitting the UX saves back to the grid.
                  There is a Submit button to save and a Close button to close if they didn't make any changes. But the Close button also validates the fields to make sure all changes have been saved.

                  In this UX is a section that you can email a link to a customer. I would enter their email address and a short message to send with it. I send the email. These fields are not saved anywhere. Don't want them saved. Ever. So if someone opens the UX to view the product, emails the link, then hits Close, the "You first must save your changes..." pops up. I want it to just close, unless some of the other fields were edited. Thus why I need to specify WHICH fields are OK to be dirty or WHICH fields are OK to not be.

                  Does that explain it more?

                  Comment

                    #10
                    Re: Submitting a UX when fields are dirty

                    can you make them unbound by removing the data binding and see if it works?
                    thanks for reading

                    gandhi

                    version 11 3381 - 4096
                    mysql backend
                    http://www.alphawebprogramming.blogspot.com
                    [email protected]
                    Skype:[email protected]
                    1 914 924 5171

                    Comment

                      #11
                      Re: Submitting a UX when fields are dirty

                      They're not bound to anything. Don't want to save them.

                      Comment

                        #12
                        Re: Submitting a UX when fields are dirty

                        I figured out a solution. I put a Submit action into the Email button. Even though it doesn't save anything, it "submits" the UX so the unbound fields appear NotDirty to the actual Close button.

                        Comment

                          #13
                          Re: Submitting a UX when fields are dirty

                          i am glad that you found a solution.
                          there is a property " warn if dialog is dirty in the pop up window before close" in the grid. if you uncheck that property the pop up won't come, but again it applies to all fields. i am not sure that is desirable in your case where you want that dialog to do some functions.
                          thanks for reading

                          gandhi

                          version 11 3381 - 4096
                          mysql backend
                          http://www.alphawebprogramming.blogspot.com
                          [email protected]
                          Skype:[email protected]
                          1 914 924 5171

                          Comment

                          Previous template Next
                          Working...
                          X