search

flowsforapex / apex-flowsforapex

Flows for APEX - Model and run process flows all within Oracle APEX!
https://flowsforapex.org
Other
80 stars 40 forks source link

Error while saving changes in the diagram (Flow Modeler screen) #697

Closed Muddasar closed 6 months ago

Muddasar commented 6 months ago

Hello,

I am facing an issue while saving my changes in the flow modeler screen:

Update: Oracle APEX 23.1.0 Flow For APEX 23.1 Oracle Database 19c

Issue:

1 error has occurred Diagram could not be parsed. Please review your diagram to ensure that it is supported.

image

Until now, it was working fine, my all the processes were also working fine. But now if I am trying to make new changes, I am getting this error.

If I try to start a new process or try to complete any existing step, I am getting following error as:

1 error has occurred No Next Step Found on subflow 178. Check your process diagram.

image

Please note that, when I tried to look into the database tables, data from some of the tables is deleted (e.g. Data related to Flow Connections in FLOW_CONNECTIONS is not available anymore, please have a look at the screenshot attached below).

Issue while saving FFA

I would like to request an urgent help here, as my application is ready to move in to Production environment, and in the last minutes I am facing this issue.

Best Regards, Muddasar

rallen2010 commented 6 months ago

As it looks like you didn't complete the bug template, please could you supply the following info:

Muddasar commented 6 months ago

As it looks like you didn't complete the bug template, please could you supply the following info:

  • APEX version
  • Flows for APEX version
  • Oracle database version
  • Have you Linted your BPMN diagram in the modeler? ( click on the lozenge at the bottom of the diagram that reads 0 Errors, 0 warnings)?

Thank you very much for your consideration and reply dear Rallen.

Here you go, sorry for missing earlier:

Oracle APEX 23.1.0 Flow For APEX 23.1 Oracle Database 19c

Plus, when I click on Errors / Warning section, it shows warnings for missing label of gateways only.

Please guide me more, how can I fix this issue.

Regards, Muddasar

rallen2010 commented 6 months ago

So this looks like a problem with the parser - either a parser bug or something unsupported in your model.
When a model is saved and parsed, it does delete the previous parsed representation of the diagram - so having flow_connections not contain records for the diagram is to be expected... So I can see more of what's going on, could you do the following:

  1. Turn on logging in the parser. If you look in the flow_configuration table, you need to have an entry for parser_log_enabled set to true. If there is an existing entry, please set the value to true. If there is no entry for parser_log_enabled, then please insert one and set it to true. You can use the APEX Object Browser to do this...

  2. Go to the Flow Modeller in the Flows for APEX app as a developer, then on the Developer Menu at the bottom of your screen, Select Debug > Enable Debug > App Trace level.

  3. Save your model again - which I assume will fail.

  4. Can you then send me the BPMN (export as BPMN), the APEX Debug output and the parser log. Either post it on here or send it to my email if that's OK.

Muddasar commented 6 months ago

Dear RAllen,

Thank you for your support.

I have followed the first three steps (i.e. set parser_log_enabled = true, enabled App Trace Level debugging and tried to save the model, yes it failed to save).

Here, I am sending the BPMN & APEX Debug in your email, as the bpmn format is not supported here to be attached. But there's no data in FLOW_PARSER_LOG table.

Debug Message Data.xlsx

image

Please check your email for BPMN file.

Thanks & Regards, Muddasar

Muddasar commented 6 months ago

Dear R Allen,

Good afternoon.

Please find the attached bpmn file.

Please note that, there's no log available in FLOW_PARSER_LOG table.

Looking forward to hearing from you.

Regards, Muddasar

On Sun, Dec 10, 2023 at 3:52 PM Richard Allen @.***> wrote:

So this looks like a problem with the parser - either a parser bug or something unsupported in your model. When a model is saved and parsed, it does delete the previous parsed representation of the diagram - so having flow_connections not contain records for the diagram is to be expected... So I can see more of what's going on, could you do the following:

1.

Turn on logging in the parser. If you look in the flow_configuration table, you need to have an entry for parser_log_enabled set to true. If there is an existing entry, please set the value to true. If there is no entry for parser_log_enabled, then please insert one and set it to true. You can use the APEX Object Browser to do this... 2.

Go to the Flow Modeller in the Flows for APEX app as a developer, then on the Developer Menu at the bottom of your screen, Select Debug > Enable Debug > App Trace level. 3.

Save your model again - which I assume will fail. 4.

Can you then send me the BPMN (export as BPMN), the APEX Debug output and the parser log. Either post it on here or send it to my email if that's OK.

— Reply to this email directly, view it on GitHub https://github.com/flowsforapex/apex-flowsforapex/issues/697#issuecomment-1848942754, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZYLHNHQVE6DHZZ27OWEJTYIWO7BAVCNFSM6AAAAABAOLR5GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYHE2DENZVGQ . You are receiving this because you authored the thread.Message ID: @.***>

Muddasar commented 6 months ago

Thank you very much for your help, after a detailed analysis of flow_bpmn_parser_pkg.parse( pi_dgrm_id => :dgrm_id ); I got to know that, during enhancement of FFA application for my custom requirements I had referenced FLOW_OBJECTS.OBJT_ID into one of my local DB tables and it was not allowing to delete the rows.

I have disabled that foreign key and now it's working perfectly fine. Apologies for the inconvenience.