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

Zeroing in a preset on a node

billthecat

HI, I'm wondering if this has come up before...

We create a node in the repository, named RFIs. In this node are stored the objects named RFI, which arise from a form + workflow.

It's my wish to have only the RFI objects stored in the RFI node, so I though it would possible to use a Preset to excluse the "Import" action from the node's File / menu. From messing around with the Admin/Preset/new/functionality, it looks like a preset can be applied to a repository, or to a specific document folder in the repository, but not to only a node's File/ menu.

Any clues on how to accomplish this exclusion from the RFI node, while leaving it intact for the document folders?

Thanks,

Bill

Find more posts tagged with

Comments

dnvhariprasad

Did you try selecting the location in the preset's page?

billthecat

Yes, tried that. The custom node I mentioned is a peer to the Admin, Subscription, inbox nodes. Screen shot attached as "RFI NODE.doc". The "RFI" node is 4 lines down from Presets in the folder tree. When I try to setup a preset for this node, using preset by location, it does not appear as a selectable location. It seems that the preset by location can be applied to an entire repository, or to a single specific folder, but not to a top-level node. Is that correct?

Have any other EMC customers done this type of preset?

Thanks,

Bill

billthecat

It is my perception that the preset by location can be applied to an entire repository, or to a single specific folder, but not to a top-level node. Is that correct?