Is the wizardheader function supported in 7.3 portal forms? I renders fine when

padmanabhanv over 11 years ago

Is the wizardheader function supported in 7.3 portal forms? I renders fine when I add it to the form, however I see the below error in application-server.log.
ERROR com.appiancorp.process.common.presentation.JSONSerializerWithLogging - Can't unmarshall the JSON value "[]" of type org.json.JSONArray to a java.lang.Long.
2014-01-07 22:52:12,191 [ajp-/0.0.0.0:8009-1] ERROR com.appiancorp.process.common.presentation.TypedValueSerializer - The value of the TypedValue bean could not be converted from its JSON representation. Target TypedValue: ActivityClassParameter[name=accountIndex,it=1,v=<null>] JSON value: []
...

Discussion posts and replies are publicly visible

0 padmanabhanv over 11 years ago

The issue is unrelated to the wizardheader; however in all the forms where I am saving a paging grid selection into an variable of type Number(Integer), I get the above error. Is this a known issue or am I missing something in my setup?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 11 years ago

Is this happening on a particular process or everywhere (across processes?) Have you tried creating a new process with grid and a simple data set - just so we eliminate the issue happening due to the data-set
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

Yes it happens in all forms(across processes) where I am saving a paging grid selection into an variable of type Number(Integer).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 11 years ago

Does the CDT that you are using in the paging grid have a primary key defined? If so, what's the data type of this PK?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

Sathya, There is no primary key defined for that CDT. Is that the cause?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 11 years ago

If you're populating the grid via a query rule, it could be. I suggest you try that and see if that addresses the issue. Generally, if its just a CDT[], then you will get the index of the selected row. To make sure that is not the case, you can try saving the query rule into a CDT[] and populating the grid using todataSubset(cdt[], pagingInfo) and see if that resolves the issue. Then you'd know what the problem was.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

I am not populating the paging grid off a CDT and am poulating the grid using todataSubset(cdt[], pagingInfo). See this error(in the application server log) while saving any form that has a grid like this. The UI works without issues though. You should be able to reproduce it easily.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

*I am not populating the paging grid off a queryRule
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sathya Srinivasan
Appian Employee
over 11 years ago

If you're able to replicate the issue, I suggest you raise a ticket with Appian support
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel