Versions Compared
| Version | Old Version 3 | New Version 4 |
|---|---|---|
| Changes made by | ||
| Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overview
Here you can find some commonly asked questions and answersproblems, and their solutions.
| Table of Contents | ||||
|---|---|---|---|---|
|
Re-used Actionflow working intermittently
Problem
An Actionflow is reused on different components, e.g. a grid and a card container. The Actionflow works as expected on one component but not the other.
| Expand | ||
|---|---|---|
| ||
Check that the fields on the component where it is not working are backed by a table attribute. |
Backed attributes not populating
Problem
Form fields on a component are not populating despite having backing attributes.
| Expand | ||
|---|---|---|
| ||
If the component is backed by a View then PhixFlow returns the data for the View, rather than the backed attribute form fields. |
"Failed to convert" error message after running Actionflow
Problem
The following error message shows when running an Actionflow:
| Warning |
|---|
Failed to convert value of type 'java.lang.String' to required type 'com.accipia.centerview.web.parameters.ActionRunParameters'; nested exception is java.lang.IllegalArgumentException |
| Expand | ||
|---|---|---|
| ||
This is caused by a Type mismatch (i.e. integer, decimal, string, etc.) between a field and its backing attribute. For example, you may have a dynamic text field set to a Type of Integer, but backed by an attribute with the Type of String. |