AnsweredAssumed Answered

How to correct the version value in XOG header in GEL scripts after an upgrade?

Question asked by Georgy N Joseph on Jul 4, 2014
Latest reply on Jul 7, 2014 by urmas

Hi Friends,

 

We finished upgrading Clarity from v13.0 to v13.3. While checking the many GEL scripts in process actions, we see that the XOG header in all these GEL scripts still has the old clarity version as : <Header action="write" externalSource="NIKU" objectType="customObjectInstance" version="13.0.1.0102"/>

 

Couple of queries:-

1. Is it mandatory that this should be changed to the new upgraded clarity version in all these GELs which use XOG? Or can we leave it safely there?

2. As we have quite a number of GELs using XOG, can we do this correction globally, through backend? Any ideas?

 

To avoid doing the above step in all future upgrades, we just checked to see if the XOGs will work without the version tag . No luck!!!

Error.JPG

So, as this version tag is mandatory in the XOG write requests, we will not be able to remove them from any GELs. Does this mean that this corrective step has to be done after each clarity upgrade?

 

Regards,

Georgy

Outcomes