TDXLib (TeamDynamix Python SDK)

TDXLib is a suite of Python libraries originally designed to take input from Google Sheets and create tickets in TeamDynamix based on the contents of the sheets. The scope of the project has broadened past its humble beginnings, and continues to do so whenever there's a feature we need that it doesn't currently support.

Quick Links

ReadTheDocs.io Documentation - TDXLib Class & Method descriptions
TeamDynamix API Documentation - Descriptions of all TDX API Endpoints

Dependencies

Required:

Python 3.6+
requests
python-dateutil
pyjwt

Quick-Start Guide

Installation

Download and install Python 3.6 or later. If you're new to Python, check out this setup tutorial. For an introduction to basic Python syntax and use, check out the guides on python.org

NOTE: although Python comes pre-installed on MacOS and many GNU/Linux systems, it's often version 2.7. For GNU/Linux, install python3 packages if available. For MacOS, check out homebrew.
OPTION 1: (Stable Release)

Install via pip using the following command:
```
  pip install tdxlib
```
This command will install any other required packages automatically.

Note: if you installed python3 packages, the Python v3 Pip may be called using pip3

OPTION 2: (Latest Code)
1. Clone or download TDXLib from GitHub.
  
  NOTE: If you use Option 2, the root folder of the repository will need to be your scripts' working directory so you can import TDXLib without making changes to your PYTHONPATH variable
2. Install the required dependencies to your environment using pip, which is bundled with Python 3.4+. If you run into issues on Windows, be sure that the location of your Python installation is specified in your system's PATH variable.
  
  The necessary packages are specified in requirements.txt and can be installed with pip
  
  If your OS comes with Python 2.7, use pip3 or whatever the name of the Python 3.6+ pip binary is on your system. A virtual environment can be helpful here:
```
pip install -r requirements.txt
```
  Alternatively, install all the packages manually:
```
pip install requests python-dateutil
```
  To get the libraries necessary to work with Google Sheets (as in the sample script), you can also install them with pip:
```
pip install gspread oauth2client
```

Making a TDXlib integration object

Start a Python console:
```
python
```
Import TDXLib into your scripting environment:
```
import tdxlib
```
To interact with the TDX API, you'll need to create an api integration object, through which all of the TDXLib commands are run. TDXLib currently supports two types of integrations:
- TDX Ticket Integration (Tickets, Ticket Tasks, etc.)
```
my_tdx_integration = tdxlib.tdx_ticket_integration.TDXTicketIntegration()
```
- TDX Asset Integration (Assets, CIs, etc.)
```
my_tdx_asset_integration = tdxlib.tdx_asset_integration.TDXAssetIntegration()
```
In order to store settings, TDXLib uses a INI-style configuration file. If there is no file set up in your working directory, TDXLib will walk you through the generation of one the first time you instantiate an integration object:
```
     $ python
     Python 3.7.3 (...) [...] on [...]
     Type "help", "copyright", "credits" or "license" for more information.
     >>> import tdxlib
     >>> tdx = tdxlib.tdx_ticket_integration.TDXTicketIntegration()
     No configuration file found. Please enter the following information:
     
     Please enter your TeamDynamix organization name.
     This is the teamdynamix.com subdomain that you use to access TeamDynamix. 
     Alternatively, enter the fully qualified DNS name of your TDX instance:
     Organization Name/FQDN ({orgname}.teamdynamix.com/{orgname}.university.edu): myuniversity
     
     Use Sandbox? [Y/N]: yes
     
     TDX API Username (tdxuser@orgname.com): myuser@myuniversity.edu
     
     TDXLib can store the password for the API user in the configuration file.
     This is convenient, but not very secure.
     Store password for myuser@myuniversity.edu? [Y/N]: no
     
     Tickets App ID (optional): 123
     
     Assets App ID (optional): 456
     
     TDXLib uses (mostly) intelligent caching to speed up API calls on repetitive operations.
     In very dynamic environments, TDXLib's caching can cause issues.
     Disable Caching? [Y/N]: no
     
     Initial settings saved to: tdxlib.ini
    
```
The generated file will look something like this:
```
 [TDX API Settings]
 'org_name': 'myuniversity',
 'full_host': 'its.myuniversity.edu',
 'sandbox': True,
 'username': 'myuser@university.edu',
 'password': 'Prompt',
 'ticket_app_id': '123',
 'asset_app_id': '456',
 'caching': True,
 'log_level': 'ERROR'
```
- The org_name field is whatever subdomain your organization uses to access TeamDynamix. For example, https://myuniversity.teamdynamix.com.
- The sandbox field specifies whether TDXLib should interact with a sandbox version of the TDX Environment, which is written over by production monthly. It is recommended to use the sandbox environment when first getting familiar with the API environment.
- The username and password fields are the login credentials for an account to be used with the TeamDynamix API. Many API endpoints (such as creating objects in TDX) require elevated permissions beyond the average user. You may need to create a user specifically for use with TDXLib and grant permissions based on what you need to do.
- If the password field is set to 'Prompt', then whenever a new integration object is made, it will request a password, and dispose of the password after getting an API token:
```
Enter the TDX Password for user myuser@myuniversity.edu (this password will not be stored):   
```
- The ticket_app_id and asset_app_id fields are the numbers that appear after Apps in your TeamDynamix URL, and are specific to your organization. You can find these ID's in the URLs in the following locations when using a TDX Tickets or Assets app through TDNext in your browser:
  - Tickets: https://myuniversity.teamdynamix.com/TDNext/Apps/{ticketAppId}/Tickets/...
  - Assets: https://myuniversity.teamdynamix.com/TDNext/Apps/{assetAppId}/Assets/...
