Articles in this section

See more

TaroWorks 7.3.x (Salesforce) Release Notes

Avatar
TaroWorks Support
  • Updated
Follow

Release(s)

What's New

  • Multi-lingual DDH Filters - Ability to add record filters when translations are activated for fields used in DDH
  • Performance Module restored - We are excited to announce that the performance module, which was temporarily unavailable in TW 7.1.x and 7.2.x versions, has been restored in TaroWorks app version 7.3! Track and analyze key performance metrics, such as productivity, efficiency, and quality, to make data-driven decisions and optimize your workflow. (This is for Partner Community Licensed Mobile Users only and excludes Platform and Salesforce Licensed Mobile Users)
  • Salesforce API Upgrade - TaroWorks App now supports the latest Salesforce API version 57.0.

Mobile Compatibility

  • Works with app version 7.3

Mobile

Upgrade Instructions to 7.3.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
  • Long text field not displaying all lines on Mobile  IBTFF-4312
  • New! The date/time picker does not appear when the SF user attempts to select a start and finish date in the filter section of the Job Activities tab.  IDALMSA-12306
  • New! Missing field level access to remote library field of Question object on TW app after upgrading to TW 7.3.x apk IDALMSA-12332

 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 Currency field not available to add to field sets for TaroWorks Mobile User object IDALMSA-10744 

Programmatic Interface to Forms (SF Built-in APIs)

  • API user can insert 'matchingField' and/or update the 'matchingField' with an invalid value and no error message will be returned on the response body. In addition, the Question Mapping will not be created on the survey builder page in SF and the user would have to update this manually. IDALMSA-12093
  • API user can insert a skip condition where the sourceQuestion is inside a repeat section (sourceQuestion should strictly be inside a regular section) and no error message will be returned on the response body. IDALMSA-12130
  • Error: “No Validation Can be Set on a Hidden Question” when API user tries to insert a form where Maximum, Minimum and ResponseValidation are set to “”. IDALMSA-12256
  • If an API user passes no value for "maximum" and "minimum" question parameters, the default is set to empty string. If the user passes empty string (as an API user will do for the POST requests to insert objects and PATCH requests to update them) it changes to 0. IDALMSA-12107
  • API user can delete the parent form mapping objects and leave orphaned ORM (Object Relationship Mapping records that do not have an associated parent record). IDALMSA-12077
  • API user can create question mapping for more than 1 repeat section. As a result, on the field mapping tab in SF, both repeat sections will be non-editable and when the SF user tries to click save an error occurs 'FIELD_CUSTOM_VALIDATION_EXCEPTION' IDALMSA-12090
  • API user can create a new section with duplicate position number. IDALMSA-11951
  • API user can update or insert a form without a name field or with an empty string for a name field and no error or warning is returned to the user. IDALMSA-12036
  • API user can insert and update a skip logic condition of a question to reference a “future/next” question as opposed to a previous question. IDALMSA-12063
  • API user can enter skipValue as 'Text' in skip logic condition for whole/decimal number question. IDALMSA-12068
  • API user can insert or update the position of questions with 0 and -1 values. IDALMSA-12210
  • API user can insert Object Relationship Mapping for the same parent and child multiple times with no warning or error message issued. IDALMSA-12099
  • Built-In APIs don't return the externalID in the response body for POST/PATCH requests.. IDALMSA-11957
  • API user can update forms in closed and published status. IDALMSA-12000 and IDALMSA-12024

Related articles

Comments

0 comments

Please sign in to leave a comment.