Skip to main content
DarrenStorey12-Amethyst
12-Amethyst
February 4, 2011
Question

Resetting custom attribute values on a type to default when revising

  • February 4, 2011
  • 7 replies
  • 1508 views
When a new version of a document is created then values held by any custom attributes on the type are inherited by the new version. This is true regardless of whether the new version is created via checkin iteration or revise.

We would like to have attributes which track information related to the document revision. As such, inheriting the value on check-in is good, but inheriting values on revise is not as the initial values of the revised version may not be relevant. Does anybody know of way to reset the custom attribute values to default on revise?

Darren

7 replies

MikeLockwood22-Sapphire I
22-Sapphire I
February 4, 2011
Documents already of course have Revision info - why have a separate attribute to "track information related to the document revision?"
DarrenStorey12-AmethystAuthor
12-Amethyst
February 7, 2011
Hi Mike,



Maybe I'm missing a trick? My understanding is documents have custom
attribute values specific to each version, with only modeled master
attributes (number, name etc).

EPMDoc also allows the creation of custom master, reference and usage
attributes and WTPart allows additionally custom instance specific usage
attribute.

I'm currently not aware of any methods of creating an attribute in the
standard UI that are specific to a revision.



I'm not necessary looking for a revision master attribute, more a way of
resetting version attributes back to default on revise, but not on check
out/in iteration.



Darren







From: Lockwood,Mike,IRVINE,R&D [
MikeLockwood22-Sapphire I
22-Sapphire I
February 7, 2011
Not aware of any type of attributes that you can create that reset on Revision but not on Iteration. Not understanding the need.

From: Storey, Darren [
ssenthil1-Visitor
1-Visitor
February 7, 2011
Hi Darren

There are two ways for meeting your requirement. If you have a workflow
associated to the initial state of the document, as a first activity you can
reset the attribute to the default value.

If you don't have a workflow, you can deploy a listener service that listens
for new revision of the document. Once you capture the event you can reset
the specific attribute to the default value.



Hope this helps.



Thank you and have a great time.

Best Regards

Swamy Senthil

Principal Solutions Architect, Swasen Inc

swamy.senthil@swasen.com(Email); 909 800 8423(M); 973 324 2729(W); 866
908 6561(F);









From: Storey, Darren [
ssenthil1-Visitor
1-Visitor
February 7, 2011
I came across a similar requirement. For some specific reason, a client
wants to update a attribute "Approved By" from the release process. But when
revising the object, ootb will retain the "Approved By" value which is not
relevant to the new revision. Hence we reset the value to blank upon
revising the document. I think Darren has a requirement similar to this.





Thank you and have a great time.

Best Regards

Swamy Senthil

Principal Solutions Architect, Swasen Inc

swamy.senthil@swasen.com(Email); 909 800 8423(M); 973 324 2729(W); 866
908 6561(F);









From: Lockwood,Mike,IRVINE,R&D [
DarrenStorey12-AmethystAuthor
12-Amethyst
February 7, 2011
Swamy



Exactly that!! Thanks for the tip

I'm looking to do this via the change process, so the document would be
an affected/resulting object in a change activity.

I'm not too hot on writing expressions (totally useless in fact) do you
think this is possible via this route or does the document need to be a
PBO.

If so I suppose I could attach a little workflow to the document LC
directly that fires when arriving at a state that requires the
attributes to be reset.... The target revise state perhaps.



Darren
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.If you have received this e-mail in error please notify the sender immediately and delete this e-mail from your system.Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Ricardo (save for reports and other documentation formally approved and signed for release to the intended recipient).Only Directors are authorised to enter into legally binding obligations on behalf of Ricardo. Ricardo may monitor outgoing and incoming e-mails and other telecommunications systems.
By replying to this e-mail you give consent to such monitoring.The recipient should check e-mail and any attachments for the presence of viruses. Ricardo accepts no liability for any damage caused by any virus transmitted by this e-mail. "Ricardo" means Ricardo plc and its subsidiary companies.
Ricardo plc is a public limited company registered in England with registered number 00222915.
The registered office of Ricardo plc is Shoreham Technical Centre, Shoreham-by Sea, West Sussex, BN43 5FG.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NirmeshJain1-Visitor
1-Visitor
February 7, 2011
Hi Darren,
If you just want to do it using affected/resulting objects table, you can customize your revise action itself. Just intercept the revise action and do your processing and then add object to resulting objects table.

-Nirmesh

From: Storey, Darren [
Ricardo plc is a public limited company registered in England with registered number 00222915.
The registered office of Ricardo plc is Shoreham Technical Centre, Shoreham-by Sea, West Sussex, BN43 5FG.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Terms & ConditionsAccessibility statement