desk_api 0.5.8 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 377a97983e2ace11f11987c8613ff3fedadcac9d
-  data.tar.gz: 1abd58b7426e200881ed64f4442bac2d3e3596c3
+  metadata.gz: 6883196206272d0b4c6d3bb2f05162fc54b69f2f
+  data.tar.gz: ee8ed10269afb814092436c08fe175a630c6e152
 SHA512:
-  metadata.gz: b5b702677936f9850abd90eadee90b2610ce7e4115425eb0d9f48a40f40724a0b3d842b98de3a2438160d9421ab7328d720b7ca22d12fbb328ec2a9910285239
-  data.tar.gz: 013ca94e41377209aab11cb2c5e8a08149a42e140794d9530a25cb0806a5d68a5cf393fd8e48c6f5f83326ee5d597886bb7b0e691a338cac59b0fb8a8ccc0f76
+  metadata.gz: 0be30c22b23542152d31eb01cd93eaae53eee661c775792922db110069084e1ef579a669edb72c98e95f44eaf1768f4ada722f2ee153a2131057bbe2d544b830
+  data.tar.gz: d8570d5cffca4ab9b65b77d5ac6ab06f1e6f0490cde0fa28f868f2a6fe71a723f7718b1386cb88460e2b8098895872c45fbcc97694f45a5aebdf926684ee81ee

data/LICENSE

@@ -1,7 +1,7 @@
-Copyright (c) 2013 Thomas Stachl <tom@desk.com>
+Copyright (c) 2013-2014 Thomas Stachl <tstachl@salesforce.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,56 +1,183 @@
-# desk.com APIv2 [![Build Status](https://secure.travis-ci.org/tstachl/desk.png)](http://travis-ci.org/tstachl/desk) [![Coverage Status](https://coveralls.io/repos/tstachl/desk/badge.png?branch=develop)](https://coveralls.io/r/tstachl/desk?branch=develop) [![Dependency Status](https://gemnasium.com/tstachl/desk.png)](https://gemnasium.com/tstachl/desk)
+# DeskApi a client for APIv2
 
