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

Tag UI onclick of Save and SaveAs of DCR

dipankar86

I want to popup the Tag UI on Save and SaveAs of the DCR.This I am being able to do but on Save and Close of the Tag UI popup it basically doesn't closes.So I have two windows open now one for thr Tag UI popup and the other for the DCR.I want to close the Tag UI popup after I save the metadata fields.I am using Next Generation form API.Please advice.

Thanks in advance

Find more posts tagged with

Comments

Adam Stoller

I want to popup the Tag UI on Save and SaveAs of the DCR.This I am being able to do but on Save and Close of the Tag UI popup it basically doesn't closes.So I have two windows open now one for thr Tag UI popup and the other for the DCR.I want to close the Tag UI popup after I save the metadata fields.I am using Next Generation form API.Please advice.

Thanks in advance

My advice is to not try to do what you are saying you are trying to do.
Either add an explicit button on the DCT form to launch the TagUI and treat it as a secondary window of the content creation process; make use of the CCStd wizard interface; or add an explicit tagging step to your workflow process

dipankar86

But this is what my requirement is.
Now my only problem is to close the tagui popup on click of Save and Close and Cancel.As I have two windows open now.

Thanks in advance.

Adam Stoller

But this is what my requirement is.
Now my only problem is to close the tagui popup on click of Save and Close and Cancel.As I have two windows open now.

Thanks in advance.

This is the requirement that you were given - it doesn't mean it has to be what actually gets implemented. You should be able to present pros and cons of different solutions to your customer to help guide them to a workable implementation.

Or you can spend a few more months trying to figure out how to handle all the possible different window communication mechanisms to try to do what you were told you needed to do - you'll get to bill for a lot more time, but ultimately you'll either fail to do what you're trying to do, or you'll succeed and the customer will not be pleased at the amount of money it cost them to do something that could have been handled in another manner, gracefully, cleanly, and less expensively - but hey - that's just my opinion.

dipankar86

I think we can customize the application_custom.xml to have the tagging feature after save of the DCR for CCstd,but does this same customization work for CCPro as well.

Adam Stoller

I think we can customize the application_custom.xml to have the tagging feature after save of the DCR for CCstd,but does this same customization work for CCPro as well.

No - the option for CCStd is the "wizard" - there is no such interface for CCPro - thus it may be preferable to include a metadata task in the workflow.

dipankar86

I am thinking to add a button on click of which the submit to workflow window comes up.I think it is a part of ccpro wizard create_form.Can anybody guide me on the parameters needed or the url to be formed.

Adam Stoller

I am thinking to add a button on click of which the submit to workflow window comes up.I think it is a part of ccpro wizard create_form.Can anybody guide me on the parameters needed or the url to be formed.

Let's see if we can be clear here. There Is NO CCPro "wizard". Therefore this can not be "part of" something that does not exist.

Add the metadata task to the workflow - disable to metadata step from CCStd wizard - and then things will be consistent regardless of which user interface your users are using.