- The caching field specifies whether or not TDXLib should cache TeamDynamix objects such as valid ticket types, statuses and priorities. Setting this option to True reduces the volume of API calls and allows TDXLib to perform some batch operations much faster.
- The log_level field specifies the python logging level that TDXLib will log at.
- The timezone field specifies the timezone you'd like TDXLib to operate in. TDXLib will translate date/time objects from TeamDyanmix in UTC to this timezone.

You can optionally specify an alternative configuration file that TDXLib should search for in your working directory. By default, it will look for tdxlib.ini.
```
  >>> tdx = tdx_ticket_integration.TDXTicketIntegration("specialconfig.ini")
```
Depending on your tdxlib.ini settings, you may be prompted for a password to authenticate into the TeamDynamix API. Once everything is working, go ahead and test out a method:
```
  >>> accounts = tdx.get_all_accounts()
```

TDXLib can also be configured directly by a python dictionary.

Settings passed in as a dictionary are overwritten by any values in a filename (and if no file name is passed, the default configuration file, tdxlib.ini in the working directory)

Use the following format for the dictionary configuration:
```
 config = {
      "org_name": "exampleorg",
      "sandbox": true,
      "auth_type": "password",
      "username": "someone@example.edu",
      "password": "a password",
      "ticket_app_id": 300,
      "asset_app_id": "",
      "caching": true,
      "timezone": "-0500",
      "log_level": "ERROR"
  }
 
```
The only required settings in this are org_name and either asset_app_id or ticket_app_id if you're creating TDXAssetIntegration or TDXTicketIntegration objects. If you set auth_type to password a username is also required. Unset settings will be defaulted per the values in tdxlib.tdx_constants.default_config.
TDXLib can also be configured via Environment variables. Any values passed in via dictionary, from a file, or in the default configuration file (tdxlib.ini in the working directory) override any values passed in as environment variables.

