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 UX as an alternate editing view for current record

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

    Open UX as an alternate editing view for current record

    From a dialog component (UX1) with a repeating section, i am opening a dialog component (UX2) to edit the the current row in UX1
    the action javascript "Open UX as an alternate editing view for current record" seems to be the right tool to achieve it, passing the values entred into the parent UX, nevertheless when UX2 opens it does not get populated with the data in UX1

    is there a video on using this action JS from UX to US. there are some from a grid to UX, and I know there are some differences between both
    Is there something i am missing here ?

    #2
    Re: Open UX as an alternate editing view for current record

    Questions
    • Just curious. Why do you need an additional entry screen?
    • Typically a repeating section is used for data input in a list, similar to a spreadsheet.
    • Why do you need to have single record input screen for a record, when uses are already in edit mode?
    • I must assume that you want to a "more detailed" input screen.
    • By this I mean are you allowing the user to input additional values, not shown in the repeating section?

    Another Approach
    In this vein, have you tried displaying the data in a read only list control, and include a detail section to edit the selected record?
    Last edited by westridge; 02-28-2015, 03:32 PM. Reason: Grammar

    Comment


      #3
      Re: Open UX as an alternate editing view for current record

      I considered entering data in the repeating section, but there are to many controls to be displayed in the horizontal layout ( it doesnt look OK), so i would rather have a child UX to edit that one record, and I would also display in the child UX a pdf file in a panel card related to the selected record

      i am also trying something else :

      - javascript action "open UX component"
      - in the event onrenderComplete read each control from the parent UX, and pass them to the child UX

      var pObj = {dialog.Object}.getParentObject();
      if (pObj){
      var row = pObj._selectedRow;
      setTimeout(function(){
      var tarefa = pObj.getValue('TXTSEGUIMENTO:row');
      // other controls to read in here

      {dialog.Object}.setValue('TXTSEGUIMENTO', tarefa);
      },1000);
      }

      - after editing the record in the child UX, i want to pass the values back to parent UX, but it does not seem easy to pass the values from the child UX wich is unbound to parent UX wich is bound.


      I will consider your list control option
      thanks for your help

      Comment


        #4
        Re: Open UX as an alternate editing view for current record

        I would use the Open a UX Component. In the child UX... client-side onRenderComplete event...

        Code:
        var pObj = {dialog.Object}.getParentObject();
        var currRS = pObj.getRepeatingSectionActiveRow('REPEATINGSECTION_1');
        
        var sysType = pObj.getValue('SystemType:'+currRS);
        var acctNbr = pObj.getValue('AccountNo:'+currRS);
        
        {dialog.Object}.setValue('SystemType',sysType);
        {dialog.Object}.setValue('AccountNo',acctNbr);
        And on a button in the Child UX...

        Code:
        var pObj = {dialog.Object}.getParentObject();
        var currRS = pObj.getRepeatingSectionActiveRow('REPEATINGSECTION_1');
        
        var sysType = {dialog.Object}.getValue('SystemType');
        var acctNbr = {dialog.Object}.getValue('AccountNo');
        
        pObj.setValue('SystemType:'+currRS,sysType);
        pObj.setValue('AccountNo:'+currRS,acctNbr);
        
        {dialog.Object}.closeContainerWindow(this);
        You don't need to get the parent Object again... you could do that once and just save it. But... this is simple and straight-forward.

        Comment


          #5
          Re: Open UX as an alternate editing view for current record

          David,
          I was able to pass the values from parent ux to child UX, and after editing back to parent again
          I just runned into 2 problems :

          the first time the Child UX opens no values are being passed, only subsequent times
          I also had to change the code into the onSynchronizeDialog

          //READING THE VALUES FROM PARENT UX
          var pObj = {dialog.Object}.getParentObject();
          var row = pObj.getRepeatingSectionActiveRow('REPEATINGSECTION_2');

          var tarefa = pObj.getValue('TXTSEGUIMENTO:'+row);
          var po =pObj.getValue('PESSOAO:'+row);
          var pd =pObj.getValue('PESSOAID:'+row);
          var dataL =pObj.getValue('DATALIMITE::'+row);
          var ck1 =pObj.getValue('CHECKBOX1:'+row);
          var ck2 =pObj.getValue('CHECKBOX2:'+row);
          var aviso =pObj.getValue('AVISO:'+row);

          {dialog.Object}.setValue('TXTSEGUIMENTO', tarefa);
          {dialog.Object}.setValue('PESSOAO', po);
          {dialog.Object}.setValue('PESSOAID', pd);
          {dialog.Object}.setValue('DATALIMITE', dataL);
          {dialog.Object}.setValue('CHECKBOX1', ck1);
          {dialog.Object}.setValue('CHECKBOX2', ck2);
          {dialog.Object}.setValue('AVISO', aviso);
          the last line of code in a button in the child UX does not close the UX, and I have to use the top right inbuilt alpha button, but even then not without getting a message saying I should submit the data
          the first inline javascript :


          var pObj = {dialog.Object}.getParentObject();
          var row =pObj.getRepeatingSectionActiveRow('REPEATINGSECTION_2');
          setTimeout(function(){
          var tarefa = {dialog.object}.getValue('TXTSEGUIMENTO');
          var po ={dialog.object}.getValue('PESSOAO');
          var pd ={dialog.object}.getValue('PESSOAID');
          var dataL ={dialog.object}.getValue('DATALIMITE');
          var ck1 ={dialog.object}.getValue('CHECKBOX1');
          var ck2 ={dialog.object}.getValue('CHECKBOX2');
          var aviso ={dialog.object}.getValue('AVISO');

          pObj.setValue('TXTSEGUIMENTO:'+row,tarefa);
          pObj.setValue('PESSOAO:'+row,po);
          pObj.setValue('PESSOAID:'+row,pd);
          pObj.setValue('DATALIMITE:'+row,dataL);
          pObj.setValue('CHECKBOX1:'+row,ck1);
          pObj.setValue('CHECKBOX2:'+row,ck2);
          pObj.setValue('AVISO:'+row,aviso);
          },3000);
          the second inline javascript :

          {dialog.Object}.setDirty();
          setTimeout(function(){
          {dialog.object}.submit(false);
          },3000);

          {dialog.Object}.closeContainerWindow(this);
          do You have an idea the reason of these 2 issues?
          Last edited by cpampas; 03-01-2015, 08:03 PM.

          Comment


            #6
            Re: Open UX as an alternate editing view for current record

            if if I use the code to read the values from the parent UX, also on the onRenderComplete, than the values are passed the first time aswell

            the first time the Child UX opens no values are being passed, only subsequent times
            I also had to change the code into the onSynchronizeDialog

            //READING THE VALUES FROM PARENT UX
            var pObj = {dialog.Object}.getParentObject();
            var row = pObj.getRepeatingSectionActiveRow('REPEATINGSECTION_2

            but, I am still struggling with closing the child ux from a button with this code, even with the setTime function , looks like it still is submiting the UX

            {dialog.Object}.setDirty();
            setTimeout(function(){
            {dialog.object}.submit(false);
            },2000);

            {dialog.Object}.closeContainerWindow(this);

            Comment


              #7
              Re: Open UX as an alternate editing view for current record

              Hi,
              just in case someone bumps into the same issue of not closing the ux after submitting data.
              I came up with this, at risk of not being an efficient way to do it, but it works:


              in the button that submits the data :

              var privateVariable = "ja";
              ja="S"

              {dialog.object}.buttonClick('BUTTON_SUBMIT');

              in the server side event, afterDialogValidade / saveSubmittedData / afterSave succeeced Javascript

              if (ja=="S"){

              var ele = {dialog.Object}.getPointer('BUTTON_SUBMIT');
              setTimeout(function(){
              {dialog.Object}.closeContainerWindow(ele);
              },2500);

              ja=""

              anything that should be changed here ?
              thanks

              Comment

              Working...
              X