# 5.1.3

### New in 5.1.3

* Fix for Googlepicker. It did not open if it was used in an Integration Wizard (bug introduced in 5.1.1).
* Modifiers are now applied in static calls - *source* (in the flow design phase). An example:

<figure><img src="https://1603660091-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgsBalkJKe24AUhfRPojx%2Fuploads%2FOz4UYULPPgAlLk5Vtjiq%2Fimage2.png?alt=media&#x26;token=4e9ed164-9f08-40b9-8aad-0d3195e38ce2" alt=""><figcaption></figcaption></figure>

Consider a component with a dynamic input port inspector. The inspector definition is returned by calling the *SourceWithModifiers* component and sending it a few parameters. The *entityType* parameter is taken from properties and passed to the input in port of the source component. Based on the value of the user provided property *entityType*, the *SourceWithModifiers* component returns different input fields of the inspector. Now assume that the *entityType* value is defined with a variable and even a modifier can be applied to it.

<figure><img src="https://1603660091-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgsBalkJKe24AUhfRPojx%2Fuploads%2FAWxxw0jLOKpW9xnHrbiy%2Fimage1.png?alt=media&#x26;token=54bc3908-e3da-4a3d-a377-b0ee2c4bf453" alt=""><figcaption></figcaption></figure>

In this example, the *entityType* is taken from the flow’s custom fields (and a modifier JSONPath is applied to it). In the previous versions of Appmixer the value propagated to the source component (*SourceWithModifiers* in this case) was not resolved, i.e. the potential variables and modifiers applied to the propagated parameter where not correctly evaluated when they reached the source component (*SourceWithModifiers*).