Objective
After reading this article, you will understand how to allow users to create new form records from the mobile app.
Before you get started
Note that this article only applies if you have Mobile Cards enabled. These articles might be helpful before you read further:
Use New Form Buttons to give users the ability to create new forms for whatever record they're currently viewing in the mobile app. For example, if an admin is choosing to use Accounts as the Primary Object on Mobile Cards, an end user can tap on an Account card, view all existing forms for that Account, and create new Form Records with the New Form Buttons configured by the admin. New Form Buttons are great for providing end users with a list of options to choose from while in the field. For example, if mobile users generally need to fill out a vehicle inspection form, then a daily time entry form, and then a job site audit for each record, all three of these buttons can be made available to the user.
The New Form Buttons can be configured in the Mobile Admin tab in the New Form Buttons section. Add at least one New Form Button by clicking Add +. This consists of a Button Label, which is what the text would say on a button that your end users would touch to launch a new form, and a Button Link which is what Youreka uses to determine things like form template and related objects.
Use the following sample as a model to build your own New Form Buttons.
templateid=a0D1C00000fb4yhUAA&disco__Form_Contact__c={!thisRecord.Contact__c}
This is constructed in the following way:
- templateid=a0D1C00000fb4yhUAA : the 18-digit template ID of the form template you want the new form to be based upon
- &disco__Form_Contact__c={!thisRecord.Contact__c}: (Optional) The template referenced in this Button Link also includes field links to a contact record. By assigning {!thisRecord.Contact__c} we are saying that we want to set the form's contact field links to the contact field on this record(the account mobile card that we are launching the form from).
Note: the field name (Contact__c) is case-sensitive and should match the api name in Salesforce exactly, including upper/lower case.
*If you have multiple field link objects, this portion can be repeated as many times as necessary.
*If you choose not to include other field links as part of the Button Link, end users will be presented with the screen where they can make their selections for any remaining field links.
*If you want your form to create a new contact rather than reference an existing one, this portion should read &disco__Form_Contact__c=NEW
Comments
0 comments
Please sign in to leave a comment.