Save button should get enabled if changes are made to initial submission

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Wed, 27 Jul 2022 21:26:57 GMT

I'm a little confused at the context here, but for times where you need to access an index (numeric position) in an array where you're not 100% sure that index will exist, you should use the index() function with a "default" parameter.

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Wed, 27 Jul 2022 18:26:57 GMT

Yes, I checked, it's not doing the data comparison.so I added the other rule input for original value and used the following code for the interface with multiple child interfaces.It works when I remove indexing for one interface but with fv!index I am getting error stating:

Interface Definition: Expression evaluation error at function a!forEach [line 148]: Error in a!forEach() expression during iteration 1: Expression evaluation error : Invalid index (1) for null value of type SS_Data?list. Any suggestions

local!changesMadeToData:a!forEach(
    items: ri!Data,
    expression: fv!item=ri!OrignalData[fv!index]
  ),

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Tue, 26 Jul 2022 18:34:49 GMT

[quote userid="88894" url="~/discussions/f/user-interface/25302/save-button-should-get-enabled-if-changes-are-made-to-initial-submission/98464#98464"]Whenever I do some changes to data buttons are not getting enabled[/quote]

You should be troubleshooting this by viewing the values of the local variables in the interface designer's "local variables" pane as you enter new values for test inputs, etc. For instance you should be able to see the value of "local!modified" change, not just judging by whether or not the buttons become enabled.

As always, I suggest you start with simpler code that you can understand, and work up from there only once you absolutely understand what's going on. If it helps, see the simplified example code I posted above, which can be copied/pasted into a blank interface designer window and tested with.

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Tue, 26 Jul 2022 18:26:33 GMT

These mistakes happened as I updated my initial code in this thread but in designer, it's correctly spelled. But somehow I feel this logic is not working . Whenever I do some changes to data buttons are not getting enabled. Adding is modified rule input to all nested interfaces will be hard. it will break the correct working from

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Tue, 26 Jul 2022 18:25:59 GMT

Here's a simplified, ready-to-paste example of exactly how this sort of thing can-and-should work, FWIW.

a!localVariables(
  local!name: "Mike",
  local!date: today()-4,
  
  local!data: {
    local!name,
    local!date
    /*ri!datasubset,
    ri!transValue,
    ri!orgValue,
    ri!ageValue*/
  },
  local!originalData: a!refreshVariable(
    value: local!data,
    refreshOnReferencedVarChange: false()
  ),
  local!modified: not(
    exact(
      tostring(local!data),
      tostring(local!originalData)
    )
  ),

  a!formLayout(
    contents: {
      a!textField(
        label: "Name",
        value: local!name,
        saveInto: local!name
      ),
      a!dateField(
        label: "Date",
        value: local!date,
        saveInto: local!date
      ),
      a!richTextDisplayField(
        value: {
          a!richTextItem(
            text: "not modified...",
            showWhen: not(local!modified),
            style: "EMPHASIS",
            color: "SECONDARY"
          ),
          a!richTextItem(
            showWhen: local!modified,
            text: "Modified!",
            color: "POSITIVE",
            style: "STRONG"
          )
        }
      )
    }
  )
)

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Tue, 26 Jul 2022 18:19:52 GMT

Also, this is not the correct name

The actual function name is "a!refreshVariable()"

Additionally the correct spelling of the parameter name is "refreshOnReferencedVarChange" - not "refreshOnReferenceVarChange". The interface designer's built-in error messages should prompt you for these things.

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Tue, 26 Jul 2022 18:16:53 GMT

I'm confused though, because the updated code you've attached here doesn't seem to have any places where local!data and/or any of the 4 RI variables it references, get modified whatsoever. So how are you actually performing changes to the underlying data to verify that local!modified isn't working correctly?

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Tue, 26 Jul 2022 18:04:54 GMT

