Release(s)
What's New
- Form Change Log - gives TaroWorks Users the ability to record changes that have been made to a Form in Salesforce, this allows API consumers to validate the latest changes they've considered to a Form before updating.
Mobile Compatibility
- Works with app version 7.2
Mobile
Upgrade Instructions to 7.2.x
Resolved Issues
Known Issues
Limits and Large Quantities (all known issues are around large number of questions, submissions, job activities, mobile users etc)
- Please expect slower performance during field mapping with large surveys.
- Photo and Signature URL's are incorrect in sandbox instances IDALMSA-9956, IDALMSA-3702
- Surveys above 300 questions are not supported. If you have survey needs greater than 300 questions, please split into multiple surveys during design.
- Surveys with more than 200 questions but lots of options in Single/Multi Select Questions are also not supported. Please split into multiple surveys during design. IDALMSA-3758
- Error Occurs when viewing or cloning a survey with 400 questions IDALMSA-8931
- The 'Export All Survey Results to CSV' function will fail after 40,000 rows. Please contact the TaroWorks support team for a workaround. IDALMSA-6512, IDALMSA-8908
- More than 24,000 job activities cannot be viewed on Job Activities tab. Workaround is to create a Salesforce report to view job activities.
- Filtering on Mobile Users or Contacts in Job Activities tab will not work with large number of contacts. Workaround is to create a Salesforce report to view job activities.
- More than 10,000 assigned performance targets cannot be updated. IDALMSA-5110. IDALMSA 5747.
- New Jobs Targets cannot be created when there are more than 1000 Partner Users in profiles that have the word 'TaroWorks' in the profile name. The workaround is to rename some profiles to exclude the word TaroWorks. IDALMSA-6637
- When viewing or editing the TaroWorks Mobile User details, the pages don't load fully intermittently for both Admin and TaroWorks Users when an org is on the Winter '22 release. IDALMSA-11252
- The Job Targets page does not load and the 'Too many SOQL queries' error when there are more than 50,000 Contacts in an org. IDALMSA-8040
- Time Displaying in SF for Date Only question IDALMSA-11078
- "Too Many DML Rows: 10001" Error displayed when user tries to update more than 10,000 records IDALMSA-10628
- "SObject row was retrieved via SOQL without querying the requested field: gfsurveys__SurveyVersion__c.gfsurveys__Survey__r" Error occurs after click on Form Preview IDALMSA-8035
- Partner community license user can only see photos which is uploaded by itself and see orange triangle for photos uploaded by Salesforce and Platform License Users IDALMSA-11631
- TMU Mobile Record Assignment performance periodic issue- Record assignment/unassignment takes several turns to effect on Mozilla Firefox IDALMSA-11636
- An error has occured. Please contact your help desk with the below information. System.SObjectException: SObject row was retrieved via SOQL without querying the requested field: gfsurveys__Submission__c.gfsurveys__Survey__c (gfsurveys) Error 00004 IDALMSA-11813
- Submissions to update a survey record using an autonumber field as id field not mapping properly IDALMSA-11779
- Note: You should not have any custom objects with the same API name as the TaroWorks Package objects.
Groups
-
If a Mobile user belongs to many groups and sub groups, they will encounter the 'Too many SOQL queries" error when logging in and syncing. Try to keep the number of groups at a minimum. IDALMSA-7499
Jobs
- Do not pass in LastViewedDate or LastReferencedDate fields will not render in your Drill-down Hierarchies IDALMSA-6687.
- There can be a delay in Queue Ownership when Publishing and Cloning Jobs. IDALMSA-7722. IDALMSA-7745
- Only 4 Drill-down Hierarchies in a single Job are supported. IDALMSA-7735.
- No mobile records will appear for a drill-down hierarchy level that has a filter on a value that is not a number or checkmark box, and the mobile user’s language does not match the company language. IDALMSA-8121
- Unexpected behavior can occur if the you've not assigned records to mobile users from the same object with which you are starting your drill-down hierarchies IDALMSA-8597
- An error is thrown for standard objects fields that are not accessible IDALMSA-8862
- Drill-down hierarchy filtering does not supporting picklist values where the label is different from the API name IDALMSA-9002
- Error occurs when applying filter if there are more than 50,000 records IDALMSA-9439
- TaroWorks does not supporting polymorphic lookups fields found in some standard objects such as Task and Event objects. When these objects are used on Drilldown Hierarchy, no records will be visible to the Mobile Users. IBTFF-3581
Mobile Users and Object Assignment
- If you delete an entire object where records have been assigned to a Mobile User, it will still display on the Mobile User's device. Work-around is to edit another object that's assigned to the Mobile User first. IDALMSA-6190.
-
TaroWorks Mobile User creation and the TaroWorks Mobile User details page take time to load. The workaround is to disable the caching setting 'Enable the Secure and persistent browser' to improve performance.
- Go to Setup, Under "Administration Setup", go to Security -> Session Settings.
- Uncheck the "Enable secure and persistent browser caching to improve performance" option under the Caching section and click on Save.
- The 'Assigned Public Group Names' and Assigned Public Group Ids have a field limit of 131072 characters. IDALMSA-10099
- If you delete the record type of Contact object, on reverse sync, TaroWorks Mobile User object 'Contact Record Type' field will not get updated. The workaround is to manually update the 'Contact Record Type' field on TaroWorks Mobile User, which is related to the particular Contact (whose record type is deleted). IDALMSA-10139.
- On the new TaroWorks Mobile User tab, only 200 MU records can be selected at a time on the list view for MRA and Public Group assignment. IDALMSA-10217.
- There are performance issue when doing bulk un-assignment of 1000 records from 200 Mobile Users on the new TaroWorks Mobile User Tab. IDALMSA-10326.
- The Salesforce CRM Content User setting is not checked by default when a Mobile User is created from the new TaroWorks Mobile User Tab. This setting will have to be checked manually on the user record. IDALMSA-10618
-
In order to use the new Mobile User management functionality, the Org needs to be on the Salesforce Lightning Experience. Only add the new TaroWorks Mobile User tab and remove the old Mobile Users tab if using the SF Lightning experience.
- When viewing or editing the TaroWorks Mobile User details, the pages don't load fully intermittently for both Admin and TaroWorks Users when an org is on the Winter '22 release. IDALMSA-11252
Cascading Selects
- Error "Apex heap size too large" Exception will occur when trying to clone a survey with over 5000 unique cascading select options IDALMSA-7734
- Cascading Selects cannot be in Repeat sections.
Field Mapping (in Jobs and Forms)
- Never delete or rename an object/field involved in Field Mapping.
- If you accidentally map to an object that's still In Development, Mobile Users will see a Generic Object Creator error. IDALMSA-6140.
- In addition, if a survey with a deleted field mapping is in both a published and a draft job, it cannot be auto-closed, and will continue to cause errors on mobile when trying to Sync. IDALMSA-5922.
- Owner Id relation does not appear in Field Mapping. IDALMSA-6839
- Submissions don't come in if they were synced after Auto-Closing of Survey due to Bad Field Mapping from another User. IDALMSA-8321
Forms and Form Results
- If you have a text answer where the first character is a comma, Survey Results will not work. Export to CSV to see results. IDALMSA-7735
Question Builder
- Odd behavior may occur in low bandwidth situations or when internet disconnects intermittently. Be careful when editing your survey. IDALMSA-2416
- Only 99 options can be added to a picklist type question on question builder, otherwise an error occurs IDALMSA-8518 IDALMSA-8531 IDALMSA-8532
Dynamic Operations Test Data
-
Dynamic Operations Validations on the TaroWorks mobile app only run when there is a response to a question. IDALMSA-11022
- An error is thrown intermittently when a form containing questions with Dynamic Operations test data is saved after updates are made, and the test data and all recent updates are lost. IDALMSA-11040
- When validating inputs for Dynamic Operations on a Date Only Questions on a Salesforce form, time is unexpectedly displayed on the result. However, time is not appended on the Mobile side of the form. IDALMSA-11078
- Values are not rounded to the nearest whole number on both Salesforce (when validating inputs with Dynamic Operations) and Mobile when Whole number questions are pre-populated from the calculation of decimal number questions. IDALMSA-11085
-
Limits on the use of the 'Contains' operator with Dynamic Operations
-
The contains operator will only have a successful save when used with multiselect questions with Dynamic Operations data validation on Salesforce. All other question types will have an error on save if they contain Dynamic Operations test data.
-
All questions can have contains operator and save will be successful on SF as long as the 'Test Dynamics operations' checkbox is not selected.
-
-
- Position check will be not done for questions referenced in Dynamic Operations when Dynamic Operation test data is added on a question.
Location Mapping
- Photos and Signatures created before upgrade to TaroWorks 4.3 will not display in maps. A script will need to be run in developer console. IDALMSA-7856
Salesforce Lightning
- Creating and sharing folders and dashboards is not yet available in Lightning - This will need to be done in SF Classic.
- TaroWorks UI and look and feel on Survey Manager in Lightning doesn't match what it is SF Classic IDALMSA-8523
- Jobs tab is not being set as landing tab for TaroWorks App in SF Lightning IDALMSA-8492
Mobile Money
- Date picker to schedule a Collections job on the Application settings page does not work on Mozilla versions that are below 56 IDALMSA-9560
General
- When query is executed using SF Standard API 'Invalid Field' error is thrown for standard objects fields IDALMSA-8862
-
There will be Profile level Permissions error whenever a user profile doesn't have access to TaroWorks Mobile User object and wants to make changes to user fields that are mapped the TaroWorks Mobile User object.
-
The workaround is to add the respective object and field access either to the user profile or Create a permission set extending the access for the TaroWorks Mobile User object. The permissions below should be added.
- TaroWorks Mobile user Object level : Read and Edit
-
TaroWorks Mobile user Field level fields access:
- Active
- Role
- Contact Name
-
The workaround is to add the respective object and field access either to the user profile or Create a permission set extending the access for the TaroWorks Mobile User object. The permissions below should be added.
- The Currency field not available to add to field sets for TaroWorks Mobile User object IDALMSA-10744
Comments
0 comments
Please sign in to leave a comment.