This term can refer to the system object definition called Account, that can be used for tracking various amounts of money allocated for specific purposes.
It can also refer to the TeamConnect records that store the User and Group information, such as name, password, rights and so on. User and Group Accounts can be accessed only by the designated users, such as TeamConnect administrators, on the Admin tab.
There are two types of actions in TeamConnect—wizard actions and rule actions.
A wizard page action is an action that is triggered by a page transition in a Wizard. For example, when a user is creating a Record using a wizard, the wizard can do one of the following actions:
- Populate a field in the record with a specified value.
- Execute a Java class file, which can create another record, do a calculation, or do another task automatically.
For more details about wizard actions, see Creating Custom Pages.
A rule action is an action that TeamConnect performs when a Rule is triggered in TeamConnect. Depending on the type of rule, the action that the rule executes could be the following:
- Deny the user the ability to do an operation, such as delete, post, void, update, or create a Record, and display a message to the user.
- Allow the user to do one of the operations above (in other words, do nothing).
- Send the record into a Route of users who can approve or reject the operation attempted by the user.
For more details about rule actions, see the Rule Actions.
These are rights that control access to all features in TeamConnect that can be accessed by the Admin tab in the user interface. These include object definition, lookup tables, routes, home pages, system settings, and so on.
Administrator (TeamConnectAdmin User)
A user whose job responsibilities include creating or maintaining user and group accounts, specifying the appropriate system settings for the organization, creating and/or maintaining system- wide Home Pages and Portal Panes, and making minor changes to the system design if necessary. These responsibilities are reflected by the Admin Rights assigned to this user accordingly.
Application Program Interface, a set of routines, protocols, and tools for building software applications.
TeamConnect's API can be used for customizing TeamConnect. You can use the API for purposes such as creating Java rules, integration with other systems, and enhancing the capabilities of various areas of TeamConnect, such as Home Pages.
See Custom Action.
A definition of a system or audit log. Appenders can be of various types, including SMTP, socket and file. File appenders are the most commonly used, as the logging statements are simply captured in a file. A log can be a general TeamConnect log, or it can be associated with a specific logger, so that it captures messages only from a certain TeamConnect area, such as portal panes or custom blocks.
A small utility written in Java. In TeamConnect, applets can be used for the document screen interface. If applets are enabled on the system, users can enable them for their own use on the Preferences tab of the Preferences screen.
A term used in the previous versions of TeamConnect to refer to Custom Objects, namely, the objects that are created for your organization.
For more details on custom objects, see Creating Custom Pages.
A System Object definition that is intended to allow end Users to track their scheduled events, engagements, or meetings. Appointments are automatically available as a system Block in Object Views for Custom Objects.
The approval process is the major component of TeamConnect Workflow. Authorization from one or more designated users (known as approvers), which is required for certain actions that are attempted by other users. For example, deleting a matter, posting an invoice, or changing the phase of a matter could require approval and therefore trigger an approval process. When users trigger an approval process, they are considered requestors in the approval process. Users' attempted actions are completed upon their final approval.
A type of TeamConnect rule, that allows you to define Conditions that when an action requiring an Approval is attempted by a user, it is automatically routed to the designated Approvers. The approval process is defined with the use of a Route.
Designated Users who have the authority to approve or reject certain actions attempted by other users who do not have the permission to complete these actions. There can be several approvers at each level of the Approval process. This approval level is also known as an approval Stop, which is a component of a Route. During an approval process, approvers may be able to send the approval request to reviewers for review before they make their decision. Approvers can view their approval requests on the My Approvals screen.
TeamConnect Users who are assigned to one or more Projects or Tasks. There can be one or several users assigned to a project. In projects each assignee can have a different role, such as attorney, agent, appraiser, paralegal, and so on. Typically, the main assignee is in charge of the whole project, whereas the rest of the assigned users are responsible for certain parts of the project. Tasks can have only one current assignee.
TeamConnect Users and members of Contact Groups (Address Books) who are expected to take part in an event, such as a meeting or conference call, for which there is an Appointment scheduled. Designer contact groups are called Address Books in the end-user interface.
Building blocks of Objects, which represent data entered by end users. Attributes correspond to columns within tables in the database.
For example, every Custom Object consists of over a dozen attributes, all of which are listed in the main database table for that object: mainAssignee, createdOn, CreatedBy, ClosedOn, defaultCategory, and so on. The corresponding collection of data constitutes an object record.
You use attributes to identify their corresponding fields when working in various areas of TeamConnect, such as Search Views, Rules, and Wizards. To navigate through selecting the necessary attributes, you can use a tool called Object Navigator. For details, see Using Object Navigator.
Settings for tracking the actions of users—which screens they access, which selections they make in the screens they visit, when they log in and log out, and other actions.