Here you can find some commonly asked questions and problems, and their solutions.
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.
Solution
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.
Solution
If the component is backed by a View then PhixFlow returns the data for the View, rather than the backed attribute form fields. To resolve this, remove the View, found in the Advanced section of the Card Component Properties, or add the required fields to the View.
"Failed to convert" error message after running Actionflow
Problem
The following error message shows when running an Actionflow:
Failed to convert value of type 'java.lang.String' to required type 'com.accipia.centerview.web.parameters.ActionRunParameters'; nested exception is java.lang.IllegalArgumentException
Solution
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.
