Read-only Access

Record-level security state in which the record cannot be modified as a result of the rights assigned to it or for workflow reasons, for example, when the record is pending approval, and the approval rule prevents anyone from modifying the record. This relates to Record Security and not to the Read-only Mode display state.

Read-only Mode

A state of a record in which you cannot modify it. Records in Read-only mode can be switched to Edit mode if you have the appropriate Rights.

Reassignment Tool

A feature to move tasks or assignments from one person to another.

Recompile

A "Recompile" button triggers the process of rebuilding or recompiling code, allowing any recent changes to be applied and errors to be checked without requiring a full restart of the application. For more information, click here.

Record

A record is a collection of data about something or someone with reference to a particular matter, such as a lawsuit, meeting, or financial transaction, saved in the database. Records have a number and a name assigned to identify the record in the database and help you search for it.

Record Security

Access protection set at the level of individual object records. For example, you can make a Record Private or Public or you can grant or deny the rights to read, update, and delete a record to other Users or Groups. This level of security can be set only on the Security tabs of individual records in the end-user interface. This is the lowest level of access rights. All rights assigned at this level take effect only if the appropriate rights are assigned at the object level.

Rejection

Denial of an Approval request to do a user-attempted operation by members of a Route. If the operation is rejected, this is noted on the Workflow tab of the Record.

Relation

An association between one record and another. They are typically displayed as hyperlinks on the screen, and can be established through Search Module fields, or the Relations tab.

Relations Block

A section in TeamConnect that shows relationships between different records (e.g., linking a project to related contracts or people).

Related Records/Objects

Associated records that can be accessed from within other records (often collectively referred to as `parent records') by clicking hyperlinks. Often they may be represented by a separate tab or section in the parent record, which has the structure of a Search Screen. For example, appointments, tasks, histories, expenses, documents, milestones, involved, and accounts are related records within Projects.

Repository 

In the TeamConnect Web Service environment, each entity has a corresponding repository class that supports operations for working with records of that entity type. For example, the ContactRepository provides methods for inserting a contact, updating a contact, reading a contact, searching contacts, deleting a contact from a TeamConnect system.

Request

An attempted operation by a user that is not completed until it has been approved by the approvers in a specified approval route. A request can be tracked by the requestor, the approvers who receive the request, and possibly a Process Manager, if one is specified for that approval process.

Requestor

A user who performs an action that triggers an approval process, such as posting an invoice, voiding an invoice, or changing the phase of a project (such as a matter). The request is sent to approvers according to the approval route that is defined for that workflow process. The requestor's request is approved or rejected by the approvers. Requestors can view the progress of their requests on the My Requests screen. They can also cancel a request if necessary.

Required Fields

Fields that must have a value entered or selected in them to save the record. TeamConnect typically indicates which fields are required whenever you attempt to save a record with no values in the required fields. The labels of required fields, by default, are displayed in red with an asterisk next to them. You can change the display settings for required fields through the Appearance options accessible from the Options drop-down list on the Main menu bar.

Reserve

A type of Account where the money is allocated from the Budget for the settlement of matters, such as paying outside counsel fees and other costs accrued while working on a matter, or an amount set aside for claim payments.

Resources

Means and facilities necessary for conducting an event, for which an appointment has been scheduled. For example, you may need to book a conference room or a projector.

Revert Line Items

The selected adjusted line item(s) are reverted to the previous state when a line item is Reverted.

Reviewer

A user who is asked by an approver to review an approval request. Reviewers are not approvers, so they do not approve or reject the request. They can provide feedback to the approver who makes a decision in the process. Reviewers can view their requests for review on the My Approvals screen.

Rights

Permissions to perform operations in TeamConnect, such as accessing, creating, updating (editing), and deleting whole records or parts of them. Rights are assigned to you by your TeamConnect system administrator based on your role within the organization.

Root

The top Category in the categories hierarchy tree. It is always automatically added to every record in TeamConnect. In Projects, this category has the same name as the object itself.

Route

A defined path of users whose Approval is required to authorize an operation in TeamConnect, such as posting an invoice. The path can consist of one or more Stops, that can each contain one or more members who can approve or reject the operation. Routes are used for Workflow purposes, to help define and control your business processes.

Rules

Business Workflow requirements that allow you to depend on TeamConnect to ensure that the proper processes, which are specific to your industry and organization, are maintained by users.

TeamConnect allows you to create rules that control whether the operations attempted by users are in accordance with your business processes. A rule is triggered when the operation is attempted, and the Qualifiers are checked to determine what should occur. For example, rules can ensure that certain Custom Fields are filled out if a particular Category is selected.

Approval rules postpone the operation until all members in the approval process, or Route, have approved the operation.

Rules written using Java class files or JavaScript can also perform Automated Actions when they are triggered.