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

Reopen current ux after save

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

    Reopen current ux after save

    I've got a tabbed ui that has a UX open in it. I have some custom code in onDialogInitialize to specify the key, then a Populate Dialog from Tables Load Server Side action to open the record when it's opened. (The record changes on each open). On my afterDialogValidate, I've got the normal Save Data Server Side Action. In that, there are a few options for the After Submit Action. There is enter another record (which gives me a blank ux), Redirect to a new page, or Edit current record. I basically need a way to just re-run the entire UX. Start over from scratch. What is the best way to accomplish this?

    #2
    Re: Reopen current ux after save

    I think you have to first decide where "Scratch" is...in other words where are you when you "open it" ? Sounds like you would have to close the pane and reopen it since it populates on initialize. For some reason, I think this is more of a logical flow issue - if the record changes every time it is opened.
    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: Reopen current ux after save

      It's a telemarketing app that pops up a new record each time the ux is opened. A new record each time is desired functionality. Right now, I have the code in onDialogInitialize, but have also tried the code under onDialogExecute. I think I may be coming to the same conclusion. I think I might have to close the pane and open a new one each time. I'm going to be playing around with Synchronize functions today and see if I can get it working that way.

      Comment


        #4
        Re: Reopen current ux after save

        Would a button click (New Record) after you close the screen work?

        Comment


          #5
          Re: Reopen current ux after save

          So here's what I seem to have got working:

          1) I turned the code to get the next Primary Key into a function and stuck it into Xbasic functions. It takes some data to get the key (not important), and returns a number (the primary key)
          2) onDialogInitialize: Runs Populate Dialog from Tables (using the key returned from step 1)
          3) Dialog get's populated
          ... (Use info in dialog, edit, etc...)
          4) Submit!
          5) afterDialogValidate: Runs Save Data server side action. Here are the important steps. e.javascript = "" (removes the action from the Save Data SSA), then I run my getNextKey function, which then runs another Populate Dialog from Tables SSA.

          Step 5 is the important one. I basically give the UX new keys and it effectively resets it back to the beginning. I think I may need to add in a {dialog.object}.resetForm() in there as well, because some fields are still showing the previous values.

          Comment


            #6
            Re: Reopen current ux after save

            afterDialogValidate: Runs Save Data server side action. Here are the important steps. e.javascript = "" (removes the action from the Save Data SSA), then I run my getNextKey function, which then runs another Populate Dialog from Tables SSA.
            confusing at least to me.
            are you saving the data or simply this is an exercise where you change the data and clean up the ux/dialog and start with a different record?
            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


              #7
              Re: Reopen current ux after save

              So this Server Side Action
              2017-07-14 10_03_01-AlphaDev.png
              Creates some Javascript that get's put into e.javascript. I don't want any of that to happen, so that's why I set e.javascript = "". Yes, the data is saved, but then I want to bring up another record to display.

              Comment


                #8
                Re: Reopen current ux after save

                Code:
                function afterDialogValidate as v (e as p)
                
                'This saves any changes to the prospect, it also saves notes
                ExecuteServerSideAction("Save Data::Save Data")
                
                'This resets any non-data-bound fields back to defaults & also stops the action specified in the "Save Data" Server side action
                e.javascript = "{dialog.Object}.resetForm(false);"
                'This get's the next Primary Key
                dim prospect as n = getNextKey(Context.Request.Variables.territory)
                'This reloads all the data-bound fields with the new Primary Key record.
                ExecuteServerSideAction("Populate Dialog from Tables::LoadNext")

                Comment

                Working...
                X