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

How to stop New Form Entry

System

Hi I am new to interwoven teamsite. Please let me know how can we stop the user to do a new form entry in Teamsite. I want that a DCR is only be edit. No user can do new form entry to save any new dcr.

Regards
Raj

Find more posts tagged with

Comments

MAK

Hi I am new to interwoven teamsite. Please let me know how can we stop the user to do a new form entry in Teamsite. I want that a DCR is only be edit. No user can do new form entry to save any new dcr.

Regards
Raj

Hi,
It would help if you give the version, etc.

Regards,

Migrateduser

Version is TS 6.7.1

Adam Stoller

Version is TS 6.7.1

You might be able to play with the role definitions - but it would probably be easier to just remove the menu item altogether via the ui_custom.xml file -- read the Interwoven User Interface Customization Guide - specifically the sections regarding Extending GUI Functionality / Custom Menu Items for details

Reghunath

You can also do a simple logical check using FormAPI and in case if its a new DCR, alert the user from using the feature(and disable the fields).

We have used this feature, as we need to control the flow based on Business User Roles(not teamsite roles)...

Cheers!
Reghu.

ACheethayil

You can do that s follows. In init() function check as follows

if ( isDCRNamed() )
{
//do whatever u want
}
else
{
//close the dcr with an alert message
}

function isDCRNamed()
{
var bolReturn;
bolReturn = false;

if ( IWDCRInfo.getDCRName() != null)
{
if (IWDCRInfo.getDCRName()!= "")
{
bolReturn = true;
}
else
{
bolReturn = false;
}
}
return bolReturn;
}

ISCBorisB

Do you really think that raj_k was patiently waiting three years for your input?

nipper

Do you really think that raj_k was waiting three years for your input?

I know I was. That is the only reason I have been on DevNet, to see an answer to this post. I can log off now......