IBM Support

IBM TRIRIGA Workflow Builder not loading tasks after Microsoft Security Patch install (KB3032359,KB3038314,KB3049563)

Troubleshooting


Problem

After Microsoft Security patches KB3032359, KB3038314 and KB3049563 deployment, IBM TRIRIGA Workflow Builder will fail to render task's properties.

Symptom

You will not be able to see any properties value for Workflow Builder tasks.

Cause

This has been identified as a product defect under APAR IV71104 due to Microsoft Security Patch change (KB3032359,KB3038314 and KB3049563). Future MS security patches may also cause this issue.

Environment

IBM TRIRIGA Platform 3.3.x versions prior 3.3.2.4
IBM TRIRIGA Platform 3.4.x version prior 3.4.1.2

Diagnosing The Problem

You will see Microsoft Security Patches KB3032359, KB3038314 and KB3049563 installed, and when running IBM TRIRIGA Workflow Builder with IE9, the tasks will not load their properties.

Resolving The Problem

The issue is related to the security restraint introduced by Microsoft Security patches KB3032359, KB3038314 and KB3049563, regarding Adobe SVG run.

IBM TRIRIGA has introduced a change in its code for working with this Microsoft Security patch change accordingly:

APAR #: IV71104
Defect: 169117
Description: The Microsoft Internet Explorer security updates no longer cause tasks to not load their properties within Workflow Builder.

There have been discussions around this issue on our IBM TRIRIGA forum page: TRIRIGA Workflow Builder Issues - Microsoft Updates - 03.10.2015

We have the possible solutions for this issue:

NOTE: The TRIRIGA FRONT_END_SERVER variable must be set to exactly match the server and port number of the users URL used to access the application. If the URL is http://<MYSERVER>.com:9081/tririga the FRONT_END_SERVER variable must be http://<MYSERVER>.com:9081


A. Temporary work around by removing those Microsoft Security patches from that Workflow Builder client machine. See that depending on the Windows policies in place, those same Microsoft Security patches can be re-installed at next start up of the machine. Work with your IT Helpdesk team for changing those Windows policies for preventing that behavior.

B. If you are running under 3.3.X version, upgrade to IBM TRIRIGA Platform 3.3.2.4 Fix Pack for having APAR IV71104 fix in place. Therefore, the best option will be you to go to 3.4.2 upgrade instead, see the explanation below (D).

C. If you are running under 3.4.0.X or 3.4.1.X version, upgrade to IBM TRIRIGA Platform 3.4.1.2 Fix Pack for having APAR IV71104 fix in place. Therefore, the best option will be you to go to 3.4.2 upgrade instead, see the explanation below (D).

D. Upgrade to IBM TRIRIGA 3.4.2 Platform (the best option!), since this will not use Adobe SVG viewer software anymore, so not sensitive to any Microsoft patch affecting that SVG viewer. The release 3.4.2 addresses the problem differently. SVG is an industry standard approach to graphic rendering. Since all of our 3.4.2 supported browsers now have SVG built in, we do not need the Adobe implementation (SVG viewer). With this release we begin using browser based SVG for rendering.

[{"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.1;3.3.2;3.4;3.4.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 June 2018

UID

swg21961795