Starting Out

When using SBM Composer, it is important that you understand the basic terminology and how to navigate the interface.

• Key Terminology

  • Process App – A process app comprises one or more applications and orchestrations.
  • Blueprint File – A file that is created by SBM Composer and contains process app design elements, which include roles, scripts, icons, tables, workflows, and orchestrations. This file is deployable to any database.
  • Orchestration – A container to collect related orchestration workflows as part of a process app.
  • Application – A collection of elements that work together in an interactive business process to solve a business requirement, such as managing a team's work tasks or tracking customer support calls. Applications typically contain workflows, fields, forms, roles, projects, reports, and notifications. Applications can include orchestrations that emit events that execute activities in other tools or applications. Orchestrations can be used to combine applications and create process apps.
  • Role – A collection of application-related privileges. Roles provide one way to assign multiple SBM privileges to users and groups. Users and groups may have different roles in different projects, and a user or group can be assigned to multiple roles. Examples of the types of permissions associated with a role are the ability to read and update fields; the ability to perform specified actions on items, attachments, notes, and reports; and the ability to specify access to, or restriction from, certain transitions. Designers create roles in SBM Composer as part of a process app, which can comprise multiple applications. The roles span the applications within the process app.
  • Forms – The pages in the SBM User Workspace in which users submit, transition, and update items. Designers can use quick forms or create custom forms for states and transitions.
  • Transitions – A key element of workflows, transitions activate a primary item's movement from state to state in the workflow process.
  • States – A key element of a workflow, states are positions that a primary item resides in while moving through the workflow process. States can also be considered a stopping point along a workflow's path.
  • Workflow – A collection of states, transitions, and fields that define an organization's tracking process.
  • Deployment – The process by which a developer or an administrator makes a process app defined in SBM Composer available on a host environment. The deployment can be performed from SBM Composer or SBM Application Administrator.
  • SBM Application Repository – An SBM Application Administrator component that provides versioning capabilities, including check-in, checkout, and labeling for design elements and process apps created in SBM Application Administrator. Version management capabilities allow application designers to collaborate on the creation of design elements.

See the Tutorial for a video about the SBM Composer user interface.