IFS Cloud glossary
Use this short reference alongside the lessons. These introductory definitions are drafts awaiting expert review; consult the linked IFS documentation for release-specific detail.
Configuration
Section titled “Configuration”Adapting a solution through the available designers and configuration tools. See choose a tailoring approach.
Configuration context
Section titled “Configuration context”The context associated with configured page changes. Confirm the intended context before planning a change. See Page Designer documentation.
Custom attribute
Section titled “Custom attribute”Additional information defined for an entity. A persistent attribute stores a value; a read-only attribute obtains related or calculated information. See understand custom attributes.
Customer solution
Section titled “Customer solution”The selected IFS components and tailoring that make up a customer’s solution. It is useful to distinguish this from the platform’s overall capabilities.
Entity
Section titled “Entity”A modeled business object whose attributes describe its data. In our introductory examples, think about the object that owns a value before thinking about the page that displays it.
IFS Cloud Web
Section titled “IFS Cloud Web”The browser interface through which users access IFS Cloud functionality.
An overview page that brings together information for a user’s work.
Page Designer
Section titled “Page Designer”A tool for adapting configurable page layouts and behavior. See plan a page change.
Tailoring
Section titled “Tailoring”Adapting a solution through configuration, extending on the inside, or extending on the outside. See the IFS tailoring guide.
Application Configuration Package (ACP)
Section titled “Application Configuration Package (ACP)”A group of related configurations managed together, for example when moving a change between environments. See plan a configuration package.
Permission set
Section titled “Permission set”An access definition that participates in the roles and grants available to users. Effective access can include indirect grants through a structure. See understand permission sets.
Access token
Section titled “Access token”A bearer credential proving a request’s identity to an API, obtained separately from a person’s interactive login. A valid token proves who is calling, not what they are allowed to do. See authentication and access.
An opaque value identifying a record’s current state, used to detect concurrent changes on an update. A rejected update with a mismatched ETag means the record changed since it was read, not that the request was malformed. See writing data.
Integration identity
Section titled “Integration identity”A dedicated, non-personal user and client credential used by an external system to call IFS Cloud APIs. Keeping it separate from personal logins makes access easier to scope, audit, and revoke. See authentication and access.
Projection
Section titled “Projection”An application service model used to expose a supported set of data and operations. Discover the actual contract in your environment rather than guessing it from a page name. See API discovery.
Correlation identifier
Section titled “Correlation identifier”A value used to connect observations about the same operation across systems. It helps an investigator follow a request and its outcome. See integration reliability.
Pagination
Section titled “Pagination”Returning a collection in portions rather than one response. A result limit does not prove that all matching records have been returned. Follow the service’s documented continuation behavior. See query shaping.
Regression test
Section titled “Regression test”A check that existing behavior still works after a change. It complements tests of the new behavior. See build a test matrix.
Smoke test
Section titled “Smoke test”A small set of checks used immediately after a delivery to confirm essential behavior. It does not replace the full test evidence. See release handover.