Minor maintenance release:
Removed mistakenly documented by oDesk but not working API call for getting team adjustments.
Fixed engagements API call, so that you can call client.hr.get_engagements() without any parameter to get all engagements for authorized user.
oTask API strongly reworked, from now Task Codes are renamed to Activities and it’s behavior is changed:
- Activity now is assigned to the engagement ID. It will appear it user’s oDesk Team Client only if it was assigned to the user’s engagement.
- You cannot delete activity. You can archive it and unarchive if necessary.
- Activities are created on the team level, you can create a company level activities by passing team_id that is equal to company_id (which is parent__team_id). There’s a methods for this already, please see the reference documentation. Note that archived activity has empty engagements list, so if you decide to unarchive an activity, you need to do an extra update call to assign the activity to someone.
- When creating/updating activities you can pass optional engagements parameter, that should be a list of engagements that will be assigned to the Activity. Otherwise the activity won’t be assigned to anyone. If you want to assign created/updated activity to all engagements in the company, you can set the all_in_company parameter.
- update_batch_tasks call is marked as experimental, use it on your own risk. It will be reworked in future.
October 2013
Backwards incompatibility changes:
Improvements:
Nov 2012
May 2011
October 2010
29 September 2010
Bug fix release
15 July 2010
Bug fix release