Workflow URLs: crashes and resurrections
In Logos desktop, if you use Copy Location to get a url or l4, and then use that url Logos desktop will crash. Logos web app will open the url.
Also, if you use a url for a Workflow after it has been deleted, it will be resurrected. Which might be a cool hidden feature except there is no way to start over from scratch.
An obvious followup of the above. If you had the workflow open in the web app when you last used it and open it up after deleting on the desktop, it will resurrect the workflow.
There is no ability to have more than one workflow on the same reference. Which is likely as intended but worth pointing out (if it hasn't already been).
BTW, I really really would love friendly urls for those links so I can easily open a workflow from a url with a nice ref like jn3.16 instead of bible.64.3.16. Please extend URL support.
Comments
-
Also, if you use a url for a Workflow after it has been deleted, it will be resurrected. Which might be a cool hidden feature except there is no way to start over from scratch.
Do you mean use the URL in the Command Box or in the web app? When I enter the link into the Command Box it crashes.
0 -
In Logos desktop, if you use Copy Location to get a url or l4, and then use that url Logos desktop will crash. Logos web app will open the url.
I've written up a bug report for this crash, thank you for reporting it.
0 -
This is putting the url in Window run box or a browser. Eg.
In Logos desktop:
- Create a workflow on Jn3.16.
- Copy the URL which should be something like:
https://ref.ly/logos4/Workflow?TemplateId=WORKFLOW%3aBASIC-BIBLE-STUDY&Key=bible.64.3.16&KeyType=bible - Delete the workflow
- Enter the url in a browser window
The web app will open the deleted workflow, resurrected. Logos desktop will open & crash, but if you open it after the crash you will find the resurrected workflow in the desktop also.
0 -
In Logos desktop, if you use Copy Location to get a url or l4, and then use that url Logos desktop will crash. Logos web app will open the url.
This crash has been fixed in 8.3 RC 1.
0
