how can I prepopulate the fields of current task with previous completed task details

Question

how can I prepopulate the fields of current task with previous completed task details?

Mike Schmitt · Accepted Answer

sireesha said: My requirement is how can I prepopulate the form details of previously completed tasks in the current task. 
 My assumption is that "the current task" is a subsequent task in the same process instance as the "previously completed task". Assuming this is true, then what I said above, and what Romulo demonstrated in their series of screenshots above, is applicable to your case. That is, the earlier task(s) will need to be configured to save their data / changes into the Process PV(s), and then subsequent task(s) will need to be configured to pass any necessary value(s) into their Task Forms. 
 The necessary configuration for this is of a fairly basic level in terms of learning Appian development, so I'd recommend you complete the Appian-supplied training course(s) on Process Model design as these concepts should be covered there. Have you explored any of the available online courses yet?

Rómulo · Answer

Hi sireesha , Yes, but please bear in mind the following: -Diferrent Processes: After see your last comment to Mike, and assuming that you have data store/database already configured, I may say that what you really want is populate a form with data which was previously stored (different process). So when a user instance a new task from a new process you want to display that data if exist (Name, Age, Country, Mail). To achieve this, you have to create a way to retrieve that data in a local variable when it loads the interface. For instance you can use a expression rule to retrieve that data: To know how to create a query entity rule, visit this page: https://docs.appian.com/suite/help/23.1/fnc_system_a_queryentity.html -Same Process: If the case is different tasks in the same process, you have to follow my first comment. Let us know if you made it :) , R&oacute;mulo

Rómulo · Answer

You're welcome.

This will retrieve all the fields:

For more info, please check: https://docs.appian.com/suite/help/23.1/fnc_system_a_queryentity.html

Also sireesha, please vote up and verify the answer as correct, in order iit will be helpful for other user in the community.

Thanks

Rómulo

Sanchit Gupta (Xebia) · Answer

This is not how this should be configured. 
 You need to save the result of expression rule called inside value parameter in a localVariable and then use that variable in value and saveInto also to store the updated value in the same variable so that the updated value reflects as a display value. 
 Please try updating your code with the below code. 
 a!localVariables(
 local!data: rule!T_EX(name: ri!expensedetails.name),
 a!paragraphField(
 label: "comments",
 labelPosition: "ABOVE",
 value: local!data,
 saveInto: { local!data, ri!expensedetails.comments },
 refreshAfter: "UNFOCUS",
 required: true,
 height: "MEDIUM",
 validations: {},
 showWhen: ri!hra
 )
)

Sanchit Gupta (Xebia) · Answer

Please use the insert code feature to paste the code. 
 
 Not sure what you are trying to do here but I think the syntax should be like this. 
 saveInto: if(
 rule!APN_isBlank(local!repeatedinternalcomment),
 {
 local!internalComment,
 a!save(
 ri!internalComment,
 'type!{urn:com:appian:types:ISR}ISR_StudyComment'(
 commentId: if(
 rule!APN_isBlank(ri!internalComment.commentId),
 {},
 ri!internalComment.commentId
 ),
 comment: local!internalComment,
 isInternal: true(),
 reviewStage: cons!ISR_TEXT_REVIEWSTAGE_CODE_MEDIREV,
 isActive: true(),
 createdBy: loggedInUser(),
 createdOn: now(),
 updatedBy: loggedInUser(),
 updatedOn: now()
 )
 )
 },
 {
 local!repeatedinternalcomment,
 a!save(
 ri!internalComment,
 'type!{urn:com:appian:types:ISR}ISR_StudyComment'(
 commentId: if(
 rule!APN_isBlank(ri!internalComment.commentId),
 {},
 ri!internalComment.commentId
 ),
 comment: local!repeatedinternalcomment,
 isInternal: true(),
 reviewStage: cons!ISR_TEXT_REVIEWSTAGE_CODE_MEDIREV,
 isActive: true(),
 createdBy: loggedInUser(),
 createdOn: now(),
 updatedBy: loggedInUser(),
 updatedOn: now()
 )
 )
 }
)

Mike Schmitt · Answer

You will need to make sure the value you want ends up being populated into your Rule Input CDT. 
 If you know the value in advance and can evaluate the expression that originally populates it, earlier (as in prior to the form being reached), one method is to pre-populate the CDT before the first task is reached. 
 However if you're just referring to a value pre-populated on the second task, then I'm unclear why the value isn't already stored in your PV CDT that you're passing into the second form. If it is, then you shouldn't necessarily need to re-initialize it on that form and shouldn't need to mess with the local variable at all. 
 Finally, one of the simplest and most standard ways to store the value captured in the local variable into the rule input CDT field, upon form submission (regardless of the answer to the above question), is to use an a!save() statement in the saveInto of the Submit button, and copy the local variable's value into the correct field. I try to reserve this method for when it's truly necessary and won't add unnecessary complexity. 
 It's hard to judge here without being able to take your full code into context... but I'd suggest revising a few things here... 
 a!localVariables(
 
 /* instead of multiple messy if(isNull()) statements, simply do that check here, then only use this local variable until Submit time */
 local!BCreviewer: a!defaultValue(
 value: ri!studyMedicalReview.BCReviewedBy,
 default: rule!ISR_toget_BC_Reviewer(ISR_Studyrequest: ri!studyRequest.studyRequestId)
 ),

 (...)
 
 value: local!BCReviewer,
 saveInto: local!BCReviewer,
 
 (...)
 
 primaryButtons: {
 a!buttonWidget(
 label: "Submit",
 submit: true(),
 
 saveInto: {
 ri!buttonPressed,
 
 a!save(
 ri!studyMedicalReview.BCReviewedBy,
 local!BCReviewer
 )
 }
 )
 }
)

