Hidden Input

HIDDEN INPUT ELEMENT

An extremely important tool for REST or SQL exchange and for branching separate workflows within you mobile service. Invisible to your mobile users it can do many things:

  • Pass/receive data with an outside system and initiate an outside trigger if a particular screen is accessed. You can do it by performing the following steps:
    • Create and name Object's column
    • Set column’s Data tab to produce the required result, remember that with #hashtags# you can insert any data held in columns into your call
    • add Hidden element to anywhere on the screen
    • input _#columnname#_ or a value into a default value. When mobile user accesses this screen the #hashtag# calls for column’s content, which is pulled from an outside source
  • Pass data to an outside system and initiate an outside trigger if a particular button is pressed. To do this – do as above, BUT in step 4 input #columnname# into a Default value instead of Text. The difference is that default value saves received data into Event to the column which was referenced.
  • Triggers a refresh of all outside data stored in Object and managed from outside server, to do this, just add Hidden element to the starting screen of your service, create a dummy column for each such operation and set it to make outside REST call, include in the URL #object id or phone number#. When your addressee server gets this request, it can parse from the link which object is being called for the operation and trigger an internal procedure to update all object data which it is set to. This allows keeping object data up to date on demand rather than with constant refreshing.
  • Submits any amount of additional info within each Event – for example in your HR mobile service, you want your accountants see Tax ID of an employee requesting a W-2 form, but your IT department should get an office number and a list of installed software with a “Help Virus” request.

HIDDEN INPUT ELEMENT PROPERTIES

  • Backend Name: is used to reference this Element from the other parts of the App. Using Backend Name the value stored in the Element could be printed or it can be called for the logical conditions.
  • Placeholder: This is what user sees until typing into this field. It’s best used to show a hint to a user, for example, “Please type in you name” or “Select one” or “Chose your city”, etc. Can contain any _hashtag_ reference.
  • Default Value: the default integer or string that the field would keep. would be stored in the backend of the system only and would not be displayed to the AppUser unless specified in the Placeholder.
  • Hide Data From Object: the AppUser would not be able to see the data in the field in the History System Screen.
  • Repeat Element: repeat the Element based on the Smart Filter.

HIDDEN INPUT ELEMENT ACTIONS

  • Save to Object Column: select the Objects Column you want the data from this field to be stored in.


How did we do?