Your first screenshot doesn't appear to be mapping the AC!output_document to a process variable (pv!)...if you want access to the document in your process then you'll need to map it to a pv! of type 'Document'.

Yes, I have mapped to the process variable. But still getting the same result like [Document:]

Dinesh Loganathan said:

getting the same result like [Document:]

Can you explain what this means?  Where and how are you seeing "[Document:]"?

This is the value getting from process variable, 

a!save(
ri!exportBusRuleDoctId,
index(
fv!processInfo.pv,
"businessDoc",
null
)
)
output of ri!exportBusRuleDoctId is - > [Document:]

a!startProcess(
processModel: cons!PROCESSMODEL,
processParameters: {
businessRule_cdt: ri!business_cdt,
clientName: "BusinessRule " & " " & now(),
},
onSuccess: {
a!save(
ri!exportBusRuleDoctId,
index(
fv!processInfo.pv,
"businessDoc",
null
)
)
},
onError: a!save(
ri!errorBusRuleMsg,
"Business Rules not available for this client"
)
)

does your process model have chaining enabled at least up until the smart service node?  The success parameter for the startProcess() function executes immediately upon break of chaining, meaning that if there isn't any chaining, it will just execute a save that will result in an empty value.

(You didn't mention before that this is the method you're using to execute your process model, so we would have had no way of knowing this is where you're seeing the issue).

BTW, if you go to /objects in Designer, and filter down to "documents", you should see generated documents there as long as the node executed successfully, regardless of what result you're getting in your interface.

does your process model have chaining enabled at least up until the smart service node?  The success parameter for the startProcess() function executes immediately upon break of chaining, meaning that if there isn't any chaining, it will just execute a save that will result in an empty value.

(You didn't mention before that this is the method you're using to execute your process model, so we would have had no way of knowing this is where you're seeing the issue).

BTW, if you go to /objects in Designer, and filter down to "documents", you should see generated documents there as long as the node executed successfully, regardless of what result you're getting in your interface.

Thanks, Mike Schmitt. Now it's working!!!!