Mike Schmitt · Answer

This version would be what I'd suggest as a starting point for handling both value fields in a similar manner, BTW. 
 Also thanks for confirming - as always I'd request clicking verify on any/all answer(s) of mine you found directly helpful, lol. 
 a!localVariables(

 /* instead of multiple messy if(isNull()) statements, simply do that check here, then only use this local variable until Submit time */
 local!BCreviewer: a!defaultValue(
 value: ri!studyMedicalReview.BCReviewedBy,
 default: rule!ISR_toget_BC_Reviewer(ISR_Studyrequest: ri!studyRequest.studyRequestId)
 ),
 local!BCReviewedOn: a!defaultValue(
 value: ri!studyMedicalReview.BCReviewedOn,
 default: null()
 ),

 (...)

 a!sideBySideLayout(
 items: {
 a!sideBySideItem(
 item: a!textField(
 label: "Business Conduct Reviewer",
 labelPosition: "ABOVE",
 value: local!BCreviewer,
 saveInto: local!BCreviewer,
 showWhen: if(
 local!businessCounduct,
 true(),
 false()
 ),
 required: if(
 ri!studyMedicalReview.decision = cons!ISR_TEXT_DECISION_MEDREVDEC_FRINFO_CODE,
 false(),
 true()
 )
 )
 ),
 a!sideBySideItem(
 item: a!dateField(
 label: "Business Conduct Reviewed On",
 labelPosition: "ABOVE",
 value: local!BCrevieweddate,
 /* If the rule value is not there I mean if there is no reviewer for that studyRequestID then value goes to table */
 saveInto: local!BCrevieweddate,

 )
 )
 }
 ),

 (...)

 primaryButtons: {
 a!buttonWidget(
 label: "Submit",
 submit: true(),

 saveInto: {
 ri!buttonPressed,

 a!save(
 ri!studyMedicalReview.BCReviewedBy,
 local!BCReviewer
 ),
 a!save(
 ri!studyMedicalReview.BCReviewedOn,
 local!BCReviewedOn
 )
 }
 
 )
 }
)

Mike Schmitt · Answer

There are as many valid answers to this as there are different implementation approaches - if you're looking for something specific, or having issues with anything in particular, you'll need to provide quite a bit more detail in order to wring anything useful out of us here. 
 However in general, the answer to this will always be some variation of: for task 1, pass any details (usually centered around user-entered info) out into PV data, and for subsequent task(s), pass any relevant information into the task form via rule input(s).

Mike Schmitt · Answer

sireesha said: Can I get an expression rule to retrieve the specific fields only from data store entity. 
 a!queryEntity has the capability to specify the particular fields you want returned, when all you want is a subset of available fields. What have you tried?

Mike Schmitt · Answer

sireesha said: So how can I save the prepopulated data without editing into the table again with same studyrequest id=2 
 The code snippet I provided in my earlier reply above should demonstrate how to do this for basically any value field. I'm unclear why you need to revert my suggested changes, as it doesn't seem to add anything that isn't still accomplished in my version (the "reviewed on" field seems to rely on totally unrelated data, no?)

Mike Schmitt · Answer

sireesha said: How can I use a!save function for above code at the submit button 
 I can't really judge by the code you've posted here as you didn't include your button or any hint of what you're currently trying. My example directly above contains a button with two a!save() commands - did you find this to not work? Are you having a particular issue? As-is, I can't really even guess as to any particular suggestions. 
 Also: thanks for using a Code Box, but I'd advise/request you to also make sure you copy your code directly out of the expression/interface editor before pasting, in order to preserve indentation -- because without any indentation, it stays pretty difficult to read in its current form.

Mike Schmitt · Answer

from what I can tell, "local!repeatedInternalComment" is text, and much like what the error message you showed here suggests, you're trying to save that into the target of ri!internalComment, which is a CDT. 
 As a refresher, when you call a!save, the first parameter (whether a single item or a list of items) is the TARGET of the save operation, and the second parameter is the VALUE. 
 If your TARGET is or includes a CDT, that implies that you're trying to overwrite that entire cdt value with the item in the VALUE parameter, which in this case is just text. This is *exactly* what your error message is telling you: 
 You should probably simplify your a!save statement, remove the (misspelled) local!int re nalComment target, and save directly into the comment property of ri!internalComment. a!save(
 ri!internalcomment.comment,
 local!repeatedinternalcomment
) 
 Additionally : i'm unclear why you're even trying to do this save on the Button Click here, because from what I can tell from your code, you're manually modifying the value of ri!internalComment every time the text value is updated as well. This is OK, but it also means that you don't really need to worry about doing the saveInto in the button - that technique is really reserved for when you want to copy local values (that is, things being stored ONLY in local values) into a Rule Input, upon Form Submission (and not until then). There's not much point in doing both.

how can I prepopulate the fields of current task with previous completed task details

Top Replies