Username not displaying after accepting user input task

RE: Username not displaying after accepting user input task

kishoren0004 — Tue, 23 Jan 2024 14:50:25 GMT

yup. already i did this in form while submitting user form it's working as expected.

Anyway, i really thanks to you investigating on this. And, also thanks to all who are provided your solution.

RE: Username not displaying after accepting user input task

Stefan Helzle — Tue, 23 Jan 2024 14:43:31 GMT

Yeah, that's the issue. The "save into" config in data inputs conflicts with the custom output in data outputs.

In such a case, I suggest to just store the output of loggedinuser() to that field in the saveInto config of the submit button.

RE: Username not displaying after accepting user input task

kishoren0004 — Tue, 23 Jan 2024 14:34:42 GMT

Yes, i think it could be overwriting in Data input tab.

here is the full process model configuration.

Step 1: I have created one main process flow like below and calling "KT Approval Process" in End node as shown in below screen shot

Approval process call configuration.

Step 2: KT Approval Process flow and process variables.

Step 3: UIT input tab

Step 4: UIT Output data tab

Actually, before calling KT Approval Process model already data is getting into(pv-statusIpdate) from existing process model variable(pv- requestData) and same status field is getting updated after UIT task is performed.

RE: Username not displaying after accepting user input task

Stefan Helzle — Tue, 23 Jan 2024 10:53:45 GMT

Now, what's the difference? Could it be that you just overwrite your data modifications as the UIT completes? Please share all the configurations for data inputs/outputs of that UIT.

Keep in mind, that any output data operation at node completion time is performed in a non-deterministic order. Storing tp!owner to a individual field might be overwritten by the "save into" configuration on data inputs.

RE: Username not displaying after accepting user input task

kishoren0004 — Tue, 23 Jan 2024 10:30:50 GMT

Yes, i tested this. i could see task owner name is storing PV in process history tab.

RE: Username not displaying after accepting user input task

Stefan Helzle — Tue, 23 Jan 2024 08:03:39 GMT

I want you to create a separate minimal process. Just a single UIT, no interface. Only store tp!owner to a PV in data outputs. Verify that this works.

Then we can continue with our investigations.

RE: Username not displaying after accepting user input task

Harshit Bumb (Appyzie) — Tue, 23 Jan 2024 05:59:33 GMT

The person submitting the form and the owner of the task will always be the same. You so you can rely on this.
Also, instead of firstName and lastName, use the username. That is unique to every user in the system.

And try using this from next time for better readability.

RE: Username not displaying after accepting user input task

kishoren0004 — Tue, 23 Jan 2024 00:02:31 GMT

Thanks for detailed explanation. however still it is not working even i am using 23.4 platform version.

i used below highlighted code in interface Form and passing value when user submitted the form. it is working fine and value is storing into DB.

But, this is not actually my requirement i need to pass the value from the user input task tab using process variables.

primaryButtons: {
a!buttonWidget(
label: "Approve",
submit: true,
value: true,
saveInto: {
ri!submit,
a!save(ri!requestStatus.status, "Approved"),
a!save(ri!requestStatus.checkerid, {user(username: loggedInUser(), property: "firstName")&" "&
user(username: loggedInUser(), property: "lastName")})
}
)

RE: Username not displaying after accepting user input task

Stefan Helzle — Sun, 21 Jan 2024 15:55:15 GMT

I did a minimal test. Works like a charm. Version 23.4

RE: Username not displaying after accepting user input task

JayaPrakash Ravipati — Sun, 21 Jan 2024 15:15:56 GMT

Strange it's working for me. Can you try with process report and pass the taskId. This method might help

RE: Username not displaying after accepting user input task

kishoren0004 — Sun, 21 Jan 2024 10:04:40 GMT

Yes, i am storing text field only.

RE: Username not displaying after accepting user input task

JayaPrakash Ravipati — Sun, 21 Jan 2024 10:02:20 GMT

Can you check that you are storing in text field or not.

RE: Username not displaying after accepting user input task

kishoren0004 — Sun, 21 Jan 2024 05:18:11 GMT

Hi,

As per suggetion, i have removed script task and i given "tp!owner" in User Input task output tab to store the checkerid value. still same issue gettig

RE: Username not displaying after accepting user input task

kishoren0004 — Sun, 21 Jan 2024 05:15:58 GMT

Yes, this is test process model to investigating the issue. but, still not working properly

RE: Username not displaying after accepting user input task

kishoren0004 — Sun, 21 Jan 2024 05:14:49 GMT

Hi JayaPrakash,

in CDT type is Text and in DB table Varchar as data type. So, i think this is not an issue.

same i used for makerId also it's returning my name right while i am triggering process model. i user in script task "pp!initiator" for makerid storing.

RE: Username not displaying after accepting user input task

Abhay Dalsaniya — Thu, 18 Jan 2024 17:34:09 GMT

Probably the statusUpdate PV is getting overwritten may be during the status update script task or write to DSE if you are saving stored value back to the statusUpdate PV. I never faced any issue storing tp!owner to a PV.

RE: Username not displaying after accepting user input task

JayaPrakash Ravipati — Thu, 18 Jan 2024 16:23:17 GMT

Check whether you are storing in the text field or not because in the target it says "checkerId"

RE: Username not displaying after accepting user input task

Harshit Bumb (Appyzie) — Thu, 18 Jan 2024 15:18:56 GMT

I too was facing this issue when trying to populate the createdBy and modifiedBy . Can be a problem in the latest update.

RE: Username not displaying after accepting user input task

Stefan Helzle — Thu, 18 Jan 2024 15:16:20 GMT

There must be some other issue. I never had any problem storing tp!owner to a process variable.

I suggest to create a tiny test model to investigate on this matter. Once it works, return to this one.

RE: Username not displaying after accepting user input task

kishoren0004 — Thu, 18 Jan 2024 15:08:40 GMT

Yes , i removed other script task after User input task node. even still not getting value for CheckerID.

if you see from below screen shot the task was accepted by other peer colleague. but username not storing into CDT field.

RE: Username not displaying after accepting user input task

Stefan Helzle — Thu, 18 Jan 2024 14:30:53 GMT

Did you remove the assignment from the other node? Not that you overwrite the value later.

RE: Username not displaying after accepting user input task

Harshit Bumb (Appyzie) — Thu, 18 Jan 2024 14:17:38 GMT

Strange. My next solution would be to create a process report.

Pre-requisite - There should only be one task in a process.

Create a process report by process model and select this process model.
Configure it to give outputs like pm!id, pp!id, tp!id, tp!owner etc. and pass the pp!id as a filter when querying data from that report.
When the query executes, it will only give you one dictionary of data and then you can index that dictionary to get the required field (task owner)

Process Report - docs.appian.com/.../Process_Reports.html

RE: Username not displaying after accepting user input task

kishoren0004 — Thu, 18 Jan 2024 13:47:14 GMT

Hi,

Thaks for your reply. i have changed it in User input task node for output tab but still it is not working.

Null value showing in process variables under process details

RE: Username not displaying after accepting user input task

JayaPrakash Ravipati — Thu, 18 Jan 2024 12:40:15 GMT

Hi kishoren0004,

In the output of the user input task configure . using below image it will store the tp!owner.

Duplicate ticket Link

RE: Username not displaying after accepting user input task

Harshit Bumb (Appyzie) — Thu, 18 Jan 2024 12:32:01 GMT

Hi,

I guess this is happening because you have configured it in a script task. tp! domain usually runs in context to the current node and because there aren't any task properties in a script task, it is not returning anything.

Instead of a script task, try adding the same in your User Input Task's output and see if this is giving you any result.