Item | Definition |
|---|---|
access permissions | Rules defining the access rights to resources. Access permissions can be granted to any combination of namespaces, groups, or users. Examples of resources are reports and folders. |
agent | The object type created and edited by Event Studio. An agent contains the event condition and the associated tasks to perform. Once defined, an agent can be scheduled to check for instances of the event. |
authentication | The process of verifying the identity of users when they log on. Users must be authenticated before they can be authorized to use any secured resources. |
burst | To create many report results by running a single report once. For example, you can create a report that shows sales for each employee, and run it once, sending different results to regional managers by bursting on region. You set up bursting in Report Studio and enable it in the portal. |
contact | A named email address to which reports and agent emails can be sent. Contacts are never authenticated. |
content locale | A code that is used to set the language or dialect used for browsers, report text, and so on; and the regional preferences, such as formats for time, date, money, money expressions, and time of day. For Reporting products, you can specify a locale for the product interface (product locale) and for the data in the report (content locale). |
credentials | Information stored about the identity of a Reporting user, usually a user name and password. You can assign your credentials to someone else so that they can use resources that you are authorized to use. Credentials are created for Reporting components. If a user schedules or programs an action, then credentials must be stored in the content store. |
deployment | The process of moving a ACI application (reports, models, and so on) to a different instance of ACI. For example, you often create reports in a test environment and then deploy them to production. When you deploy an application, you export, transfer, and import it. |
event | An exceptional item of data, defined by specifying a query expression against items in a package. When data is detected matching the event condition, it causes an agent to perform tasks. |
group | In security, a list of users or other groups that can be used to assign access permissions and capabilities. Groups can be referenced from third-party authentication sources or can be local to ACI. Local groups are managed from the administration portal. The list of groups that an authentication user is a member of is part of the users passport for a ACI session. In reporting, grouping is the action of organizing common values of query item together and only displaying the value once. Headers and footers often appear after each instance of a common value in a grouped column |
job | A group of runnable objects, such as reports, agents, and other jobs that you run and schedule as a batch. |
locale | A code that is used to set the language or dialect used for browsers, report text, and so on; and the regional preferences, such as formats for time, date, money, money expressions, and time of day. For Reporting products, you can specify a locale for the product interface (product locale) and for the data in the report (content locale). |
metric | A measurement of performance in key areas of a business that compares current results to planned values. |
metric package | An ATG Reporting Center representation of a Metric Studio application. A metric package contains connection information, reports, and metric management tasks for that application. |
model | A physical or business representation of the structure of the data from one or more data sources. A model describes data objects, structure, and grouping, as well as relationships and security. A model, called a design model, is created and maintained in Framework Manager. The design model or a subset of the design model must be published to the ACI server as a package for users to create and run reports. |
namespace | For authentication and access control, a configured instance of an authentication provider. Allows access to user and group information. In XML, a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names. In Framework Manager, namespaces uniquely identify query items, query subjects, and so on. You import different databases into separate namespaces to avoid duplicate names. |
package | A subset of a model, which can be the whole model, to be made available to the ACI server. For Metric Studio users, see metric package. |
portlet | A mechanism for displaying Web content as part of a portal page. |
product locale | The code or setting that specifies what language, regional settings, or both to use for parts of the product interface, such as menu commands. |
publish | To expose all or part of a Framework Manager model via a package to the ACI server, so that Reporting BI Users can use it to create reports and other content. |
report | A set of data deliberately laid out to communicate business information. Depending on the context, “report” may refer to report specification or report output. Report (more precisely, report specification) is the generic term for the objects created by edited by Query Studio, Report Studio, and Analysis Studio. |
report output | A report output combines data at the point in time when the report was run with a report specification. It is a document that can be displayed, printed or emailed. ACI can produce report outputs in HTML, PDF, Excel, or CSV formats. |
report specification | The definition of queries, prompts, layouts, and styles that make up a report. A report specification is combined with data by a run operation to create report outputs. You create report specifications by using Report Studio, Query Studio, Analysis Studio, or through the Software Development Kit. |
report view | A reference to another report that has its own properties, such as prompt values, schedules, and results. You use report views to share a report specification instead of making copies of it. |
really simple syndication | See rich site summary. |
rich site summary | An industry standard format for displaying transient data, such as breaking news, in a web page or standalone viewer. ATG Reporting Center includes a portlet type for displaying RSS format data. This can be used to display data from a public RSS service or to display news items generated by agents detecting events. A synonym for Really Simple Syndication. |
session | The time during which an authenticated user is logged on to ACI. |
user | A person accessing a ACI application. Authenticated user definitions and information, such as first and last names, passwords, IDs, locales, and email addresses, are maintained in third-party authentication sources. Other user information, such as the location of personal folders or preferred formats for viewing reports, is stored in ACI. |
Web Services for Remote Portlets | A standard for creating presentation-oriented Web services so that they can be easily integrated within other applications, such as Web portals. |
