transient value is not getting saved after the process model is debugged

RE: transient value is not getting saved after the process model is debugged

t v s satyanarayana rao — Tue, 20 Jul 2021 16:35:29 GMT

Hi mamathak001,

Hope this might be helpful,

Use a script task ,

create a new custom output , in the expression editor , use this code

Expression: repeat(count(pv!ammenities),pv!list.listingId)

saveInto : pv!ammenities.listingIdFk

Process Flow:

1 Write to DB (list)

2. Script Task (in the Data , create a new custom output and use the above code)

3. Write to DB (ammenities)

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Thu, 15 Jul 2021 11:44:04 GMT

then mapping key value will be empty right in the variable tab right.

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Thu, 15 Jul 2021 10:24:18 GMT

Oh okay, sorry I forgot about that transient. Now I got the issue. The output of the node stores the value that it got from the database as a result of the write operation.

So in your case, the transient value will not be there in the database. Hence null is stored in the CDT.

If your use-case is just to store the primary key in the variable, then I would suggest creating a new output mapping like - index(ac!storedValues,"listingId",null()) & into the respective field of the CDT.

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Thu, 15 Jul 2021 10:09:07 GMT

please don't mind if I am wrong

1.I am not using the transient value in the database it is only up to my database entity as per my requirement

so I am using the XSD code as

<xsd:element name="mappingKey" nillable="true" type="xsd:int">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">@Transient</xsd:appinfo>
</xsd:annotation>
</xsd:element>

2.yes it is done correctly and published with recent version of the CDT only

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Thu, 15 Jul 2021 10:03:02 GMT

No worries! Just a couple of questions from my end:

1. Is the value stored in the database correctly?

2. Is the XSD mapping done correctly in the CDT? Is the datastore published with the recent version of the CDT?

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 15:47:52 GMT

as you suggested I checked the inputs and output tab I unable to find the error will you please check sorry for asking you again

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 11:34:11 GMT

thank you so much, it helped me

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Wed, 14 Jul 2021 07:39:18 GMT

mamathak0001

I think the issue is in your Write to Data Store Entity Node. It's clearly visible that the variable has the value in your script task & after the Write to DSE node the variable value is overridden. I suggest you to check the inputs& outputs tab of this node.

Since the value in your list variable is null, it is being updated as null in your other variable as well.

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 07:33:33 GMT

yes

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 07:31:16 GMT

sorry i forgot to share another screet shot regarding the amenity CDT

this is the code I have written in expression editor, to get the listingId PRIMARY KEY from list CDT and store into the ammenity CDT

a!forEach(
pv!ammenities,
a!update(
data: fv!item,
index:"listingIdFk",
value: index(
pv!list.listingId,
wherecontains(
fv!item.mappingKey,
pv!list.mappingKey
),
null
)

)
)

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Wed, 14 Jul 2021 07:30:39 GMT

Can you please share the other screenshots as well? If you can scroll down, you can see the changes made to the variable by the process

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 07:28:16 GMT

sure

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Wed, 14 Jul 2021 07:27:22 GMT

If possible, can you please share the screenshots of your process history view?

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 07:23:13 GMT

I did not do any update to that particular variable, I updated only the audit fields.

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Wed, 14 Jul 2021 07:18:51 GMT

If you're able to see it first, then the value might have been overridden in the process flow. Have you traversed through all the updates done to that variable?

RE: transient value is not getting saved after the process model is debugged

mamathak0001 — Wed, 14 Jul 2021 07:15:20 GMT

thank you Selvakumar Kumarasamy,I able to see the values in the process history but Y those values r not storing in the process variable may know the reason please

RE: transient value is not getting saved after the process model is debugged

Selvakumar Kumarasamy — Wed, 14 Jul 2021 07:11:39 GMT

Hi mamathak0001,

Did you track the changes in the variable using Process History view? This might help you to find the issue at the process level. Or, if the process history doesn't have this value, then the change may occur in your interface when you click on any submit button.