Today I am going to present you another interesting anamnesis. Enjoy!
The patient has recently installed a fix pack (in this particular case it was on WLE 7.2.0. FP5)
After installation, the patient discovered that changes to environment variables were not picked up by the process app
For instance, our patient had an environment variable called „testVar“ which was set to 25 for DEVELOPMENT before the upgrade was performed. Now after changing it to another value (like 100, see screenshot), the value of 25 was picked up every time.
At the patient the symptom can be confirmed by our excellent diagnosis tool - the Execution Evaluator:
Even creating a new snapshot did not help the patient
The patient was quite suprised as there were no issues in that respect before WLE/BPM had been upgraded
The reproduction attempt of the symptom at a test person (test environment – not upgraded) showed a working scenario. Here, the environment variables switched to the proper values.
A further test on the patient was to create and test another environment variable. At this test the patient showed no symptom.
Summarized, Dr. Debug faced the following situation:
The symptom is related to process applications which existed before the upgrade
After the upgrade the environment variables revealed an inconsistency
This inconsistency was not saved in the .twx-file as a further test person showed no symptoms
Hence, it seemed to belong to the database and a specific references there
Dr. Debug's assumption was that some references of the affected process app might have gotten corrupted by the upgrade. He further thought, an export of the process application before the upgrade and an import back after the upgrade might have prevented this issue.
Now, what could Dr. Debug try to heal the patient?
Right, he can try to treat this disease by creating new database entries and references.
For instance, a potential treatment can be the cloning of the affected process application. By doing so, new references in the database are created and all environment variables should work as expected.
Another option would be to remove the affected artifacts and create new ones. However, this needs to comprimise all affected artifacts.
It seems that the better option is the cloning since an entirely new process application is created.
Hence the cloning approach was Dr. Debug's Advice in this case. The result was very positive. All environment variables took the proper values according to the environment type used. Hence, the patient no longer showed the symptoms and Dr. Debug's Advice helped another patient back on his feet.
And if this does not help in your case, take two of these and call me in the morning.
Your Doc D.