Beta - May 15th Release

Bug fixing:

• API to see cases - Category is Missing. See #787
• API to see cases - Next Step Date is missing. See #788

Beta - May 14th Release

New functionalities:

API Key to retrieve cases for a given user

See PR #780
The API is documented on the Unee-T API documentation.

Input:

API key for the user

Ouput:

list of the cases that this user is allowed to see.
the format is

{
	"unitId": String,
	"name": String,
	"cases": 
		[{
			"assignee": 
				{
					"userId": String,
					"name": String,
					"role": String
				},
			"reporter": 
				{
					"userId": String,
					"name": String,
					"role": String
				},
			"caseId": int,
			"involvedList": 
				[
					{
						"userId": String,
						"name": String,
						"role": String
					},
					{
						"userId": String,
						"name": String,
						"role": String
					}
				],
			"userRelevance": 
				[
					String
				],
			"creationTime": String (Date in ISO format),
			"subCategory": String,
			"solutionDeadline": String (Date in ISO format),
			"nextSteps": String,
			"title": String,
			"solution": String
		}]
}

API Key to retrieve units for a given user:

Include the Role of the user in that unit.
It can be one of the following 5 possibilities:

• Contractor
• Management Company
• Tenant
• Landlord/Owner
• Agent

The payload is now:

{
        "_id": String (ObjectId),
        "displayName": String,
        "unitType": String (enum),
        "createdAt": String (Date in ISO format),
        "streetAddress": String,
        "city": String,
        "zipCode": String,
        "state": String,
        "country": String,
        "moreInfo": String
        "designatedRole": String
    }

Beta - May 8th Release

New Functionalities:

See PR #774 and issue #773

API Key for each individual user:

When a user is created in the Unee-T Enterprise interface (aka via the MEFE API CREATE_USER) we now return a unique MEFE API for that user.
This API key can be used to get information from Unee-T via our REST API.

API to get information from Unee-T :

Input:

API key for the user

Output:

list of the unit that this user is allowed to see.
the format is

{
        "_id": String (ObjectId),
        "displayName": String,
        "unitType": String (enum),
        "createdAt": String (Date in ISO format),
        "streetAddress": String,
        "city": String,
        "zipCode": String,
        "state": String,
        "country": String,
        "moreInfo": String
    }

Bug fix:

When we do an update of a unit, if the field in the payload is empty, then the field in the database will be empty too.

Beta - May 6th Release - Hotfix

Hotfix:

• hotfix: height indexing with unit's bz name instead of id- critical

Beta - May 6th Release

Performance improvements:

• Make sure we are using INT instead of VARCHAR for indexes and select that involve outside variables.
  See
  • #unee-t/bz-database#128
  • Int id for collation fix (#770)

Beta - May 2nd Release

Bug Fix:

• Fix an edge case scenario in the MEFE API remove_user_from_unit

Beta - April 22th Release

Improvements:

• Links to case in notifications are now magic links if the user has not yet set a password for Unee-T #758

Bug Fix:

• User role removal check relies on ownership and creatorId #760 (#761)

Beta - April 16th Release - Hotfix

Hotfix:

• Make sure tests are working as intended

Beta - April 16th Release

Improvements:

• Optimize case notifications perf (#755)
• Better logs on the MEFE.

Beta - April 10th Release - Hotfix

Bug fixing:

• feat: removed "ready" sub handle usage to prevent retries on failure (#754). Prevent endless spinning wheel in the MEFE