Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: Upgrading Flows for APEX after upgrading APEX - Doc links to # #690

Closed
rallen2010 opened this issue Nov 20, 2023 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@rallen2010
Copy link
Collaborator

rallen2010 commented Nov 20, 2023

Flows for APEX version

23.1 (latest)

Oracle Database version

19c

Oracle APEX version

23.1

Have you used the BPMN-Linter in Flow Designer to Validate your Diagram?

Yes

What happened?

After upgrading to APEX 23.1, then re-opening the Flows for APEX application I get a warning that the APEX version has been upgraded and Flows needs to run an update script. The Warning links to a non-existing message...

Screenshot 2023-11-28 at 14 20 12

Reported by several customers.

Steps to reproduce

Upgrade the APEX system underneath Flows for APEX 23.1. Sign in to the engine app. A Warning is displayed at the top of the page warning that APEX has been updated.

Expected behaviour

  1. Warning should link to documentation.
  2. Script should be provided to run any update required.
@rallen2010 rallen2010 added the bug Something isn't working label Nov 20, 2023
@rallen2010 rallen2010 self-assigned this Nov 20, 2023
@rallen2010
Copy link
Collaborator Author

script after_apex_upgrade.sql added to the Flows for APEX v23.1 release assets. This should be run by the Flows for APEX user after any APEX version upgrade (so, e.g., 23.1 to 23.2 - not necessarily minor patching versions e.g., 23.1.2 to 23.1.3).

@rallen2010 rallen2010 pinned this issue Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant