# Changes to the Term, Course, and Section models; introduces a Session

## Changes to the Term, Course, and Section models; introduces a Session

| Version      | 1.3.4      |
| ------------ | ---------- |
| Release Date | 2018-06-29 |

## Key features <a href="#id-20171005engage2.20.8hotfix-keyfeatures" id="id-20171005engage2.20.8hotfix-keyfeatures"></a>

This release introduces changes to the Term, Course, and Section models with corresponding changes to a University's data integration feeds. The release also introduces a new Session model with its own integration feed. Please see our data integration documentation for a description of the changes.

## Details <a href="#id-20180629ordertool1.3.4changestotheterm-course-andsectionmodels-introducesasessionmodel-details" id="id-20180629ordertool1.3.4changestotheterm-course-andsectionmodels-introducesasessionmodel-details"></a>

* **Sessions** - The Order Tool now understands an Institution's Terms and Sessions, enabling an ordering experience closer to faculty, instructor, and course coordinator expectations.
* **Courses** - have become Course offerings in 1.3, enabling a better modeling of instructional offerings and their relations to Sessions and Terms.
* **The Section model has new data attributes!** - These include a Label, Section number, Class number, and Section type. The last element –Section type– will not be used in the UI in 1.3.0 but will drive future features that optimize ordering by Section type.
* **Section label** - Institutions may now specify the label used to describe a section to users. This gives Institution's the ability to customize a section label in a way that makes sense for their users.
* **Bill after date** - The Session model includes a "bill\_after\_date" attribute that institutions must provide. For any given Session, this date indicates the point in the Session after which Unizin invoices institutions for their digital course materials.

## Known Issues

None.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.unizin.org/products/content/unizin-order-tool/release-notes/2018-06-29-order-tool-1.3.4-changes-to-the-term-course-and-section-models-introduces-a-session-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.