Submit error when change dropdown label

[sonytrinhcvn]

I just changed the label of dropdown and still keeping KEY but cannot add a new Unit, just got Lamda error.

check this commit

[sonytrinhcvn]

I've just updated the files following the guide here. But still got error, also please see lastest commit.

[franck-boullier]

Fix Step 1 DONE:

We need to make sure that the values in the table ut_role_types in the BZ database are also updated:

• 'Tenant' <--> 'Account Manager(Agent, FA)'
• 'Owner/Landlord' <--> 'PolicyHolder'
• 'Contractor' <--> 'Insurer'
• 'Management Company' <--> 'My Human Resource Manager'
• 'Agent' <--> 'Others'

Fix 1 did NOT fix the issue.

More information:

Details from the console:

BZ Db:

Working as expected:

• The new record for the policy is correctly inserted in the table ut_data_to_create_units
• The new product is created in the BZ side.
• All components are correctly created.
• All the groups we need to correctly manage permissions and accesses are created.

Issues/unexpected stuff:

• The existing user is NOT assigned to the role in the unit. No record in the table ut_invitation_api_data
• We have no record for that new policy/unit in the table ut_data_to_replace_dummy_roles

Mongo DB:

Working as expected:

• The new unit/policy is created as expected:
• All default assignee are created as expected using the new category names:
• We HAVE a pending invitation for the user who created that unit

Issues/unexpected stuff:

• The existing invitation for the user in the role for the new unit/policy is NOT processed as it should be.

Logs from Cloudwatch:

...
{
    "fields": {
        "app": "processinvitations",
        "commit": "1f48f08",
        "error": "sql: no rows in result set",
        "invite": {
            "_id": "kifEmBZCyhEGJXM8m",
            "caseId": 0,
            "invitedBy": 7,
            "invitee": 7,
            "isOccupant": false,
            "mefeInvitationIdIntValue": 27,
            "role": "My Account Manager",
            "type": "replace_default",
            "unitId": 30
        },
        "plugin": "relay",
        "region": "ap-southeast-1",
        "requestID": "c0648514-ecf5-469c-b0ba-90bebd1c4120",
        "stage": "production",
        "version": "29"
    },
    "level": "error",
    "timestamp": "2020-02-16T04:37:05.121056108Z",
    "message": "failed to run step1Insert"
}
{
...

Learning:

The issue seems to happen when we try to assign the user to the renamed role in the newly created unit.

To Do:

• Check the code for the Unee-T lambda API processinvitations to continue debugging.
• Double check the actual values we need to replace in the frontend code (this repo).

[franck-boullier]

@sonytrinhcvn what is the latest commit for a version that was working as expected (unit is created without the API error)?

[franck-boullier]

The values for the roles in the table ut_role_types were NOT consistent with the data in Mongo DB.

Replace the values for the roles in the table ut_role_types with the values we have in the Mongo DB:

• 'Tenant' <--> 'My Account Manager'
• 'Owner/Landlord' <--> 'PolicyHolder'
• 'Contractor' <--> 'My Insurer'
• 'Management Company' <--> 'My HR'
• 'Agent' <--> 'Other'

This fixed the issue . We are now able to create a new policy