Page History
...
Field | Field visible | Field required | Value | Currently visible |
---|---|---|---|---|
Income type | Always | Always | 'Wage labor' | Yes |
Profession | If Income type = 'Wage labor' | If Income type = 'Wage labor' | 'IT analyst' | Yes |
Gross salary | If Income type = 'Wage labor' | If Income type = 'Wage labor' | € 50.000 | Yes |
The user changes the value of field Income type
from 'Wage labor' to 'Pension income'. Both the fields Profession
and Gross salary
are no longer visible on screen. A new field becomes visible: Pension Income
. The user enters a value for this new field.
Field | Field visible | Field required | Value | Currently visible |
---|---|---|---|---|
Income type | Always | Always | 'Pension income' | Yes |
Profession | If Income type = 'Wage labor' | If Income type = 'Wage labor' | 'IT analyst' | No |
Gross salary | If Income type = 'Wage labor' | If Income type = 'Wage labor' | € 50.000 | No |
Pension income | If Income type = 'Pension income' | If Income type ='Pension income' | € 50.000 | Yes |
...
Although the values of the fields Profession
and Gross salary
are not visible nor required anymore, they are still present in the profile. They might not do any harm, but saving them in a database to be collected later or when the profile values are used in a data mapping to another system, could cause problems.
...
When clearing irrelevant values can wait until the page is left, for instance when navigating to a next step in the application, you can model a service call or flow to clear irrelevant values using the Service call type: AQ_Instance_Update service type. An example is shown below. Field Income type
determines which fields are cleared in the conditional node. You could use sub flows containing the Service call type: AQ_Instance_Update service calles as as in the example below or service calls directly. As in the example above Income type
has been changed from 'Wage labor' to 'Pension income', which will result in clearing all values for specific fields for 'Wage labor' and for instance 'Freelance'. Any general fields, possibly astarting date or duration, will remain unchanged.
...
Tip |
---|
Create reusable expressions to use in preconditions on your page and in the flows for clearing irrelevant values. |
Clear irrelevant values with a Flow on Refresh container
When clearing irrelevant values cannot wait until the page is left, for instance when the values are used in calculations on the same page, you can model a service call and flow to clear irrelevant values using the Service call type: AQ_Instance_Update service service type and call this flow with a FlowOnRefresh container type. Often, however, this will not be necessary when using adequate logic in the expressions, making it more robust.
...
In some situations it might be possible to just keep the irrelevant values in your profile and deal with them by writing adequate expressions. For instance, you could make sure Profession
is not used in a datamapping whenever income type is not 'Wage labor'.