Missing element in NikuDataBus when migrating process defenition using process by XOG.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

We have a migration process that can migrate processes from one environment to another one. It migrates fine except all processes with a NikuDataBus tag loose the xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" element.

Steps to Reproduce: 

1. Login as Admin user.
2. XOG in attached 2 process definitions. One process will be the one migrated and the second process responsible for migration itself.
3. Validate and active the migration process.
4. Attempt to run migration process via Organizer.
5. Check the destination environment to confirm the process was created successfully.
6. On the destination environment open the process and check the GEL script.
7. Notice NikuDataBus tag lost the xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" element

Expected Results: It should keep NikuDataBus tag xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" element.

Actual Results: It removes NikuDataBus tag xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" element.

Environment

Clarity 16.3.2

Cause

DE173060

Resolution

Working as designed.

Engineering team recommend removing namespaces attached to NikuDataBus inside the GEL script within the process XOG.  The GEL parser is purposely removing the xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" namespace because it feels it is not needed, leaving the noNamespaceSchemaLocation in place.  That creates an unbound error when the script is parsed to run.  When we removed both namespaces from the script within the process and it ran without any issues.