githubbob42 / mingle2github2

0 stars 1 forks source link

eForm does not display in Mobile #4709

Closed githubbob42 closed 7 years ago

githubbob42 commented 7 years ago

Mingle Card: 5056 Steps to Reproduce

| | |
|-|-|
|**Version #**|

FieldFX™ 4.0.1.3704 4.0.1.3689 on 9.1.4

(sandbox.fieldfx.com)

   |
|**Hardware**|Laptop|
|**OS**|Windows 10|
|**Browser**|Windows Chrome 57.0.2987.133|
|**Username**|tjones.mobile@shawcor.fieldfx.com.fsb|
|**Password**|Use LastPass (Tom has control of it)|
|ORG ID|00DV000000890JN|
|User ID| |
|RayGun Error ID| |
  1. Log into Mobile as user above.
  2. Go to Ticket, T-47C-888-16A6.
  3. Go to Forms and click on any existing eForm.

Expected Result

The eForm details should render.

Actual Result

Blank screen.

NOTE: You may get a Sync Incomplete error on 3689.  This is covered by Mobile Mingle #5055 and does not appear to adversely affect the defect described in this card.  This defect was also reproduced on version 3620 without the sync incomplete error.  This, along with #5055 is preventing Shawcor (DesertNDT) from going live with Sync V4.

UPDATE 4/28/2017 (Scott Mercer): I did a little further troubleshooting and found that the URL that is being generated for the eForm card has “Manual” in it instead of the eForm API Name, which should be “RPQ__c”.  If I edit the URL to include the correct object name, the details render correctly.

Also, I am not sure if this is related or not, but the eForm Config is configured to show the RPQ “Computed RPQ” eForm Record Type on the “CRT_Inspection” Ticket Record Type.  However, when I go to add a new RPQ eForm on a “CRT Inspection” ticket, it allows me to add both RPQ record types instead of “Computed RPQ”.  If this is a separate and isolated issue, I can write it up separately on a new Mingle card.

Analysis

CC: There’s a naming collision between a field (called Type__c) and a view model property we use to hold the record type. Since we use fuzzy matching on field names in the xhref binding, we end up using the field instead of the view model property. 

You can work around this issue by renaming the field Type__c to something else. We’ll issue a fix to ensure we don’t have any collisions.

Steps to reproduce for qafield@test4.com:

* In back Office, add a field named Type__c to an fx-form (such as Inspection__c)

* In Mobile, Open a ticket (I'm using T-45E-BEB-76EB

* Navigate to forms tab

* Click + button to add new form

* Fill in required fields

* Type a value into the field labelled "Type" (any text will do)

* Hit the + button to add the form

* Navigate back to the ticket's list of forms (quickest way to do that is by clicking the "Forms" link in the header: Tickets > T-45E-BEB-76EB > Forms > Form Name

* You should see the forms list with an entry for the new form you've added

* click the form in the list

* the page links to a blank screen with no links back - broken!

Related Cards

Test Plan

githubbob42 commented 7 years ago

Godswill : 05/17/2017 10:27 CDT Test Result: Pass Version #: FieldFX™ 4.0.1.pr2398 on 9.1.4 Hardware: Ipad, Macbook, Android tablet OS: iOS 10.3.2, MacOS 10.12.4 (16E195), Android 6.0.1 Browser: Version 58.0.3029.81 (64-bit) Username qafield@test4.com Password Use LastPass

githubbob42 commented 7 years ago

Pull Request #2398