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

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Rendering external forms

arunshankar_c

Hi All,

I need help in rendering external forms. Can anyone help me in achieving the below task (if possible with an example). I went through the User Guide but found very less information. Please help

1) Need to create a user/java task which calls an URL/form which takes input from user like user name and password.
2) Get the input provided by user to the Activiti WorkFlow.
3) Do processing on the inputs provided by user (like validating the user name and password exists in DB)

Can anyone please help me in implementing it.

Thanks,
Arun

Find more posts tagged with

Comments

trademak

Hi,

That's strange, because the userguide covers it in quite good detail:

http://activiti.org/userguide/index.html#externalFormRendering

So you could use the formKey attribute to define that page/view navigation string in your application.
This means you can implement the view itself in any UI technology you want.
You only need to call Activiti to retrieve the formKey and to submit the task variables you want to pass to Activiti.

Best regards,

arunshankar_c

Thank you so much for the answer

I now know that external forms/Form properties can be used to ask user to provide details for further processing.

I don't know if I am asking the question again, but can you please suggest on how to invoke an URL (External URL not concerned with Activiti) which will provide input information for further processing for the process.

ronald_van_kuij

I don't know if I am asking the question again, but can you please suggest on how to invoke an URL (External URL not concerned with Activiti) which will provide input information for further processing for the process.

You retrieve the form key as a page or full url in your web front end and run it like you would every other web page. In that page or corresponding backing beans (e.g. in case of jsf) just use the activiti api (e.g. the cdi way)…

Not sure what you mean otherwise…

b_schnarr

Am I right that this approch would lead to the situation that forms cannot be reused for other user tasks? Let say I have a form for a certain user task. The user task has the url to this form as its form key. The user enters the user data in this form and presses the submit button. The submit button now contains logic to complete this user task (using the task id) eg. via REST-API.

Then, I cannot use this form for another user task because another user task has another task id. Since the submit button needs the current task id to complete the task, I need for each user task another form.

Is this right?

Thanks and best regards
Ben

jbarrez

In a sense, it depends how sophisticated the logic behind that url is 😉

We prefer using json for the form and have a form renderer that understands that json.

ilyass_act

Hi , I'm tryin to connect my JSF pages to my Workflow , for example in process start i want to display a JSF pages then validate data using a Service Task , do you have any idea how to link my JSF pages to my Workflow ?