a!localVariables(
  local!data: {
    
       
        ri!datasubset,
        ri!transValue,
        ri!orgValue,
        ri!ageValue
      
    
  },
  local!originalData:a!refreshVariables(
  value:local!data,
  refreshOnReferenceVarChange:false()
  ),
    local!modified: not(
      exact(
        tostring(local!data),
        tostring(local!originalData)
      )
    ),

    a!formLayout(
      buttons: a!buttonLayout(
        primaryButtons: 
        if(
          ri!isEditable,
          {
            if(
              ri!canSubmit,
              a!buttonWidget(
                label: cons!BUTTON_VAL_SUBMIT,
                style: "PRIMARY",
                submit: true(),
                validate: true(),
                value: cons!BUTTON_VAL_SUBMIT,
                saveInto: ri!buttonAction,
                disabled: 
                if(

                  and(rule!APN_hasValue ( ri!SubmissionDate),local!originalData<>local!modified),
                 false(),
                 true(),
                )

              ),
              {}
            ),
            a!buttonWidgetSubmit(
              label: cons!BUTTON_VAL_SAVE,
              style: if(
                ri!canSubmit,
                "NORMAL",
                "PRIMARY"
              ),
              submit: true(),
              validate: true(),
              value: cons!BUTTON_VAL_SAVE,
              saveInto: ri!buttonAction,
              disabled: 
              if(

                and(rule!APN_hasValue ( ri!SubmissionDate),not(local!modified),
                false(),
                true(),
              )
            )
          },
          {}
        )
      )
      )
    
  )

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Tue, 26 Jul 2022 17:59:06 GMT

Where and how are you saving the updates to the "local!data" variable (and/or its refernced variables)?

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Tue, 26 Jul 2022 17:57:11 GMT

I tried this way and it seems it's not performing data comparison. Is there any other possible way, it can perform a logical comparison and gets enables button with the changes

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Tue, 26 Jul 2022 15:51:28 GMT

This would work except the way you've declared local!originalData, is causing it to automatically update any time any change is made to local!data.

Remember that a!localVariables() variables have a default behavior which assumes "refresh on referenced var change" is TRUE. That means, as you have it written, if you save anything into ri!orgValue (for instance), it automatically refreshes local!data, which by update chaining, updates local!originalData (which you don't want).

Luckily the fix is very simple.

  local!originalData: a!refreshVariable(
    value: local!data,
    refreshOnReferencedVarChange: false()
  )

With the above change in place, your "local!modified" variable should now properly hold its existing value in spite of updates made to the referenced variable.

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Tue, 26 Jul 2022 15:46:25 GMT

a!localVariables(
  local!data: {
    
       
        ri!datasubset,
        ri!transValue,
        ri!orgValue,
        ri!ageValue
      
    
  },
  local!originalData:local!data,
  
    local!modified: not(
      exact(
        tostring(local!data),
        tostring(local!originalData)
      )
    ),

    a!formLayout(
      buttons: a!buttonLayout(
        primaryButtons: 
        if(
          ri!isEditable,
          {
            if(
              ri!canSubmit,
              a!buttonWidget(
                label: cons!BUTTON_VAL_SUBMIT,
                style: "PRIMARY",
                submit: true(),
                validate: true(),
                value: cons!BUTTON_VAL_SUBMIT,
                saveInto: ri!buttonAction,
                disabled: 
                if(

                  and(rule!APN_hasValue ( ri!SubmissionDate),local!originalData<>local!modified),
                 false(),
                 true(),
                )

              ),
              {}
            ),
            a!buttonWidgetSubmit(
              label: cons!BUTTON_VAL_SAVE,
              style: if(
                ri!canSubmit,
                "NORMAL",
                "PRIMARY"
              ),
              submit: true(),
              validate: true(),
              value: cons!BUTTON_VAL_SAVE,
              saveInto: ri!buttonAction,
              disabled: 
              if(

                and(rule!APN_hasValue ( ri!SubmissionDate),local!originalData<>local!modified),
                false(),
                true(),
              )
            )
          },
          {}
        )
      )
      )
    
  )

I tried this code for the interface with multiple child interfaces. buts it's not working.even if data is changed , the buttons are not getting enabled. Any suggestions?

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Mon, 25 Jul 2022 19:17:54 GMT

for any child interfaces where data could also be modified, and which would thus need to trip the "isModified" flag, simply pass in the "isModified" local variable into a rule input in the child(ren), and save into it from any relevant field(s) there.

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Mon, 25 Jul 2022 18:37:28 GMT

if there are nested interfaces, where the above example for data comparison cant be used?

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Mon, 25 Jul 2022 15:07:14 GMT

A simplified example:

a!textField(
  label: "my data",
  value: ri!textField1Value,
  saveInto: {
    ri!textField1Value,
    a!save(
      local!isModified,
      true()
    )
  }
)

RE: Save button should get enabled if changes are made to initial submission

Tan18 — Mon, 25 Jul 2022 14:35:31 GMT

do u have any example to quote?

RE: Save button should get enabled if changes are made to initial submission

Mike Schmitt — Mon, 25 Jul 2022 14:06:26 GMT

For what it's worth, this could have just been a new comment in your existing thread on the same subject. The problem with arbitrarily staring brand new threads is that people seeing it for the first time won't be able to review the past comments and any context they may provide.

RE: Save button should get enabled if changes are made to initial submission

Stefan Helzle — Mon, 25 Jul 2022 13:33:41 GMT

I recommend to not implement one huge form covering all use cases. This becomes complex and hard to maintain.

But, to answer your question, add a local variable "isModified" and default it to false. Then add a a!save() to all fields to update isModified to true(). Then use that status to add some logic to the submit button.

Now, check my first sentence ...