BCC/CA

228 views
Skip to first unread message

Reddy

unread,
Apr 4, 2009, 1:51:09 AM4/4/09
to atg_...@googlegroups.com
Hi,
 
I want edit the catalog id ,category id and product id, But these fields are disable(not writable) in BCC. How to enable these fields in BCC.
 
Regards,
Reddy

Sumit Gupta

unread,
Apr 4, 2009, 1:58:45 AM4/4/09
to atg_...@googlegroups.com
Hi Reddy,

Things which are shown disabled and not editable depends upon the access rights given to a particular user on that field. You need to change the access rights by modifying the ACL's corresponding to that property for a particular user. By the way just for info ACL's are Access Control Lists. You can get an idea about ACL's in the secured repository topic of ATG Repository Guide.

Regards,
Sumit

Reddy

unread,
Apr 4, 2009, 2:06:20 AM4/4/09
to atg_...@googlegroups.com
Thanks Sumit

russel...@mac.com

unread,
Apr 4, 2009, 11:19:07 AM4/4/09
to ATG_Tech
actually it is due to an attribute set in the base productCatalog.xml:
<property category-resource="categoryInfo" name="id" column-
name="category_id" display-name-resource="categoryId">
<attribute name="uiwritable" value="false"/>
<attribute name="propertySortPriority" value="-3"/>
</property>

uiwritable has been set to false. To reenable it, you should overwrite
it in localconfig, however, best practices you *should* use the out of
box id generator, and not set these manually (is why they are disabled
to begin with).

If you have another ID that you want to capture as part of the item-
descriptor (say an external identifier in another system), you should
extend the item descriptor with a property that is writable. The
default id field should be reserved for repository usage.

In CA/Merch, this is particularly tricky, because of what happens when
you create a new item. The ID will be populated, and you cannot change
it. If you allow users to set it, then they cannot ever change it once
they click "apply" because the id field is used for asset history
(note the primary keys on the table are id and asset_version).

would strongly advise against allowing users to manually manage ids.

David Herman

unread,
Apr 4, 2009, 11:27:38 AM4/4/09
to atg_...@googlegroups.com
I thought ATG yelled at you when yoy tried to modift the repository id if an already persisted item?

Burhan Surti

unread,
Apr 6, 2009, 6:24:57 AM4/6/09
to atg_...@googlegroups.com
better use ID generate for your own seed rather than allowing user to doso.
Reply all
Reply to author
Forward
0 new messages