Date: Thu, 28 Mar 2024 08:26:43 -0700 (PDT) Message-ID: <358797355.3.1711639603751@ip-172-30-17-85.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2_1576943468.1711639603742" ------=_Part_2_1576943468.1711639603742 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This table provides defini= tions of important technical concepts in Agiloft.
Concept | Brief Explanation |
---|---|
Administrator |
An administrator is a user who belongs to at least one group that is an = administrator group. Administrators use the advanced capabilities of Agiloft to create, administer, and mai= ntain knowledgebases. See: Administrator Guide. |
Knowledgebase (KB) |
A knowledgebase (KB) is a particular deployment of Agiloft. It contains = the entire collection of tables, records, teams, groups, views, reports, an= d associated data. A given Agiloft installation may include multiple KBs, but each KB is lo= gically independent. Knowledgebases can be exported as a single file in XML= format and imported onto another server. The system administrator of one K= B cannot overwrite another. |
Field |
Fields represent the different types of infor= mation stored within tables, such as a telephone number. Fields correspond = to columns in the database and in table views. See: Fields. |
Record |
A collection of field values. See: Working with Records. |
Workflow |
Workflows control record states and the rules= that apply when a record moves from one state to another. It may refer to = the graphical workflow editor used to create and manage workflows in the Ta= ble wizard. See: Workflows. |
Table |
Tables organize your information within the k= nowledgebase. A table is the whole set of fields, relationships, and rules = on which individual records are based. Tables represent an object = ;in the database with columns, or fields, and rows, or records. Knowl= edgebases typically contain several different standard and custom tables, s= uch as Leads, Users, Companies, Support Cases, Contracts, and so on. See:&n= bsp;Tables. |
Subtable |
Subtables are made up of specifically defined= records within a larger table. Tables can be hierarchical and inherit fiel= ds and rules from their parents. For example, Employees and External Users = might be subtables of the People table, in which case they would automatica= lly contain all the fields from People table as well as their own unique fi= elds. |
Grouping | A grouping is a set of tables or items wit= h a similar function. For example, your knowledgebase might have a Contract= Management grouping that contains the Contracts, Approvals, Attachments, a= nd Tasks tables. |
Nav Bar | The nav bar is at the top of the knowledgebase a= nd displays the menu icon, tables, and other navigation options, such as th= e Last Opened list, My Assigned records, and Chart Collections. See: Nav Bar |
Group |
Groups help secure your instance of Agiloft by defining the access permi= ssions that each user has. Group permissions define which tables, records, = and fields that users may view or edit, as well as their access to special = menu permissions like exporting and setup options. See: Groups. |
Team |
Teams are used to i= dentify working units of users, such as those that share a role in the syst= em. Teams are used to send email notifications, define working hours, and d= etermine aspects of the interface such as Views<= /a> and Saved Searches. Users = are assigned to a Primary Team and additional teams if necessary. See: = ;Teams. |
Report |
A summary of record information that may be p= resented in graphical, HTML, text, or Excel format. See: Reporting. |
Search |
A filter applied to a table to find specific = information. For example "Find all Support Contracts that are due to expire= within the next 30 days". See: Se= arching. |
Table View | A table vi= ew is what users see when they click on a table from the Left Pane. It incl= udes a view of the records contained within the table as well as the table = name, table summary, action bar, and table search block. See: Table View. |
View |
A view determines which fields from a type of= record are shown in a list of records in the table view. Views can include= row coloring by issue, search filters, and custom column settings. For exa= mple, a "Company Name, End Date, and Value" view would show those specific = fields from Contracts. See: Views.= |
Rule |
A statement of business logic that Agiloft executes automatically. See:&= nbsp;Rules and Workflows. |
Wizard |
A wizard is a series of screens and tabs in which you can select options= for configuring a specific part of the system. When working in any Agiloft= wizard, the left side of the screen has a description of each option, as w= ell as tips and guidance and links to additional information. Wizards are m= ost often used by Agiloft administrators. |
Power User | A power user is a user who belongs to at least o= ne group that is a Power User group. Power users can access charts and repo= rts and edit other people=E2=80=99s records. They require an assigned power= -user or floating power-user license. See: Power User Guide. |
End User | An end user is a user who belongs only to a grou= p that is an End User group. End users cannot edit other people=E2=80=99s r= ecords. They may use an unlimited end-user license. |