04. TaroWorks Mobile User Permission set

Introduction

Starting TaroWorks 7.1.X, the TaroWorks Mobile User Permission set is now available and can be assigned to mobile users on any supported license type.
This permission set contains the permissions necessary to allow users on Salesforce and Salesforce Platform Licenses to log into the TaroWorks mobile application and submit Jobs. These are the same permissions as the TaroWorks Partner User profile assigned to mobile users on Partner Community Licenses. However, you will also need to give your users access to the objects and fields required for their TaroWorks Jobs - either on their profile or an additional permission set. 

Note :
If you clone the TaroWorks Mobile User permission set, it will need to be manually maintained.  We would recommend maintaining separate permission sets containing your customizations and the necessary access to your custom objects, then create a permission set group to assign to your mobile users.

The below permissions are for TaroWorks version 4.4.X and above. If you are on a previous version, you can skip any fields, objects, apex classes, or Visualforce pages that you are not available in the Profile..

• A. Field Level Permissions - Once a user has at least read access to an object, they need to be granted visibility to fields on that object.
• B. Object Permissions - There are many objects that are unique to TaroWorks that TaroWorks Users will need access to, in order to work with TaroWorks in Salesforce.
• C. Apex Class Access - There are some functions unique to TaroWorks that the TaroWorks User will also require access to.
• D. Visualforce Page Access - There are some custom pages that TaroWorks Users will need to access.  

A. Field Level Permissions

Under Setup >Users > Permission set > TaroWorks Mobile User, the minimal field level security settings are as follows.

Note: If you add any custom fields that you want the TaroWorks User profile to have access to, you'll need to give visibility to those fields as well. 

All of the fields for all of the objects listed below will need to have at least Read Access checked with the exceptions of SObject Filter Condition object.

• Answer
• Application Version
• Assigned Target
• CascadingLevel
• Cascading Select
• Cascading Select Value
• Client Assignment
• Device
• Field Mapping
• Form
• Form Library
• Form Mapping
• Form Version
• Group
• Job
• Job Activity
• Member
• Mobile Money Collection
• Mobile User
• Object Relationship Mapping
• Option
• Performance Target
• Poverty-assessment Tools Table
• Poverty-assessment Tools Table Data Set
• Poverty-assessment Tools Table Line
• Question
• Score Value
• Scoring Group
• Skip Condition
• Sobjects Contact Association
• Submission
• Submission PAT Value
• Submission Score
• Target
• Task
• Task Activity
• TWErrorLog

Example:

The SObject Filter Condition object will only need the following fields set to have Read Access:

B. Object Permissions

The following objects should be assigned Read (R), Create (C), Edit (E) or Delete (D) permissions:

• Answers - RCE
• Application Version - R
• Assigned Targets - RCE
• Cascading Levels - R
• Cascading Selects - R
• Cascading Select Values - R
• Client Assignments - RCED
• Devices - RCE
• Field Mappings - R
• Form - RE
• Form Libraries - R
• Form Mappings - R
• Form Versions - RE
• Groups - R
• Jobs - RCE
• Job Activities - RCE
• Members - RCED
• Mobile Money Collection - R
• Mobile Users - RED
• Object Relationship Mappings - RED
• Options - R
• Performance Target - RE
• Poverty-assessment Tools Results - RCE
• Poverty-assessment Tools Tables - R
• Poverty-assessment Tools Table Data sets - R
• Poverty-assessment Tools Table Lines - R
• Questions - RE
• Score Values - R
• Scoring Groups - R
• Skip Conditions - R
• SobjectContactAsociation - RCED
• SObject Filter Associations - R
• Submissions - RCED
• Submission PAT Associations - RCE
• Submission PAT Values - RCE
• Submission Score - RCE
• Targets - R
• Tasks - RCE
• Task Activities - RCE
• TWErrorLog - RCED

C. Apex Class Access

Enable the following classes:

• gfsurveys.ApplicationUpdate
• gfsurveys.CascadingSelectWebService
• gfsurveys.FFSubmitJobs
• gfsurveys.FormDetailsWebService
• gfsurveys.MobileUserLogin
• gfsurveys.MobileUserLogout
• gfsurveys.PerformanceManagementEndpoint
• gfsurveys.QuestionTriggerLogic
• gfsurveys.RemoteActionUtils
• gfsurveys.ResourceDownload
• gfsurveys.SFDCEncoder
• gfsurveys.ScoringWebService
• gfsurveys.SiteUrlRewriter
• gfsurveys.SurveyDistribution
• gfsurveys.SurveyFormList
• gfsurveys.SurveySubmissionService
• gfsurveys.SurveySubmissions
• gfsurveys.SurveyTriggerLogic
• gfsurveys.SurveyVersionTriggerLogic
• gfsurveys.TaroRESTJobTemplates
• gfsurveys.TaroRESTJobTemplatesLogic
• gfsurveys.TaskSelector 
• gfsurveys.TWErrorLogDomain

D. Visualforce Page Access

Enable the following pages:

• gfsurveys.DownloadApk
• gfsurveys.RemoteSurveyList
• gfsurveys.SurveyBuilderPreview
• gfsurveys.SurveyPreview
• gfsurveys.formList

Conclusion

Now that this permission set is available starting TaroWorks 7.1.X, it is not longer required to use the TaroWorks Partner User profile.