[ashridharan]

I want to create a new case using REST API. According to documentation here:
http://wiki.processmaker.com/REST_API_C ... T_.2Fcases
the process id/project id (pro_uid) and task id (tas_uid) are mandatory fields. I can get the pro_uid by using the API to get list of projects (/api/1.0/{workspace}/project). Where can get the tas_uid from? Please help!

[ashridharan]

Does anyone have any answers for this please?

[amosbatto]

You can create a case manually in ProcessMaker. Then use the REST endpoint GET /api/1.0/{workspace}/cases to get the task ID, which you can use to create new cases.

[ethanpresberg]

You can also see this example app written in angularjs.. It does everything you are asking about.

http://github.com/ethnp/pmangular

[ashridharan]

Thank you so much, the /api/1.0/{workspace}/project/{pro_uid}/starting-tasks API does it for me. Many thanks for sharing the angularjs code base!
Though there is no mention of this API in the http://wiki.processmaker.com/REST_API_Designer documentation.

[ethanpresberg]

Happy it helped!

We are always updating our documentation with the latest features. Please keep checking as we are continuously improving the documentation.

P.S. the angular app was updated a few days ago to work with the latest version of the api as well as some other improvements.

[gresham]

@ethanpresberg

I've had a look at the git repository, do you have any instructions on how to implement and where to change/add the Oauth2 codes ? Also do you perhaps have some screenshots of what the UI looks like. I'm new to PM and would like to experiment with UI a bit more.

[ethanpresberg]

@gresham

The only places you should need to make changes to should be the configuration yml file in the root directory.

[amosbatto]

I added documentation for this endpoint:
http://wiki.processmaker.com/3.0/REST_A ... ting_tasks

By the way, the easiest way to get the task ID is simply run a case with the Debugger turned on and look at the @@TASK system variable ( or look at the case summary), but you always do it the hard way with REST.