Release of REI3 Workflows

segelfreak

I certainly will!!!

allanregistos

Hi Gabriel,

Thanks for the release of workflow feature in REI3. Today, I have tested but it generates an error every time I start testing. So, I simplified the workflow and created one to detect if a ticket is created:
Start --> Sends Email ---> Then "Ends" the workflow. The only action is "sends an email". However, when testing the workflow Start test phase, the same error: ERROR: case not found (SQLSTATE 20000) if I save the ticket.
Stopping or returning to draft, saves the ticket. I think I have missed something?

allanregistos

gabriel I had a look at making a workflow graph with echarts a year or two ago for a customer project and it was quite limited and would probably not work for a complex workflow. If it´s possible to use echarts that way, we could easily enough add a visualization, though it would not make it possible to edit the workflow.

We are using the open-source version of ProcessMaker 3.x, it is stable. It uses BPMN for workflow visualization, I think if you add visuals in R3 workflow, it would be BPMN.

lsw-fabian

Hi @allanregistos, Thanks for the detailed info, we’ll check it out.

lsw-fabian

Could you please share a screenshot from your 'Sends Email' action?

allanregistos

Hi Fabian, thanks for responding.
I am on mobile, so the screenshot might be not detailed enough.

lsw-fabian

Thanks for the screenshot. Your action step seems to be set up correctly.

Could you take a look at the START conditions as well? There might be something configured there.

allanregistos

Hi Fabian, late response here, as we might have different tz.
Start step:

lsw-fabian

Thanks for the screenshot, everything seems to be pretty fine. Unfortunally, i'm not able to replicate the issue by myself.
Could you tell me, if you modified any of the lsw applications, like tickets or organization?

With R3.12.1 we improved our system logs and added more information to make troubleshooting easier. Do you already use the newest Version? If so, could you please reproduce the issue and provide us the event from the instance logs?

allanregistos

Hi Fabian, the log, when I trigger the Start test phase is:

Warning
node1	-	Websocket clients	TRANSACTION 313464 failure (login ID 2), ERROR: case not found (SQLSTATE 20000)

I have not modified the tickets. However, I do remember tinkering with it in development mode. If there were any changes, they would have been overwritten when I upgraded the ticket application after an update became available from the rei3 repository.
I will check my other rei3 instance (which I rarely use and only keep for testing) to see if it has the same error. If it doesn’t, then it’s likely due to a change I made that I’ve already forgotten.
I logged in to my PostgreSQL server, and this screenshot of the lsw_tickets if this help:

allanregistos

Hi Fabian,

I have confirmed that my other dev RE3 instance is working. The issue lies with the RE3 instance we have in production.

If deleting the tickets application, should also delete the data?
Regards,
Allan

lsw-fabian

allanregistos Hi Allan,
Yes when removing the application you will also remove your data. We'll update the ticket application today, If you made any changes, they will be overwritten after.

Could you please check If you can find the issue in the REI3 instance logs (located in the REI3 admin panel)?

allanregistos

Yes:

Warning
node1	-	Websocket clients	TRANSACTION 313464 failure (login ID 2), ERROR: case not found (SQLSTATE 20000)

This is the exact log added when the error occurred.

gabriel

allanregistos

@lsw-fabian asked whether you were running on r3.12.1, because this patch release extended the error logging in cases like this. If you are and you still get only this error, no luck. If you have not been on r3.12.1 yet, you could upgrade and then try again - the log should give us much more context detail, which would help with finding the cause.

allanregistos

Hi Gabriel, I updated to the latest release and here is the log:

TRANSACTION 159049 failure (login ID 2), ERROR: case not found (SQLSTATE 20000)
CONTEXT: PL/pgSQL function lsw_workflow.get_step_event_condition_side_value(integer,bigint,jsonb) line 22 at CASE
PL/pgSQL function lsw_workflow.get_step_event_conditions_met(integer,bigint,jsonb) line 31 at assignment
PL/pgSQL function lsw_workflow.app_announce_event(text,text,jsonb) line 46 at FOR over SELECT rows
SQL statement "SELECT "lsw_workflow"."app_announce_event"(
			_c->>'app',
			_event_name,
			(
				SELECT JSONB_BUILD_OBJECT(
					_c->'data'->>'ticket_id',       		"id",
					_c->'data'->>'contact_id_assigned_to',  "assigned_to",
					_c->'data'->>'is_closed',   			"closed",
					_c->'data'->>'closing_text',    		"closing_text",
					_c->'data'->>'context_id',      		"context",
					_c->'data'->>'contact_id_created_by',   "created_by",
					_c->'data'->>'criticality_id',  		"criticality",
					_c->'data'->>'description',     		"description",
					_c->'data'->>'is_mail',         		"is_mail",
					_c->'data'->>'is_problem',      		"is_problem",
					_c->'data'->>'is_spam',         		"is_spam",
					_c->'data'->>'ticket_key',      		"key",
					_c->'data'->>'pending_reached', 		"pending_reached",
					_c->'data'->>'pending_time',    		"pending_time",
					_c->'data'->>'update_reason_id',		"reason",
					_c->'data'->>'contact_id_requested_for',"requested_for",
					_c->'data'->>'state_id',        		"state",
					_c->'data'->>'ticket_subject',  		"subject",
					_c->'data'->>'team_id',         		"team",
					_c->'data'->>'ticket_template_id',		"template",
					_c->'data'->>'type_id',         		"type",
					_c->'data'->>'ticket_url_agent_record', FORMAT(
					'https://%s/#/app/lsw_operations/lsw_tickets/form/36a5d752-c57a-40a9-8a40-bc02df51d9d5/%s?menu-app=0&menu-header=0',
						instance.get_public_hostname(),
						_ticket_id
					),
					_c->'data'->>'ticket_url_requestor_record', FORMAT(
					'https://%s/#/app/lsw_operations/lsw_tickets/form/834b01b4-4350-4c1a-a64c-22c01ebd9b71/%s?menu-app=0&menu-header=0',
						instance.get_public_hostname(),
						_ticket_id
					)
				)
				FROM "lsw_tickets"."ticket"
				WHERE "id" = _ticket_id
			)
		)"
PL/pgSQL function lsw_tickets.wf_announce_ticket_events(integer,text,record) line 53 at PERFORM
SQL statement "SELECT "lsw_tickets"."wf_announce_ticket_events"(
					_ticket, 
					'CREATED'
				)"
PL/pgSQL function lsw_tickets.trg_worklog_source_insert_after() line 99 at PERFORM

gabriel

Thank you for sharing the updated logs.

Following this, I was able to replicate this behaviour by leaving one side of a event condition empty:

Is it possible that you have a workflow template that uses an empty event condition? If yes, we found the issue.
We will address it in REI3 Workflows so that this input is flagged as invalid in any case.

allanregistos

Noted. Thank you for this update. I will test it later.