-desk.com has released v2 of their REST API a few months ago and provides a lot more functionality. You should read up on the current progress of the [API](http://dev.desk.com/API/changelog). This library wraps all of it into an easy to use ruby module. We'll try to keep up with the changes of the API but things might still break unexpectedly.
+[![Build Status](https://secure.travis-ci.org/tstachl/desk_api.png)](http://travis-ci.org/tstachl/desk_api)
+[![Coverage Status](https://coveralls.io/repos/tstachl/desk_api/badge.png?branch=develop)](https://coveralls.io/r/tstachl/desk_api?branch=develop)
+[![Dependency Status](https://gemnasium.com/tstachl/desk_api.png)](https://gemnasium.com/tstachl/desk_api)
 
-## Installation
+___
+## An Awesomely Unofficial Desk API Client
+___
+
+DeskApi takes the capabilities of the Desk.com API and wraps them up in a Ruby
+client so that it's easy-as-pie to get working with your support site's API.
+
+Desk publishes a changelog monthly, which you can keep up with at
+[dev.desk.com/API/changelog](http://dev.desk.com/API/changelog).
+
+We do our best to keep DeskApi, but please
+don't hesitate to open an [issue](https://github.com/tstachl/desk/issues) or send a [pull request](https://github.com/tstachl/desk/pulls) if you find a bug or would like to new functionality added.
+
+
+___
+## Getting Started
+___
+
+### Installation
+Easy!
 
 ```ruby
 gem install desk_api
 ```
+___
+### Configuration
 
-## Example
-This example shows you how to create a new client and establish a connection to the API. It shows the four request methods supported by the desk.com API (`GET`, `POST`, `PATCH` and `DELETE`).
+There are two different ways to configure DeskApi to send and receive requests:
+
+#### First Configuration Option
+
+Configure `DeskApi` itself to send/receive requests by calling the `configure` 
+method to set up your authentication credentials:
 
 ```ruby
-# Basic Auth
-client = DeskApi::Client.new username: 'thomas@example.com', password: 'somepassword', subdomain: 'devel'
-# OAuth
+DeskApi.configure do |config|
+  # basic authentication
+  config.username = 'thomas@example.com'
+  config.password = 'somepassword'
+
+  # oauth configuration
+  config.token           = 'TOKEN'
+  config.token_secret    = 'TOKEN_SECRET'
+  config.consumer_key    = 'CONSUMER_KEY'
+  config.consumer_secret = 'CONSUMER_SECRET'
+
+  config.endpoint = 'https://devel.desk.com'
+end
+
+DeskApi.get '/api/v2/topics'
+DeskApi.post '/api/v2/topics', name: 'My new Topic', allow_questions: true
+DeskApi.patch '/api/v2/topics/1', name: 'Changed the Topic Name'
+DeskApi.delete '/api/v2/topics/1'
+```
+
+#### Second Configuration Option
+
+Initialize a new `DeskApi::Client` to send/receive requests
+
+This example shows you how to initialize a new client and the four main request
+methods supported by the Desk.com API (`GET`, `POST`, `PATCH` and `DELETE`).
+
+```ruby
+# basic authentication
+client = DeskApi::Client.new username: 'thomas@example.com', password: 'somepassword', endpoint: 'https://devel.desk.com'
+# oauth configuration
 client = DeskApi::Client.new({
   token: 'TOKEN',
   token_secret: 'TOKEN_SECRET',
   consumer_key: 'CONSUMER_KEY',
   consumer_secret: 'CONSUMER_SECRET',
-  subdomain: 'devel'
+  endpoint: 'https://devel.desk.com'
 })
 
 response = client.get '/api/v2/topics'
 response = client.post '/api/v2/topics', name: 'My new Topic', allow_questions: true
 response = client.patch '/api/v2/topics/1', name: 'Changed the Topic Name'
-response = client.delete '/api/v2/topics/1' 
+response = client.delete '/api/v2/topics/1'
 ```
 
-For ease of use and if you only create one connection to the desk.com API you can use `DeskApi` directly:
+
+___
+## Resources
+___
+
+Resources are automatically discovered by the DeskApi. When requesting a
+resource from DeskAPI, the client sends the request and returns a
+`DeskApi::Resource`. If the client receives an error back from the API a
+`DeskApi::Error` is raised.
+
+___
+### Create Read Update Delete
+
+One of the most important features; we support creating, updating and deleting
+resources but not all resources can be deleted or updated or created, if that's
+the case for the resource you're trying to update, it'll throw a
+`DeskApi::Error::MethodNotAllowed` error. For ease of use and because we wanted
+to build as less business logic into the wrapper as possible, all of the methods
+are defined on each `DeskApi::Resource` and will be sent to desk.com. However
+the API might respond with an error if you do things that aren't supported.
 
 ```ruby
-DeskApi.configure do |config|
-  config.username = 'thomas@example.com'
-  config.password = 'somepassword'
-  config.subdomain = 'devel'
+# let's create an article
+new_article = DeskApi.articles.create({
+                subject: 'Some Subject',
+                body: 'Some Body',
+                _links: {
+                  topic: DeskApi.topics.first.get_self
+                }
+              })
+
+# as you can see here a `Resource' always includes a method `.get_self'
+# which will return the link object to build relationships
+
+# updating the article
+updated_article = new_article.update subject: 'Updated Subject'
+
+# deleting the article
+if updated_article.delete == true
+  # article has been deleted
 end
 
-DeskApi.get '/api/v2/topics'
-DeskApi.post '/api/v2/topics', name: 'My new Topic', allow_questions: true
-DeskApi.patch '/api/v2/topics/1', name: 'Changed the Topic Name'
-DeskApi.delete '/api/v2/topics/1'
+# ATTENTION: Cases can not be deleted!
+begin
+  DeskApi.cases.first.delete
+rescue DeskApi::Error::MethodNotAllowed => e
+  # too bad
+end
 ```
+___
+### Getters & Setters
+
+As you have seen in prior examples for each field on the resource we create a
+getter and setter.
+
+```ruby
+customer = DeskApi.customers.find(1)
 
-## Working with Resources and Collections
+puts customer.first_name
+puts customer.last_name
+puts customer.title
 
-The API supports RESTful resources and so does this wrapper. These resources are automatically discovered, meaning you can navigate around without having to worry about anything. We also support two finder methods `by_url` and `find`.
+# for updates you can either use the setter or a hash
 
-### Finders
+customer.first_name = 'John'
+customer.last_name = 'Doe'
+
+updated_customer = customer.update title: 'Master of the Universe'
+
+# users are not updatable
+begin
+  user = DeskApi.users.first
+  user.update name: 'Not updateable'
+rescue DeskApi::Error::MethodNotAllowed
+  # too bad
+end
+```
+___
+### Find
+
+The method `by_url` can be called on the client, for backwards compatability we
+haven't yet removed it from the `DeskApi::Resource` but it will be removed once
+we release v1 of this client. `by_url` will return a lazy loaded instance of the
+resource.
+
+```ruby
+first_reply = DeskApi.by_url '/api/v2/cases/1/replies/1'
+```
 
-The method `by_url` can be called on all `DeskApi::Resource` instances and will return a lazy loaded instance of the resource. Since the update to v0.5 of the API wrapper the `find` method can now be called on all `DeskApi::Resource` instances too. _Gotcha:_ It will rebuild the base path based on the resource/collection it is called on. So if you call it on the cases collection `DeskApi.cases.find 1` the path will look like this: `/api/v2/cases/:id`.
+Since the update to v0.5 of the API wrapper the `find` method can now be called
+on all `DeskApi::Resource` instances. _Gotcha:_ It will rebuild the base path
+based on the resource/collection it is called on. So if you call it on the cases
+collection `DeskApi.cases.find 1` the path will look like this:
+`/api/v2/cases/:id`.
 
 | Method                                                      | Path                        |
 | ----------------------------------------------------------- | --------------------------- |
@@ -60,10 +187,11 @@ The method `by_url` can be called on all `DeskApi::Resource` instances and will
 | `DeskApi.cases.search(subject: 'Test').entries.find(1)`     | `/api/v2/cases/1`           |
 | `DeskApi.cases.entries.first.replies.find(1)`               | `/api/v2/cases/1/replies/1` |
 | `DeskApi.cases.entries.first.replies.entries.first.find(1)` | `/api/v2/cases/1/replies/1` |
-
+___
 ### Pagination
 
-As mentioned above you can also navigate between resources and pages of collections. _Please Notice:_ `DeskApi.cases` doesn't behave like an `Array` any longer, it's just a `DeskApi::Resource` so links like `next`, `previous`, `first` and `last` can be called directly. However you'll have to request the `entries` before you can loop through all the records on the page.
+As mentioned above you can also navigate between resources and pages of
+collections.
 
 ```ruby
 cases = DeskApi.cases
@@ -86,10 +214,29 @@ last_page = previous_page.last
 # or go to the first page
 first_page = last_page.first
 ```
+___
+### `all` and `each_page`
+
+As a recent addition we made it even easier to navigate through all the pages.
 
+```ruby
+DeskApi.cases.all do |current_case, current_page_number|
+  # do something with the case
+end
+
+DeskApi.cases.each_page do |current_page, current_page_number|
+  # do something with the current page
+end
+```
+
+Both methods use the max `per_page` for the API endpoint for that particular
+resource.
+___
 ### List params
 
-Some lists allow for additional params like [cases](http://dev.desk.com/API/cases/#list). This allows you to filter the cases endpoint by using a `company_id`, `customer_id` or `filter_id` list param.
+Some lists allow for additional params like [cases](http://dev.desk.com/API/cases/#list).
+This allows you to filter the cases endpoint by using a `company_id`,
+`customer_id` or `filter_id` list param.
 
 ```ruby
 # fetch cases for the company with id 1
@@ -101,130 +248,124 @@ customers_cases = DeskApi.cases(customer_id: 1)
 # fetch cases for the filter with id 1
 filters_cases = DeskApi.cases(filter_id: 1)
 ```
-
+___
 ### Sorting
 
-A recent update on APIv2 now imposes a maximum page limit. This is why sorting got very important and now you can even sort the list endpoints like [cases](http://dev.desk.com/API/cases/#list).
+There is a maximum `page` limit on some Desk.com API endpoints. As of right now
+(May 2014) the limit is 500 for all endpoints that are limited, but please
+consult the #list documentation for each resource:
+
+- [Case list](http://dev.desk.com/API/cases#list)
+- [Company Case list](http://dev.desk.com/API/companies#cases-list)
+- [Customer Case list](http://dev.desk.com/API/customers#cases-list)
+- [Filter Case list](http://dev.desk.com/API/filters#list-cases)
+- [Case search](http://dev.desk.com/API/cases#search)
+- [Customer search](http://dev.desk.com/API/customers#search)
+- [Company search](http://dev.desk.com/API/companies#search)
+- [Article search](http://dev.desk.com/API/articles#search)
+
+
+To work around page limits, you can specify `sort_field` and `sort_direction`
 
 ```ruby
 # fetch cases sorted by updated_at direction desc
 sorted_cases = DeskApi.cases(sort_field: :updated_at, sort_direction: :desc)
 ```
-
+___
 ### Links
 
-Pagination is pretty obvious but the cool part about pagination or rather resources is the auto-linking. As soon as the resource has a link defined, it'll be navigatable:
+Once a `DeskApi::Resource` has loaded, its [linked resources](http://dev.desk.com/API/using-the-api/#relationships) can be retrieved
+by calling the linked resource as a method of the `DeskApi::Resource`, e.g., 
 
 ```ruby
-# get the customer of the first case of the first page
-customer = DeskApi.cases.entries.first.customer
-
-# who sent the first outbound reply of the first email
-user_name = DeskApi.cases.entries.select do |my_case| 
-  my_case.type == 'email'
-end.first.replies.entries.select do |reply|
-  reply.direction == 'out'
-end.first.sent_by.name
+# Get a ticket
+ticket = DeskApi.cases.entries.first
+
+# Get the ticket's assigned_user from the ticket
+assigned_user = ticket.assigned_user
+
+# Get the customer from the ticket
+customer = ticket.customer
+
+# Get the customer's company from the customer.
+company = customer.company
+
+# Getting the name of the user who sent the first outbound reply on a ticket
+user_name = DeskApi.
+              cases.
+              entries.
+              select { |my_case| my_case.type == 'email' }.
+              first.
+              replies.
+              entries.select { |reply| reply.direction == 'out' }.
+              first.
+              sent_by.
+              name
 ```
-
+___
 ### Lazy loading
 
-Collections and resources in general are lazily loaded, meaning if you request the cases `DeskApi.cases` no actual request will be set off until you actually request data. Meaning only necessary requests are sent which will keep the request count low - [desk.com rate limit](http://dev.desk.com/API/using-the-api/#rate-limits).
+Resources are lazy loaded. This means that requests are only sent when you
+request data from the resource. This helps a lot with flying under the Desk.com
+API [rate limit](http://dev.desk.com/API/using-the-api/#rate-limits). E.g.,
 
 ```ruby
 DeskApi.cases.page(10).per_page(50).entries.each do |my_case|
-  # in this method chain `.entries' is the first method that acutally sends a request
+  # in this method chain, no HTTP request is fired until `.entries'
 end
 
 # however if you request the current page numer and the resource is not loaded
 # it'll send a request
 DeskApi.cases.page == 1
 ```
+___
+### Embedding
 
-### Side loading
+Some endpoints support [embedding](http://dev.desk.com/API/using-the-api/#embedding) related resources. E.g., when getting a list
+of cases from `/api/v2/cases` you can embed the customer on each case by adding
+`embed=` to the query string: `/api/v2/cases?embed=customer`
 
-APIv2 has a lot of great new features but the one I'm most excited about is side loading or embedding resources. You basically request one resource and tell the API to embed sub resources, eg. you need cases but also want to have the `assigned_user` - instead of requesting all cases and the `assigned_user` for each of those cases (30 cases = 31 API requests) you can now embed `assigned_user` into your cases list view (1 API request).
+The client supports this: `tickets_and_customers = DeskApi.cases.embed(:customer)`
 
-Of course we had to bring this awesomeness into the API wrapper as soon as possible, so here you go:
+Taking advantage of `.embed` is a great way to be conscious of the rate limit
+and minimize necessary HTTP requests.
 
-```ruby
-# fetch cases with their respective customers
-cases = DeskApi.cases.embed(:customer)
-customer = cases.first.customer
 
-# you can use this feature in finders too
-my_case = DeskApi.cases.find(1, embed: :customer)
-# OR
-my_case = DeskApi.cases.find(1, embed: [:customer, :assigned_user, :assigned_group, :message])
+**Not using embedded resources**
+```ruby
+tickets = DeskApi.cases.per_page(100).entries # HTTP request
+tickets.each do |ticket|
+  puts ticket.customer.first_name # HTTP request (100 iterations)
+end
 
-customer = my_case.customer
-assigned_user = my_case.assigned_user
-assigned_group = my_case.assigned_group
+# Total Requests: 101
 ```
 
-### Create, Update and Delete
-
-Of course we support creating, updating and deleting resources but not all resources can be deleted or updated or created, if that's the case for the resource you're trying to update, it'll throw a `DeskApi::Error::MethodNotAllowed` error. For ease of use and because we wanted to build as less business logic into the wrapper as possible, all of the methods are defined on each `DeskApi::Resource` and will be sent to desk.com. However the API might respond with an error if you do things that aren't supported.
-
+**Using embedded resources**
 ```ruby
-# let's create an article
-new_article = DeskApi.articles.create({
-                subject: 'Some Subject',
-                body: 'Some Body',
-                _links: {
-                  topic: DeskApi.topics.first.get_self
-                }
-              })
-
-# as you can see here a `Resource' always includes a method `.get_self'
-# which will return the link object to build relationships
-
-# updating the article
-updated_article = new_article.update subject: 'Updated Subject'
-
-# deleting the article
-if updated_article.delete == true
-  # article has been deleted
+tickets = DeskApi.cases.per_page(100).embed(:customer).entries # HTTP request
+tickets.each do |ticket|
+  puts ticket.customer.first_name # No HTTP Request, customer is embedded
 end
 
-# ATTENTION: Cases can not be deleted!
-begin
-  DeskApi.cases.first.delete
-rescue DeskApi::Error::MethodNotAllowed => e
-  # too bad
-end
+# Total Requests: 1
 ```
 
-### Getters & Setters
-
-As you have seen in prior examples for each field on the resource we create a getter and setter.
-
+**Using embedded resources in `find`**
 ```ruby
-customer = DeskApi.customers.find(1)
-
-puts customer.first_name
-puts customer.last_name
-puts customer.title
-
-# for updates you can either use the setter or a hash
-
-customer.first_name = 'John'
-customer.last_name = 'Doe'
-
-updated_customer = customer.update title: 'Master of the Universe'
+my_case = DeskApi.cases.find(1, embed: :customer)
+# OR
+my_case = DeskApi.cases.find(1, embed: [:customer, :assigned_user, :assigned_group, :message])
 
-# users are not updatable
-begin
-  user = DeskApi.users.first
-  user.update name: 'Not updateable'
-rescue DeskApi::Error::MethodNotAllowed
-  # too bad
-end
+customer = my_case.customer
+assigned_user = my_case.assigned_user
+assigned_group = my_case.assigned_group
 ```
-
+___
 ### API Errors
 
-Sometimes the API is going to return errors, eg. Validation Error. In these cases we wrap the API error into a `DeskApi::Error`. Here are the common errors:
+Sometimes the API is going to return errors, eg. Validation Error. In these
+cases we wrap the API error into a `DeskApi::Error`. Here are the common errors:
 
 ```ruby
 DeskApi::Error::BadRequest             #=> 400 Status
@@ -239,19 +380,32 @@ DeskApi::Error::UnprocessableEntity    #=> 422 Status
 DeskApi::Error::TooManyRequests        #=> 429 Status
 ```
 
-Please also have a look at all [desk.com API errors](http://dev.desk.com/API/using-the-api/#status-codes) and their respective meanings.
+Please also have a look at all
+[desk.com API errors](http://dev.desk.com/API/using-the-api/#status-codes) and
+their respective meanings.
 
+___
 ## License
+___
 
 (The MIT License)
 
-Copyright (c) 2013 Thomas Stachl <thomas@desk.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-[![Bitdeli Badge](https://d2weczhvl823v0.cloudfront.net/tstachl/desk/trend.png)](https://bitdeli.com/free "Bitdeli Badge")
-
+Copyright (c) 2013-2014 Thomas Stachl <tstachl@salesforce.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the 'Software'), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.