nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Meta-Data in new version2Store

jpfi

Hi guys,
I've just taken my first look into the new version2Store…and I'm a little bit confused.
It seems to me, that only a few properties (frozen properties) like Creator & Modified are versioned.
But what about description, title and of course custom properties and assocs? Did I miss sth.?
If I'm right, how can I achieve that more properties are going to be versioned? Switch back to the old lightweightversionstore (is there a switcher in a config file)?
Cheers,
Jan

Find more posts tagged with

Comments

jpfi

Hi guys,
nobody like to answer?
cheers, jan

mrogers

I'm sure you are "missing something" and that properties and "assocs" can be versioned in a version2Store, the "creator" and "modified" fields are very special cases so that's not where versioned properties are stored.

However you will need to wait a little more patiently untill someone who knows the low level details reads your posting and decides to answer.

jpfi

Hi,
thanks for your reply. I'm waiting 😉
cheers, jan

janv

All aspects & properties are versioned, by effectively replicating the live node to a version node (plus a few decorated properties). Since the version node is now stored natively, the new store implementation is significantly smaller (and faster) than previously. It also means that it could be optionally indexed and queried in a more meaningful way. As Mark mentions, the auditable properties are a special case.

http://wiki.alfresco.com/wiki/3.0_Version_Store

Thanks,
Jan

ps. If you have a specific test case that causes a repeatable regression then please contact support and/or log in JIRA

jpfi

Hi Jan,
yub, I read the Wiki page before, but I don't get it. Perhaps help me with a little sample.
For example how can i read the cm:description property of an versioned node. I tried to find this value via nodebrowser, but I don't find it.
You mentioned properties and aspects, what about assoc?
Thanks for your reply,
Jan

jpfi

Hi,
ok, I tried with Alfresco Explorer & properties like description & title are versioned as expected. Using Share (Alfresco 3.0.1 Ent) it isn't (Aspect title isn't part of the versionNode)…So it seems to be an issue with Share/Webscripts used by Share. I also recognized that properties set in your Working Copy in Share are also lost when checkin, e.g. description is empty an not copied from Working Copy or previous version…
So, its hopefully fixed in coming 3.1 Ent, otherwise I'll raise an issue.
I now get, that a versionNode is "simply" a copy of the orginal node, copied to version2Store + same special properties like frozenXXX.
Thanks for your efforts…
Jan