"Save Draft" option in Tasks

Thank you.

Hi karlon2336 

Did you come right with this? 

We have an interface that has: 

• rule inputs 
• the process model does have the variables mapped to ac!
• the save draft check box is ticked

However, when we save draft, close the form and then come back to the task, the values entered initially are not displaying on the form.

Any idea how to fix this?

Thanks

I think you will have to share some code snippets and explain the matter in more detail.

In the Interface , this is the code to save to  the rule input:

In the process model, the output on the interface is as follows: 

and the "Allow users to save draft" is ticked in the Form of the process model:

We fill the fields in on the form ( ie. ingredient declaration for the technical information ) , click save draft and then close the form.

We then reopen the task and the ingredient declaration for the technical information paragraph field is blank. The draft values were not saved.

 What are we doing incorrectly?

Thanks

Hi Stefan

This is the code to save the rule inputs on the interface: 

This is the process model where we are mapping the ACP: 

In the form of the process model, the " allow users to save draft" is ticked : 

The task is accepted and the user fills in the field for technicalInformation.ingredientDeclaration then clicks save draft and closes the form.

The user then goes back to the task but the technicalInformation.ingredientDeclaration  values are blank. 

Any idea what is wrong here?

Thanks

Paroshni Naidoo said:

Any idea what is wrong here?

I'd bet a few dollars that it has to do with how you're declaring the local variable, "local!technicalInformation".  Mind showing a screenshot of where you set its initial value upon form load?

It is being set like this: 

local!technicalInformation: 'type!{urn:com:appian:types:PRD}PRD_BlendTechnicalInformation'()

Paroshni Naidoo said:

local!technicalInformation: 'type!{urn:com:appian:types:PRD}PRD_BlendTechnicalInformation'()

So the local variable is not making any reference to the current value of the rule input.  And then the field's "value" parameter only makes reference to the local variable.  So no matter what the user does, when they re-open the form, it's going to appear blank.

Instead you need to try defining the local variable such that it observes the current value (if any) of the rule input:

local!technicalInformation: ri!technicalInformation,

Paroshni Naidoo said:

local!technicalInformation: 'type!{urn:com:appian:types:PRD}PRD_BlendTechnicalInformation'()

So the local variable is not making any reference to the current value of the rule input.  And then the field's "value" parameter only makes reference to the local variable.  So no matter what the user does, when they re-open the form, it's going to appear blank.

Instead you need to try defining the local variable such that it observes the current value (if any) of the rule input:

local!technicalInformation: ri!technicalInformation,

Thank You! By changing the local variable, it now works!

Cool, that's what I suspected (but didn't want to make any large promises, lol) - if you get a chance I'd be grateful for a "verify answer" click, if you see that option.