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

Add a new button in the template

manpreet1

Hi,

I am using Interwoven TeamSite 6.7.1 Service Pack 1.

I need to add a button on the template with Preview, generate, save.. buttons and need to capture its click event.

Can anybody please provide pointers on how to do this.

Thanks,
Manpreet

Find more posts tagged with

Comments

curiousmaverick

hmm, no straight forward way I guess. You are only allowed to play around with the existing ones in a template.

However you can do some hack. Use javascript (formAPI).

gzevin

Hi,

I am using Interwoven TeamSite 6.7.1 Service Pack 1.

I need to add a button on the template with Preview, generate, save.. buttons and need to capture its click event.

Can anybody please provide pointers on how to do this.

Thanks,
Manpreet

cannot do. but what kind of new button would you want to have?

manpreet1

I want to add a button called "Push to live", which will deploy the template to live web server when clicked.

gzevin

I want to add a button called "Push to live", which will deploy the template to live web server when clicked.

IMO, this is the wrong application of the button. The form should not be used for that purpose. The most natural way would be to attach a workflow event to tt_data, so our workflow will do the actions. That makes much more sense, because most of deployement and other tasks are usually done in the workflow context as well.

having said that, you could probably add a button that would call server and do some background action. Again, for me it would be a big no-no

manpreet1

I want to use generic deployment to push the template to live server on click of this "Push to live" button.

We don't want to use Workflow deployments, as this is the client requirement.

Adam Stoller

I want to use generic deployment to push the template to live server on click of this "Push to live" button.

We don't want to use Workflow deployments, as this is the client requirement.

As stated - I would agree with gzevin - the requirement sounds like it is based on faulty understanding of the product.
That being said, you can add a button to your DCT(s) to do what you want - it won't appear at the same level as Preview, Generate, etc., but rather would appear within the DCT form and you can either have it perform a [cgi-]callout or capture the click event and have it perform an inline script. Either could achieve your supposed requirement functionality, but it is still a highly questionable "requirement".
Using tt_data you could fire off a non-interactive workflow that simply performed the deployment (though frankly, I think you would want to have the file versioned via submitting too)

nipper

I want to use generic deployment to push the template to live server on click of this "Push to live" button.

We don't want to use Workflow deployments, as this is the client requirement.

It *can* be done by following Ghoti's method. However, who ever gave you this assignment is an idiot. They are asking you to develop something that may be unsupportable down the road and cost them way too much time/money invested in functionality that has little business benefit.

A true TS architect will tell the customer when they areasking for something that makes no sense. This is one of those cases.

gzevin

It *can* be done by following Ghoti's method. However, who ever gave you this assignment is an idiot. They are asking you to develop something that may be unsupportable down the road and cost them way too much time/money invested in functionality that has little business benefit.

A true TS architect will tell the customer when they areasking for something that makes no sense. This is one of those cases.

a true TS architect should be able to tell the client they are an idiot. I know me and you could. We are brothers of House MD. Smiley Very Happy

Satish125

Sometimes I think this requirement makes sense such as button can be used to push the content for preview i.e submit the job instead of saving the DCR and going back to the file list, select the DCR and submit. Instead of four clicks you should have capablity to submit the job from the DCR itself.

Thanks
Satish

jagadesh

Sathish,
You should know what will make sense to achieve in short time. You are trying to add button like preview, save in top of DCT. It requires lots of analysis, implementation and testing. And one more thing success rate is less and Teamsite crash percentage is high in your requirement. Before you start something you should try to know all the existing files and functionalities in product.

My suggestion should be here instead of placing button near by save, just use dialog button in your DCT as item. Then call whatever ipl you want there.

Note:
In IPL you should capture all the workflow information/file info before starting whatever workflow.

You should tell to ur customers, what will be the impacts and what is the possible of alternative solution here.