My app must have the ability to create new things (Actions in this app) and update them in response to various user actions on any of several pages. When a new Action is created, it must be linked in a many-to-one relationship with a Project thing.
Obviously, it would be best to have the create and update functions defined once and used wherever needed to ensure that referential integrity and consistency of field values can be maintained.
It appears that I can create API workflows for this. Is this a wise thing to do? If not, what is the best method for encapsulating database actions? I certainly don’t want multiple instances of essentially the same code strewn throughout the app.
Somehow, I thought I’d be able to access the Action created in the API Workflow, but I don’t see that it is available.
It is defined as a return value.