I'm having an issue in upload document. The situation is that I have to disp

gaurava322 over 7 years ago

I'm having an issue in upload document. The situation is that I have to display the Upload Document control in a grid and once it is uploaded i need to store the document ID in DB. And if i'am again returning to this screen, and since i have already uploaded the document earlier and it is in DB, it should show the link to that document. In gridRowLayout, i am doing following:
if(
rule!APN_isBlank(ri!items[ri!index].appianDocId),
a!fileUploadField(
value: ri!items[ri!index].appianDocId,
saveInto: ri!items[ri!index].appianDocId,
target: cons!WMG_GBL_UPLOADED_DOCS_TARGET,
readOnly: true,
align: "RIGHT"
),
a!linkField(
label: "",
links: {
a!documentDownloadLink(
label: ri!items[ri!index].appianDocId,
document: ri!items[ri!index].appianDocId
)
}
)
)

Now the problem is as soon as i upload the document in the cell i...

Discussion posts and replies are publicly visible

Parents

0 kumaraveln over 7 years ago

As mschmitt said, use of pv! variables can be eliminated by extracting the information directly from ac! variables in the output section of human task .. But if something goes wrong it would be difficult to understand whether the document object is captured properly from UI and which index are empty (or has value) in case if it is multiple .. You can keep the pv! till your logic is implemented and working perfectly and then remove them and map the rule directly to the ac's

My opinion is to still keep the pv variables for debugging purpose, as few pv's of document type and the fact that they are used only within the same process should not cause a memory issue
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 kumaraveln over 7 years ago

As mschmitt said, use of pv! variables can be eliminated by extracting the information directly from ac! variables in the output section of human task .. But if something goes wrong it would be difficult to understand whether the document object is captured properly from UI and which index are empty (or has value) in case if it is multiple .. You can keep the pv! till your logic is implemented and working perfectly and then remove them and map the rule directly to the ac's

My opinion is to still keep the pv variables for debugging purpose, as few pv's of document type and the fact that they are used only within the same process should not cause a memory issue
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data