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, 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 display state.

Record

An individual instance of a System Object or Custom Object in TeamConnect, created and accessed in the user interface. Note that Custom Object records are sometimes generically referred to as Projects.

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.

Related Objects

Objects that are in one way or another are associated with other objects in TeamConnect, either using hierarchical relations (child-parent, Involved, Embedded Objects), or non-hierarchical relations established in Custom Fields of type Custom Object.

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 in them because a Record cannot be saved. Depending on the end-user TeamConnect configuration, required field labels might be identified in the user interface in red (or other color different from the default text color), or other special formatting applied to the label text, such as bold or italics.

You can make Custom Fields required by specifying them as such when you create them. You can also make fields required only under certain conditions, with the use of Rules.

Resources

Resources are means and/or facilities necessary for conducting an event, for which an Appointment has been scheduled. For example, you might need to book a particular conference room or a projector.

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

Privileges or permissions to use information that taken together constitute security at different levels, object, category, and individual Record. In TeamConnect, access rights ensure that no record information can be read and/or compromised by unauthorized individuals. Typically, rights are assigned by the TeamConnect system Administrator to individual Users and/or Groups.

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 hierarchy of users whose Approval is required to authorize a requested operation. It is an approval path that can consist of one or more nodes, called Stops, that can contain one or more Members who can approve or reject the operation. Routes are used for the Workflow purposes, to control the actions that take place in 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.