/decision-types

Foundational GET all handler for: decision-types
Decision Types must include:
Decision
Resolution
Action Without Meeting
ID: NUMBER: This is the Primary Key (Numeric) of the Decision Type
MACHINE_NAME: VARCHAR2(255): This is the Machine Name (all upper case and only underscores) for this status
LABEL: VARCHAR2(255): This is the name (label) for the Goal Status
LABEL_DESCRIPTION: VARCHAR2(255): This is the description of the label that is assigned to this status
ACTIVE: NUMBER: This indicates if the status is active or not
EFFECTIVE_DATE: DATE: This is the date that this status became active
END_DATE: DATE: This is the date that this Status iswas no longer available for use
SYSTEM_GUID: VARCHAR2(36): This is used to track a unique identifier for a system specificaly a System GUID generated by SYSGUID()
UUID: VARCHAR2(36): This is the UUID for this record
METADATA: JSON: This is a JSON metadata field
DATA_LINEAGE: JSON: This field includes any specifications about where the source system is any external identifier time last updated etc
UDFS: JSON: This is used to track the UDFs (User Defined Fields) that might get added
CREATED_ON: DATE: The Date-time that this record was created
CREATED_BY: VARCHAR2(255): The User ID of the user account that created this record
LAST_UPDATED_ON: DATE: This is the Date-time when this record was Last Updated
LAST_UPDATED_BY: VARCHAR2(255): The User ID of the user account who last updated this record

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Request

Responses