Utilize a single entry point to ENOVIA with a Dynamic Web Service

mA solution to a recent customer engagement was a dynamic web service. The web service accepts a JSON object that contains the name of a processing JPO, a method, and the data package. This allows a single entry point with potential for multiple processing JPOs, and offers minimal to no maintenance of the web service itself.

Whenever new functionality is needed, just write a new processing JPO, and call it.

Attached is the Dynamic Web Service source and an example processing JPO.

What use cases can you come up with for this solution?

l_thumb