how to pass a cdt through an interface

RE: how to pass a cdt through an interface

Chris — Mon, 24 Aug 2020 17:12:21 GMT

Great! 🙂

RE: how to pass a cdt through an interface

kevinr0001 — Mon, 24 Aug 2020 16:26:11 GMT

it works! thank you guys so much!

for anyone checking on this later the bug was solved by making sure that there were no duplicate saves.

here the code that works for anyone that is checking later

 buttons: a!buttonLayout(
    primaryButtons: {
      a!buttonWidget(
        label: "Approve",
        icon: "check",
        value: true,
        saveInto: {ri!userInformation.supervisorDecision,
        a!save(ri!userInformation.supervisorsDecisionDate,now())
          },
        submit: true,
        style: "PRIMARY"
      )
    },
    secondaryButtons: {
      a!buttonWidget(
        label: "reject",
        icon: "exclamation-triangle",
        value: false,
        saveInto: {
          ri!userInformation.supervisorDecision,
          a!save(ri!userInformation.supervisorsDecisionDate,now())
        },
        submit: true,
        style: "DESTRUCTIVE",
        validate: false
      )
    },
    showWhen: or(
      isnull(
        ri!readOnly
      ),
      not(
        ri!readOnly
      )
    )
  )

RE: how to pass a cdt through an interface

Mike Schmitt — Sat, 22 Aug 2020 15:55:14 GMT

[quote userid="2401" url="~/discussions/f/general/19455/how-to-pass-a-cdt-through-an-interface/76103"]Additionally, remove the "a!save(ri!userInformation,ri!userInformation)" in both submit buttons. [/quote]

Shoot, I missed the fact that that was still there - it was the first save previously i think, so wasn't looking at the end of the save list. luckily i think in this case it wouldn't be causing anyhing to get lost since the a!save()s are executed in order, so it would just be (redundantly) saving its current value back into itself.

RE: how to pass a cdt through an interface

Chris — Sat, 22 Aug 2020 15:29:07 GMT

As Mike notes, please expand the userInformation variable in the Rule Inputs area to verify data is saving on the form, when you click your buttons in /design. Additionally, remove the "a!save(ri!userInformation,ri!userInformation)" in both submit buttons. Once we can confirm data is saving on the form we can move to monitoring the process instance to review variable updates in Process History.

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 21:44:26 GMT

So in the Rule Inputs section (which you've pictured the left half of in your second screenshot), what is the value contained in ri!userInformaton after you click either button? That's where you should be looking first to make sure the saveIntos are working.

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 20:58:58 GMT

so:

and ?

thanks for looking at this with me 😀 Have a great weekend! talk to you Monday

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 20:51:21 GMT

That should be the first place you test/troubleshoot.

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 20:50:42 GMT

I'm specifically asking you to confirm the values you see in the rule inputs panel when in the interface designer, though.

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 20:49:38 GMT

my whole problem is that clicking the submit/ reject does not affect the PV's . I cannot understand why

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 20:45:25 GMT

This all looks basically right unless I'm missing a subtle detail again. When on the form designer, can you confirm that clicking "approve" and "reject" sets the value of ri!userInformation as you're expecting? What does the value end up being when you view the PVs in the running instance after submitting?

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 20:45:19 GMT

I hope my screen shots answered your questions,

yes I am saving into that pv either if I approved or rejected

Thanks guys!

it is late Friday... Have a great weekend 😉,

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 20:38:48 GMT

here is the output tab

here are my a!saves

RE: how to pass a cdt through an interface

Chris — Fri, 21 Aug 2020 20:29:56 GMT

Can you confirm what your interface a!save()'s are now, and a screen shot of the node's Output tab?

In the first screen shot, the input variable is ri!User_Data, however the a!save()'s are using ri!GFIM_User_Access_User_Information.

In the second screen shot the variable name has changed to "userInformation".

Is this input being saved into within any other interface fields, or only on the Approval button save?

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 20:26:43 GMT

thanks for sticking with me Mike, I am still not seeing any changes to my PV

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 20:24:46 GMT

thanks I removed it and the other redundant things but it still does not save anything.

like there is no difference to the variables before and after

here is my process now

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 19:42:58 GMT

The first thing you should do is resolve the issue Chris pointed out below. After that, let us know whether you're still not seeing changes within the PV - i'm guessing this was the primary issue.

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 19:19:00 GMT

I am unable to see any of the variables in the process that I was changing in the form.

Specifically it is an approval form and it does not change the boolean to true. when I hit the submit button

RE: how to pass a cdt through an interface

Chris — Fri, 21 Aug 2020 16:50:33 GMT

Yep! From overwriting my own data on a few occasions, I can confirm the Output expressions fire last and will essentially reset any of the Inputs if there is a conflict. Been there, done that! :)

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 16:27:45 GMT

Oh yeah, good catch - I didn't even notice the interface output node was referencing the PV in saving the PV back into itself. That said I'm not clear (without testing) whether the save-out to the PV from the Input tab would happen before or after the Output save executes... but in any case there's no need for such confusion since there's a potential overwrite and/or race condition.

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 16:20:11 GMT

[quote userid="49829" url="~/discussions/f/general/19455/how-to-pass-a-cdt-through-an-interface/76077"]I am unable to see any of the values that I was populating in that form.[/quote]

Can you expand on this? Under what circumstances are you trying / expecting to see values that you populated in that form? Are you saying you don't see the values getting written to the DB table after the process completes, or something else?

RE: how to pass a cdt through an interface

Chris — Fri, 21 Aug 2020 16:18:54 GMT

In this case your Interface Output save for pv!User_Data is overwriting your interface updates. Only the Save Into from the Input tab is correct, you will want to delete the Output Save Into, as this is overwriting with the pv! value (what the variable was set at prior to the form save). If you had used ac!User_Data in the output this would function correctly but be redundant.

RE: how to pass a cdt through an interface

kevinr0001 — Fri, 21 Aug 2020 15:57:27 GMT

Thanks for the reply Mike,

I am unable to see any of the values that I was populating in that form.

It seems like the write to data store is not functioning at all.

RE: how to pass a cdt through an interface

Mike Schmitt — Fri, 21 Aug 2020 15:48:17 GMT

A few redundancies here.

The first line of your saveInto does literally nothing. It saves the current RI value back into itself - which will have net zero effect. You can remove this as far as I can tell. Keep lines 2 and 3, these should work correctly for what you're seemingly trying to do.

You save the value from the node Inputs tab into a PV, and then you save it into a PV in the Outputs tab. This is also unnecessary - you only need to do it in one place or the other. Usually in cases like this it's easiest to just do it from the Inputs tab, unless you need to do some sort of transformation to the CDT upon form submission, in which case you should only use the Outputs tab (i don't think this applies to you though). NOTE: per what Chris pointed out below, even if you did want to save the CDT value in the Output tab, the data output should reference ac!User_Data instead of pv!User_Data.

Your Write to Data Store is configured correctly.

What exactly is the issue you're having? Despite the redundancies I noted, I don't spot any errors that would (necessarily) prevent proper function.