Pass Metadata with Workflow Initiation (Attributes/ Form) with REST API

MarkedOne · 2025-01-26T14:07:00+00:00

There was an error rendering this rich post.

Hi,

I'm looking for a way to somehow initiate a workflow with some custom metadata that I want to store in the WF process (data could be stored in WF attributes, maybe a form)

My main goal is to run WF several times to do the same job but with different metadata. The only thing that came up in mind is to run a over a list in a custom code to run the WF X times with X rest api calls. I was able to create draft process and then run the draft process. But it doesn't seems to be getting any inputs.

If there is a built in way to do this I'd be glad to hear. I didn't find any step in WF that can loop.

Any Ideas on how can I achieve this?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

appuq

I the workflow REST API I understood by looking at the POST/GET calls on smartui debugging. If you can do what you need to do with SmartUI you can do the same with REST API.

Unfortunately, there doesn't seem to be an official OT sample. Before I published this there was a thread by big hitters like Christopher Meyer, Vishal Kalekar, Greg Griffiths, and Hugh Ferguson from memory.

This is where I showcased my work I would see if what I put in this is any good

“WF REST API EXPERIMENTS.docx”

As usual, the community of programmers who support this are people who will not get bogged down by OT supports saying these kinds of statements"

we don't answer this types of questions in Support, go to the forums or engage Professional Services

" (for a fee)

All comments

appuq

I the workflow REST API I understood by looking at the POST/GET calls on smartui debugging. If you can do what you need to do with SmartUI you can do the same with REST API.

This is where I showcased my work I would see if what I put in this is any good

“WF REST API EXPERIMENTS.docx”

As usual, the community of programmers who support this are people who will not get bogged down by OT supports saying these kinds of statements"

we don't answer this types of questions in Support, go to the forums or engage Professional Services

" (for a fee)

appuq

Talking strictly from a Livelink WF perspective you have the ability to start a Main map and then at some desired point, you could start a SubWF.The SubWF should be created by transferring attributes from the main which Livelink allows. So in your first iteration, you send a map downstream you should spawn a submap with whatever attributes and once it finishes you can start another. I also see administration nightmares as your subworkflows can only be one at a time.For more complicated aspects I would certainly use a better package like AnswerModules

MarkedOne

https://forums.opentext.com/forums/developer/discussion/comment/970251#Comment_970251

@appuq Thank you very much for the reply. I was about to use the draftprocesses but didn't finish it to the end. and the official documentation is really confusing. I would never thought that :

WorkflowForm_1x4x1x2

is the name of of the possible attributes that WF can have. I was sending the request with the actual attribute name. without any actual changes.

Thank you for your help!