LawesD Posted January 10, 2019 Posted January 10, 2019 (edited) Hi @Victor I seem to have the same thing as in this post I had a few issues after a node pinged off into infinity, past the point the scroll bar could get to (I think this was when expanding a group). I copied as much as I could and started a new BPM. For a while this did not save at all and so to retain my progress on it I saved the stage as a template. Since then I've managed somehow to get the BPM to save again but this last node is unreachable Can you work your magic or tell me what to delete out of the text file? - attached sits-project.bpm.txt Edited January 10, 2019 by LawesD Grammar
Victor Posted January 11, 2019 Posted January 11, 2019 @LawesD I can't see what's wrong with the process by looking at it from here... I need to see how it behaves in your instance... can you give me (via PM) and API key I can use to access your instance and look at the process?
LawesD Posted January 14, 2019 Author Posted January 14, 2019 Hi Victor, Went to your profile on here, clicked 'Message' completed all the required fields - but it says Victor cannot receive messages. Can I email you instead? Regards
Victor Posted January 14, 2019 Posted January 14, 2019 @LawesD - I do apologise, my inbox always gets full so it does not accept new messages. I have cleared some up you should be able to send a PM now.... before other messages come in
LawesD Posted January 16, 2019 Author Posted January 16, 2019 No worries. Message sent. See if you can do this to it
LawesD Posted January 21, 2019 Author Posted January 21, 2019 Hi @Victor Did you find anything? Much appreciated. David
Victor Posted January 21, 2019 Posted January 21, 2019 @LawesD - I did actually... the issue is fixing it... I did not find a way yet without completely breaking the process...
Victor Posted January 22, 2019 Posted January 22, 2019 @LawesD - ultimately I was unable to fix the process so I had to pass this to our BPE developers. They identified a set of nodes that were belonging to a group which did not exist anymore and this is why they were not visible. They implemented a fix in the next admin tool update which will make such "orphaned" nodes visible so they can be edited by a process designer. Meanwhile, I have cleaned up the "SITS" process in your instance (the "Data Migration" stage). I have created a "Hornbill" copy of the process for this purpose. One thing remains in this process which is to think of how the "Developer Stage" is configured because it does not have a "Go To Nex Stage" node, something that is required... 1
LawesD Posted January 22, 2019 Author Posted January 22, 2019 @Victor **Celebratory Noises** I've managed to get the Hornbill draft to save with no errors! Thank you very much for sorting out the bad stages, and for passing it on to be fixed fundamentally. I need to make some other changes to the process but I'm staying far away from any groups going forward. Regards 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now