Page History

...

In a mortgage application information about the applicants' incomes are needed. One of the incomes was entered as permanent contract full time, but it turned out to be a pension income. The fields belonging to the full-time contract are on screen and are user set present in the profile. 

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.

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 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 AQ_Instance_Update service calles as in the example below or service calls directly. As in the example above Income type has been changed from Wage labor to 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. 

...

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 Profession is not used in a datamapping whenever income type is not not 'Wage labor'.