- Overview
- ProcessMaker REST Error Messages
- ACTIVITY
- CASE SCHEDULER
- CASE TRACKER
- DATABASE CONNECTIONS
- DYNAFORMS
- EVENTS
- FILES MANAGER
- INPUT DOCUMENT
- OUTPUT DOCUMENT
- PM GROUP
- PM USER
- PROCESS OF A PROJECT RESOURCES
- PROCESS PERMISSIONS
- PROCESS SUPERVISOR
- PROJECT USER
- REPORT TABLE
- WEB ENTRY
- STEP
- SUB PROCESS
- TRIGGER WIZARD
- TRIGGERS
- OAUTH
- CALENDAR
- CASE TRACKER OBJECTS
- DEPARTAMENT
- PROCESS CATEGORY
- WEB ENTRY v.2
- CASES
- CASES - INPUT DOCUMENT
- CASES - OUTPUT DOCUMENT
- BPMNWORKFLOW
- WORKFLOWBPMN
- BPMN
- WORKFLOW
- PROCESS
- PMTABLE
Overview
A call to a REST endpoint which is processed without errors will return an HTTP status code of 200
(OK) or 201
(Created).
Any HTTP status code above 201
indicates that a problem
has occurred. If ProcessMaker detects an error, it will return an HTTP status code of 400
and one of the error messages listed
below. If the HTTP status code is any other number besides 200
, 201
or 400
, the error message does not come from ProcessMaker
and was probably generated by the web server.
ProcessMaker REST Error Messages
The following tables list the ProcessMaker REST error messages when the HTTP status code is 400.
ACTIVITY
# | Feature | Error Message |
---|---|---|
1 | ACTIVITY | Invalid value specified for |
2 | ACTIVITY | Invalid value specified for 'tas_selfservice_time' |
3 | ACTIVITY | Invalid value specified for 'tas_group_variable' |
4 | ACTIVITY | Invalid value specified for 'tas_selfservice_timeout' |
5 | ACTIVITY | Invalid value specified for 'tas_assign_variable' |
6 | ACTIVITY | Invalid value specified for 'tas_selfservice_trigger_uid' |
7 | ACTIVITY | Invalid value specified for 'tas_duration' |
8 | ACTIVITY | Invalid value specified for 'tas_timeunit' |
9 | ACTIVITY | Invalid value specified for 'tas_type_day' |
10 | ACTIVITY | Invalid value specified for 'tas_calendar' |
11 | ACTIVITY | Invalid value specified for 'tas_def_subject_message' |
12 | ACTIVITY | Invalid value specified for 'tas_def_message_type' |
13 | ACTIVITY | Invalid value specified for 'tas_def_message_template' |
14 | ACTIVITY | Invalid value specified for 'tas_def_message' |
15 | ACTIVITY | This id for `prj_uid`: ... do not correspond to a registered process |
16 | ACTIVITY | This id for `act_uid`: ... do not correspond to a registered activity |
17 | ACTIVITY | invalid value specified for `start`. |
18 | ACTIVITY | invalid value specified for `limit`. |
19 | ACTIVITY | Record not found for id: |
20 | ACTIVITY | This id: ... do not correspond to a registered .... |
21 | ACTIVITY | This row does not exist! |
22 | ACTIVITY | The project with prj_uid: '...', does not exist. |
ASSIGNEE & ADHOC ASSIGNEE
# | Feature | Error Message |
---|---|---|
1 | ASSIGNEE & ADHOC ASSIGNEE | This id for `prj_uid`: 12345678912345678912345678912345 do not correspond to a registered process |
2 | ASSIGNEE & ADHOC ASSIGNEE | This id for `act_uid`: 12345678912345678912345678912345 do not correspond to a registered activity |
3 | ASSIGNEE & ADHOC ASSIGNEE | invalid value specified for `start` |
4 | ASSIGNEE & ADHOC ASSIGNEE | invalid value specified for `limit` |
5 | ASSIGNEE & ADHOC ASSIGNEE | Record not found for id: 12345678912345678912345678912345 |
6 | ASSIGNEE & ADHOC ASSIGNEE | This id: 12345678912345678912345678912345 is already assigned to task: 12345678912345678912345678912345 |
7 | ASSIGNEE & ADHOC ASSIGNEE | This id: 12345678912345678912345678912345 do not correspond to a registered USER/GROUP |
8 | ASSIGNEE & ADHOC ASSIGNEE | This row does not exist! |
CASE SCHEDULER
# | Feature | Error Message |
---|---|---|
1 | CASE SCHEDULER | This id: 12345678912345678912345678912345 do not correspond to a registered case scheduler |
2 | CASE SCHEDULER | The User `12345678912345678912345678912345` doesn't have the activity `12345678912345678912345678912345` assigned. |
3 | CASE SCHEDULER | task not found for id: 12345678912345678912345678912345 |
4 | CASE SCHEDULER | `sch_name` can`t be empty |
5 | CASE SCHEDULER | duplicate Case Scheduler name |
6 | CASE SCHEDULER | invalid value specified for `sch_start_time`. Expecting time in HH:MM format (The time can not be increased to 23:59) |
7 | CASE SCHEDULER | invalid value specified for `sch_start_date`. Expecting date in `YYYY-MM-DD` format, such as `2014-01-01` |
8 | CASE SCHEDULER | invalid value specified for `sch_end_date`. Expecting date in `YYYY-MM-DD` format, such as `2014-01-01` |
9 | CASE SCHEDULER | `sch_start_date` can`t be null' |
10 | CASE SCHEDULER | `sch_week_days` can`t be null |
11 | CASE SCHEDULER | invalid value specified for `sch_week_days` |
12 | CASE SCHEDULER | `sch_start_day` can`t be null |
13 | CASE SCHEDULER | `sch_start_day_opt_1` can`t be null |
14 | CASE SCHEDULER | invalid value specified for `sch_start_day_opt_1`. Must be between 1 and 31 |
15 | CASE SCHEDULER | `sch_start_day_opt_2` can`t be null |
16 | CASE SCHEDULER | invalid value specified for `sch_start_day_opt_2` |
17 | CASE SCHEDULER | invalid value specified for `sch_start_day_opt_2` |
18 | CASE SCHEDULER | `sch_start_day` can`t be null |
19 | CASE SCHEDULER | `sch_months` can`t be null |
20 | CASE SCHEDULER | invalid value specified for `sch_months` |
21 | CASE SCHEDULER | `sch_repeat_every` can`t be null |
22 | CASE SCHEDULER | invalid value specified for `sch_repeat_every`. Expecting time in HH.MM format |
CASE TRACKER
# | Feature | Error Message |
---|---|---|
1 | CASE TRACKER | The UID "{0}" doesn't exist in table {1} |
2 | CASE TRACKER | The "{0}" attribute is not defined |
3 | CASE TRACKER | The record "{0}", exists in table {1} |
4 | CASE TRACKER | The "{0}" position for the record "{1}", exists in table {2} |
DATABASE CONNECTIONS
# | Feature | Error Message |
---|---|---|
1 | DATABASE CONNECTIONS | The dababase connection with dbs_type: '' is invalid |
2 | DATABASE CONNECTIONS | The dababase connection with dbs_server: '', is invalid |
3 | DATABASE CONNECTIONS | The dababase connection with dbs_database_name: '' |
4 | DATABASE CONNECTIONS | The dababase connection with dbs_port: '', is invalid |
5 | DATABASE CONNECTIONS | The dababase connection with dbs_encode: '', is invalid |
6 | DATABASE CONNECTIONS | Error Testting Connection: Resolving Host Name FAILED : '' |
7 | DATABASE CONNECTIONS | Error Testting Connection: Checking port FAILED : '' |
8 | DATABASE CONNECTIONS | Error Testting Connection: Trying to connect to host FAILED '' |
9 | DATABASE CONNECTIONS | Error Testting Connection: Trying to open database FAILED '' |
10 | DATABASE CONNECTIONS | The project with prj_uid: '', does not exist. |
11 | DATABASE CONNECTIONS | The database connection with dbs_uid: '', does not exist. |
DYNAFORMS
# | Feature | Error Message |
---|---|---|
1 | DYNAFORMS | The DynaForm with {0}: {1}, does not exist |
2 | DYNAFORMS | The DynaForm title with {0}: "{1}", already exists |
3 | DYNAFORMS | The DynaForm with {0}: {1}, not is grid |
4 | DYNAFORMS | You cannot delete this Dynaform while it is assigned to a step |
5 | DYNAFORMS | The "{0}" attribute is not defined |
6 | DYNAFORMS | The "{0}" attribute is empty |
7 | DYNAFORMS | Invalid value specified for "{0}" |
8 | DYNAFORMS | The attribute {0}, has an element invalid (incorrect keys) |
9 | DYNAFORMS | The field {0}: {1}, is not an primary key field of the PM Table |
10 | DYNAFORMS | The primary key field {0} of the PM Table, is missing in the attribute {1} |
11 | DYNAFORMS | The total primary key fields of the PM Table is {0}, the attribute {1} has {2} primary keys |
12 | DYNAFORMS | It is trying to create a DynaForm by "{0}", please send only one attribute for creation |
EVENTS
# | Feature | Error Message |
---|---|---|
1 | EVENTS | This process doesn't exist! |
2 | EVENTS | This row doesn't exist! |
3 | EVENTS | The field "tas_uid" is required! |
4 | EVENTS | The field "evn_tas_uid_from" is required! |
5 | EVENTS | The field "evn_tas_uid_to" is required! |
6 | EVENTS | The project with prj_uid: '', does not exist. |
7 | EVENTS | The event with evn_uid: '', does not exist. |
8 | EVENTS | The task with tas_uid: '', does not exist. |
9 | EVENTS | The trigger with tri_uid: '', does not exist. |
FILES MANAGER
# | Feature | Error Message |
---|---|---|
1 | FILES MANAGER | invalid value specified for `prf_uid`. |
2 | FILES MANAGER | invalid value specified for `path`. |
3 | FILES MANAGER | invalid value specified for `prf_filename`. |
4 | FILES MANAGER | invalid value specified for `prf_path`. Expecting `templates/` or `public/` |
5 | FILES MANAGER | The file: sample.html already exists. |
6 | FILES MANAGER | Can`t edit. Make sure your file has an editable extension. |
INPUT DOCUMENT
# | Feature | Error Message |
---|---|---|
1 | INPUT DOCUMENT | The InputDocument with {0}: {1}, does not exist |
2 | INPUT DOCUMENT | The InputDocument title with {0}: "{1}", already exists |
OUTPUT DOCUMENT
# | Feature | Error Message |
---|---|---|
1 | OUTPUT DOCUMENT | invalid value specified for `out_doc_pdf_security_permissions` |
2 | OUTPUT DOCUMENT | invalid value specified for `out_doc_title`, can`t be null |
3 | OUTPUT DOCUMENT | The registry cannot be updated! |
4 | OUTPUT DOCUMENT | This row doesn't exist! |
PM GROUP
# | Feature | Error Message |
---|---|---|
1 | PM GROUP | The group with {0}: {1}, does not exist |
2 | PM GROUP | The group title with {0}: "{1}", already exists |
3 | PM GROUP | The user with {0}: {1}, is not assigned to the group |
4 | PM GROUP | The user with {0}: {1}, is already assigned to the group |
PM USER
# | Feature | Error Message |
---|---|---|
1 | PM USER | invalid value for `usr_country` |
2 | PM USER | invalid value for `usr_city` |
3 | PM USER | invalid value for `usr_location` |
4 | PM USER | invalid value specified for `usr_email`, can`t be null. |
5 | PM USER | invalid value specified for `usr_status`, can`t be null |
6 | PM USER | `usr_status`. Invalid value for status field. |
7 | PM USER | invalid value specified for `usr_role`, can`t be null |
8 | PM USER | `usr_role`. Invalid value for role field. |
9 | PM USER | This user: 12345678912345678912345678912345, can`t update the data. |
10 | PM USER | The user with usr_uid: 12345678912345678912345678912345, cannot be deleted while has assigned cases. |
11 | PM USER | This id for `usr_uid`: 12345678912345678912345678912345 do not correspond to a registered user |
12 | PM USER | invalid value specified for `start` |
13 | PM USER | invalid value specified for `limit` |
PROCESS OF A PROJECT RESOURCES
# | Feature | Error Message |
---|---|---|
1 | PROCESS OF A PROJECT RESOURCES | The "{0}" attribute is not defined |
2 | PROCESS OF A PROJECT RESOURCES | The "{0}" attribute is empty |
3 | PROCESS OF A PROJECT RESOURCES | Invalid value specified for "{0}" |
4 | PROCESS OF A PROJECT RESOURCES | The "{0}" attribute is not array |
5 | PROCESS OF A PROJECT RESOURCES | Invalid value specified for "{0}". Expecting positive integer value |
6 | PROCESS OF A PROJECT RESOURCES | The project with {0}: {1}, does not exist |
7 | PROCESS OF A PROJECT RESOURCES | The user with {0}: {1}, does not exist |
8 | PROCESS OF A PROJECT RESOURCES | The project title with {0}: "{1}", already exists |
9 | PROCESS OF A PROJECT RESOURCES | The calendar definition with {0}: {1}, does not exist |
10 | PROCESS OF A PROJECT RESOURCES | The project category with {0}: {1}, does not exist |
11 | PROCESS OF A PROJECT RESOURCES | The PM Table with {0}: {1}, does not exist |
12 | PROCESS OF A PROJECT RESOURCES | The activity with {0}: {1}, does not exist |
13 | PROCESS OF A PROJECT RESOURCES | The routing screen template with {0}: {1}, does not exist |
PROCESS PERMISSIONS
# | Feature | Error Message |
---|---|---|
1 | PROCESS PERMISSIONS | This row doesn't exist! |
2 | PROCESS PERMISSIONS | The project with prj_uid: '', does not exist. |
3 | PROCESS PERMISSIONS | The process permission with op_uid: '', does not exist. |
4 | PROCESS PERMISSIONS | The user with usr_uid: '', does not exist. |
5 | PROCESS PERMISSIONS | The group with usr_uid: '', does not exist. |
6 | PROCESS PERMISSIONS | The task with tas_uid: '', does not exist. |
7 | PROCESS PERMISSIONS | The dynaform with dynaforms: '', does not exist. |
8 | PROCESS PERMISSIONS | The input with inputs: '', does not exist. |
9 | PROCESS PERMISSIONS | The output with outputs: '', does not exist. |
PROCESS SUPERVISOR
# | Feature | Error Message |
---|---|---|
1 | PROCESS SUPERVISOR | This id for `pu_uid`: 12345678912345678912345678912345 do not correspond to a valid relation |
2 | PROCESS SUPERVISOR | This id: 12345678912345678912345678912345 do not correspond to a registered process supervisor |
3 | PROCESS SUPERVISOR | This id: 12345678912345678912345678912345 do not correspond to a registered USER/GROUP |
4 | PROCESS SUPERVISOR | This relation already exist! |
5 | PROCESS SUPERVISOR | This id for `dyn_uid`: 12345678912345678912345678912345 do not correspond to a registered Dynaform |
6 | PROCESS SUPERVISOR | This id for `inp_doc_uid`:12345678912345678912345678912345 do not correspond to a registered InputDocument |
7 | PROCESS SUPERVISOR | This row doesn't exist! |
PROJECT USER
# | Feature | Error Message |
---|---|---|
1 | PROJECT USER | This id for `prj_uid`: 12345678912345678912345678912345 do not correspond to a registered process |
2 | PROJECT USER | This id for `usr_uid`: 12345678912345678912345678912345 do not correspond to a registered user |
3 | PROJECT USER | This user `usr_uid`: 12345678912345678912345678912345 has no initial activities assigned in this project. |
4 | PROJECT USER | The `usr_uid` `12345678912345678912345678912345` doesn't have the activity `act_uid` `12345678912345678912345678912345` assigned |
REPORT TABLE
# | Feature | Error Message |
---|---|---|
1 | REPORT TABLE | The property fld_size: '', is incorrect numeric value. |
2 | REPORT TABLE | The property fld_name: '', is incorrect value. |
3 | REPORT TABLE | The property fld_dyn: '', is incorrect. |
4 | REPORT TABLE | The fields must have a key 'fld_key' |
5 | REPORT TABLE | The value of key column is required |
6 | REPORT TABLE | The property rep_uid: '', is incorrect. |
7 | REPORT TABLE | The property pmt_uid: '', is incorrect. |
8 | REPORT TABLE | The field for column '' is required |
9 | REPORT TABLE | The key '' not exist |
10 | REPORT TABLE | The field for column '' is required |
11 | REPORT TABLE | The project with prj_uid: '', does not exist. |
12 | REPORT TABLE | The property rep_tab_name: '', is incorrect. |
13 | REPORT TABLE | The property rep_tab_connection: '', is incorrect. |
14 | REPORT TABLE | The property rep_tab_grid: '', is incorrect. |
15 | REPORT TABLE | The property fld_type: '', is incorrect. |
WEB ENTRY
# | Feature | Error Message |
---|---|---|
1 | WEB ENTRY | The task "{0}" isn't initial task |
2 | WEB ENTRY | Web Entry only works with tasks which have "Cyclical Assignment", the task "{0}" doesn't have a valid assignment type. Please change the Assignment Rules |
3 | WEB ENTRY | The task "{0}" doesn't have users |
4 | WEB ENTRY | The DynaForm "{0}" isn't assigned to the task "{1}" |
5 | WEB ENTRY | The Web Entry exist |
6 | WEB ENTRY | The user "{0}" doesn't have the task "{1}" assigned |
7 | WEB ENTRY | The Web Entry doesn't exist |
STEP
# | Feature | Error Message |
---|---|---|
1 | STEP | The UID "{0}" doesn't exist in table {1} |
2 | STEP | Invalid value specified for "{0}" |
3 | STEP | The "{0}" attribute is not defined |
4 | STEP | The "{0}" attribute is empty |
5 | STEP | The record "{0}", exists in table {1} |
6 | STEP | The record "{0}", doesn't exist in table {1} |
SUB PROCESS
# | Feature | Error Message |
---|---|---|
1 | SUB PROCESS | The project with prj_uid: '', does not exist. |
2 | SUB PROCESS | he task with tas_uid: '', does not exist. |
TRIGGER WIZARD
# | Feature | Error Message |
---|---|---|
1 | TRIGGER WIZARD | The library with {0}: "{1}", does not exist |
2 | TRIGGER WIZARD | The function with {0}: "{1}", does not exist in library |
3 | TRIGGER WIZARD | The trigger with {0}: {1}, does not been created with the wizard |
4 | TRIGGER WIZARD | The trigger with {0}: {1}, has been modified manually, is invalid for the wizard |
5 | TRIGGER WIZARD | The wizard with the library "{0}" and function "{1}", is invalid for the trigger with {2}: {3} |
6 | TRIGGER WIZARD | The "{0}" attribute is not defined |
7 | TRIGGER WIZARD | The "{0}" attribute is not array |
8 | TRIGGER WIZARD | The trigger with {0}: {1}, does not exist |
9 | TRIGGER WIZARD | The trigger title with {0}: "{1}", already exists |
TRIGGERS
# | Feature | Error Message |
---|---|---|
1 | TRIGGERS | There is a triggers with the same name in this process |
2 | TRIGGERS | The trigger with {0}: {1}, does not exist |
3 | TRIGGERS | The trigger title with {0}: "{1}", already exists |
OAUTH
# | Feature | Error Message |
---|---|---|
1 | OAUTH | invalid_token', 'The access token provided is invalid' |
2 | OAUTH | invalid_token', 'Malformed token (missing "expires" or "client_id")' |
3 | OAUTH | invalid_token', 'The access token provided has expired' |
4 | OAUTH | Argument "is_authorized" must be a boolean. This method must know if the user has granted access to the client. |
5 | OAUTH | access_denied', "The user denied access to your application" |
6 | OAUTH | First argument to OAuth2\Storage\Pdo must be an instance of PDO or a configuration array |
7 | OAUTH | configuration array must contain "dsn" |
CALENDAR
# | Feature | Error Message |
---|---|---|
1 | CALENDAR | The calendar with {0}: {1} does not exist. |
2 | CALENDAR | The calendar name with {0}: "{1}" already exists |
3 | CALENDAR | Value specified for "{0}" does not exist in "{1}". |
4 | CALENDAR | Undefined value for "{0}", it is required. |
5 | CALENDAR | Invalid value for "{0}", it can not be empty. |
6 | CALENDAR | Invalid value for "{0}", it only accepts values: "{1}". |
7 | CALENDAR | Invalid value for "{0}". |
8 | CALENDAR | Invalid value for "{0}", this value must be an array. |
9 | CALENDAR | Invalid value for "{0}". Expecting positive integer value. |
10 | CALENDAR | The calendar name with {0}: "{1}" already exists |
11 | CALENDAR | Invalid value for "{0}", it can not be empty. |
12 | CALENDAR | Invalid value for "{0}", it only accepts values: "{1}". |
13 | CALENDAR | Invalid value for "{0}". |
14 | CALENDAR | Invalid value for "{0}", this value must be an array. |
15 | CALENDAR | Invalid value for "{0}", it can not be empty. |
16 | CALENDAR | Invalid value for "{0}", it only accepts values: "{1}". |
17 | CALENDAR | The calendar with {0}: {1} does not exist. |
CASE TRACKER OBJECTS
# | Feature | Error Message |
---|---|---|
1 | CASE TRACKER OBJECTS | The UID "{0}" doesn't exist in table {1} |
2 | CASE TRACKER OBJECTS | Undefined value for "{0}", it is required. |
3 | CASE TRACKER OBJECTS | The UID "{0}" does not exist in table {1} |
4 | CASE TRACKER OBJECTS | The record "{0}", exists in table {1} |
DEPARTAMENT
# | Feature | Error Message |
---|---|---|
1 | DEPARTAMENT | The departament with $nameField: '' does not exist. |
2 | DEPARTAMENT | The departament with $nameField: '$dep_uid' does not exist. |
3 | DEPARTAMENT | The user with $nameField: '' does not exist. |
4 | DEPARTAMENT | The user with $nameField: '$usr_uid' does not exist. |
5 | DEPARTAMENT | Invalid value for '$nameField' it must be an array. |
6 | DEPARTAMENT | The field '$nameField' is empty. |
7 | DEPARTAMENT | The Department row cannot be created! |
8 | DEPARTAMENT | The row '" . $aData['DEP_UID'] . "' in table Department doesn't exist! |
9 | DEPARTAMENT | The row '$ProUid' in table Group doesn't exist! |
PROCESS CATEGORY
# | Feature | Error Message |
---|---|---|
1 | PROCESS CATEGORY | Invalid value for "{0}". Expecting positive integer value. |
2 | PROCESS CATEGORY | cat_name. Process Category name can't be null |
3 | PROCESS CATEGORY | cat_name. Duplicate Process Category name |
4 | PROCESS CATEGORY | The Category with cat_uid: '.$cat_uid.' doesn't exist! |
WEB ENTRY v.2
# | Feature | Error Message |
---|---|---|
1 | WEB ENTRY v.2 | The web entry title with {0}: "{1}" already exists |
2 | WEB ENTRY v.2 | Undefined value for "{0}", it is required. |
3 | WEB ENTRY v.2 | Invalid value for "{0}", it can not be empty. |
4 | WEB ENTRY v.2 | Invalid value for "{0}", it only accepts values: "{1}". |
5 | WEB ENTRY v.2 | Invalid value for "{0}". |
6 | WEB ENTRY v.2 | Invalid value for "{0}", this value must be an array. |
7 | WEB ENTRY v.2 | Invalid value for "{0}", it only accepts values: "{1}". |
8 | WEB ENTRY v.2 | The web entry with {0}: {1} does not exist. |
9 | WEB ENTRY v.2 | The activity with {0}: {1} does not exist. |
10 | WEB ENTRY v.2 | The DynaForm with {0}: {1}, does not exist. |
11 | WEB ENTRY v.2 | The user with {0}: {1}, does not exist. |
12 | WEB ENTRY v.2 | The task "{0}" is not initial task |
13 | WEB ENTRY v.2 | Web Entry only works with tasks which have "Cyclical Assignment", the task "{0}" does not have a valid assignment type. Please change the Assignment Rules |
14 | WEB ENTRY v.2 | The task "{0}" does not have users |
15 | WEB ENTRY v.2 | The DynaForm "{0}" isn't assigned to the task "{1}" |
16 | WEB ENTRY v.2 | The user "{0}" does not have the task "{1}" assigned |
17 | WEB ENTRY v.2 | The project with {0}: {1} does not exist. |
18 | WEB ENTRY v.2 | The registry cannot be created!. |
CASES
# | Feature | Error Message |
---|---|---|
1 | CASES | Invalid value for '$nameField' it must be an array. |
2 | CASES | The user with userId: '' does not exist. |
3 | CASES | The user with $nameField: '' does not exist. |
4 | CASES | The user with $nameField: '$usr_uid' does not exist. |
5 | CASES | The value for $action is incorrect. |
6 | CASES | The process with $nameField: '$pro_uid' does not exist. |
7 | CASES | The category with $nameField: '$cat_uid' does not exist. |
8 | CASES | The value '$date' is not a valid date for the format '$format'. |
9 | CASES | Incorrect or unavailable information about this case: ' .$applicationUid |
10 | CASES | Invalid value specified for 'pro_uid' |
11 | CASES | Invalid value specified for 'tas_uid' |
12 | CASES | The Application with app_uid: '.$applicationUid.' doesn't exist |
13 | CASES | Invalid value for '$nameField' it must be a string. |
14 | CASES | The application with $nameField: '$app_uid' does not exist. |
15 | CASES | Invalid value for '$nameField' it must be a integer. |
16 | CASES | The case '$app_uid' is already canceled |
17 | CASES | The case '$app_uid' is canceled |
18 | CASES | The trigger with $nameField: '$tri_uid' does not exist. |
19 | CASES | Invalid value for '$note_content', the permitted maximum length of 500 characters. |
20 | CASES | Invalid value for '$nameField' it must be a boolean. |
CASES - INPUT DOCUMENT
# | Feature | Error Message |
---|---|---|
1 | CASES - INPUT DOCUMENT | This input document with id: '.$inputDocumentUid.' doesn't exist! |
2 | CASES - INPUT DOCUMENT | This document filename doesn't exist! |
CASES - OUTPUT DOCUMENT
# | Feature | Error Message |
---|---|---|
1 | CASES - OUTPUT DOCUMENT | This output document with id: '.$applicationDocumentUid.' doesn't exist! |
BPMNWORKFLOW
# | Feature | Error Message |
---|---|---|
1 | BPMNWORKFLOW | Can't create Bpmn Project. |
2 | BPMNWORKFLOW | Can't create Bpmn Project with prj_uid: %s, workflow creation fails. |
3 | BPMNWORKFLOW | Required param "EVN_TYPE" is missing. |
4 | BPMNWORKFLOW | Invalid Gateway direction, accepted values: [%s|%s], given: %s. |
5 | BPMNWORKFLOW | Unsupported Gateway type: %s |
6 | BPMNWORKFLOW | For ProcessMaker is only allowed flows between "gateway -> activity" ."Given: bpmnGateway -> " |
7 | BPMNWORKFLOW | `prj_name` is required but it is empty. |
8 | BPMNWORKFLOW | Project with name: {$projectData["prj_name"]}, already exists. |
9 | BPMNWORKFLOW | For activity: {$value['act_uid']} `act_name` is required but missing. |
10 | BPMNWORKFLOW | For event: {$value['evn_uid']} `evn_name` is required but missing. |
11 | BPMNWORKFLOW | Update Activity ({$activityData["ACT_UID"]}) Skipped - No changes required |
12 | BPMNWORKFLOW | Update Artifact ({$artifactData["ART_UID"]}) Skipped - No changes required |
13 | BPMNWORKFLOW | Update Gateway ({$gatewayData["GAT_UID"]}) Skipped - No changes required |
14 | BPMNWORKFLOW | Update Event ({$eventData["EVN_UID"]}) Skipped - No changes required |
15 | BPMNWORKFLOW | Update Flow ({$flowData["FLO_UID"]}) Skipped - No changes required |
WORKFLOWBPMN
# | Feature | Error Message |
---|---|---|
1 | WORKFLOWBPMN | Can't create Workflow Project. |
2 | WORKFLOWBPMN | Can't create Project with prj_uid: %s, workflow creation fails. |
BPMN
# | Feature | Error Message |
---|---|---|
1 | BPMN | Create Project with data: ", $data |
2 | BPMN | Create Project Success! |
3 | BPMN | Project with prj_uid: {$this->getUid()} can not be deleted, it has started cases. |
4 | BPMN | Remove Project With Uid: {$this->prjUid} |
5 | BPMN | Remove Project Success! |
6 | BPMN | Error: There is not an initialized project. |
7 | BPMN | Error: There is not an initialized diagram. |
8 | BPMN | Error: There is not an initialized diagram for Project with prj_uid: %s. |
9 | BPMN | Add Activity with data: |
10 | BPMN | Add Activity Success! |
11 | BPMN | Update Activity: $actUid, with data: |
12 | BPMN | Update Activity Success! |
13 | BPMN | Remove Activity: |
14 | BPMN | Remove Activity Success! |
15 | BPMN | Add Event with data: |
16 | BPMN | Add Event Success! |
17 | BPMN | Update Event: $evnUid", "With data: |
18 | BPMN | Update Event Success! |
19 | BPMN | Remove Event: |
20 | BPMN | Remove Event Success! |
21 | BPMN | Add Gateway with data: |
22 | BPMN | Add Gateway Success! |
23 | BPMN | Update Gateway: $gatUid", "With data: |
24 | BPMN | Update Gateway Success! |
25 | BPMN | Remove Gateway: |
26 | BPMN | Remove Gateway Success! |
27 | BPMN | Add Flow with data: |
28 | BPMN | Invalid Object type, accepted types: [%s|%s|%s|%s], given %s.","BpmnActivity", "BpmnBpmnGateway", "BpmnEvent", "bpmnArtifact |
29 | BPMN | Reference not found, the %s with UID: %s, does not exist! |
30 | BPMN | Add Flow Success! |
31 | BPMN | Update Flow: $floUid", "With data: |
32 | BPMN | Update Flow Success! |
33 | BPMN | Remove Flow: |
34 | BPMN | Remove Flow Success! |
35 | BPMN | Add Artifact with data: |
36 | BPMN | Add Artifact Success! |
37 | BPMN | Update Artifact: $artUid", "With data: |
38 | BPMN | Update Artifact Success! |
39 | BPMN | Remove Artifact: |
WORKFLOW
# | Feature | Error Message |
---|---|---|
1 | WORKFLOW | Create Process with data: |
2 | WORKFLOW | Create Process Success! |
3 | WORKFLOW | Remove Process with uid: |
4 | WORKFLOW | Remove Process Success! |
5 | WORKFLOW | Error: There is not an initialized project. |
6 | WORKFLOW | Add Task with data: |
7 | WORKFLOW | Add Task Success! |
8 | WORKFLOW | Update Task: $tasUid", "With data: |
9 | WORKFLOW | Update Task Success! |
10 | WORKFLOW | Remove Task: |
11 | WORKFLOW | Remove Task Success! |
12 | WORKFLOW | Adding SubProcess with data: |
13 | WORKFLOW | Adding SubProcess success!, created sp_uid: |
14 | WORKFLOW | Remove SupProcess: |
15 | WORKFLOW | Remove SupProcess Success! |
16 | WORKFLOW | Setting Start Task with Uid: $tasUid: |
17 | WORKFLOW | Setting Start Task -> $value, Success! |
18 | WORKFLOW | Setting End Task with Uid: $tasUid: |
19 | WORKFLOW | Setting End Task -> ".($value ? "TRUE" : "FALSE").", Success! |
20 | WORKFLOW | Invalid Route type, given: $type, expected: [".implode(",", $validTypes)."] |
21 | WORKFLOW | Update Route: $rouUid with data: |
22 | WORKFLOW | Update Route Success! |
23 | WORKFLOW | Remove Route: |
24 | WORKFLOW | Remove Route Success! |
25 | WORKFLOW | Remove Route from $fromTasUid -> to |
26 | WORKFLOW | Remove Route Success! |
27 | WORKFLOW | Add Route from task: $sTaskUID -> to task: |
28 | WORKFLOW | Add Route Success! - ROU_UID: |
29 | WORKFLOW | Adding Case Scheduler with data: |
30 | WORKFLOW | Adding Case Scheduler success!, created case Scheduler id: |
31 | WORKFLOW | Remove Case Scheduler: |
32 | WORKFLOW | Remove Case Scheduler Success! |
33 | WORKFLOW | Update Case Scheduler Success! |
34 | WORKFLOW | Adding Web Entry success!, created Web Entry id: |
35 | WORKFLOW | Remove Web Entry: |
36 | WORKFLOW | Remove Web Entry Success! |
37 | WORKFLOW | Update Web Entry Success! |
PROCESS
# | Feature | Error Message |
---|---|---|
1 | PROCESS | Undefined value for "{0}", it is required. |
2 | PROCESS | Invalid value for "{0}", it can not be empty. |
3 | PROCESS | Invalid value for "{0}", it only accepts values: "{1}". |
4 | PROCESS | Invalid value for "{0}". |
5 | PROCESS | Invalid value for "{0}", this value must be an array. |
6 | PROCESS | Invalid value for "{0}". Expecting positive integer value. |
7 | PROCESS | The project with {0}: {1} does not exist. |
8 | PROCESS | The user with {0}: {1} does not exist. |
9 | PROCESS | The project title with {0}: "{1}" already exists. |
10 | PROCESS | The project category with {0}: {1} does not exist. |
11 | PROCESS | The PM Table with {0}: {1} does not exist. |
12 | PROCESS | The activity with {0}: {1} does not exist. |
13 | PROCESS | The routing screen template with {0}: {1} does not exist. |
14 | PROCESS | Process data do not exist |
15 | PROCESS | User data do not exist |
16 | PROCESS | Process title data do not exist |
17 | PROCESS | Process description data do not exist |
18 | PROCESS | Process category data do not exist |
19 | PROCESS | The Process Title "{PRO_TITLE}" already exists! |
PMTABLE
# | Feature | Error Message |
---|---|---|
1 | PMTABLE | The table "{0}" already exits! |
2 | PMTABLE | Could not create the table with the name "{0}" because it is a reserved word. |
3 | PMTABLE | The property fld_size: '". $columns[$i]['field_size'] . "' is incorrect numeric value. |
4 | PMTABLE | The fields must have a key 'fld_key' |
5 | PMTABLE | ERROR: The class fie "{0}" doesn't exist! |
6 | PMTABLE | The value of key column is required |
7 | PMTABLE | Error trying insert into |
8 | PMTABLE | The property rep_uid: '$tab_uid' is incorrect. |
9 | PMTABLE | The property pmt_uid: '$tab_uid' is incorrect. |
10 | PMTABLE | The field for column '$value' is required |
11 | PMTABLE | The key " . implode(',', $params) . " not exist |
12 | PMTABLE | Table does not exist... skipped! |
13 | PMTABLE | The field for column '$value' is required |
14 | PMTABLE | The project with prj_uid: '' does not exist |
15 | PMTABLE | The report table with rep_uid: does not exist. |
16 | PMTABLE | The pm table with pmt_uid: does not exist. |
17 | PMTABLE | The property $nametype: '$rep_tab_name' is incorrect. |
18 | PMTABLE | The property rep_tab_connection: '$rep_tab_connection' is incorrect. |
19 | PMTABLE | The property rep_tab_grid: '$rep_tab_grid' is incorrect. |
20 | PMTABLE | The property fld_type: '$fld_type' is incorrect. |