OnDemand User Group

Support Forums => MP Server => Topic started by: nikeshpj on August 14, 2019, 02:46:59 AM

Title: Version control - CMOD Objects
Post by: nikeshpj on August 14, 2019, 02:46:59 AM

Hi Guys,
Have anyone tried Version Control of CMOD Objects?
It it really possible and useful?

1. Extracting the CMOD Objects using arsxml and pushing to a GIT repo.
2. Use the xml for deploying objects to higher environments (instead of Export option in Administrator)?

The whole idea gets complicated when it comes to deleting an object.
Any suggestions and comments would be of great help.

/Nikesh

Title: Re: Version control - CMOD Objects
Post by: rjrussel on August 14, 2019, 06:54:57 AM

Why do you think you need this? OnDemand objects are static.

Title: Re: Version control - CMOD Objects
Post by: Justin Derrick on August 15, 2019, 07:01:39 AM

Yeah, you'd be better off creating an extra field, putting a default value in it (like -1) and updating it nightly by searching for the number of times the metadata appears previously, and setting the version number appropriately, or having version control happening elsewhere.

And really, if that's a core requirement that you'll be leaning heavily on, you should consider CMv8 or Filenet for this solution.

-JD.

Title: Re: Version control - CMOD Objects
Post by: nikeshpj on August 19, 2019, 08:27:43 AM

Thanks Justin and Russel for the response.