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; } } }

DCR Copy | Event for TeamSite menu "Copy" & "Copy To"

rohitspathak123

Hi,

Does "Copy" & "Copy To" link that are present on 'Edit' menu of TeamSite generates any event which DCT can read and call a user defined function. (Like we have in DCT ..FormAPI...onItemChange etc)

Background
- We have a DCT
- On "Save" and "Save As" of a DCR i call my idGenerator() function to get a new ID for my DCR
- This uinque ID is stored in DCR hidden field called "ID"
- So if you have a dcr called event1.dcr and you want to duplicate the DCR then 'Edit' the event1.dcr & click on "Save As" button. This event will trigger my idGenerator() function and set the value of hidden ID field in 'event2.dcr'

What user does right now
- Now the problem is that the Content Author is not using "Save As" button on a DCR (event1.dcr) to create duplicate DCR (event2.dcr)
- In order to create duplicate DCR, they select the checkbox of first dcr (event1.dcr) in TeamSite UI
- After selecting the DCR, they goto 'Edit->Copy' menu and copy the event1.dcr to event2.dcr

Problem
- When user uses 'Edit->Copy' menu to create duplicate of DCR then my idGenerator() function which is present inside the DCT is not called and so now the 2 dcrs (event1.dcr & event2.dcr) are having same ID

Question
- Is there any way by which I can call my idGenerator() function on DCT when a user creates a new DCR using 'Edit->Copy' menu
- Same is working fine when 'Save As' button is clicked on first DCR (event1.dcr)

Find more posts tagged with

Comments

RonaldV

Hi,

storing an numeric ID in a DCR should better be avoided. The only valid ID for an DCR in Teamsite is the file path&name. This value (or a derived value) should be used if an id is needed. Generating an unique ID via FormApi is simply a design-error (and BTW how unique is 'unique').

A clear solution for your situation is not easy. I would remove the 'Save As' button from the DCR-GUI. And you could create an custom-cgi in the ts-menu to mimic the 'Copy to' feature. You could then remove the old 'Copy to' menu-option but the flipside is that this impacts other branches/project that share the same server.

Good luck, you will need it!

rohitspathak123

Hi

Thanks for your reply.

I am using database sequence to generate unique number (sequence.nextval). So its really 'unique'. Any other thoughts apart of this suggestion.

Rohit Pathak

Adam Stoller

Hi

Thanks for your reply.

I am using database sequence to generate unique number (sequence.nextval). So its really 'unique'. Any other thoughts apart of this suggestion.

Rohit Pathak

Replacing the OOTB Copy / Copy To menu items with your own custom scripts (utilizing iwcp or the java equivalent within) is probably your only choice - I don't believe there is any [unique] event thrown during these operations on which to fire off a trigger script or call a custom function.

Frederik

I agree with Ronald that dcr_path is the only really unique id that TS offers.

maybe you could add the numeric id as part of the submit workflow (you can detect that it's a version 1 DCR, and add id only in that case). But then is it acceptable not to have the numeric id until submit? Does it affect how you generate / preview?

Smita

I had same requirement. I created a new link under Edit menu and invoke a cgi form on click of that custom link.
This cgi form asks the user for destination location.
On submitting this form I am calling my perl file (.ipl) which reads the source and destination locations from the cgi form parameters, reads source file into an xml, generates a unique id (DB sequence), sets it in xml and add extended attribute to that new xml file to make it a DCR. This now becomes the new DCR with unique id value.

RonaldV

Once over: you should not want to do it this way, really!

But if you still do you might consider: http://search.cpan.org/dist/Sys-UniqueID/

ISCBorisB

The only valid ID for an DCR in Teamsite is the file path&name...

Every TS Object has a unique numeric Object ID. To get one on the SFS Element (File/Directory/Symlink): iwattrib vpath objid
Whether it's a good idea to store this information in a Database, etc is a different issue.

Adam Stoller

Every TS Object has a unique numeric Object ID. To get one on the SFS Element (File/Directory/Symlink): iwattrib vpath objid
Whether it's a good idea to store this information in a Database, etc is a different issue.

Remember, that while it is unique - it is unique per server (if you have multiple servers the same id could be used on each - but I suppose it is unlikely that you'll deploy content from both servers to the same DB) - and if you migrate / re-migrate the content into a store you're not guaranteed that the same id will be associated with each object, so the value of the ID could change (this also isn't all that likely to happen, but ....)

ISCBorisB

Remember, that while it is unique - it is unique per server (if you have multiple servers the same id could be used on each - but I suppose it is unlikely that you'll deploy content from both servers to the same DB) - and if you migrate / re-migrate the content into a store you're not guaranteed that the same id will be associated with each object, so the value of the ID could change (this also isn't all that likely to happen, but ....)

Good points! One more thing to emphasize is perhaps the fact that an ID changes with the version, it's a different Object
after all. So, File ...WORKAREA/boo/foo.jsp modified today gets an ID that differs from it's submitted Version of yesterday.
Granted, you can get the latest asset's version by any ID in the chain - providing that corresponding Object still exists.

For that matter, DB approach outlined by Smita is IMO the best one. I am a big proponent of surrogate keys in DB (ones without semantics)
and successfully used this schema before. Sequences are the best source of surrogates, another plus for Smita's post. Unfortunately, not
all RDBs have them

EditGroup.png