ProcessMaker Developers Documentation
processmaker.comKnowledge CenterProcessMaker University
Guides
Guides
  • Getting Started
    • Installing ProcessMaker
  • Authentication
    • Creating a Client Application
    • Getting an Access Token
    • Getting a Refresh Token
  • Working with the API
    • Starting a Request via REST API
    • Starting a Request via Web Hook
  • Embedding Forms
    • Starting a Request via Anonymous Web Entry
    • Participating in a Workflow via Intermediate Web Entry (Anonymous)
    • Participating in a workflow via Intermediate Web Entry (Authenticated)
    • Angular Inbox Tutorial
      • Part 0: Overview
      • Part 1: Hello World
      • Part 2: Services & Dependencies
      • Part 3: Components
      • Part 4: The Inbox
      • Part 5: The Screen & Form Elements
  • Script Task Examples
    • PHP
  • Packages
    • ProcessMaker Platform Packages
      • Actions By Email Package
      • Advanced Screens Package
      • Advanced User Package
      • Auth Package
      • C# Package
      • Collections Package
      • Comments Package
      • Conversational Forms Package
      • Data Connector Package
      • Decision Tables Package
      • Documentation Package
      • DocuSign Package
      • Dynamic UI Package
      • File Manager Package
      • Google Places Package
      • IDP Package
      • Java Package
      • PDF Generator Package
      • PM Blocks Package
      • Process Optimization Package
      • Python Package
      • R Package
      • Saved Searches Package
      • Send Email Package
      • Signature Package
      • Slack Notification Package
      • Translations Package
      • Versioning Package
      • Vocabularies Package
      • Web Entry Package
    • Custom Packages
      • The Package Skeleton
      • Creating Your First ProcessMaker Package
Powered by GitBook
On this page
  1. Packages
  2. ProcessMaker Platform Packages

Vocabularies Package

Maintain uniform JSON schemas for all ProcessMaker Platform assets in your organization.

PreviousVersioning PackageNextWeb Entry Package

Last updated 1 year ago

Overview

Need to Learn How to Develop JSON Schemas?

Start with .

Use the Vocabularies package to maintain uniform JSON schemas across all assets in your organization. These assets include Processes, Screens, and Scripts.

Use Vocabularies to enforce compliance with a specific data structure in Request data for your Processes. Apply one or more Vocabularies to your Processes and/or specific BPMN elements in your Process models to ensure the JSON data model in Request data complies with a data structure you need to meet regulatory specifications or ensure Request data contains required information as each Request routes through workflow.

A Vocabulary is a JSON schema designed to annotate and validate ProcessMaker Platform assets to which that Vocabulary is applied. The JSON schema describes your existing data format(s) in both a machine and human readable structure. Any ProcessMaker asset to which that Vocabulary applies must conform to that JSON schema.

Use Vocabularies for the following reasons:

  • Ensure that data associated with the ProcessMaker Platform asset to which the Vocabulary applies complies with a required data format. For example, use a Vocabulary on a Task element. By extension, the Vocabulary applies to the Screen referenced by that Task element. The Vocabulary ensures that the Screen designer complies with the JSON schema as structured in the Vocabulary. This maintains consistency, validation, and compliance across any Task to which that Vocabulary applies.

  • Ensure the quality and compliance of submitted data. For example, ensure that information entered into a Screen for a Task complies with a regulatory specification.

The Vocabularies package has the following components after it is installed:

  • Manage your Vocabularies: Manage your organization's Vocabularies. See .

  • Set Vocabulary permissions: Determine which users and/or groups have permission to view, create, edit or delete Vocabularies. See .

  • Start Event element configuration: to a Start Event element.

  • Intermediate Message Catch Event element configuration:

    to an Intermediate Message Catch Event element.

  • Form Task element configuration: to a Form Task element.

  • Manual Task element configuration: to a Manual Task element.

  • Script Task element configuration: to a Script Task element.

  • Sub Process element configuration: to a Sub process element.

JSON Schema
Vocabularies Management
Vocabulary permissions
Configure how to assign Vocabularies
Configure how to assign Vocabularies
Configure how to assign Vocabularies
Configure how to assign Vocabularies
Configure how to assign Vocabularies
Configure how to assign Vocabularies