The following glossary contains terms that are relevant to BMC Helix Platform:
In BMC Helix Platform Cognitive Service, accuracy is the ratio of number of correct predictions to the total number of input samples.
|action button||A predefined view component available in the View Designer, that lets you perform an action in a view definition. For example, you can create action buttons in a view definition for saving the view, deleting a record instance, launching a URL, and so on.|
|alias||An alias is a placeholder for a tenant-specific configuration for connectors or RESTful services.|
|ancestor group||A top-level group within the hierarchy, with one or more subgroups associated with it. An ancestor group can be attached to one or more user groups.|
|application||A type of bundle that provides business functionality to the users. Remedy customers, partners, and software developers who need business functionality can create and use applications.|
|application license||A license that is application-specific and is required for using an application.|
|application scoped definition||A definition which is used only within the same application and within the same customization layer in which the definition is created. This definition cannot be customized by a user of the application or accessed by custom definitions, even if the custom definitions are within the same application.|
An association lets you define a relationship between the record definitions. While creating a record association, you specify the cardinality and the constraint for the association.
Defines relationships between records and relates record instances.
|assignment policy||Specifies the sequential rules for automatically assigning the application requests.|
Specifies the rules for identifying the correct assignee when automatically assigning the application requests. The assignment rules are based on foundation data. As per the assignment rules, BMC Helix Platform identifies the correct assignee for the request. If multiple assignees are available, the predefined assignment methods are used to identify an assignee for the request.
|assignment process||Defines and executes the business logic as a flow of usable set of activities and conditional gateways for assigning requests. The assignment process trigger the assignment rules.|
A read-only record that gets created when the record auditing is enabled. Whenever the source record is modified, BMC Helix Platform records the audit data from the source record to a new read-only audit record.
|BMC application||An application having Author Type value as 1, which is assigned by a developer using Maven license command.|
|BMC Modern Shell||A special built-in configurable View that exists for all Application bundles. It is used as the outer container of an Application that creates an entry point for users to access the application on the Web.|
A bundle consists of the following properties:
|bulk data loading|
The process of copying the Foundation data sets from template Excel spreadsheets and loading the data sets to BMC Helix Platform.
|container||A built-in view component available in the View Designer, that lets you define the layout for a region of a view that can include view components or nested containers.|
Provides access to complex document types and rich media
|context Key||A context key is a unique identifier that you can assign to a process instance. You can use the context key to identify a process and to find out the context in which the process is activated. Typically the context key is set by means of a process input parameter with some meaningful value. For example, an Approval Process that has a context key as HPD0002340 indicates that the Incident request HPD0002340 started the Approval Process. A context key can be a text value or a record type only. You can search a process instance using the context key. Once the system displays all process instances|
|custom application||An application having Author Type value as 3, which is assigned by a developer using Maven license command.|
|Developer ID||Uniquely identifies the organization creating the smart bundle. Each organization developing a Digital Service application must have a Developer ID. When you create a Bundle project using archetype, a Developer ID is assigned to the smart bundle by the archetype.|
Every definition deployed with the smart bundle has a Developer ID property which is used to identify the organization that creates the definition.
|Data Caching Service|
BMC Helix Platform provides a Data Caching Service (com.bmc.arsys.rx.services.cache.CacheService) to enable applications to cache data, metadata, and configuration items. The cache is created during application deployment and when the data entries are created.
A single tenant environment is renamed to dedicated system. A dedicated system is an environment that contains only one tenant identified by the tenant's domain name, such as example.com.
|deployment package||A zip file containing the compiled OSGI bundle jar and the bundle's definition file. It is produced using the maven "package" command.|
|descendant group||A child group within the hierarchy, that is attached to an ancestor group. A child group can be attached to only one ancestor group.|
|development deployment||Once a bundle is compiled and packaged using the maven commands, it's Deployment Package is deployed to a development server using the -Pdeployoption.|
|development Server||A dedicated system with a configured developer-id, ready to be used for Development Deployment of bundles. Such a system is NOT used for production use.|
BMC Helix Platform Foundation library, direct affiliation is an association between two foundation data elements where the one foundation data element is a part of or associated with the second foundation data element.
For example, when you create a direct affiliation between person and support organization such as Support Groups, the affiliation implies that the associated person works for, or reports to the manager of the support organization and performs task for that support organization.
A package created by using BMC Helix Innovation Studio, which contains only the customized definitions and configuration data. You cannot include application code in an export package.
The export package is used by administrators to deploy the application's tailoring changes only to test or production environments.
|extension record definition||A regular record definition with fields that you want to add to the record definitions and view definitions that are not customizable.|
|extension view definition||A view definition that displays the fields added in the extension record definition and the fields in view that is not customizable (view that is being extended).|
|extension association definition||A direct association between the extension record definition and the record definition that is not customizable (record definition that is being extended).|
|extension Container||A view component that can be added to the view that is not customizable (view that is being extended).|
In BMC Helix Platform Cognitive Service, F-score is the harmonic average of precision and recall. F-score reaches its best value at 1 (indicating perfect precision and recall) and worst at 0.
|hierarchical group||Defines the relationship of user groups with each other and rank them according to the level of importance or authority. A hierarchical group is headed by an ancestor group with descendant groups beneath it. At each level above the bottom of the hierarchy, the descendant groups themselves can be ancestor groups.|
In a record definition, an index is a list of record fields that are frequently searched. Indexes reduce the database search time and optimize the performance of your Digital Service application by returning search results faster. You can index the fields that users frequently search for. However, you should use indexes carefully, as adding too many indexes to a single record definition may lead to performance degradation.
For example, a record definition for 'Task' can include an index based on the 'Assignee' field.
In BMC Helix Platform Foundation library, an indirect affiliation is an association between two foundation data elements where the one foundation data element is not a part of or not associated with the second foundation data element, but can access data from the second foundation data element
For example, when you create an indirect affiliation between person and support organization such as Support Groups, the affiliation implies that the associated person does not work for, or reports to the manager of the support organization but performs task for that support organization.
|inner join record||This type of join record combines only the matching data from multiple records. An inner join searches for fields that have corresponding values in the multiple records and then combines the matching data to form a join record. If a field does not have a corresponding value in any one of the record, then that field is omitted from the join record.|
BMC Helix Platform license
This is a one-time platform license required for using BMC Helix Innovation Studio.
BMC Helix Platform SDK
|A zip file containing the Java libraries and maven infrastructure to build and deploy projects onto a Development Server. Indirectly it includes API documentation and sample code as well.|
A package created from BMC Helix Innovation Studio, which contains the entire application data, such as code, definitions, and configurations. The install package is used by application business analysts or developers to:
A join record definition is a combination of data that is retrieved from multiple record definitions. Join record definitions are similar to database joins.
Join records lets you perform the following operations:
Join records are further divided into the inner join or outer join records.
A type of bundle that provides a reusable building block for developing applications. A library is a subset of an application. Remedy customers, partners, and software developers who are building applications can create and use libraries.
|library scoped definition||A definition which is used only within the same library and within the same customization layer in which the definition is created. This definition cannot be customized by a user of the application or accessed by custom definitions, even if the custom definitions are within the same library.|
|named list definition||A reusable list of data that you can associate with a record field to make data entry faster and more accurate.|
|named list service|
Provides the specified set of valid options for the record fields.
|named license||This license is always associated with a user name and is always reserved for that user. A Named user license enables a user to create, modify, save requests besides reading the requests.|
Node Side is a parameter used for disassociating one-to-many record instances. Node Side specifies the left side or right side record definition in an association. There can be only two values for the Node Side parameter:
Node A: Left side record definition in the Association
Node B: Right side record definition in the Association
|palette||The available types of behavioral tasks, flows, and other elements that can be used in the Process Designer.|
An application whose Author Type value is 2, which is assigned by a developer using Maven license command.
In BMC Helix Platform Cognitive Service, precision is the number of correct positive results divided by the total number of relevant samples.
|process definition||An application service that performs application business logic and achieves the application purpose.|
Defines and executes the business logic as a flow of are usable set of activities and conditional gateways.
|production deployment||A Deployment Package is deployed to a Production Server using the BundleDeployment.bat utility, where it can then be configured and tailored.|
|production server||A shared system ready for Production Deployment of bundles, and configuration / tailoring by administrators. This system is not used for development.|
|public scoped definition||A definition which is used by all applications or libraries. The definition can be customized by configuring the customization options for the definition.|
In BMC Helix Platform Cognitive Service, recall is the number of correct positive results divided by the number of positive results predicted by the cognitive service.
|record editor||A built-in view component available in the View Designer, that lets you create record instances or modify existing record instances from the view definition.|
|record editor inputs||Record Editor Inputs are used to add the record fields to the record that is associated with the record editor.|
Units of information that collectively form a record definition. A single record definition consists of multiple fields, and each field has its own attributes.
|record grid||A built-in view component available in the View Designer. Record grid is used to display the record fields in a tabular format on the user interface of the application.|
Record instance is the data created by the application for which the structure of the data is specified by the record definition.
For example, a 'Task' record definition can consist of the following record instances:
Defines business entities of a data model.
Manages record instances by performingSCRUD(Search, Create, Read, Update, Delete) operations on data
A record definition is a collection of the data required for building the application for your business process. A record definition is made up of specific record fields.
|rule definition||A rule, along with a process, models the business logic of an application. The purpose of a rule is to perform data validation, and interact with a process on record events or timer events.|
Defines conditions with certain actions to enforce business constraints.
In a hierarchical group, a security label is used to dynamically control record and field access. The label can be populated with group names through a rule or a process. Security labels protect your database tables at the row level, by assigning different levels of security. Only those users with the appropriate permissions can access the row data.
For example, in a car dealership company, you create security labels like car type, sales group, or dealership, and only users with the appropriate security classification are allowed access to the relevant data.
|scope||Defines if the application is limited to be used within the Digital Service application or library or can be used by any other application or library.|
Multitenant environment is renamed to shared system. A shared system is an environment that includes one or more tenants identified by their domain names for each user, such as example.com and example1.com.
Customize the smart bundle to suit your environment and business requirements. The following tasks are involved when you tailor a smart bundle:
A package created from BMC Helix Innovation Studio, which contains only the incremental changes for an application. Importing configuration data is optional.
The update package is used by application business analysts or developers to:
|unique record Id||Helps to identify a record internally in an application and move the application data from environment 1 to environment 2. It also ensures that the Id of a record is the same, regardless of the environment from where you load Foundation data.|
In BMC Helix Innovation Studio, a view definition is a graphical representation of your application. You use the view definitions to design the user interface for applications. For example, a view definition called Tracking Item, which will be used to create and update Item Console records.
Defines the user interface of a standard application.
|webhook definition||An HTTP callback mechanism to receive real-time event notifications. Administrators can register applications to the Webhook to receive notifications or data when a record event takes place.|