REST Api - Workflow Attributes

Options

I see that the Rest API documentation for Processes has been updated with some new endpoints. However, it's hard to tell from the documentation if it's possible now to update Workflow Attributes from the Rest Api. Is this something that can be done yet? And if so are there any examples?

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=67789539&objAction=browse&viewType=1

Best Answers

Answers

  • That's disappointing, I had thought that was something that was going to be added in soon. I hope it's on the roadmap still for Workflow APIs.

  • AJ Gorczyca
    edited December 3, 2019 #7
    Options

    Thanks Ivan, do you happen to know if there is documentation anywhere for what is acceptable for the different "actions" for this?

    The API documentation is really lacking in this area. Very rarely does it show what actually are acceptable values it can accept in cases like this.

  • I am not aware of the existence of such documentation.

  • How were you able to figure it out without documentation then if you don't mind me asking? Just wondering if I'm missing a way I could discover some of this for myself in the future.

  • Hi All, can you please provide an API to fetch the attribute values from the workflow using workflow id, i am able to retrieve the Attribute name via api/v2/workflows/status/processes/{workflowid} but not able to retrieve the values

  • Hi!

    How to get workflow data/information ?

  • appuq
    Options

    As a typical reply to questions like this, I usually answer this

    1. OT created SmartUI so they can use REST API as the way to offer functionality so if the SMARTUI shows WF Attribute data you can look at the payload using developer tools/fiddler and craft your calls. We all do this as REST API has almost no examples other than a few(including stuff I put out)
    2. For all Content Server activities(the one they renamed from Livelink) the toolkit called Web Reports(WR) has almost everything/anything conceivable with that. So if you know your workid/subworkid then getting WF Attribute data is like a 2 min job. Add on top of it that any WR can be made to work as a REST API endpoint you have a considerable anvil with which you can please your boss/as well as tide over any crisis:).Well, this is not the REST API OT put out but a different way if one needed a solution.
    3. As always an Oscript developer can get this or add any new REST api's.

  • Hello @appuq, I'm new, could you share an example with me?
    
  • appuq
    edited March 19 #14
    Options

    What have you done now as a starting work can the forum users see it? Are you saying you are a developer who doesn't know how to use Browser Tools or Fiddler?. Can you do F12 when the smartui page of CS opens up and try to identify requests/responses….I sometimes find Fiddler to be easier.

    BTW in my blog, I have worked out a fairly decent workflow example with screencaps etc.It was done a few years back so if the API has changed I wouldn't know

    https://appukili.wordpress.com/2022/04/17/take-some-rest/