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

Creating folder using WFM instantiation Screen

Vax

Hi TeamSiters,

FIRST POST in Devnet

I have a client requirement in which we are not allowing end users to create the folders in TeamSite 672 SP2 UI. Instead they can send folder creation request through WF. We have created custom workflow instantiation forms where end users will have to provide the foldername, folderlocation(vpath) and inheritance (yes or no).

I have few doubts here
1) How shall I capture the end user input data/value (through instantiation form) in my external task?
2) How to restrict users to create folders in certain vpaths?

I would appreciate if you have sample codes also along with the suggestions Smiley Happy

.

Regards,
Vaxing

Find more posts tagged with

Comments

nipper

Not posting sample code, you need to write it.

The UI piece is easy. That can be done in the custom_instantiation.cfg file for your WF. Read the workflow modelers guide for more information.

Using the submit.cfg file and appropriate permissions you can restrict certain folders from being modified, you can also just remove the New Folder menu item from the GUI. Those are documented in the TS Admin and TS User Interface Customization Guides respectively.

Now I also think this is a stupid plan. But have fun.

Vax

Hey Nipper,

Thanks for the reply.

Actually, we have already removed "new folder" option from the UI and created WF instantiation screen (though we are not able use replicant as it is a bug).

Now, the major concern is to capture the value (provided by end user through instantiation screen) in external task (preferably a java code).

Please let us know your thoughts!

-Vaxing

Ram_IWOV

Hey Nipper,

Thanks for the reply.

Actually, we have already removed "new folder" option from the UI and created WF instantiation screen (though we are not able use replicant as it is a bug).

Now, the major concern is to capture the value (provided by end user through instantiation screen) in external task (preferably a java code).

Please let us know your thoughts!

-Vaxing

Hi Vaxing,

Please try to follow the below procedure

1.)Create a workflow variable in Workflow Modeler.
2.)Create a item in Custom instantiation screen.
3.)Get the variable using the below code
String variablename = task.getWorkflow().getVariable("variablename ");

Regards
Ram

Vax

Hello Ram,

Thanks a lot for the inputs. I really appreciate your help.

Regards,
Vaxing