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 disable Action -> New Job ??

Ambuj

We want to disable Action -> New Job for a particular Branch. Is it possible? If yes then how to do this?

Find more posts tagged with

Comments

kaalraa

We want to disable Action -> New Job for a particular Branch. Is it possible? If yes then how to do this?

Not possible

Ambuj

Not possible

Can we associate any message with this command?

For example if user clicks on Action -> New Job it will prompt a message.

ISCBorisB

Can we associate any message with this command?

For example if user clicks on Action -> New Job it will prompt a message.

The way to conditionally block "New Job" is to substitute TS "New Job" menu item with your own CGI code. In it you would validate Branch and either deny
access or run CC URL Command "newjob". See "Interwoven® User Interface Customization Guide" for details on GUI Menus customization
and CC URL commands.

Alternatively you may perhaps configure "fake" WF in the available_templates with the <branch_list> for the desired Branch only.
Make sure that other WFs lists exclude that Branch. In the WF instantiation screen you can warn your user and do nothing, just close the window.

Ambuj

The way to conditionally block "New Job" is to substitute TS "New Job" menu item with your own CGI code. In it you would validate Branch and either deny
access or run CC URL Command "newjob". See "Interwoven® User Interface Customization Guide" for details on GUI Menus customization
and CC URL commands.

Alternatively you may perhaps configure "fake" WF in the available_templates with the <branch_list> for the desired Branch only.
Make sure that other WFs lists exclude that Branch. In the WF instantiation screen you can warn your user and do nothing, just close the window.

We have created a dummy workflow where we are just showing a message to users. It has a Tag Info used to show the message.

When user initiates the workflow through Action -> New Job it is showing the message and there are two buttons available, “Start Job” and “Cancel”. Can we remove one button from here?

Ambuj

I'm still looking for solution....

nipper

I do not know if you can remove the start button, but you can have a blank required field (that is hidden) so that the start button will never work.

Adam Stoller

We have created a dummy workflow where we are just showing a message to users. It has a Tag Info used to show the message.

When user initiates the workflow through Action -> New Job it is showing the message and there are two buttons available, “Start Job” and “Cancel”. Can we remove one button from here?

Try this instead: A dummy workflow that has no TAG_info fields, with a start task which is a cgitask owned by iw_user, that:

Ambuj

[QUOTE=ghoti]Try this instead: A dummy workflow that has no TAG_info fields, with a start task which is a cgitask owned by iw_user, that:

Sounds good... let me try this out...

moonkhanna

I'm still looking for solution....

Doesnt the UICG remove menu items stuff apply to New Job menu item?..

Adam Stoller

Doesnt the UICG remove menu items stuff apply to New Job menu item?..

Yes - but its an all-or-nothing setting - whereas this thread was about limiting the availability on a per-branch basis.

Since we don't have the ability to limit the availability on a per-branch basis, the next best thing is to trap the branch information where we can and provide a decent mechanism to inform the user that they happen to be trying to do something that isn't [locally] being supported.

moonkhanna

Hi Adam,

Yes, that seems correct for the requirement

Best Regards,

Munish Khanna

Ambuj

Yes - but its an all-or-nothing setting - whereas this thread was about limiting the availability on a per-branch basis.

Since we don't have the ability to limit the availability on a per-branch basis, the next best thing is to trap the branch information where we can and provide a decent mechanism to inform the user that they happen to be trying to do something that isn't [locally] being supported.

That's correct and through CGI task it worked well.

Thanks Smiley Happy