Input dialogue box name (subject to change in the future?)

[Koichi_Tsuji]

Input expression is still in beta, so it’s behavior is always subject to chnage until the feature is fully released, but I noticed that the input dialogue box (poping up in the upper right corner) does have it’s “view name”.

Logic was rather simple. It looks the dialogue box (window) name is inheriting the name of the view the input action is fired from.

For instance, the action is invoked from inline action of table view, then the dialgue box name is the name of the table view. Similarly, the action is invoked from detail view, the dialogue box name is the one of this detail view.

We could use this logic to dynamically change “Save” system names for those particualr dialogue boxes, as well as making some fields “required” only on this dialogue box etc.

For this sample/demo app, we passed following expression to the Save system language to change dynamically to test.

@takuya_miyai

[Suvrutt_Gurjar]

Good one @Koichi_Tsuji

[Koichi_Tsuji]

Thank you. Now we got what their names are .

It should be a part of the view the action button resides. It is not a form view, while it looks like a form view. This is making sense to me (actually not making sense) as we are not able to fire the action on save such a dialogue box event, as they are actually not a form view…

Hope this dialogue box turns to be proper form view (could be systematically generated once we made input action) and we can attach the action to invoke on save event.