We have 12.3.2 in our test/staging environent and I just replicated the problem, too. The environment is being used for functional verification of jobs ("Abnahmetests") and failures of it can delay projects, so people in management get rather irrate about these things.
Should we have a true test environment that nobody cries over? Maybe. There's other considerations at play.
So I just had to write an email and tell everyone to stop editing SAP and SQL jobs.
The only good news is, version restoration can recover jobs that are now broken. But we all know that has it's limits, there's no versioning for things that move with Transport Case, and transport case is widely utilized in Automic, e.g. for bulk edits.
At Broadcom I ask, with all due respect:
How can this not be catched in QA? That parser that parses XML into your forms, I mean, even without access to the source I am of the opinion that this must be an "intricate" bit of software. When a release makes changes affecting it, this needs to be QA'd! Preferably automated, or if nothing else by a student who tests the basic functions, like editing the most common job types, and checks off on them still starting.
Also @David Ainsworth, can we downgrade? Can we run a 12.3.1 AWI with a 12.3.2 engine, and will that prevent the problem?
Nevermind, seen it.
Thanks!
------------------------------
# signature.sh --verbose=[true|false]
# no configurables beyond this point, only signature
Using the slide show widget for posting individual images is wrong. Please use the "insert image" button in the editor.
Did you know? I will NOT respond to PM asking for help unless there's an actual reason to keep the discussion off of the public forums!
"Efficient Solutions Monthly Magazine" says: These contain very good advise on asking good questions. No, you do not need StackExchange for Automic, but asking questions the right way never hurts:
http://www.catb.org/~esr/faqs/smart-questions.htmlhttps://www.chiark.greenend.org.uk/~sgtatham/bugs.html------------------------------
Original Message:
Sent: 06-10-2020 09:17 AM
From: Wolfgang Brueckler
Subject: Bug in AWI 12.3.2.hf2 using SQL Jobs
Hi all,
JFYI: a user reported a possible bug in AWI
there seems to be a bug in latest AWI Version 12.3.2.hf2 - if you edit SQL Jobs using forms view in process tab - this may mismatch the order of commands within SQL Job.
If you save the jobs its broken, editing only (without save) does no harm.
KR Wolfgang
------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------