Here's a sample of environment variables you can use (they are the same as the config values for dictionary config, but uppercase and prefixed with TDXLIB_):
```
     export TDXLIB_ORG_NAME=exampleorg
     export TDXLIB_SANDBOX=true
     export TDXLIB_AUTH_TYPE=password
     export TDXLIB_USERNAME=someon@example.edu
     export TDXLIB_PASSWORD=mypassword
     export TDXLIB_TICKET_APP_ID=300
     export TDXLIB_ASSET_APP_ID=400
     export TDXLIB_CACHING=true
     export TDXLIB_TIMEZONE=-0500
     export TDXLIB_LOG_LEVEL=ERROR
```
Congratulations! You now have the power of the TeamDynamix API at your fingertips. For more detailed tutorials on how to use TDXLib to manipulate Tickets and Asset, as well as for information on the methods and classes included with TDXLib, check out our documentation on ReadtheDocs.io.

TDXLib Implementation status and Future Plans

TDXIntegration:

This base class that contains the methods necessary to authenticate to Teamdynamix. This class also contains methods to interact with TeamDyanamix objects that are universal across various Apps (Locations, People, Accounts, etc.)

Currently Implemented & Tested:
- Authentication (only simple auth, no loginadmin or SSO)
- Locations & Rooms (read-only)
- People & Groups (read-only) (no group members)
- Accounts (read-only)
- Custom attributes for Tickets & Assets (read-only)
- Import & Export of TDX-Style DateTime objects into python datetime objects
- Read-write support for Accounts
Future Plans:
- Read-write support for Locations, Rooms, People, Groups, and Custom Attributes (in progress)
- Support for custom attributes in Projects, CIs
- Support for manipulating attachments
- Support for inspecting/manipulating group members
- Support for inspecting/manipulating roles & user lists
- Support for mass-importing users from csv
Unlikely to be supported:
- Time entries
- Time types
TDXTicketIntegration:

The class (inherited from TDXIntegration) that allows interactions with Ticket objects.

Currently Implemented & Tested:
- Ticket Priorities
- Ticket Statuses (including creation of custom statuses) (WIP)
- Ticket Types
- Ticket Urgencies
- Ticket Sources
- Ticket Impacts
- Ticket Classifications (not available directly through API)
- Ticket Forms (not available directly through API)
- Tickets
  - Creation (including templated batch-creation from Google Sheets)
  - Editing (including batch-editing of multiple )
  - Manipulating
    - Rescheduling
    - Reassigning
  - Searching (by any attribute)
  - Updating
  - Getting Feed Items
  - Uploading Attachments
- Ticket Tasks
  - Creating
  - Editing
  - Deleting
  - Updating
  - Getting Feed Items
Future Plans:
- Tickets in combination with Assets
Unlikely to be supported:
- Blackout Windows
- Ticket Searches/Reports
TDXAssetIntegration:

The class (inherited from TDXIntegration) that allows interactions with Asset objects.

Currently Implemented & Tested:
- Assets
  - Creating
  - Editing
  - Searching
    - By Tag, SN, ID, Type, Owner, or any other attribute
  - Moving child assets fron one Asset to another
  - Copying attributes from one Asset to another
- Product Types
  - Creating
  - Editing
  - Searching
- Product Models
  - Creating
  - Editing
  - Searching
- Vendors
  - Creating
  - Searching
- Asset Forms
  - Searching
- Asset Statuses
  - Searching
Future Plans:
- Asset Statuses
  - Creating
  - Editing
- Product Models
  - Editing
- Vendors
  - Editing
  - Deleting
- Accepting Suggestions... (Submit an Issue!)

emmyoh/tdxlib

TDXLib (TeamDynamix Python SDK)

Quick Links

Dependencies

Required:

Quick-Start Guide

Installation

Making a TDXlib integration object

TDXLib Implementation status and Future Plans

TDXIntegration:

TDXTicketIntegration:

Currently Implemented & Tested:

Future Plans:

Unlikely to be supported:

TDXAssetIntegration:

Currently Implemented & Tested:

Future Plans: